Graphify is the fastest Open Source @ycombinator company to reach 150,000 @github ⭐️in under 8 months with over 11M downloads of our PyPI package
Really grateful to the devs + community behind it who made this widespread distribution possible <3
My agents don't start from zero each morning.
An Obsidian vault holds how the business works. @graphify maps every codebase, so agents ask a graph before they search. Memory files carry what one agent learned on Tuesday into Wednesday.
zuluassistant.com
the love from the community + devs all around the globe is compounding each day and as a solo founder i couldn’t ask for anything better
we just had out all time max DAU yesterday crossing 11,500 active users/agents) on the platform
last few weeks have been insane for graphify, it’s very rare when you build a product and strangers on the internet instantly understand it + fall in love with it.
we now are serving a DAU of 11,000+ at a D7 of 19% and most of it all came from the feedbacks of our users that we kept on implementing.
ty for such an amazing community and feedbacks are always welcome
until next time!
last few weeks have been insane for graphify, it’s very rare when you build a product and strangers on the internet instantly understand it + fall in love with it.
we now are serving a DAU of 11,000+ at a D7 of 19% and most of it all came from the feedbacks of our users that we kept on implementing.
ty for such an amazing community and feedbacks are always welcome
until next time!
Graphify is now an official Anthropic connector.
No CLI, no config file, no claude mcp add.
Search Graphify in the directory, sign in, and ask anything about your code. Claude answers with the full context of your repos across sessions, so you can ship faster. Works in claude.ai, Desktop, mobile, and Claude Code.
Well, that escalated quickly.
Yesterday, we were getting close to one signup a minute.
Today, Graphify hit 1,996 signups in 24 hours.
6,431 daily active users (+88% WoW), and retention is climbing.
44,000+ users in just 9 weeks.
One sign up on graphify.com every minute of the day, we are nearly there
We are growing more than 50% week over week, doing 5M MCP calls per month (yes agents love graphify) with over 42,000 users in 9 weeks
running a company nowadays feels kinda dystopian
my team is 50+ people in 12 countries, but i talk to my agents more than my human teammates
- voice note to grokbot
- mattpocock/skills /grill-me so the agent interrogates the idea before anything gets built
- spec drops into linear through the linear mcp
- exa + firecrawl agent reads every competitor site, pricing page and changelog
- ideabrowser.com to find ideas and trends
- apify pulls g2, reddit and app store reviews
- prompt: "find the 10 complaints that show up most and quote the users"
- context7 so the agent reads the latest docs before it touches any api
the design
- claude code + paper mcp
- 4 versions of every screen before a single line of code
- pick pieces from 2, it merges them. diverge then converge
- frontend-design skill from anthropic/skills + our own design system skill
- cleanshot screenshots of any ui i like go straight in with "make it feel like this"
the build
- pingdotgg/t3code as the control surface for every agent, from my phone too
- stablyai/orca runs a fleet of agents in parallel, each in its own git worktree
- graphify maps the whole codebase into a knowledge graph so agents navigate instead of guess
- headroom compresses tool outputs before they hit the model, so tokens go 20-95% further
- lsp plugins so the agent sees types and errors like an ide does
- security guidance hook flags risky edits before they land
- supabase mcp for the database, stripe for billing
- github mcp opens the pr, vercel spins up a preview
- loops run overnight, i check what shipped over coffee
the user testing
- lightpanda as the headless browser, way lighter than chromium so you can run hundreds at once
- agents click every flow on the preview like a first-time user
- one persona is impatient, one is confused, one is on a phone
- playwright + chrome devtools mcp for regression tests
the bugs
- sentry mcp catches the error
- agent reads the stack trace and opens a fix pr in under 10 minutes
- human just approves
the data
- posthog mcp cron at 7am on yesterday's funnel
- any step that drops more than 10%, the agent watches 20 session replays and tells me why
- stripe mcp pulls every cancellation reason into one doc every monday
the agents' tools
- orgo so every agent gets its own computer
- agentmail so every agent gets its own inbox
- agentphone so i can call them from the car
- composio connect-apps for every other connector
- akitaonrails/ai-memory, a git-backed markdown wiki so they remember what we decided last week
the skills
- wshobson/agents so skills work across claude code, codex and opencode
- my writing voice
- our design system
- how we write specs
- skill creator so the agents write new skills themselves
some helpful tricks
- one agent per platform. the x agent never touches email
- cheap model for triage, opus for anything that ships
- every output gets scored 1-10 by an llm judge. under 8 goes back
- every agent writes a 5-line log at night so i can read the whole company in 2 minutes
- every agent mistake becomes a new skill, so it only happens once
the team
- humans get version 5, not my voice note which they are happy about lol
- their job is creative feedback, relationships and telling the agents what they got wrong
a human pm reviews the funnel once a week. this reviews it every morning
running a company is now voice notes and inference
week 9 of graphify cloud closed with our highest DAU so far at 3,723 and 26% WoW growth.
people keep finding value in it, from the oss days through the cloud product and now with enterprise customers. the funnel keeps compounding.
the tough part of agentic SDLC in big companies is that agents lose track of context on software in production, especially when one change can affect stuff upstream or downstream that already went through review. graphify keeps the full picture of the codebase, the dependencies, and the history so the agent can actually see what gets impacted
usage keeps climbing because the problem is only going to get bigger