—ACUs used this month
—overage ACUs billed
—effective cost per active hour
Core vs Team at this usage
—
Cost by active hours per day
Everything else held at the values above, swept across hours of active Devin work per day, comparing Core and Team plan totals. The highlighted row is closest to your current input.
| Hours/day | ACUs/month | Core total | Team total | Cheaper plan |
|---|
Your usage priced against Core vs Team
Same hours/day and active days as above, priced against each Devin plan's real billing terms, next to your current custom settings.
| Plan | Included ACUs | Overage ACUs | Total cost |
|---|
How this connects to other tools
This calculator prices one specific mechanic: Devin's ACU-based compute-time billing, how many ACUs your actual autonomous work hours consume, and what that costs on Core versus Team. That's a different question from the AI coding agent: subscription vs API calculator, which compares a flat subscription against raw metered API cost without modeling any plan-specific unit economics. For agents billed on a dollar-denominated credit pool tied to token cost instead of wall-clock compute time, see the Cursor credit-pool overage calculator; for agents billed on discrete per-request allowances, see the GitHub Copilot premium request calculator. If you want the raw token math underneath any LLM-backed agent, the context window cost calculator breaks that down separately.
How this calculator works
The Devin AI ACU Cost Calculator starts from active work time: hours of active Devin work per day multiplied by ACUs per hour (default 4, i.e. 15 minutes per ACU) gives ACUs per day — at the defaults (2 hours/day, 4 ACU/hour) that's 8 ACUs/day. Multiplying by active days per month gives ACUs used this month (8 × 20 = 160 ACUs). On the Core plan ($20/mo base, no included ACUs, $2.25/ACU) the bill is $20 + 160 × $2.25 = $20 + $360 = $380.00/month, an effective $9.00 per active hour before the flat fee. On the Team plan ($500/mo, 250 ACUs included, $2.00/ACU overage), 160 ACUs sits entirely inside the included allowance, so the bill stays flat at $500.00/month with zero overage — more expensive than Core at this usage level.
The Core vs Team box solves for which plan is cheaper at your exact inputs. Because Team's $500 fee already "pre-pays" for 250 ACUs, light usage wastes most of that allowance and Core wins; the crossover sits around 213 ACUs/month (roughly 53 hours of active work, e.g. ~2.7 hours/day over 20 active days) — solve 20 + 2.25a = 500 for a. Push hours/day up to 4 instead: ACUs/month rises to 320, Core costs $20 + 320 × $2.25 = $740.00, while Team costs $500 + (320 − 250) × $2.00 = $500 + $140 = $640.00 — now Team is the cheaper plan by $100/month. That crossover is the core tradeoff this calculator makes visible: below roughly 53 hours of active Devin work per month Core wins, above it Team's bundled ACUs and lower overage rate pull ahead.
Frequently asked questions
What is an ACU (Agent Compute Unit) and how is it billed?
An ACU (Agent Compute Unit) is Cognition's normalized measure of the compute Devin consumes while actively working on a task — virtual machine time, model inference and networking bandwidth bundled into one unit. Cognition states one ACU represents roughly 15 minutes of Devin's active autonomous work, so four ACUs is roughly an hour, though the exact conversion drifts over time as Devin gets faster or slower per task. On the Core plan you pay $20/month plus $2.25 per ACU consumed, pay-as-you-go with no included allowance. On the Team plan you pay $500/month which includes 250 ACUs, and anything beyond that is billed at $2.00 per ACU. Enterprise pricing is custom with volume ACU rates.
How much does Devin cost per hour of actual work?
At 4 ACUs per hour (the standard 15-minutes-per-ACU conversion), Devin working continuously costs about $9.00 per hour on the Core plan ($2.25 × 4) and about $8.00 per hour on the Team plan's overage rate ($2.00 × 4), before accounting for each plan's flat monthly fee. That per-hour figure only applies to time Devin is actively executing a task — idle time between tasks, waiting on your review, or blocked on external dependencies doesn't burn ACUs, so a full 8-hour workday rarely means 8 hours of billed compute.
Is Devin Core or Team cheaper for my usage?
It depends entirely on how many ACUs you burn per month, and the crossover is lower than most people assume. Core has no included allowance, so every ACU costs $2.25 on top of the flat $20 fee — cost rises linearly from the start. Team's $500 fee already includes 250 ACUs "for free," so light usage wastes most of that allowance, but heavy usage benefits from both the bundled ACUs and the lower $2.00 overage rate. Working the algebra, Core stays cheaper only up to roughly 213 ACUs per month (about 53 hours of active Devin work); past that, Team's flat $500 plus cheaper overage pulls ahead. Solo developers or light automation almost always want Core; teams running Devin on multiple parallel tasks daily typically cross into Team territory fast.
How does Devin's ACU pricing compare to Cursor's credit pool or GitHub Copilot's premium requests?
All three are usage-based coding-agent pricing, but they meter different things. Cursor's credit pool (see our Cursor Credit-Pool Overage Calculator) bills a dollar-denominated pool 1:1 against real per-request token cost — it's essentially metered API spend wrapped in a subscription. GitHub Copilot's premium-request model (see our Copilot Premium Request Cost Calculator) counts discrete requests against a monthly allowance regardless of how long each one runs. Devin's ACU model is closer to metered compute-time billing: it doesn't care how many requests you send or how many tokens they use directly — it cares how long Devin's autonomous agent loop is actively running, which suits Devin's longer-running, less-interactive task style (kick off a task, let it run for 20-40 minutes, review the result) versus the request-by-request interaction pattern Cursor and Copilot are built around.