Graphite review

Graphite is an AI code review platform that combines pull request review, stacked changes, and merging in one workflow. Its AI Reviews check pull requests for critical bugs and suggest fixes. Graphite Chat gives code-change context, helps address CI failures, and can apply suggested fixes from the PR page.

For larger pieces of work, stacked PRs split changes into smaller, sequenced pull requests. A merge queue lands pull requests in order and helps keep branches green. The PR inbox brings a team’s pull requests into one review workflow, while CI optimizations run stacking-integrated CI only when needed. In short, Graphite covers several steps between opening a PR and merging it; it is not just an AI comment bot. The published plan details include a CLI, VSCode extension, and MCP on Hobby, and all GitHub Organization repos on Starter.

Graphite’s clearest strength is coverage of the review-and-merge process. AI Reviews can flag critical bugs and suggest fixes, while Graphite Chat adds code context and can help with CI failures from the PR page. Stacked PRs make a large change easier to review in smaller, sequenced pieces; the merge queue then handles landing changes in order. The inbox and stacking-integrated CI round out that workflow.

The paid plans also separate team needs in a fairly legible way. According to the pricing details, Starter is $20 per user per month with annual billing and adds all GitHub Organization repos, Slack notifications, and team insights. Team is $40 per user per month with annual billing, adding unlimited Chat and AI Reviews, review customizations, automations, and the merge queue. That makes the queue and automations a clear reason to consider Team rather than assuming every paid tier includes them. Annual billing is listed as 20% off, though monthly prices are not published.

The biggest buying gap is price transparency. The pricing details list annual rates for Starter and Team, but do not publish monthly prices for paid plans. Enterprise pricing is also not published, so organizations needing advanced merge-queue settings, custom analytics and ACLs, SAML, audit logs, GHES support, or private uploads cannot estimate the cost from the listed plans.

Hobby is free, but its AI Reviews and Graphite Chat are limited, and the plan is for personal project repos. The plan details give no numerical usage caps for those limits, so teams cannot tell from the listed information how much review or chat they get before upgrading. Starter includes neither unlimited AI use nor the Team plan’s automations and merge queue. Those features sit behind the $40-per-user annual Team price. Graphite has broad workflow coverage, but the free tier’s practical ceiling and the monthly bill remain unclear.

Graphite has a free Hobby plan, but its AI Reviews and Graphite Chat are limited. The pricing page lists Hobby for personal projects, with personal-account repos, CLI, VSCode extension and MCP.

Paid prices are published only for annual billing: Starter is $20 per user per month and Team is $40 per user per month. That is a $20-per-seat monthly jump from Starter to Team. Starter adds access to all GitHub Organization repos, Slack notifications and team insights; Team adds unlimited AI Reviews and Chat, AI Review customizations, automations and Merge Queue.

Graphite says annual billing is 20% off, but it does not publish monthly prices for paid plans. Don’t treat the annual rates as monthly-billing quotes. Enterprise pricing is also not published; its listed features include advanced Merge Queue settings, custom analytics and ACLs, SAML, audit log (SIEM), GHES support and private uploads. No add-ons are listed. Budgeting therefore means asking sales for monthly and Enterprise terms before committing.

Graphite brings AI review, stacked pull requests, a PR inbox and a merge queue into one workflow. Teams considering a switch should first check how that workflow fits their current pull-request process, CI setup and GitHub organization. The published product and pricing information does not specify migration steps, data-export options or what happens to historical review data, so confirm those points with Graphite before moving.

The published sources also contain no Reddit posts or comments, so we can’t responsibly say what users report as reasons for leaving. We also can’t verify a specific lock-in risk from this material. Before adopting Graphite, ask whether you can export relevant data and how to unwind stacked changes and queue settings if you leave. For teams switching away, map those workflows and confirm what transfers to the replacement; don’t assume portability. If monthly costs or Enterprise terms matter, get them in writing first: Graphite does not publish either.