AI Commander pricing
Giving an AI real access to your own computers — running commands, launching jobs that outlive the conversation, seeing the desktop — is the free tier here, for up to 10 machines. Pro is $49/month, and it is for two things: running a fleet, and moving artifacts (checkpoints, models, renders, log bundles) on and off those machines.
- Up to 10 usable saved machines
- Remote commands (
remote_exec) over MCP and REST - Detached background jobs that survive the conversation ending
- Desktop screenshots (macOS and Windows desktops, owner opt-in)
- NVIDIA GPU discovery and per-job GPU reservation
- The anonymous first hour after a code is created — no signup at all
- No new file transfers (upload,
remote_pull,remote_push)
- Everything in Free, on every one of your machines
- No machine limit you'll hit in practice — technical ceiling: 100 machines*
remote_pull: bring one file back from a machineremote_push: deliver a file to a machine- Caller uploads via
POST /api/v1/files, up to 100 MiB per file - Billed monthly through Stripe; cancel yourself at any time
What each plan includes
Every row below is an entitlement the relay actually enforces, not a marketing line. Free and Pro differ on exactly two axes: how many saved machines are usable, and whether a new file transfer may start. Nothing else about a machine changes with the plan.
| Entitlement | Free | Pro — $49/month |
|---|---|---|
| Usable saved machines | 10 | Up to 100 (technical ceiling*) |
| Saved machine records | Kept and visible, marked planRestricted | Every record usable to the ceiling |
Remote commands (remote_exec) | Yes | Yes |
| Detached jobs (start, list, status, logs, cancel) | Yes | Yes |
Desktop screenshots (remote_screenshot) | Yes — macOS/Windows desktops, owner opt-in | Yes |
| GPU discovery & per-job GPU reservation | Yes | Yes |
| Anonymous access in a code's first hour | Yes | Yes |
| MCP endpoint, REST API, Agent Skill | Yes | Yes |
Start a new file transfer (remote_pull, remote_push, upload) | No | Yes |
| Collect a blob that already exists | Yes, until its TTL | Yes |
| Command time cap | 1 hour hard kill | 1 hour hard kill |
| Command output cap | 1 MiB, then truncated | 1 MiB, then truncated |
| Billing period | — | Monthly (no annual option) |
* 100 machines is a technical ceiling, not a policy limit. Need more? Get in touch — we'll sort it out.
remote_exec are properties of the protocol, not of a plan. Paying more does not raise them; anything
longer or chattier belongs in a detached job, which is free.
What happens when you hit a limit
Free's 10-machine entitlement is not a deletion policy and not a hidden failure. It is computed at read time and behaves the same way through every transport — MCP, REST, and the dashboard.
- Nothing is deleted. Records above the free limit stay visible in your machine list,
marked
planRestricted:true. That flag is computed at read time and never persisted. - The 10 oldest are the usable ones, ordered by creation time and then by id as a tie-break. The ordering is stable, so which machines work does not change between two calls.
- Deleting one promotes the next. Remove a restricted-out machine you no longer need and the next record in that order becomes usable immediately.
- Restricted records carry no telemetry. They report
online:false,lastSeenAt:null, and omit platform and GPU details. Do not read that as proof the machine itself is offline. - Operations fail with a reason, not a mystery. Any attempt to use a restricted machine
is refused with
reason:"plan_device_limit"and the message: "Device not available due to account plan limit. Remove newer devices until your account has at most 10 devices, or upgrade to Pro." - Blocked and plan-restricted are independent. A machine you (or its operator) blocked still occupies a plan slot: operator approval and account-plan access are separate dimensions.
# A machine restricted by the free entitlement, as any transport reports it
{
"alias": "render-node-12",
"blocked": false,
"planRestricted": true,
"online": false,
"lastSeenAt": null
}
# …and what using it returns
{
"ok": false,
"reason": "plan_device_limit",
"error": "Device not available due to account plan limit. …"
}The file-transfer gate refuses the same way, and it deliberately tells two different callers two different things. A signed-in Free account is pointed at the upgrade; an anonymous session-code caller has no plan to upgrade at all and is pointed at signing in first. In both cases commands, detached jobs, and screenshots on that machine are unaffected.
Billing FAQ
How much does AI Commander cost?
The Free tier costs nothing and covers up to 10 usable saved machines, with remote commands, detached background jobs, desktop screenshots and GPU discovery. Pro costs $49 per month, billed monthly through Stripe, and adds file transfer plus every saved machine up to the technical ceiling of 100*. There is no annual plan and no per-seat team tier.
How do I upgrade to Pro?
Sign in to the dashboard and start the upgrade there. The dashboard calls
POST /api/billing/checkout, which creates a Stripe Checkout Session for the Pro
subscription and returns its URL; the payment itself happens on Stripe's hosted page. Promotion codes are
enabled on that session, so a discount code can be entered at checkout. Once Stripe reports the subscription
active, the relay writes pro onto your account and the Pro entitlements apply immediately —
every saved machine up to the ceiling becomes usable and file transfer opens. If you already have a
subscription that is not cancelled or expired, that same action sends you to the customer portal instead of
creating a second one.
How do I cancel or manage my subscription?
In the Stripe customer portal. The dashboard calls POST /api/billing/portal,
which creates a portal session for your Stripe Customer and returns its URL; cancelling, changing the
payment method, and downloading invoices all happen there. AI Commander stores only a Stripe Customer
identifier and your local plan — it never sees your full card number. Cancelling keeps Pro for the period
you have already paid for; when that period ends, your account returns to the Free entitlements, meaning the
10 oldest saved machines stay usable and new transfers stop.
What happens to files I already transferred if I downgrade?
Blobs that already exist stay collectable until their TTL. The plan gate refuses to
start a transfer; it does not revoke anything already created. A relay blob made while you had Pro
remains readable for its ordinary lifetime — access to the blob ends 24 hours after creation, and a
download link lasts 1 hour — and an existing link is not invalidated by the downgrade. This is a
deliberate decision: a broken download link is a support ticket, and someone who pulled a file yesterday is
not the person a paywall is for. What stops is starting a new upload, remote_pull, or
remote_push.
Can an anonymous session-code caller transfer files?
No — they must sign in first. An anonymous caller has no plan at all, so there is nothing to upgrade and the refusal points at signing in rather than at a checkout page. Anonymous session-code access can still use commands, detached jobs, and screenshots. Transferring files needs an account identity, and that account needs Pro.
What counts as a machine?
One saved machine record on your account — one computer or server running the agent, which auto-links to your account the first time you connect to it. The count is of saved records, not of machines currently online: an offline machine still holds its slot, and so does a blocked one, because operator approval and account-plan access are independent. Deleting a record frees its slot right away.
Is there a machine limit on Pro?
Yes, and we will not dress it up as boundless. Pro removes the 10-machine Free entitlement and enables every saved record up to a technical ceiling of 100* machines — an abuse and safety limit, not an upsell step. It is not a number a Pro fleet realistically reaches, but it is a real number and it is in the code. It is also not a policy boundary: if you need more than that, get in touch and we'll sort it out.
Is there an annual plan, or a team tier?
No. One paid plan exists — Pro, $49 per month, billed monthly through Stripe. There is no annual discount, no per-seat pricing, and no enterprise tier.
Do I have to pay to let an AI reach my own computer?
Not here. Remote command execution, detached jobs that keep running after the chat ends, desktop screenshots, GPU discovery, and the anonymous first hour are all free for up to 10 machines. Pro exists for fleets and for artifacts.
Start on Free. Upgrade when the fleet or the files demand it.
Install the agent, connect your AI client, and run the first command in a couple of minutes.
Pricing published 2026-08-26 · Pro: $49/month USD, billed monthly · Free machine limit: 10 · Pro machine ceiling: 100* · Current agent version at publication: 1.0.56