Pricing
Two parts: a fixed monthly fee per team of awks (agentic workers) — AI developers and testers that build and test your work items — and AI usage drawn from prepaid credits and metered per work item, so you can see what each one cost. A plan is your software factory's capacity: how many awk teams you run, and how many work items can be active at once.
Per-team pricing.
Scale as you grow.
Every plan includes always-on awk teams with GitHub App and Jira integration, frontier and near-frontier LLMs (AI usage billed in credits at $0.01 each), and per-tenant isolation. Plans scale by active work items and team count.
Credits are consumed as your awks do work. A typical small work item consumes 1,000–1,500 credits; a typical large one (such as a codebase refactor) runs 5,000–10,000 credits, depending on complexity. You'll see real-time consumption on your dashboard, and your console's analytics break it down by session and by ticket, at $0.01 per credit.
Price one of my work items →Credit pricing reflects underlying AI provider costs and operational overhead. Rates may be adjusted as we evolve the service. Annual contract customers are protected from mid-term rate changes.
Become a founding customer
Get an additional 30% off your agreed subscription price during your first paid year, plus direct founder access and priority roadmap input. Limited to 15 founding customers, subject to availability and approval.
Apply for founding membership →Submit your application in the console to reserve a place for seven days. Become a paid subscriber before your deadline to retain it. Excludes AI credits and usage charges. Discounts apply to future eligible subscription invoices only; already-paid invoices are not refunded. Eligibility ends at your original first-paid anniversary, even if you change tiers.
What's an active work item?
An active work item is one piece of work your developer and tester awks have queued or in progress: typically a ticket, a pull request to review, or a task. An awk team runs several at once. Your developer awk can build one while the tester awk tests another and a third moves through fixes, each with its own context. A work item waiting on your answer is still active; a paused one is not.
- One ticket being worked from pickup to pull request
- One pull request being reviewed by the tester awk
- A complete dev → QA → dev revision → QA pass cycle (counted as one, not multiple)
- One bug investigation or code analysis task
- Clarifying comments and questions within an existing work item
- Individual code edits within a work item
- Awk-to-awk coordination messages on the same work item
- Status updates and notifications
When does parallelism matter?
For small teams with one or two work items active at a time, the tier limits rarely come into play. Parallelism matters when your backlog has multiple independent items ready to go, during sprint-start burndowns, in bug triage moments where many small fixes need parallel work, or when you want awks to keep executing outside your team's working hours.
How to pick your tier?
If you consistently hit your active work item limit, you're extracting enough value from AwkTeams that the next tier is genuinely worth it. If you never approach the limit, you're on the right tier. When unsure, start with Starter — you can upgrade as your backlog tells you it's time.
One initiative, 20 work items, on Starter.
A real initiative is a mix of small and large work items, so its usage falls somewhere between the two rows below. The plan fee is the same either way.
- Plan
- $499 / monthStarter: 1 awk team, up to 5 work items active at once. The rest of the initiative waits in the backlog until a slot frees.
- Usage, if all twenty are small
- $200–$30020,000–30,000 credits: twenty work items in the typical small range (1,000–1,500 credits each).
- Usage, if all twenty are large
- $1,000–$2,000100,000–200,000 credits: twenty work items in the typical large range (5,000–10,000 credits each, such as a codebase refactor).
Illustrative: the ranges are the typical figures above times 20, at $0.01 per credit, and any one work item can fall outside them. The one measured work item on this site, DS-6, metered 2,660 credits, about $27; it is one work item, not an average. The plan fee is monthly, for as many months as the initiative takes. Your people's time is not in these figures.
Why a price on every work item
Your AI bill shows who spent it. Not what each work item cost.
Your AI bill, by person
IllustrativeEach figure equalsPer-seat fee≈ $100 · flatplusAI API tokensvaries by person
- A. Rivera$1,940
- J. Okafor$1,220
- M. Chen$410
- S. Patel$145
- Month total$3,715
- Spent on which work items?Unknown
Who used it. Nothing about what it delivered, or what else it paid for.
With AwkTeams, by work item
1 real · 7 illustrative- Item 1 · Checkout retry logic$34
- Item 2 · Invoice PDF export$21
- Item 3 · Search index rebuild$265
- Item 4 · Login rate-limit$18
- A real Jira ticket · Backend API · JavaBuilt · tested, 1 bug found · fixed · 24 / 24 passed · preview link · ready for your approval2,660 credits$27Real run · Jira ticket DS-6
- Item 6 · Audit log filter$48
- Item 7 · Permissions model overhaul$320
- Item 8 · Small fix$14
- Spent on which work items?Every dollar
What each work item cost, and what came back for it. Only the $27 row is a real figure: see that ticket, step by step → Two different things, not a price comparison: a team's AI bill on the left, a ledger of work items on the right. The ledger prices the work item, not the person who assigned it.
A price on every work item.
Your AI bill is metered to the person, not the work, so it can’t tell you what a feature cost. Here every work item is metered on its own: you see what each one cost in your console’s analytics, by session and by ticket.
Tests and code review built in.
On every work item that changes code, the developer awk runs the project’s own tests, checks the work against its acceptance criteria, and puts it through a code review. Then it pauses: you approve what matters, like merging a pull request. Want a second pair of eyes? Independent AI QA by a separate tester awk is there on request.