Graphite

• Pricing model: Per-user SaaS subscription with tiered plans: free Hobby tier for personal use, paid Starter and Team seat-based plans, and custom-priced Enterprise. Billing is subscription-based (monthly or annual), with published annual-seat pricing and automatic seat-based adjustments; Enterprise is quote-based.
• Starting price: $20/user/month (billed annually)
• Typical range: $20–$40/user/month (billed annually)
• Billing: Per user / seat subscription. Graphite states workspaces can be on monthly or annual subscriptions; Starter and Team are self-serve card billing via Stripe, with annual pricing published and seat changes prorated onto subsequent invoices. Enterprise is custom sales-led billing.
• Contract terms: 30-day Team plan trial. Seat counts adjust as users join/leave; annual subscriptions are invoiced yearly, with possible additional monthly invoices for added users. Startup program credit is valid for 12 months or until used.
• Free trial: Yes — 30-day Team plan trial. During the trial, you can invite as many contributors as you'd like to the workspace with Team features.

Graphite.dev itself publishes the clearest current pricing: Hobby is free, Starter is $20/user/month billed annually, Team is $40/user/month billed annually, and Enterprise is custom. The company also documents that billing can be monthly or annual, but the public price points surfaced on its pricing page are annual-billing seat prices; no public month-to-month rate was found. A third-party F6S listing shows older/different pricing ($25 Standard, $20 Diamond add-on, $15 Reports add-on), which appears to reflect a prior packaging model rather than the current Graphite.dev pricing, so buyers should treat that as historical/possibly outdated rather than current official pricing.

I found enough evidence to describe a real Graphite engagement as a product onboarding and adoption workflow: teams connect GitHub/org access, install Graphite’s tooling, start creating smaller stacked PRs, optionally enable AI reviews, conduct review/approval work inside Graphite’s PR interface, and merge through Graphite while monitoring review analytics.

1. 1

   Connect GitHub access and select repositories

   The engagement starts by authenticating Graphite with GitHub and choosing the organization or personal account plus repositories to use. Graphite’s onboarding docs show customers joining an organization where the Graphite App is already installed or installing/authenticating the Graphite GitHub App themselves if needed.

2. 2

   Install the Graphite workflow tooling

   After access is connected, the team installs Graphite’s tooling and learns its workflow. Graphite’s getting-started docs position the CLI quick start as the way to create, review, and merge stacked pull requests, with the platform layered on top of existing Git/GitHub workflows rather than replacing them.

3. 3

   Break work into stacked, incremental pull requests

   Developers then use Graphite to split larger tasks into smaller dependent changes and open stacked PRs. Both Graphite’s docs and a third-party comparison article describe Graphite as centered on stacked diffs / stacked pull requests so large changes can be broken into smaller logical updates.

4. 4

   Enable and tune automated AI review

   If the customer uses Graphite Agent, an admin enables AI reviews for selected repositories or the whole organization, after which Graphite automatically analyzes new PRs, comments on issues it finds, and suggests fixes. The setup docs also show optional customization through rules, exclusions, and team coding-guideline settings.

5. 5

   Review changes, discuss fixes, and submit approvals

   Review work happens in Graphite’s PR interface, where reviewers can batch comments into a final review, leave suggested edits, and use Graphite Agent chat on selected lines to explain or improve code. Graphite’s materials also describe this as additive to the team’s existing PR workflow, with human reviewers working alongside AI feedback.

6. 6

   Merge the stack through Graphite

   Once reviews are complete, the team merges from Graphite rather than plain GitHub so Graphite can handle the stack order plus the underlying rebasing and merging. The quick-start documentation explicitly recommends merging stacks from Graphite and describes using the top-of-stack merge action.

7. 7

   Monitor review performance and iterate on setup

   After rollout, teams use Graphite dashboards to monitor review activity and outcomes. Graphite’s AI review setup and docs reference overview dashboards and insights such as issues found, acceptance rates, and PRs reviewed over time, which customers can use to refine rules and workflow usage.