Free for one. Free for ten. Never a cut of what we route.
The money in this market is in seats with walls and in tokens; the exchange takes a share of the flow; the tools around the work charge ten to forty dollars a seat. sleds prices like a tool around the work, because a dispatcher that earns more when work runs on the expensive rail is not neutral, and neutrality is the product. Billed to the workspace, never to an engineer's card.
FreeYou, your agent, your list. Forever.
- The meter: bars, credits, the reset, in the status line
- Estimates before you run, actuals when you merge
- The exits at the wall, on your own seat
- Hand-offs to a buddy in another workspace
- A receipt on everything you ship
- Intake for everyone around you, also free
Free to tenA workspace with a tracker, a Slack and a policy at the wall.
- Everything in One, for everyone with a seat
- Sizes, worth and receipts written back to Jira, Linear and GitHub
- Worth and cost on every row; the roll-up
- Hand-offs across the team; the platform key within allowances
- Overnight on the batch tier; the connector for the business side
Per seatTens to hundreds of seats on several agents and platforms.
- Everything in Team; the eleventh seat starts the meter
- SSO, SCIM, MFA and an admin portal through WorkOS
- Self-hosted: the record, the proxy and the connector in your cloud, on your keys, in your region
- Sensitivity as a dispatch constraint; restricted work stays home
- Audit export and a written data-handling statement
The per-seat number past ten is not on this page yet. It gets set after the first team records exist to justify it, and it will sit in the band a tracker costs. What it will never be: a percentage of what we route, or a margin on the rail.
The record is the only thing we have. Run it where your data has to live.
Teams self-host a tracker for three reasons: data sovereignty, a regulated industry, and a per-seat bill that grew. All three point at the record, and the record is the whole of what sleds holds. Everything else is already yours and already reviewed: the head is the Claude or ChatGPT your security team approved; the harness runs on the engineer's laptop, installed by them as them. A sleds container in your VPC is the one new thing to approve.
That is a shorter conversation than a self-hosted tracker with a UI your IT team now owns. There is no sleds UI to host. Headless and self-hosted is a stronger combination than either alone.
| component | self-hosted as | notes |
|---|---|---|
| The record | Your database, your backups, your retention | Every row, brief, size, worth, actual and receipt. Nothing leaves. |
| The proxy | On your platform keys, in your region | Bedrock and Vertex when the keys live in your cloud account. |
| The connector | mcp.<you>/mcp behind your SSO | The same verbs, answered inside your network. |
| The sizing model | A service call by default; a snapshot in the container for air-gapped work | Your actuals never leave to calibrate it. |
| Ships as | One docker compose up · Helm for Kubernetes | Signed images; a written data-handling statement. |
| Mirrors | Linear, Jira, GitHub · Plane, YouTrack, GitLab | Self-hosted trackers where you already run one. The sled is the record; each is a view. |
| Open on the laptop | CLI, hooks, status line, proxy client | Open source. Easier to believe when you can read it. |
| Not open | The record service and the sizing model | Source-available terms if a self-hosting customer needs them for review. |
Everyone gives the small team the product. The money starts at the tenth seat or the first token.
| tool | free | paid | where the agents sit | what it tells us |
|---|---|---|---|---|
| Linear | Unlimited members · 250 issues · 2 teams | Basic $10 · Business $16 · Enterprise custom | Agent workflows on every tier | Free by issue count, not by seat. The paid line is the tracker band: $10–16. |
| Jira | Up to 10 users | Standard ≈ $7.91 · Premium ≈ $14.54 · Enterprise custom | "Every paid plan includes AI agents"; assign a work item to Claude, Cursor, Copilot or its own | Free to ten is the norm. Agents are a paid-tier feature, priced nowhere by the task. |
| GitHub | Free repos and 2,000 CI minutes | Team $4 · Enterprise $21; Copilot Pro $10 · Pro+ $39 · Business $19 · Enterprise $39 | Copilot coding agent; code review also spends Actions minutes | Since June 2026 Copilot bills by token at API rates. The seat is a credit balance with a wall. |
| Factory | — | Pro $20 · Plus $100 · Max $200; Teams $60 + $40 per seat to 10 | Its own droids, model choice inside the harness, cost by ticket and PR for its own work | The $20 / $100 / $200 ladder with usage inside. Teams capped at ten, then a sales motion. |
| sleds | One engineer, forever. A team to ten seats. | Per seat past ten, in the tracker band. Enterprise per seat with SSO and self-host. | Every agent, model and person you already run, priced before and signed after | Never a percentage of what we route and never a margin on the rail. The seat is the unit; the work is what we price. |
About a third of the compute bill, and the hours nobody was counting.
| mechanism | the decision | illustrative | what proves it |
|---|---|---|---|
| Overnight at half price | Work whose worth keeps until morning runs on the batch tier. | $1,000 / mo | Batch rows against the same work at daytime rates. |
| The right model per step | Sonnet is a fifth of Fable; Haiku a tenth. "Sonnet fits" is the estimator's call, before the run. | $600 / mo | Estimate versus actual by model per task type. |
| Headroom, not credits | The over-runner's next task goes to a seat with headroom or to tonight, not to extra usage. | $900 / mo | Credits reconciled month over month. |
| Hours not lost at the wall | The policy decides the exit; nobody spends 45 minutes finding a way around. | 26 h / mo | Wall events with the exit taken and when. |
| The review queue | Plan in minutes, merge in hours. The pile-up made visible per area. | not claimed | The number the CTO asks for and nobody has. Measured first. |
| Knowing how long anything takes | A priced backlog with actuals is planning capacity restored. | not a savings line | The reason the platform lead buys. |
Start with one engineer.
One line on one laptop is useful the same day and costs the workspace nothing. When the team wants the sled, the roll-up and the policy, write to us and we set the early-access terms together.
Which agents and seat platforms the team runs today.
Which tracker, and whether tickets carry a size or a priority.
Whether a platform key exists and who holds it.
A name for the policy at the wall: hold by default, or continue within an allowance.