Pricing
Pay for the runs you make
Start with 5,000 free credits. Then $0.002 per credit, with spending limits and auto refill. Add the whole team at no extra cost.
- 5,000 free credits
- Usage pricing
- Every teammate included
Plans
Start free. Pay as you use it.
Choose usage billing for day-to-day work, or talk to us about volume pricing and contract terms.
Free
Put your first workflow on a real task.
5,000 credits to start.
- Chat and workflows on any trigger
- A sandbox for every run
- All integrations with full API access
- Databases and MCP servers
- Full run transcripts
- Community support
Growth
Most teamsFor teams with workflows running every day.
Usage billing with every teammate included.
- Everything in Free
- Credits billed as runs happen
- Monthly spending limit you set
- Auto refill so long runs keep going
- Roles, groups, and service accounts
- Share with an expiry date
Enterprise
For rolling workflows out across the company.
Custom credit volume and terms.
- Everything in Growth
- SAML and OIDC SSO through WarpBuild auth
- SCIM provisioning
- Data processing agreement
- Private networking to your systems
- Invoice billing
Compare
What each plan includes
Every plan runs the same product. The rows below show where credits, access controls, and paperwork differ.
| Feature | Free | Growth | Enterprise |
|---|---|---|---|
| Credits | |||
| Credits included | 5,000 to start | 5,000 to start | Custom volume |
| Price per credit | Free credits only | $0.002 | Custom |
| Monthly spending limit | Not included in Free | Included in Growth | Included in Enterprise |
| Auto refill | Not included in Free | Included in Growth | Included in Enterprise |
| Runs | |||
| A sandbox for every run | Included in Free | Included in Growth | Included in Enterprise |
| All integrations with full API access | Included in Free | Included in Growth | Included in Enterprise |
| Databases and MCP servers | Included in Free | Included in Growth | Included in Enterprise |
| Full run transcripts | Included in Free | Included in Growth | Included in Enterprise |
| Library with proposed changes you approve | Included in Free | Included in Growth | Included in Enterprise |
| CLI and terminal app | Included in Free | Included in Growth | Included in Enterprise |
| Access | |||
| Roles and groups | Not included in Free | Included in Growth | Included in Enterprise |
| Service accounts | Not included in Free | Included in Growth | Included in Enterprise |
| Sharing with an expiry date | Not included in Free | Included in Growth | Included in Enterprise |
| SAML and OIDC SSO through WarpBuild auth | Not included in Free | Not included in Growth | Included in Enterprise |
| SCIM provisioning | Not included in Free | Not included in Growth | Included in Enterprise |
| Private networking to your systems | Not included in Free | Not included in Growth | Included in Enterprise |
| Billing and support | |||
| Data processing agreement | Not included in Free | Not included in Growth | Included in Enterprise |
| Invoice billing | Not included in Free | Not included in Growth | Included in Enterprise |
| Support channel | Community | Priority | |
Calculator
Estimate a month of runs
Pick how often workflows run, how long each run takes, and how heavy the model work is. The estimate updates as you move the sliders.
Credits per run
150
5 min × 30 credits/min
Credits per month
45,000
300 runs
Estimated monthly cost
$90.00
at $0.002 per credit
First month after free credits
$80.00
40,000 paid credits
How far the free credits go
33 runs covered
About 3 days at this pace.
Assumptions
- This is an estimate. The credits a run uses depend on the model you pick and how long the sandbox stays open.
- The model tiers are assumptions. Edit the credits per minute to match what your runs report.
- Model usage is billed at 2x the provider cost. Sandbox time is billed at 1.5x cost. Every run reports the credits it used, so you see the real number after the first run.
Credits
What uses credits
A credit is $0.002. Two things draw credits during a run. Everything else is free.
| Item | Uses credits | How it is metered |
|---|---|---|
| Model tokens | Yes | Every token the model reads and writes during a run. Billed at 2x the provider cost. |
| Sandbox minutes | Yes | The time a run keeps its sandbox open. Billed at 1.5x cost for the vCPU and memory used. |
| Triggers | No | Schedules, webhooks, and integration events cost nothing to set up or fire. The run they start is what uses credits. |
| Seats | No | Invite everyone. People who watch, approve, or start runs are not charged. |
| Integrations and MCP servers | No | Connect as many as you need. API calls the agent makes are covered by the run's tokens and sandbox time. |
Spending limits
Cap the month before it starts
Usage pricing only works if the bill cannot surprise you. Limits are built into the product.
A limit per product
Helios and WarpBuild CI each get their own monthly spending limit. Set the Helios limit to the number you are comfortable with. Change it any time.
Triggers stop at the limit
When credits run out, scheduled, webhook, and event triggers stop starting runs. Nothing runs on credit you did not approve.
Auto refill for long runs
Turn on auto refill and Helios buys more credits when the balance drops below a threshold. The default threshold is $25 and the smallest refill is $10.
One balance with WarpBuild
Prepaid credits are shared between Helios and WarpBuild CI. Buy once and spend on either product under its own limit.
The bill follows the work
The meter in Helios is the run itself. An engineer who sets up ten workflows and an operator who checks them once a week both join for free. Each run reports the credits it used, and the spending limit keeps the month inside the number you chose.
FAQ
Billing questions
Start with a single run
5,000 credits are enough to connect a tool, run a chat, and put the same prompt on a schedule.