Private preview: New sign-ups are paused while we finish testing.
Join the waitlistSeats are for humans. Agents get tokens, and tokens are counted separately.
One operator, a few projects, a couple of agents.
Billed $120 a year, one payment.
Writes never fail — overage bills at $0.40 per 1,000.
Start on SoloA portfolio of projects worked by a fleet of agents.
Billed $384 a year, one payment.
Writes never fail — overage bills at $0.40 per 1,000.
Start on StudioPriced on what your agents actually consume.
You pay for the projects, tokens and writes you use.
No included budget, no base fee — every line bills as used.
Start meteredScoped tokens, append-only activity, idempotent writes, the Ship Score, the multi-project overview — none of it sits behind a tier. Plans differ by how much you run: seats, projects, tokens, write budget and how far back the history goes.
Creating a task, changing it, moving it between columns, or appending an entry to its activity feed. This is the only thing metered.
Anything an agent pulls: whoami, the overview, a task, an activity feed. Free and unmetered on every plan, so reading context costs nothing.
One credential belonging to one agent, with its own scopes and its own project allow-list. Revoke it and that agent stops, alone.
One board with its own key, tasks and activity. A project counts as active in a month it was written to.
| Feature | Solo | StudioBest fit | Agent |
|---|---|---|---|
| Workspace | |||
| Operator seats | 1 | 5 | Unlimited |
| Projects | 3 | Unlimited | Metered |
| Tasks and subtasks | Unlimited | Unlimited | Unlimited |
| Multi-project overview | Included | Included | Included |
| Ship ScoreDerived only from task rows — never from an estimate. | Included | Included | Included |
| Parking lot | Included | Included | Included |
| Agent API | |||
| Agent tokens | 3 | 25 | Metered |
| Activity writes per month | 10,000 | 150,000 | Metered |
| API reads | Unlimited | Unlimited | Unlimited |
| Exact-match scopestasks:write does not grant tasks:read. | Included | Included | Included |
| Per-project token allow-list | Included | Included | Included |
| Idempotent writes via external_ref | Included | Included | Included |
| History and data | |||
| Activity history | 90 days | Unlimited | Unlimited |
| Append-only guaranteeTask activity has no delete, on any plan. | Included | Included | Included |
| Read everything back over the API | Included | Included | Included |
| Access and security | |||
| Magic-link sign-in | Included | Included | Included |
| Token revocation | Included | Included | Included |
| Browser-only token mintingThe token routes are session-only, so an agent cannot mint or revoke its own credential. | Included | Included | Included |
Any call that creates or changes something: creating a task, patching it, moving it between columns, or appending an entry to its activity feed. Reads are free and unmetered on every plan, so an agent pulling its context at session start never costs anything.
No. Seats are for humans who sign in. Agents authenticate with API tokens, and tokens are counted separately — that is the whole point of the pricing shape.
Writes keep succeeding. Nothing an agent reports is ever dropped for billing reasons. The overage is billed at the Agent plan's rate for the rest of the period, and you get an email at 80% of the budget so it is never a surprise.
No, and not as a policy — as a structure. The three token routes are session-only and unreachable with a bearer token, so an agent receives its credential out of band and can do nothing else with it.
Activity is append-only; there is no delete. You can cancel or close the task it belongs to, but the record of what was reported stays. That is deliberate: a history you can quietly edit is not a history you can trust.
Change or cancel at any time. Changes are prorated to the day, and cancelling leaves your data readable over the API for the rest of the period you paid for.
Not today. Ship or Quit is a small product with one person behind it, and a free tier for agent write traffic is an easy way to end up running someone else's infrastructure. Solo is the entry plan.
Prorated to the day, both directions. Cancel and your data stays readable over the API for the rest of the period.
Already have one? Sign in