Graphite
AI-assisted code review platform with stacked PRs, merge queue, and collaborative chat for faster shipping.
≈ 89.6kvisits/mo
Established · estimate, read 2026-09-21
- For
- Engineering teams reviewing code and shipping pull requests faster with AI assistance
- Price
- Free plan · From $20/user/mopricing page, read 2026-09-21
- Activity
- Actively maintainednothing dated on the site
- Company
- founding year not on record
- review code changes and catch bugs before merging
- resolve CI failures and apply suggested fixes
- manage stacked pull requests without waiting for feedback
- #30
Devin
Executes software engineering tasks including code migrations, bug fixes, testing, and documentation generation across multiple repositories.
30.6kActiveFrom $20/mo - #152
Tessl
Manages and optimizes agentic workflows with skill registry, evaluation, and governance for development teams.
6.1kActiveFrom $100/mo2024 - #172
Zencoder
Orchestrates AI agents to plan, code, test and review across repositories and tools.
7.2kMaintainedFrom $45/user/mo - #238
Factory
Deploys autonomous agents to plan, build, review and ship software changes across codebases.
1.6kActiveFrom $20/mo - #264
QA Wolf Autopilot
Generates test cases from app exploration and runs web and mobile tests in parallel.
71.8knot readFree plan - #346
Checksum
Generates, runs, and automatically repairs Playwright tests across your application as code changes.
95ActiveFree plan
What is Graphite?
AI-assisted code review platform with stacked PRs, merge queue, and collaborative chat for faster shipping.
Who is Graphite for?
Engineering teams reviewing code and shipping pull requests faster with AI assistance
How much does Graphite cost?
Graphite has a free plan; paid plans start at $20/user/mo, per its pricing page on 2026-09-21.
Do people use Graphite?
Established: ≈ 89.6k visits a month · estimate, 2026-09.
Is Graphite still maintained?
Actively maintained.
What are alternatives to Graphite?
In Developer tools, by use: Devin, Tessl, Zencoder, Factory, QA Wolf Autopilot, Checksum.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one row at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.