Billing
Billing covers compute, the machine time your runs and cloud sessions use, and team seats. Manage both on the Billing page: Settings → Billing for yourself, or the team’s Billing tab.
Plan and compute
| Plan | Price | Included compute |
|---|---|---|
| Personal | Free | $3 every month |
| Team | $39 per seat per month | $15 per seat every month, pooled for the team |
| Enterprise | Custom | Custom |
Personal compute resets on the 1st of each month (UTC). Team compute renews when the monthly invoice is paid. Included compute is used first and does not roll over. Funds already reserved for a running job stay allocated until the job ends.
All prices are in US dollars (USD) and billed monthly.
Additional compute
Add any whole-dollar amount from $10 to $10,000 on the Billing page. Purchased compute stays until used.
Compute is billed per minute at the published rate for the machine you choose. Studio shows the maximum cost before every run. A running job reserves that maximum before it starts, and unused funds return when it ends. Platform failures release their reservation. GPU scientific jobs are compute, including jobs that run neural networks.
Team-owned runs use only the team pool. They never fall back to someone’s personal compute.
When compute runs out, new compute stops. Team features keep working.
Seats
Every accepted member of a team uses a seat, including owners, admins and viewers. Invitations and agent connections do not use seats.
- Activate the Team plan for the team’s existing members.
- Add a seat before another person accepts an invitation. Adding a seat is prorated and billed immediately; the seat and its compute are granted once the invoice is paid.
- Removing a person frees their seat for someone else without granting compute again.
- Reducing the number of seats on the Billing tab takes effect at renewal.
The Team plan unlocks shared editing, execution, private publication and team connections. Personal sharing is available for review.
Cancellation
A team cancels at the end of the paid period. The team then keeps read access and exports, while new shared edits and runs require reactivation. Purchased compute and billing history are kept.