Cursor Origin Pricing: What We Know So Far (2026)

Nothing extra, for now. Origin's early beta, which began rolling out on August 17, 2026, is included with paid Cursor plans, and the docs say it is not available on free plans. That is the whole published position: no Origin tiers, no per-seat number, no usage meter, no statement about what happens when the beta label comes off. Anyone quoting a standalone Origin price today is guessing.

Here is the full state of play, and it is short.

No, and the distinction is worth being blunt about because search engines currently blur it. Search "cursor origin pricing" and nearly every result is the pricing page for the Cursor editor, the Hobby, Individual and Teams plans that cover Tab and Agent inside the IDE. Those numbers are real, and they have nothing to do with Origin. Origin is a separate product, a git hosting platform, and no Cursor plan mentions it.

The editor plans, for the record: a free Hobby tier, Pro at $20 a month on the individual side, Teams Standard seats at $40 monthly or $32 on annual billing, and custom Enterprise pricing, as listed on cursor.com/pricing in July 2026. If those are what you were looking for, Cursor pricing explained breaks them down properly. The one thing the beta changed is that those plans now gate Origin: Pro and up get it, Hobby does not. What Origin will cost on its own, if it ever does, nobody can tell you yet, including Cursor's own pricing page.

The mix-up costs more than a wrong number. A hosting bill and an editor seat are different budget lines with different owners, and quoting one at the other's price is how a platform team ends up defending a figure Cursor never published. On a five-person team the same person owns both lines and the error dies quietly. At a few hundred engineers those lines sit with different people, and a wrong number gets copied into three planning docs before anybody checks it. If a spreadsheet already has an Origin row on it, leave the cost cell empty.

This section is inference, clearly labelled as such. The team building Origin came from Graphite, and Graphite still sells a code review product with published per-seat pricing today. That, plus the shape of Cursor's own plans, is the closest thing to a pricing signal that exists, which is not saying much.

Graphite's live pricing is the most relevant precedent, because it prices the review layer Origin inherits.

The lines Graphite draws are more informative than its numbers. Free to Starter is a boundary about organizations: the free tier covers personal-account repos, and organization repos start at Starter. Starter to Team doubles the seat price, and what the second twenty dollars buys is review volume, unlimited AI reviews plus the merge queue. That second boundary is the one to watch for Origin, since it shows the same team already deciding that the meter belongs on review.

Read across Graphite and the Cursor editor and a pattern shows up: a free entry tier, per-seat paid plans in the tens of dollars a month, and custom enterprise on top. If Origin prices like its siblings, that is the shape to expect. To be precise: this is inference from the same company's other products, not anything Cursor has said about Origin.

Origin will launch into a market with well-established price anchors, so today's forge pricing is the frame buyers will judge it against. All three majors give the entry tier away.

The spread is wide for a reason. GitHub anchors low at $4 and sells the ecosystem; GitLab's $29 Premium bundles compliance, security and project management for teams who buy a platform, not a repo host. Origin's pitch, review throughput for agent-written code, reads closer to the GitLab end of that argument than the GitHub end. Where it lands on the price spread will say a lot about who Cursor thinks the buyer is: individual developers, or the platform teams already paying for GitLab Premium.

One caution about the table: those are advertised rates, and the billing terms underneath them differ. GitLab's $29 is an annual-billing number, as are Graphite's paid rows further up, which is the kind of detail that makes two prices look closer or further apart than they are. When Origin's number lands, pull last month's invoice and compare against that.

Size changes the stakes, and I had that backwards at first. The instinct is that a cheap seat matters most to the small team counting dollars. Across five seats, though, the gap between the cheapest and the dearest plan above is a rounding error against one engineer's afternoon, so these anchors do their real work at five hundred seats, where they set the opening position in a negotiation.

When Origin grows a pricing line of its own, at general availability or before, the headline number will get the attention, but these details will decide your actual bill.

• Seat versus usage. Whether agent activity (automated review, merge-queue runs, conflict resolution) bills like a seat or like a meter. BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition.'s usage-based billing is the precedent to watch.
• Bundling. Whether Origin stays folded into Pro, Teams and Enterprise the way the beta is, or prices as a standalone product with its own contract.
• The free tier's shape. Private-repo limits, collaborator caps and agent-workload caps. Is Origin free? covers the outlook in depth.
• Migration incentives. Launch discounts on top of the GitHub sync the beta already ships, a standard move for a challenger forge.
• Enterprise gating. Which controls (SSOSingle Sign-On. One company login (usually via SAML or OIDC) instead of a separate password per tool. Press Enter for the full definition., audit logs, access policies) sit behind the custom tier. Both Cursor and Graphite currently gate those at enterprise.

Of the five, bundling is probably the one to read first, because it decides how much of the rest you have to negotiate at all. The beta's answer is bundled, and if that holds, the seat conversation has already happened and the only new line is whatever meters agent work. If it prices standalone at GA, procurement runs a fresh vendor review, and those run on their own calendar.

If the eventual bill surprises anyone, the mechanism to check first is the one Cursor already runs on the editor: every plan includes a set amount of model usage, and going past it means switching on on-demand spend, charged at the same API rates. A meter with an included allowance produces a bill nobody can derive from the seat count. The allowance and the on-demand rate are worth reading before the headline price, and the enterprise checklist frames the same question for procurement.

Until then the summary does not move. Origin has no price of its own, only a plan gate, and the anchors above are the only frame anyone has for judging one when it lands.