Devin enterprise pricing: what an ACU contract looks like

What the enterprise meter actually is

Cognition’s enterprise billing documentation is unusually direct about this: Devin Enterprise customers are billed in Agent Compute Units at the rate set in their order form. There is no public enterprise rate card to look up, and any article quoting one is either describing the retired self-serve ACU plan or guessing.

An ACU is a normalized unit of agent work rather than a unit of time or a count of requests. It absorbs the virtual machine time, the model inference, and the network activity a session consumes, which is why one ACU covers roughly a quarter hour of active autonomous work rather than a fixed number of tokens. A tightly scoped change with a clean test suite consumes fewer than an exploratory investigation that reads half the repository before it edits three lines.

The self-serve ladder is your anchor

Never negotiate an enterprise agreement without the public ladder in front of you. It is the only external reference either side has, and it is more favorable to a buyer than most vendors’ self-serve tiers.

The Teams structure is worth understanding properly because it changes what "we need Enterprise" actually means. A full seat is $40 a month and carries a Pro-equivalent daily and weekly allowance plus Desktop access. A flex seat is free, unlimited in number, and draws entirely from the team’s shared pool of on-demand credits. The $80 monthly minimum can be satisfied by any combination of full seats and credits. On Teams, credits are shared across all members with no per-member balance, and they roll over month to month rather than expiring.

The full self-serve breakdown, including quota shape and overage behavior, is in the Devin pricing guide.

What Enterprise adds over Teams

The enterprise tier is a governance and deployment purchase, and the list is short enough to evaluate honestly against your actual requirements.

• Identity is the most common trigger. SSO and SCIM sit only on Enterprise, so an organization with a hard provisioning requirement has exactly one option. This is worth knowing early, because it means identity alone can force the tier regardless of usage volume.
• Deployment is the strongest single differentiator. The dedicated option runs Devin inside your own cloud environment so source never crosses the boundary. Very few agent vendors offer this, and where it is a requirement it decides the entire evaluation.
• Multi-organization admin matters at scale. If you have several business units with separate budgets, a single admin plane over multiple organizations is the difference between one contract and several.

The org controls, which are genuinely good

This part deserves credit rather than skepticism. Devin’s enterprise consumption controls are more concrete than most of the category, and they behave the way a finance team expects rather than the way a growth team would prefer.

The cost of that design is the other side of the same coin: a cap reached at four in the afternoon before a release is an outage in your delivery process, not a warning. Set the cap with headroom, decide in advance who can raise it and how quickly, and make sure that person is reachable. A hard stop is only better than soft overage if the escalation path is fast.

What to put in the order form

An enterprise agreement priced in a unit with no public rate is only as good as the questions you asked. These are the ones that change the number.

1. The ACU rate, in writing, with the volume it assumes. A rate quoted against a commitment you will not hit is not the rate you will pay.
2. How the rate compares to a self-serve credit. Cognition documents them as the same dollar value, so ask directly. If the contracted rate is worse than the public one, you want that on the record before signing.
3. What happens to unused ACUs at the term boundary. Self-serve credits roll over and do not expire. Confirm whether your contracted volume does the same, because a use-it-or-lose-it annual commitment changes the effective price materially.
4. Overage rate above the committed volume. Ask whether it matches the committed rate or reverts to something higher. This is where enterprise agreements most often diverge from the headline.
5. Whether the dedicated deployment changes the rate. Running inside your cloud shifts compute cost onto you. Establish whether that is reflected in the ACU price or charged as an uplift.
6. Seat treatment alongside the ACU commitment. Confirm whether full and flex seats persist as a concept at Enterprise or are folded into the contracted volume.
7. Who can raise an org cap and how fast. A hard stop is an operational dependency. Get the escalation path and the response time named.
8. Data retention, model routing, and which models are in scope. Devin runs several vendors’ models plus Cognition’s own. Establish which are permitted, because model choice moves consumption more than usage volume does.

How a different org model compares

Continuum is not an autonomous engineer and does not compete with Devin on the agent itself. It is worth putting beside it because the two draw the organizational boundary differently, and if you are evaluating an agent contract you are implicitly choosing a boundary.

To model the seat side before either conversation, the AI team cost calculator and the spend cap simulator take a headcount and a usage distribution and return the totals. For the Devin comparison in full see the Devin comparison page, and for teams whose pilot did not land as expected, the migration guide starts by diagnosing why.

Questions people ask

Keep reading

Continue through AI spend and governance with AI spend management: the four controls that actually hold.