Billing

Plans

Every enterprise is on one of five plans: Free, Starter, Company, Scale or Enterprise. A new enterprise starts on Free, with no card. What each plan includes and costs is on pricing, and what is held to is in Plan limits. Each enterprise is billed on its own: two enterprises are two plans.

An enterprise that already exists upgrades from Billing, in the portal. A new one starts from its plan's button on /pricing: Sign up on Free and the paid plans, and Request access on Enterprise, which is priced for your contract.

The model bill stays your own. Runs use the model connections you add, with your own keys, and the provider bills you for them directly (Spend and models). Your plan pays for the company around them: its members, runs, workspace runners and storage.

The Billing page

Billing shows:

• the plan, its current billing cycle, and the plans side by side, monthly or annual, each with what it includes and costs;
• this cycle's usage of what the plan includes an amount of: members, workspace runner minutes, portal runs, concurrent runs and storage;
• each member's inbox: its mail today against the plan's daily cap, and how long the plan keeps mail;
• Concurrent runs, where a paid plan buys extra concurrent runs;
• the payment methods on file;
• every invoice, with its document to download;
• each closed billing cycle: what it used, and what was reported to be billed.

An owner sees all of it, and so does anyone allowed to see billing (billing:read). Changing anything on it takes the right to change billing (billing:write). See The billing grant.

Checkout

Choosing a paid plan on Billing starts a checkout. Payments are taken by FloPay, our payment provider. Before anything is charged, you confirm you are buying for a business and accept the product terms. Checkout then takes the business details (the legal business name, the billing address, the country, and a tax ID where the country has one) and the card, on FloPay's checkout page or in FloPay's own fields on Billing.

The plan moves when FloPay confirms the payment, not at the moment you check out. Enterprise is priced for your contract: its card on Billing asks you to talk to us.

When the product terms change, the next change onto a paid plan asks you to accept the new version first. Cancelling and withdrawing a downgrade never ask.

Payment methods and invoices

Once the enterprise has a subscription, Billing lists the payment methods on file. With billing:write you can remove one and, where FloPay supports it for your subscription, add a card and choose which one is charged.

Every invoice is listed with its amount and status, and its document downloads from Billing. A downloaded invoice shows the company's current name, including on invoices issued before a rename.

Changing plan

With billing:write, choose another plan on Billing:

• Upgrade now. A move up the plans applies at once, and FloPay charges the prorated difference for what is left of the current period.
• Downgrade at the period end. A move down, cancelling a paid plan included (a move to Free), takes effect at the end of the subscription's current period, with no refund. Until then the plan you have stays, and Billing shows the downgrade waiting and its date.
• Withdraw a downgrade. Choosing the plan you are on while a downgrade waits withdraws it. Choosing another lower plan replaces it, and choosing a higher one upgrades now instead.

A downgrade deletes older history and mail. Once it takes effect, run history and mail older than the smaller plan keeps are deleted at the next clean-up, and cannot be brought back. Until the period ends you can withdraw the downgrade, and nothing is deleted because of it.

Before a downgrade, Billing lists what the smaller plan cannot hold, and what happens to each from the day it takes effect:

Nothing shrinks on a move up. Paused members and schedules run again the moment a plan that holds them is in force, with nobody retrying them.

Overage

On a paid plan, work runs on past what the plan includes, and what is used past it is billed per billing cycle on the renewal invoice:

• A billing cycle is a month counted from the day your subscription started, on that day of each month (the last day of a shorter month). An annual subscription is counted in the same monthly cycles.
• When a cycle ends, what it used past the included amounts is reported to FloPay, dated inside the cycle, and Billing shows it under that cycle. Each cycle is billed at the plan in force during it: a downgrade at the period end bills the next cycle at the new plan's rates.
• When it is charged: on your subscription's renewal invoice. On a monthly plan, that is the invoice at the end of each cycle, so each month's extra use is charged a month at a time. On an annual plan, extra use is still counted month by month, and charged once a year, on the yearly renewal invoice.
• Members are counted by member-days: each day a member is in the enterprise is one member-day, and the extra members billed are the member-days past the plan's included members, as a share of the cycle's days. The COO counts as a member. The CEO, the people who sign in and the OS's own tasks never do.
• Workspace runner minutes and portal runs are counted over the cycle. The OS's own tasks take no portal runs.
• Storage is billed in GB-months: the gigabytes held past what the plan includes, over the cycle.
• Extra concurrent runs are not usage. They are a number you buy under Concurrent runs on Billing, at the plan's price per run per month, billed with the plan: each month on a monthly plan, and twelve months of them at each renewal on an annual plan. More applies now, prorated as an upgrade is; fewer applies at the period end.

Free never bills overage: where Free says stop, work past it waits for an upgrade or the next month (Plan limits).

When a renewal fails

If FloPay cannot collect a renewal, the subscription is past due:

• A banner says so, across the portal and at the top of Billing: the last payment did not go through, and it will be tried again. Someone without access to Billing is told to tell the owner.
• The owners are mailed each time a payment for the plan does not go through, with the amount due and a link to Billing.
• The work carries on while FloPay tries again, on the plan you have. Update the card on Billing to pay.
• If the payment cannot be collected, the subscription expires and the enterprise returns to Free, with Free's limits from then on.
• Once a payment goes through, the past due mark clears and the plan carries on. After an expiry, choosing a plan on Billing again starts a new subscription, and the plan comes back once FloPay confirms the payment.

Deleting the enterprise cancels a paid subscription at once, with no refund (Closing your enterprise).

The billing grant

Who may see Billing, and who may change it, is part of a person's grant: seeing it is the scope billing:read, and changing it is billing:write.

billing:write can only be held by a signed-in person: an API token can hold billing:read, never billing:write, and a connected app never writes billing. Owners hold both by owning. See People and access.