Personal Free
New Personal spaces include 50 actual sandbox hours once and 10 simultaneous member sandboxes across the whole Personal space. You also get 100 Sensei free prompts once, counted from their release. There is no recurring refill of either.
Earlier Personal spaces keep their current terms.
Tasks, previews, Deploys, sandbox-backed Crons and member-attributed warm-up sandboxes share the same balance and slots.
One sandbox running for one hour consumes one hour at every size. Five sandboxes running for one hour consume five hours. USD rates do not multiply or discount this allowance.
At launch, each Personal space the hours cover receives a fresh allowance. Historical usage is not deducted. Existing spaces above ten running member sandboxes can let those sandboxes finish, but cannot start, resume or replace compute until fewer than ten remain. That launch exception does not override exhaustion.
At zero hours, all covered compute stops, including active tasks, previews, Deploys and Crons. Starts, wakes, retries and replacements are refused. Work does not receive a finish-first exemption. Stored files, logs, saved artifacts and recoverable work remain available. No Free Personal usage is charged after zero.
The Personal capacity display shows remaining hours, the shared sandbox count and exhaustion status. A full sandbox limit blocks additional starts; an already-running sandbox needs no extra slot.
New workspaces and capacity
The sidebar workspace +, account menu, workspace selector, Settings picker and project creation's New workspace action show the same demo content:
Book a Demo to unlock more capacity
Book a Demo for additional parallel capacity, depleted hours or a new workspace. Closing the dialog or opening the calendar grants nothing and changes no billing state.
Ordinary Free work remains available while hours and a slot remain. Existing workspace access, memberships and invitation acceptance continue to work.
New self-serve subscriptions, upgrades and capacity increases are gated on the server as well as the client. This restriction is independent of whether Stripe is enabled.
Plans
These are legacy workspace billing terms, retained for existing subscribers and historical records. They are not new self-serve purchase offers, and do not define Personal Free.
| Plan | Price | Included usage | Sandboxes at once | Support |
|---|---|---|---|---|
| Trial | Free | $10 once, or $30 with a promo code | 3 | |
| Starter | $20 a month, or $216 a year | $25 every month | 5 | Best-effort, by email |
| Pro | $190 a month, or $2,040 a year | $250 every month | 10 | Dedicated Slack channel, next business day |
| Enterprise | Contracted | Contracted | No limit | Contracted |
The annual prices work out to $18 a month for Starter and $170 a month for Pro. Included usage renews every month on both intervals.
What usage costs
These USD sandbox rates apply to existing workspace billing. They remain separate from Personal's actual-hour allowance and from platform cost reporting.
| Sandbox tier | CPU and memory | Price per hour |
|---|---|---|
| Small | 2 vCPU, 4 GB | $0.51 |
| Medium | 4 vCPU, 8 GB | $0.98 |
| Large | 8 vCPU, 16 GB | $1.95 |
| XLarge | 16 vCPU, 32 GB | $3.49 |
Each project's Sandbox Tier is set in Project settings. Existing paid and promotional balances, free-credit claim records, contracts and Stripe records are preserved. They are not converted to hours or reset.
Trial and free credits
The historical workspace rule remains recorded separately: A new workspace starts on Trial with $10 of free credits. Free credits were granted once per person, not per workspace.
A previously eligible promotional code is also a historical record. It grants $30 instead of $10. Those grants are not the Personal Free allowance and are not removed by it.
New workspace creation now requires the demo flow. Automatic Personal-space creation does not consume or replace those historical claims.
Existing subscriber maintenance
Open Settings > your workspace > Billing. Existing customers retain payment recovery, invoices, cancellation and necessary account maintenance through Manage billing. The portal must use the configured maintenance-only flow; it must not permit a new capacity purchase.
A failed payment can still be recovered. Canceling an existing subscription retains the normal lifecycle and records. The Personal policy does not cancel subscriptions, change contracts, erase balances or add charges.
Existing overage can be disabled or reduced. Enabling spending or increasing a cap requires a demo. No recurring Personal refill or paid Personal plan is offered by this change.
When existing workspace usage runs out
Legacy workspace billing remains separate from Personal's stop-at-zero rule. Existing workspace credit restrictions and subscription recovery continue to apply. Personal's allowance does not alter an existing contracted workspace's billing policy.
Payment failures direct existing subscribers to billing maintenance. Capacity increases direct members to the shared demo. External AI-provider subscription setup and provider top-up links remain unchanged.
Sandboxes at once
Legacy workspace limits count chat-session sandboxes. That is 3 on Trial, 5 on Starter and 10 on Pro, with no limit on Enterprise. Personal Free instead defaults to ten member sandboxes in total across covered kinds and projects. Explicit staff overrides remain auditable; they do not bypass the Personal hour balance.
See your usage
Personal shows actual hours remaining and the shared sandbox limit. Existing workspace Usage continues to show USD billing and sandbox hours separately. Cost reporting and historical usage remain available; the new grant does not rewrite old records.
In the Usage chart, a sandbox's time shows once the sandbox stops, on the day it stopped in your own timezone, the same days Token usage shows. Included usage and billing keep counting in UTC.
Who can change billing
Existing workspace owners and admins retain authorized billing maintenance. They cannot bypass new-purchase gates through direct requests, old clients or workspace membership roles.
Next steps
- Members and roles for existing workspace access.
- Project settings to pick a Sandbox Tier.
- AI providers for the accounts that run your models.