Pay per seat. Every seat is the same.

Start free, solo, on your own machine. Add seats as your team grows — each one adds a runner, more parallel tasks, a bigger crew, and monthly credits. The per-seat price drops as the total grows.

Your runner or ours — the AI is always yours: six engines today, Claude, Codex, Kimi Code, Grok, Cursor, and OpenCode, on keys and sign-ins you already have, never marked up. Credits pay for two things only: tasks on Uai Cloud runners and inference through the Uai engine.

Every account is a workspace. Free is solo; a subscription owns seats, and every seat is billed at the rate your total lands in — Dev, Pro and Max are the names of those rates, not different products.

Free

$0
No credit card
Solo — 1 seat, just you
No monthly credits

Kick the tires solo, on your own machine.

Start free
  • 1 runner · 3 concurrent tasks
  • 2 agents per task · 3 repositories
  • Your own runner and AI keys

Dev

1–2 seats
$19.99 / seat / mo
1 seat from $19.99 / mo
$199.90 / seat / yr
1 seat from $199.90 / yr
Two months free
$20.00 in credits per seat, every month

For a developer running real parallel work every day.

Get Dev
  • 1 runner · 10 concurrent tasks per seat
  • 5 agents per seat · 8 per task
  • Unlimited repositories, teams and members

Max

8+ seats
$15.99 / seat / mo
8 seats from $127.92 / mo
$159.90 / seat / yr
8 seats from $1,279.20 / yr
Two months free
$20.00 in credits per seat, every month

The best rate, from eight seats up — no ceiling.

Get Max
  • 1 runner · 10 concurrent tasks per seat
  • 5 agents per seat · 8 per task
  • Unlimited repositories, teams and members

Every seat is billed at the rate your total lands in, and adding a seat never lowers your bill. Add seats any time, prorated; reduce at your renewal.

What a seat includes
Capability Free Paid (any tier)
Runners 1 1 per seat
Concurrent tasks 3 10 per seat
Agents 2 5 per seat
Agents per task 2 8
Repositories 3 Unlimited
Teams 1 Unlimited
Members 1 One per seat
MCP connections — ✓
Shared files — ✓
Team members & task collaborators — ✓
API access — ✓
Public previews — ✓
Generated task digest — ✓
Monthly credits — ✓

Tiers change the price, never the capacity: a Dev seat and a Max seat buy the same runner, tasks and agents. Limits are enforced server-side.

Credits

Seats buy the team. Credits buy the cloud.

Your own runners and your own AI keys are never billed. When you run on a Uai Cloud runner, or through the Uai engine instead of your own key, that usage is metered from credits — the monthly ones every seat brings, and any you add.

Uai Cloud runner

$0.35 per hour while a task runs, $0.01 per hour while it is parked for resume. A whole machine per task, destroyed when the task ends.

Uai engine

Hosted models metered per million tokens, at the rates listed in the app. Bring your own key instead and inference never touches your credits.

Monthly credits, and top-ups

Every seat brings credits each month, which expire at the end of that month. Add any amount on top — those never expire — and subscribed workspaces get bonus credits on every top-up.

Roles & permissions

Seats buy the capacity. Roles decide who spends it.

Included with every seat, not sold as a tier. Build additive roles, set usage caps, and decide which agents and runners each role unlocks. A member holds as many roles as you like and their access is the union — the model you already know from Discord, pointed at a dev team.

Caps before the fact

Usage caps are spend control before a task runs — not only the admin close switch after one is already burning. A role holds a member below your workspace's limits and never above them. Roles distribute the capacity you already bought; they don't sell more of it.

Start tasks (uses compute)

Launch a task's container. This is the action that spends money. Safe capabilities are granted by default; destructive capabilities require an explicit grant — including the ones that spend.

One catalog, humans and agents

The same permission ids gate what a member does and what an agent's CLI does, so the rule for a person and the rule for a persona can't drift apart as the workspace grows.

Nothing narrows by default: new workspaces start with Workspace Admin and Member, and Member grants what a member could always do. Spend-shaped powers stay off until you hand them out. How roles work →

Enterprise

A bigger team, or a bigger conversation? Let's talk.

There is no seat ceiling — buy as many as you need. For a negotiated per-seat rate, annual invoicing, a local currency, security review, or priority support, shaped to how your team actually works, get in touch.

  • Negotiated per-seat rate
  • Annual invoicing & procurement
  • Priority support & onboarding
Contact us

Self-hosting is always free.

Your own machine is unbilled compute — a deployment mode, not a plan. Bring your runner and your AI keys; the cloud stays secret-blind and never sees either.

Set up a runner

Common questions

How does per-seat pricing work?

You buy seats. Every seat costs the same and buys the same capacity — one more runner, 10 more concurrent tasks, 5 more agents — and the per-seat price drops as the total grows: 1–2 seats at $19.99, 3–7 seats at $17.99, 8+ seats at $15.99 per seat per month. Every seat is billed at the rate its total lands in, so ten seats are ten at the Max rate. Dev, Pro and Max are the names of those rates.

What's the difference between Dev, Pro, and Max?

Only the price per seat, and the monthly credits each seat brings. All three grant the exact same capabilities per seat and the same full feature set. They are the names of the rates your seat count lands in — Dev for 1–2 seats, Pro for 3–7, Max for 8 and up — so you don't pick one: you pick a number of seats, and every seat is billed at that rate.

What do credits pay for?

Two things: tasks running on Uai Cloud runners ($0.35 per running hour, $0.01 per hour while a task is parked for resume) and AI inference through the Uai engine, metered per million tokens at the rates listed in the app. Every seat brings monthly credits — $20.00 on Dev, $20.00 on Pro, $20.00 on Max per seat — which expire at the end of each billing month; credits you buy never expire, and subscribed workspaces get bonus credits on every top-up.

Do you mark up tokens or charge for inference?

Not on your own keys. Your agents run on your own AI keys and you pay the model provider directly — we never mark up those tokens. Seats buy orchestration capacity (parallel tasks, agents, runners) and collaboration. If you choose to run through the Uai engine or on a Uai Cloud runner instead, that usage is metered from credits at the rates listed in the app — every seat brings monthly credits, and you can add more.

Can I add or remove seats whenever I want?

Yes. Adding seats takes effect immediately, prorated for the rest of the period. Reducing seats takes effect at your next renewal — the seats stay usable until then, and seats already paid for are not refunded. You can't drop below the members and open invitations you have.

Monthly or yearly?

Either. Yearly is 17% cheaper — the equivalent of two months free — and your credits still land every month. Switching to yearly applies right away; switching back to monthly applies at your renewal.

Can I control what each person can do?

Yes, with every seat — and on Free. A workspace defines roles: a role carries permissions, caps, and the personas and runners it unlocks, and a member can hold several — their access is the union. The same catalog governs your agents, so the rule for a human and the rule for an agent's CLI can't drift apart. Role caps only clamp down against your plan, never up: a role distributes the capacity you already bought. New workspaces start with two roles, Workspace Admin and Member, and Member grants exactly what a member could always do — nothing narrows until you narrow it.

Can I limit spend before a task runs?

Yes. Build additive roles, set usage caps, and decide which agents and runners each role unlocks — spend control before the fact. The permission that launches a container is Start tasks (uses compute): Launch a task's container. This is the action that spends money.

Who can stop a task that's burning capacity?

Its owner, and any admin of the workspace it belongs to. A task is one person's authorship but the workspace's spend, and it pins one of the workspace's runner slots — so if it was started by someone now on holiday, an admin can close it. Everything else at that level still acts under the owner's own credentials, never on their behalf.

Can I share work with my team?

Yes. Every account is a workspace. Free is solo (one member); a subscription owns seats and every seat holds a member — there is no cap on how many — so invite people into the workspace and collaborators into a task's chat, and @mention agents and people in the same channel. Each task carries its creator's own credentials, so commits and PRs attribute to the actual person.

Do I need a GPU?

No. Uai orchestrates AI agents that call hosted models — currently Claude, Codex, Kimi Code, Grok, Cursor, and OpenCode; the runner advertises which engines and models it can run — with your keys. No local inference, no GPU requirement.

Do you store my code?

Depends on which runner you pick. Self-hosted — your machine, or your own AWS account — the worktree lives on your runner; app.runuai.com never holds a copy. Uai Cloud: the worktree lives on an ephemeral machine in Uai's own AWS, destroyed when the task ends — same isolation, different custody.

Is self-host free?

Yes. Self-hosting is a deployment mode, not a plan — your own machine is unbilled compute. You pay for seats; Uai Cloud runners and the Uai engine are paid from credits.

Start free, on your machine.

No credit card, ever — your first seat is yours the moment you sign up.