Graphify pricing
Free
$0
for one developer · no card required
- 3 repositories
- 25,000 graph nodes per repo
- 10 push builds per repo/day
- 15 PR reviews per workspace/month
- 1 formal verification run/day
- 1 verification run at a time
Pro
$10 / month
billed yearly · one developer
- Unlimited repositories
- Uncapped graph size
- 100 push builds per repo/day
- 400 PR reviews/day
- 400 formal verification runs/day
- 2 verification runs at a time
- Deep reading of your docs
- Early access: Jira, Confluence, Sentry AI SRE, Google Drive and Vercel connectors
- Two weeks free · card required · renews unless you cancel
Teams
$20 per seat/month
billed yearly · min 2 · for the first 100 teams, then $28
- Unlimited shared repositories
- Uncapped graph size
- 100 push builds per repo/day
- 700 PR reviews/day
- 800 formal verification runs/day
- 2 verification runs at a time
- Shared graphs, one central bill
- Team Digest
- Agent Radar
- Dedicated Slack support channel
- Everything in Pro, including the early-access connectors
- Two weeks free · card required · renews unless you cancel
Enterprise
Custom
self-hosted
- Unlimited repositories
- Self-host on your infrastructure
- Security and compliance
- SSO/SAML
- GitHub Enterprise support
- Dedicated Slack support channel
- Custom invoicing and payment terms
- Custom DPA and terms of service
- Automated legacy migration
What you pay for.
The open-source CLI is free and builds the same kind of graph on your machine. The hosted plans keep it current for you and review every pull request, starting with Pro for one developer.
- Kept current on every push
- Hosted Graphify re-indexes your default branch on each push. The CLI rebuilds on a git hook, graphify update or watch, on each machine separately.
- Shared with the team
- One graph and one workspace memory for every teammate and assistant. With the CLI, each clone builds and keeps its own graph.
- Used in pull request reviews
- Hosted Graphify reviews pull requests against the indexed graph and the diff, and can run formal verification on changed functions. The CLI has no automatic reviews.
- Search hooks
- The CLI installs Claude Code hooks that add graph context before each grep. The hosted MCP server has no hook; an instruction block in your rules file does that job.
- Compare in full
- Graphify vs Graphify CLI, side by side, in the docs.
Questions about plans
What people ask before picking one.
3 repositories, 25,000 graph nodes per repo, and 10 push builds per repo/day. Each workspace gets 15 PR reviews/month and 1 formal verification run/day. No card required.
Both include unlimited repositories, uncapped graph size, and 100 push builds per repo/day. Pro gets 400 PR reviews and 400 verification runs/day; Teams gets 700 and 800, respectively. Teams adds shared graphs, central billing, Team Digest, Agent Radar, and dedicated Slack support, with a minimum of 2 seats. Both include early access to the Jira, Confluence, Sentry AI SRE, Google Drive and Vercel connectors, which are rolling out to paid workspaces.
Quarterly plans show the full amount billed every 3 months, with the monthly equivalent underneath. Pro is $36/quarter ($12/month), saving $36 a year or 20% compared with monthly billing. Teams is $72/developer/quarter ($24/developer/month) for the first 100 teams, saving about 17%; after that, it is $96/developer/quarter ($32/developer/month), saving 20%. Teams requires at least 2 developers.
Annual plans show the monthly equivalent and are billed once per year. Pro is $10/month ($120/year), compared with $15 billed monthly. Teams is $20/seat/month ($240/seat/year) for the first 100 teams, then $28/seat/month ($336/seat/year). Monthly Teams pricing is $29/seat/month for the first 100 teams, then $40/seat/month. Teams requires at least 2 seats.
Free allows 2 PR reviews and 1 verification run at a time. Pro allows 10 reviews and 2 verification runs; Teams allows 20 and 2. All hosted plans allow 1 index build per repo and 10 across a workspace at a time.
Every plan allows 2,000 memory ingests per day, 10,000 stored memory turns per repo, and 1 memory consolidation at a time per workspace. Request limits are 30/minute for Ask, 120/minute for queries, and 240/minute for MCP.
Two weeks on both Pro and Teams; a card is required to start the trial. The Free plan stays free with no card, within the allowances listed above.
Enterprise adds automated legacy migration, the option to self-host, security and compliance, SSO/SAML, GitHub Enterprise support, and a dedicated Slack support channel. Formal verification and graph-aware PR review are in every plan. It also includes custom invoicing, payment terms, a DPA and terms of service. Licensing is per developer seat; deployment and pricing are scoped with your account team.
Graphify is free for qualified non-commercial projects with MIT or Apache licenses. Apply at graphify.com/oss with your repository details.
Pre-Seed and Seed startups with under $1M in revenue over the past 12 months get 50% off Graphify Teams plan for up to 6 months. Apply at graphify.com/startups.
Yes, and it always will be. The CLI is Apache 2.0, needs no account, and runs on your machine. It is the right pick if you are happy to keep your own graph fresh and do not need pull request reviews. Free, Pro and Teams are for the hosted product, which keeps the graph current for you and reviews every pull request; Enterprise is self-hosted.
A review on every pull request and a graph that stays current without you maintaining it. The CLI builds the same kind of graph and is great on your own machine, but you keep it fresh with a git hook, graphify update or watch, and it never reviews your pull requests. On Pro, Graphify re-indexes your default branch on every push, reviews each pull request against the graph and the diff (400 reviews a day), runs formal verification on changed functions (400 runs a day), and keeps workspace memory your assistants can query over the hosted MCP server. Unlimited repositories, no cap on graph size, $10/month billed yearly, two weeks free to try. On Teams, everyone shares that one graph instead of each clone keeping its own. Full comparison: docs.graphify.com/platform/graphify-vs-local.
No. The open-source CLI installs Claude Code hooks that add graph context right before each grep. The hosted MCP server has no hook; an instruction block in your assistant's rules file tells it to query the graph first. Setup: docs.graphify.com/cookbooks/make-agents-use-the-graph.