Plans and billing
What a plan refuses, that buying ends the free month that day, up now and down at the period's end, the choice at a downgrade, and why agents are counted rather than servers.
A plan is a set of promises about what Runjet will refuse. Three plans — Solo, Pro and Business — differ in three numbers; the prices and the numbers are at runjet.dev and this page deliberately does not repeat them, so that it cannot be lying at the moment somebody buys.
What a plan limits
| Axis | What happens at the limit |
|---|---|
| agents | the next agent enrolment is refused with a 409 and the sentence the pro plan allows 15 agents; nothing already enrolled changes |
| accounts | the next invitation is refused the same way |
| a run's output | text past the cap is discarded; the run finishes |
| the window for output text | text older than the window is swept by the nightly sweep; a run's state and timings stay for ever |
What a plan does not limit: the number of jobs and the length of the run history. Jobs are unlimited on all three, and a run's row — when, where, how it went — is never deleted. No plan puts a time limit on a run.
Agents are counted, not servers. One machine running three agents in
containers has used three. The word "server" would read as room to spare to
exactly the person who has none, and the surprise would arrive as a 409.
The free month is Pro
A new workspace is created on the Pro plan and pays nothing for thirty days. It is not a fourth plan with Pro's numbers copied into it: the free period is the Pro row, so "thirty days of full access at Pro level" holds by construction.
Buying ends the free month
Paying for any plan ends the free month that day, and billing starts at once. The free period is what you have until you pay — not a discount on the first month of what you bought. So deciding on the twelfth day costs the rest of the month, and the plan picker says so beside the amount: This ends your free month: billing starts today, with how many days were left.
Buying and changing
The Billing screen, for the admin role. Before a first payment it offers Subscribe on each plan and a Billing period switch (Monthly, or yearly for ten months' money); the payment happens at the payment provider and sends you back to the same page with Thank you — the payment went through. The plan is written when the provider confirms the payment — anyone who opens the payment page and closes it has changed nothing (That checkout was cancelled).
After a first payment the plan changes on the same screen, with no new payment page, using Move to … now and Move to … at the period's end. Runjet holds neither invoices nor cards; What Runjet keeps on that page says exactly that and points at the provider.
Up now, down at the period's end
An upgrade applies immediately and pro rata: the unused remainder of the period is set against the new plan's price to the end of it. Somebody is asking for more and paying for it, and making them wait would refuse money for a limit they need today.
A downgrade applies at the end of the period already paid for. It takes back something the period has already bought. Until then the change is scheduled and the page says so; and choosing the plan you are already on cancels a scheduled change — no second button, because "stay here" can be said with the controls already on the screen. While a downgrade is scheduled, Runjet counts new agents and accounts against the plan that is coming: you said you were going to Solo, so Solo is what you may fill.
Which direction a move goes is ranked on the monthly price; ranking on what is actually charged would make yearly Solo to monthly Pro a downgrade and leave somebody plainly asking for more waiting a year for it.
A downgrade asks what you will give up
When not all your agents or all your accounts fit into the new plan, a dialog opens at the confirmation and the choice is mandatory: the button stays shut until you have chosen enough. Runjet switches the chosen agents and accounts off on the day the plan lands, not when you click — until then they are paid for. Jobs that lose their last agent to a switched-off one are named by the dialog (This job stops running) but not refused: somebody who has to move down has to be able to.
An agent or account switched off this way is marked as locked by the plan and releases its place; an ordinarily disabled agent or a blocked account keeps its place. Switching a locked one back on is an addition like any other, refused by the ceiling until the plan has room: A larger plan does not switch them back on — an upgrade frees your hands and you switch back on what you want.
What a downgrade does not take away
Outputs you could read the day before the change you can read the day after: a move to a shorter window writes a floor and the sweep does not reach past it (the output floor). The window is a promise about how long output is kept from here on. The run history is not swept at all, jobs are unlimited, and the output cap applies only to later runs. The plan picker says so: What is already stored stays.
Extra agents
Capacity beyond a plan's count can be bought on Business only — on a lower
plan the overage would overshoot into the one above — as an explicit purchase
rather than a limit that quietly starts charging. Buying it is switched off
today; when it is switched on it will be on the Billing screen and in
the log as billing.capacity.
When a payment fails
Nothing stops. The provider retries the card over a couple of weeks and an email arrives. Only the end of the subscription suspends the workspace, and paying brings it back.