·
typed Team ($25/seat), Team Max ($100/seat) and Team Ultra ($200/seat) pool one quota across the whole org instead of N per-developer silos, and add hosted codebase indexing.
Update, 23 September 2026: the economy tier is now spelled typed (it was typed--), the free tier that runs on your machine is typed-local (it was typed), and with a paid account the CLI defaults to typed.
Today we shipped two new tiers on typed.cloud: typed Team at $25/seat/month and typed Team Max at $100/seat/month. They bring the solo product's two best ideas -- a real monthly usage envelope and optional top-ups when you want more -- to a whole engineering org, and they add a surface we have wanted for a while: hosted codebase indexing.
If you run a team and you have been watching per-developer AI spend creep up, the headline is the billing mechanic, not the price. Let me show you the math.
First, the part that costs nothing and needs no seat. typed's free tier runs on the developer's own machine and needs no account and no key: point the CLI at a model server on the box (llama-server, or an NPU server if you have one) and it adapts to whatever answers -- it reads the window off /props and probes for tool support. typed local sizes a known-good setup if picking a model is not how anyone on the team wants to spend the afternoon. One tier lives there, typed-local, and it never reaches typed.cloud. That is why it is free.
Paid seats buy the two hosted tiers, typed++ and typed. A seat names the tier with --model, for example typed --model typed++, and with no flag gets typed (a seat is a paid plan) -- or typed-local with --model typed-local -- so it can move between the two families per invocation without changing anything else.
This is the part worth reading twice. When you buy Team for N seats, you do not get N isolated quotas that each developer has to live inside. Usage aggregates across every member of the org and is measured against one pool: per-seat envelope x seat count.
Here is why pooled beats siloed. On a real team, usage is never uniform. One developer is deep in a refactor burning through context; another is on call and barely touching the CLI that week. With per-seat silos, the heavy user hits a wall while four light users leave most of their quota on the floor -- you paid for capacity nobody could reach. With a shared pool, the heavy user draws from the same bucket the light users are not touching. You size the org, not each person's worst week.
The pool is a soft ceiling, not a hard stop. When aggregate org usage crosses the monthly envelope, the next request returns a 429 with a one-click top-up -- at the org level, so anyone on the team can extend the shared pool, not just the billing owner. The envelope itself is monthly rather than a rolling window: included volume resets each month, so there are no 5-hour windows to plan around.
Prefer it hands-off? Enable org auto-top-up in $5 / $10 / $20 / $50 increments, with an optional monthly ceiling so a runaway week can't surprise you. Same top-up model as the solo product, scaled to the whole org.
| Tier | Price | Quota envelope | Billing |
|---|---|---|---|
Free (typed-local) | $0 | None -- runs on your machine | No account, no key |
| Starter | $10/mo | Starter | Monthly |
| Pro | $20/mo | Pro | Monthly |
| Max (solo) | $100/mo | Max | Monthly |
| Ultra (solo) | $200/mo | Ultra | Monthly |
| Team | $25/seat/mo | Pro-equivalent per seat, pooled | Monthly |
| Team Max | $100/seat/mo | Max-equivalent per seat, pooled | Monthly |
| Team Ultra | $200/seat/mo | Ultra-equivalent per seat, pooled | Monthly |
Billing is straightforward: per-seat price times seat count, through our payment processor's volume pricing. You pick a seat count at checkout -- a 5-seat Team is 5 x $25 = $125/month. The team tiers are additive, not a replacement. The solo plans below Team buy the same two hosted tiers a seat does, typed++ and typed, and the free local tier stays free for everyone, seat or no seat.
Local context -- the files your client attaches to a request -- still works the way it always has, on every tier and in every Anthropic-API-compatible client (the typed CLI, Cursor, Cline, Roo Code, aider, Claude Code). Nothing about that changes, and you do not need anything new to keep working exactly as you do today. Not to be confused with the free local tier, where the model itself runs on your machine: it never reaches us, so hosted indexing does not apply to it.
What's new is hosted codebase indexing for orgs that want one shared map across seats. Your org uploads a codebase; we run it through our managed embedding pipeline and build a shared, server-side vector index. Any seat then opts a request in -- a CLI flag or an attach header -- and the model retrieves relevant snippets from across the whole repo, not just the files that happen to be open locally.
One person uploads; everybody benefits. A new hire on their first day can attach the org's index and get repo-wide retrieval without indexing anything locally. The explanation of how the auth layer connects to the job queue lives in the index, not in one senior dev's head.
To be clear about what this is and isn't: it is an added convenience for orgs that want a shared index across seats. It is not a missing feature on the solo tiers, and it is not required to use Team. If your workflow is happy with local context, stay with local context.
Uploaded archives and the index built from them are stored in our own storage, encrypted at rest. Chunk text is sent out to be embedded when a codebase is indexed, and the query text is sent the same way on each request. Access is org-scoped. If you cancel, an uploaded codebase keeps a 30-day grace period, then hard-deletes within 14 days after that. If you are evaluating this for privacy-sensitive code, read the privacy policy first.
We hold ourselves to a "be honest" section, so here it is:
typed-local never reaches us, so it cannot debit a quota. A team that keeps routine turns local and spends seats on the hosted tiers sizes a smaller pool than headcount would suggest.For a side-by-side against the subscription CLIs you already use, the honest comparison lives at typed.cloud/migrate -- including where we are not the cheaper option.
Onboarding is five steps, about five minutes:
typed login -- that key is what reaches the paid hosted tiers.None of it is a prerequisite for trying typed. Install it and run the free tier today: no account, no key, and the installer takes the key as an optional argument for when you do have one.
Create an org, invite your team, and size one pool instead of N. That is the whole idea.
Published by Yaw Labs.