Billing
Infrastructure is billed on what your resources used, at a published rate per unit. Kuppit meters every resource itself, prices the meter at the rates below, and shows the month so far on the dashboard's Usage page. Nothing here is a markup on someone else's invoice, and nothing is estimated from one: the figure on the page and the figure on the invoice are the same meter at the same rates.
Rates
| Resource | What is metered | Billed per | Rate |
|---|---|---|---|
| Web service | CPU while serving | vCPU-hour | $0.030 |
| Web service | Memory while serving | GB-hour | $0.015 |
| Worker, scheduled worker | CPU while allocated, or per run | vCPU-hour | $0.055 |
| Worker, scheduled worker | Memory while allocated, or per run | GB-hour | $0.008 |
| PostgreSQL | Compute while active | CU-hour | $0.125 |
| PostgreSQL | Storage | GB-month | $0.45 |
| Every resource | Bandwidth out | GB | $0.05 |
A compute unit (CU) is one vCPU with four gigabytes of memory, which is how a database's compute is measured; a database that scales down uses a fraction of one. Memory is metered in binary gigabytes (GiB) and billed per GiB-hour; the page and the invoice say GB. A web service that scales to zero costs nothing for compute or memory while idle; a worker's instances are billed for as long as they are allocated, whether or not there is work; a scheduled worker is billed only while a run executes; a database is billed for its compute while active and for its storage while it exists.
Rates apply from the first of a month and do not change inside one. A rate change is a new rate table with a start date; a month that was closed at the old rates stays closed at them.
Measured, not billed
Two things the Usage page shows carry no charge:
- Builds. Kuppit measures how long each build ran and shows the minutes. They cost nothing.
- Requests. The count of requests a service served is shown for reference. It is never billed.
How a month closes
A billing month is a UTC calendar month. While it is running, the Usage page shows the month so far, current through the last metering window Kuppit collected; the line under the figure says how current that is, and says so plainly when collection has fallen behind.
The month closes one day after it ends, once the meter has collected every window up to its end for every piece of infrastructure your resources ran on. At that point every line is written down — the resource, the metric, the quantity, the rate and the amount — and never changes again. What you were shown is what you are invoiced.
A month is never closed short. If any usage cannot be priced — a resource whose kind Kuppit could not establish, or usage that reached the organization but no resource — the month stays open until the cause is fixed. Nothing is guessed and nothing is quietly left off; Kuppit would rather invoice you later than invoice you wrong.
A resource deleted during the month keeps its place on the Usage page under its own name, marked deleted, for what it used before it went.
Plans
Developer is $0 a month for one member, and pays for the infrastructure it uses. A new organization starts with $5 of infrastructure to use before a payment method is needed; once that is used, new builds and deployments wait for a card, and everything already running keeps running.
Team is $20 a month, and includes $20 a month of infrastructure usage. Unlimited team members. Additional infrastructure is pay as you go.
The included usage is the whole $20: a team using $20 of infrastructure in a month pays $20 in total, not $40. In practice:
| Infrastructure used | Subscription | Infrastructure invoice | Paid in total |
|---|---|---|---|
| $12 | $20 | $0 | $20 |
| $20 | $20 | $0 | $20 |
| $32 | $20 | $12 | $32 |
| $70 | $20 | $50 | $70 |
The included usage follows the subscription's own billing date rather than the calendar month: it becomes available when the subscription invoice is paid, covers the month that invoice covers, and is used up by the infrastructure invoices of the calendar months that fall inside it. It does not roll over.
The subscription is invoiced on its own date. Infrastructure is invoiced once per calendar month, after the month closes, with one line per kind of resource — web services, workers, databases — then bandwidth, then the included usage taken off.
Estimates
Where the dashboard shows what a size might cost — when you choose one for a new resource — the figure is the published rates applied to a stated month: one instance running the whole month for a web service or a worker, thirty runtime hours for a scheduled worker, storage alone for a database. The sentence beside the figure says which. It is for comparing sizes, not a price; the bill is what actually ran. See sizes.
Spending limits
A spending limit you set on the Billing page, and the daily ceiling each plan carries, are measured against the same meter at the same rates. What each does when it is reached is on the limits page.