Skip to content
Subako Docs
Esc
navigateopen⌘Jpreview
On this page

Plans and billing

What each plan includes, what Subako Credits pay for, and how an organization subscribes, changes plan, and tops up.

Subako Cloud bills in Subako Credits (SC). One dollar buys 100 SC, so an SC is worth one cent wherever it is spent. An organization holds two things on the commercial side: a plan, which sets what it may create and how many SC it is granted each month, and a credit balance, which its runs draw on.

Both belong to the organization, not to a workspace or a member. Every billing command acts as the signed-in profile’s organization and needs its admin role.

Plans

Plan Price Credits granted Members Workspaces Agents Skills Vaults API keys Model providers
Free $0 500 SC once, at sign-up 1 1 3 5 50 2 2
Pro $19 / month 1,900 SC / month 1 3 20 30 500 10 5
Team $79 / month 7,900 SC / month 5 10 100 150 2,000 50 20
Scale $199 / month 19,900 SC / month 15 30 300 500 10,000 100 50

Each paid plan grants the same face value in SC as it costs in dollars. Sessions are unlimited on every plan.

To the CLI the paid plans are pro, team, and scale; Free is default, and is what billing show reports for an organization that has never subscribed.

What a limit means

A limit caps what the organization holds across all of its workspaces. It is checked when the next one is created, and the creation is refused with a 403 that names the cap. Nothing already created is touched — an organization moved to a smaller plan keeps everything it has and simply cannot add more until it is back under the cap or on a larger plan.

Members count pending invitations as well as people who have joined. Deleting a vault, skill, or model provider frees its slot, as does revoking an API key or letting one expire. The model provider limit counts the providers you register with your own key; Subako’s platform provider is not one of them.

What credits pay for

Two things draw on the balance: calls to Subako’s own platform models, and the engine time a run uses.

Platform models

Subako Cloud’s Subako platform provider offers three models you can publish against without bringing an upstream key. Select it with --model-provider when publishing, and name the model in the version’s config. Sparrow is the lightweight one and Hawk the largest, each with a rate of its own — up to a twentyfold spread from end to end, so which model a version names is the largest lever on what its sessions cost.

Rates are per million tokens:

Model Best for Input Cached input Cache write Output
Sparrow (sparrow) Simple, high-volume agent tasks 30 SC 3 SC 37.5 SC 180 SC
Crow (crow) Everyday tasks, balancing capability and cost 300 SC 30 SC 375 SC 1,800 SC
Hawk (hawk) Complex reasoning and coding 600 SC 60 SC 750 SC 3,000 SC

At 100 SC to the dollar that is $0.30 per million input tokens on Sparrow, and $30 per million output tokens on Hawk. Within a model, cached input is a tenth of the input rate and a cache write one and a quarter times it.

The rates are fixed: a long input does not move to a higher one. Calls made through a model provider you registered with your own key are not charged by Subako at all — you pay your upstream directly.

Engine time

Every run is charged for the time the engine holds it, at 0.01388889 SC per second — $0.50 an hour — whichever provider its model comes from. The time lands on the ledger when the run’s claim ends: when it finishes, parks, is handed back, or its lease lapses. Until then it is unsettled, so a balance can read above zero while a running run is still spending it, and can settle below zero once it ends.

How credits expire

Credit arrives in lots, and each lot carries its own expiry. Spending draws from the lot that expires soonest.

Lot Granted Expires
Sign-up grant 500 SC, once per person, to the first organization they create 60 days after sign-up
Plan grant The plan’s monthly SC, each time Stripe records the subscription invoice paid 60 days after that invoice is paid
Purchase What you bought 180 days after the purchase

Consecutive plan grants overlap by a month, and one left unused is gone two months in; purchased credit lasts six. Expiry is not extended.

Running out

An organization at or below zero is refused every creation and every platform-model call with a 403 until credit lands. Reading a session’s log, listing resources, and everything already created stay reachable. The balance comes back with the next paid subscription invoice, or with a credit purchase.

Subscribing

Everything here is a subako cloud billing command, and each purchase opens a Stripe-hosted page: the CLI prints the URL and opens your browser, and the card never passes through Subako. Stripe confirms the payment to Subako a moment after the page says paid, which is when the plan and its grant show up.

See where the organization stands

subako cloud billing show

This prints the plan, the balance in SC, the subscription’s status and period end, and the card on file. Before a first purchase the last two read (none).

Subscribe to a plan

subako cloud billing subscribe --plan pro

This opens Stripe Checkout for the plan. Once the payment is confirmed the organization is on the plan and its first monthly grant is on the ledger; billing show reports both.

Changing plans

The same command with a different plan changes the subscription in place. Instead of a new checkout, it opens the billing portal’s confirmation page for the change, which shows the proration and the effective date.

subako cloud billing subscribe --plan team

Stripe issues one invoice for the difference. An upgrade grants the SC that invoice’s net covers — the new plan’s share of the remaining month — and a downgrade grants nothing and claws nothing back.

The change is refused with a 409 when the subscription is not in good standing, already has a change scheduled, or already bills the plan named. The first two are settled or reviewed in the portal.

Buying credits

subako cloud billing credits --amount 1000

This opens Checkout for a one-off purchase at one cent per SC. The smallest purchase is 500 SC ($5) and the largest is 90,000,000 SC. The credits are deposited once Stripe confirms the payment and expire 180 days later.

Credits can be bought on any plan, Free included, and they keep working after a subscription ends — what a subscription adds is the monthly grant and the higher limits.

The billing portal

subako cloud billing portal

This opens the Stripe customer portal, where the card is changed, invoices are downloaded, and the subscription is changed or cancelled. It is refused with a 409 until something has been bought, since there is no customer to open it for.

When a payment fails

Stripe retries a failed renewal on its own schedule. While it does, the subscription reads past_due and the plan is kept, though nothing is granted for the unpaid period. If the retries run out, or the subscription is cancelled, the organization returns to Free: it keeps everything it holds, including unexpired credit, and is capped at Free’s limits for anything new. A payment that later succeeds restores the plan.

Reading the balance from the API

The organization endpoints of the Core API expose the same ledger to your own tooling: GET /v1/organization/credits returns the balance and every lot, with each lot’s source, what remains of it, and when it expires. Amounts there are in hundred-millionths of an SC, fine enough to carry per-second engine time below a whole cent.

Was this page helpful?