Steepworks pricing
Pay for credits, not seats.
Steepworks credits from $25 a month at $50 per million, with any coding harness. They measure Steepworks usage—human expertise, model usage we run and time on our servers—not a provider's token bill.
Steepworks credits
A monthly baseline. Extra credits when work picks up.
Credits cover Steepworks human expertise, AI work and server time. No tiers, no seats, no sales call at any size.
Choose your monthly baseline
2M credits a month
$100 /month
$50 per million Steepworks credits: human expertise, model usage and server time, metered as one unit. The $25 minimum keeps your account active with 500K credits a month. Baseline credits expire at the end of each billing period; extra credits carry forward.
Request access · $100/monthIncluded at every volume
- Unlimited members and projects
- Any harness: Codex, Goose, Claude Code
- CLI, API, cloud and every integration
- Funded stages, ceilings and run gates
- Build map and usage receipts
- Evidence review and named acceptance
- Spending limits and usage policies
- Community and ticket support
How to choose a baseline
- Not sure? Start at the $25 minimum. Your account, projects and history stay live.
- Size it to the work you expect every month, not your busiest month.
- Cover a launch or a busy stretch with extra credits. If you buy extras most months, raise the baseline at your next renewal.
- Every baseline has the same price per credit: a larger one buys predictability, not a discount.
Busy month? Buy extra credits once.
Extra credits cost the same $50 per million and cover a launch, a larger project or a busy stretch. They never change your baseline: change that yourself when your normal month changes.
| Month | Credits used | Baseline | Extra credits | What happens |
|---|---|---|---|---|
| Normal | 1.8M | 2M · $100 | None | 200K baseline credits expire |
| Launch | 5.4M | 2M · $100 | 3.5M · $175 once | 100K extra credits carry forward |
| Following | 1.6M | 2M · $100 | None | Baseline renews unchanged |
Prices do not include applicable taxes. Access is provisioned on request while self-serve sign-up is closed.
How credits work
One usage unit across the work that gets a result.
Credits measure Steepworks work: human expertise, model usage we run and time on our servers. The same simple price applies whatever the mix.
-
01
Plan
Set the goal, scope and milestones before work starts, with a credit estimate.
-
02
Fund
Stages reserve credits at dispatch and stop at their ceiling. Nothing runs unfunded.
-
03
Build
The people, models and servers Steepworks uses draw from the same credit balance.
-
04
Review
Evidence and acceptance keep every unit of work connected to the result it served.
Model usage, people's time and server time each draw credits at their own rate, and your usage receipts show which kind each draw was. People's time and server time start drawing credits only once their rates are set. Until then, any agreement you have keeps its own terms for that work.
Where it works
Every door included. Integrations never cost extra.
-
Agent CLI
Available -
REST and MCP API
Available -
Cloud workspace
Available -
ChatGPT and Codex
In progress -
Claude and Claude Code
In progress -
Linear
In progress -
Notion
In progress -
Jira
In progress
Available means verified end to end in this deployment. In progress means built and awaiting that verification. Planned means committed direction, not a date.
Have us build it
Managed builds, priced on what you get.
Named Steepworks builders deliver working software, accepted milestone by milestone. You pay for the finished capability, not the usage behind it.
Data Foundation
From $3,500
Your business data, rules, and permissions, connected to the systems you already run. A reliable foundation for your team and the capabilities you build next.
Domain Application
From $7,500
Everything in Data Foundation, plus one production application that runs a defined part of your business, on your domain, with the workflows and tools your team needs.
Domain Platform
From $15,000
Multiple connected applications sharing data, identity, customer engagement, and integrations—with the tools to run the business behind them.
Starting prices. Your proposal prices the full scope and invoices each acceptance milestone, with the plan included for the life of a managed build.
Then operate · monthly
A monthly credit allotment, sized to what we run.
No management tiers. For example, $1,000 a month is 20M credits a month.
- Platform care
- Infrastructure, security, governance and maintenance.
- Application management
- Each application we operate, by scope and service level.
Sized in your proposal; begins at accepted launch. No per-seat fee.
Usage and results
Usage is evidence. A person accepts the result.
Usage
Steepworks counts the credits each project uses for the work it does, with the model, provider and payer recorded. Runs you pay your own provider for are recorded on the map but not charged.
Beyond your baseline, extra credits fund work before it runs, and new work pauses at the funded limit rather than running up a bill. For an agreed project, we invoice the agreed estimate before activating usage or infrastructure, and unused funds carry forward until the project ends. Usage that arrives after the limit, such as a run already under way, is reconciled at the monthly close under your terms. Nothing new starts until renewed funding is in place.
Estimates and limits
Every brief and every funded stage comes with a credit estimate: a range, not a quote.
Spending limits and funded stages stop work at the limit instead of running past it. Extra credits are bought only when you choose to; we always ask first.
Outcome-based pricing
Selected projects can carry a fee for a verifiable business result, agreed before work begins. No qualifying result, no fee.
Frequently asked questions
Credits, plans and the managed build.
What is a Steepworks credit?
The one unit Steepworks uses to meter and bill its own platform: human expertise, model usage we run and time on Steepworks servers, alongside planning, evaluation, gating and the other services the work uses. One price: $50 per million credits.
Is a credit the same as a model token?
No, and they don't convert. A token is a provider's measure of model use; a credit is Steepworks' measure of the work we do. Credits do not track an individual provider's price. Our price reflects the value of a planned, funded, checked build.
Why one price per credit?
One unit keeps pricing predictable when the work needs a different mix of human expertise, models and servers. It replaces seats, subscription tiers and provider rate cards. When model prices move, our credit price does not follow.
Which usage counts?
Steepworks is agent-neutral and never holds your provider keys. Build with your own local or cloud coding agent on your own account and those runs use no Steepworks credits. Teams without a coding agent can have Steepworks builders do it as a managed build. Steepworks' own services always use credits: analysis, planning, Ask, verification, code review, gating and the build map. Every project uses them, and you are never charged twice for the same work.
How do I choose a baseline?
Size it to the work you expect every month, not your busiest one, and start at the minimum if you're not sure. A brief at /start suggests one from the work that keeps going after your first project. Every baseline has the same price per credit, so a larger one buys predictability, not a discount.
How is my monthly price set?
You choose a monthly baseline at one price per million, with a $25 floor. Size it to the work you expect every month; change it for any renewal. No tier to qualify for and no call to book.
What if a month is busier than usual?
Buy extra credits at the same price, once. Your baseline doesn't change, and we always ask before you buy. If the busier pace becomes your normal, change your baseline for the next renewal; we never raise it for you.
What does the $25 minimum buy?
An active account: projects, histories, receipts, build maps, Knowledge and storage stay live, with 500K credits a month. Drop to the minimum after a build ships.
Do credits expire?
Baseline credits cover one billing period and expire at its end. Extra credits carry forward. Credits bought for one project last until it ends. All are funded before they run.
Does usage add charges on its own?
No. Usage draws on credits that are already funded, and new work pauses at the funded limit until you choose to add more. Fixed-price work is never billed again as usage, and missing cost shows as unknown, not zero.
How do outcome fees work?
The qualifying event, evidence, attribution, rate and cap are agreed before work begins. No outcome fee is due unless the result qualifies, and costs inside an outcome rate are not billed again as usage.
What is a managed build?
Steepworks builders deliver a finished, working capability through the same system. It is priced on what that capability does for your business, invoiced per accepted milestone. The credits it uses are tracked on your build map; they don't set the price.
Can we use Steepworks without a managed build?
Yes. The plan is the product. Every goal, spec, funded stage, run and map from a managed build is yours.
Think monthly. Plan for the year.
The plan is billed monthly with no minimum term. Managed builds are invoiced per accepted milestone. Operations is a 12-month service agreement, billed monthly, with no separate annual fee. Annual prepayment of a monthly credit allotment can be agreed; usage and outcome fees still reconcile monthly.