Billing

Cloud bills by the month, after the fact, and bills each of your organizations on its own. At the start of every hour it counts what is running, and on the 1st of each month it adds up each organization's month before and charges it to the card Paddle keeps for that organization, or sends an invoice if Cahaves bills that organization that way. Prices are in US dollars, and tax is added where it applies.

Everything about money lives under Settings, then Billing. It is the billing of the organization the console is in, and the line under its title begins "Billing for" and the organization's name. To see another organization's, switch to it at the top of the sidebar, as Organizations describes. This page explains how billing works. For current rates, look where you choose a size: the Size menu and the Order summary show each size's hourly rate when you create an application, and its rate per GB-month when you create a database (Sizes and replicas). Each organization's monthly limit is on its Billing page.

The page has five parts, all about the organization the console is in:

• Payment method: the organization's card on file, such as "Visa ending in 4242" with its expiry, and Add a card or Change card. With no card it reads No card on file. An organization billed by invoice shows how it is billed instead, such as Invoiced monthly in rupiah.

• This month: Used so far, Projected for the month (what the month comes to if everything running now keeps running to its end) and the organization's Monthly limit, with a meter of the projection against the limit, and a table of each service with its project, size, hours and amount. The Usage chart under it shows the months before.

• Statements: one row for each month Cloud has closed for the organization, with its Total, its State and its Document, and Pay now when a charge failed or an invoice is unpaid.

• Billing details: for an organization billed by invoice, the name, company, address and tax number its invoices carry. One that pays by card gives its address to Paddle instead, in the card form.

• Invoices and receipts: shown once the organization has a document, every invoice, receipt and credit note Cahaves has issued to it, newest first, each with its PDF, and Pay now on an open invoice that the statements above do not already offer.

When the organization's paid services are stopped for billing, or a stop is coming, the page says so, with the date and what clears it, as Stopped for billing describes. A stop that lasts adds the date Cloud archives the paid services, as Archived for billing describes.

At the start of every hour, on the hour in UTC, Cloud counts what each service has running and records that hour's charge. An application or a compose stack is charged by its running containers, at the hourly rate of its size in its capacity pool. A database is charged by the data it holds, at its size's rate per GB-month:

application or stack:  charge = running containers × the hourly rate of its size and pool
database:              charge = GB held × the rate per GB-month of its size and pool ÷ 730

• An application with three replicas running is charged three times its rate. A compose stack is charged for each of its running containers.

• A database is charged for each hour it runs by the data it held when Cloud last measured it. Cloud measures its volume once an hour, the same figure the Storage screen shows, and a GB is 1,000,000,000 bytes. Its page shows the figure under Data held. A database not measured yet is charged nothing for its hours until it is, and if a measurement fails the last one is used.

• The charge is per hour, not per minute. A service that is running when Cloud counts is charged for that hour; a service started after the count is first charged at the next hour.

• An hour in which a service has nothing running is not charged. A stopped or suspended service costs nothing, a database included, and so does one stopped for billing.

• Each charge uses the rate in force for that hour. When Cahaves changes a rate, hours already charged keep their price.

• If Cloud misses an hour, it charges each missed hour at the lower of the counts on either side of the gap, up to 72 hours back, and marks those hours as estimated.

• Volumes, backups and domains carry no separate charge.

For example, at a rate of $1.00 per GB-month, a database that holds 2 GB costs $1.00 × 2 ÷ 730, about $0.0027, for each hour it runs: $2.00 over a month of running. Sizes and replicas explains the sizes and the shared and dedicated pools.

The free allowance is yours, not each organization's, so owning more organizations does not add to it. Across all of them, you run some of what you need without charge:

• Your first nano application in the shared pool runs free. Its hours are not charged and leave no line on a statement.

• Your first nano database holds a set amount of data free, which its Order summary states when you create it. Each GB past that is charged at the nano database rate: with half a GB free, a free database holding 2 GB is charged for 1.5 GB.

First means the oldest of those that exists now, in any of your organizations, and each is free in whichever organization it runs. If you delete the free one, or change its size, your next oldest nano application or nano database takes its place from the next hourly count, wherever it runs. A compose stack is never free, since it runs only on dedicated capacity. The console marks a service the allowance covers Free, beside its state, on its page and in its project's list of services.

Running only what the allowance covers needs no card. The allowance is never paid out, and like a rate it can change for hours still to come.

Early on the 1st of each month, from 01:30 UTC, Cloud closes the month before, counted in UTC, into a statement for each organization. Once the month is charged or invoiced, its document has one line for each service and rate, such as "shop / api, small, 312 h at $0.0137 an hour". A rate that changed during the month gives two lines, and a database's data is a line of its own. The free allowance's hours are left out, and a month with nothing to pay makes no statement.

A month whose total is too small to charge on its own is not charged. Its statement reads Carried to next month, and its total opens the same organization's next statement as a line of its own, such as "Carried from November 2026".

Hours the meter records late, after their month's statement has closed (when it catches up after an outage, for example), are not lost: they go on the organization's next statement as a line of their own for each earlier month, such as "Usage in October 2026 recorded after its statement closed".

Anything past the free allowance needs a card on the organization it runs in, and each organization has its own: a card saved in one pays for that organization alone. Under Payment method, press Add a card. A page opens with Paddle's form beside a summary that reads "Paddle charges nothing to save the card. Any past month waiting for a card is charged to it once it is saved, and after that Cloud charges it on the 1st of each month for the month before." Paddle, Cahaves' payment provider, keeps the card on a subscription of $0.00 a month, which charges nothing itself, and your bank may ask you to confirm the card. When the form completes, the page reads "Paddle has the card. Saving it to this organization.", then Your card is saved, and Payment method shows the card's brand, last four digits and expiry. Cloud never receives the card number.

On the 1st, Cloud charges the organization's month to that card. Paddle takes the payment as merchant of record, adds tax where it applies and emails you its receipt, and the statement's document is Paddle's invoice for the charge. Change card opens the same page for another card, which takes the place of the one on file for every charge from then on. If the subscription that keeps the card is cancelled at Paddle, the organization has no card any more.

A card checkout belongs to the organization it was started in. If the console moves to another organization before the form completes, in this tab or another, the card page says "This checkout belongs to another organization": switch back to finish there. Payments covers the messages.

A month that closes while the organization has no card is not lost. Its statement reads Waiting for a card, Cloud emails you, naming the organization, and the month is charged once you add one.

Paid services need the card before the month closes, too. An organization billed by card that runs a paid service with no card on file, because its card was removed at Paddle or because the service was running before its card was asked for, gets an email with a date: "Add a card to Kopi Tiga by 13 December 2026 at 12:00 UTC, or its paid services stop". Without a card by then, its paid services stop, as Stopped for billing describes.

Cahaves can bill an organization by invoice instead, in US dollars or in rupiah: write to support, naming the organization, to arrange it. Each organization billed this way is a client of its own in Cahaves' invoicing, with invoices of its own. On the 1st, its month goes to Cahaves' invoicing service, which emails you the invoice with a link to pay it, through Paddle for US dollars or through SingaPay for rupiah, by virtual account, QRIS, card or e-wallet. An invoice in rupiah converts each line at the exchange rate Cahaves set, rounded to whole rupiah, and prints the rate and the date it was set.

The statement reads Invoiced until the invoice is paid, and Overdue once its due date has passed by the calendar in Jakarta (UTC+7), where the invoices are issued. Pay now opens the invoice's payment link in a new tab; a link that ran out at the end of the due date is renewed within the hour. Cloud checks the invoice against the invoicing service the next time you open billing, not the moment you pay: that is when the statement turns to Paid, and when new paid work is accepted again. The statement's document is the invoice. If Cahaves voids an invoice, its statement reads Voided: nothing is owed for it, and a corrected invoice for that month, if there is one, comes separately. Billing details holds the name, company, address and tax number the organization's invoices carry; change them there before the 1st, and the next invoice carries them. With no company given there, an invoice names the organization as its company, except for an organization named after you or the one your account had before organizations: theirs carry no company, only the name.

Work that costs nothing needs nothing: the free application and the free database are created, deployed, started and kept at nano as always. Paid work needs the organization it is in to be in good standing. Paid work is creating, deploying, starting, restoring or resizing a service you pay for, and opening a paid database's public access or choosing its settings before its first start. A database's password can always be changed, and its public access always closed, whatever the organization owes. Backups, and the deploys Cloud or Cahaves staff run for you, are not paid work. Good standing means, for that organization:

• a card on file, when it pays by card;

• no card charge that failed, and no invoice past its due date;

• its month, with what you ask for, inside its monthly limit.

When one is missing, Cloud refuses the action with one sentence, in a toast with an Open billing button to the page. Standing is each organization's own: what one owes never refuses work in another. A refusal stops nothing that is already running; what runs stops only as Stopped for billing describes. Work that costs less, such as a stop, a smaller size or fewer replicas, is never refused for being over the limit or unpaid, and work that adds nothing to the hour, such as deploying a service that is already running, is never refused for the limit.

The month and the amounts in these sentences are the organization's. While the organization is stopped for billing, its refusals say so instead, as What is refused while it lasts lists.

Every organization has a monthly limit of its own in US dollars, shown on its Billing beside this month. Cloud works out what the organization's month comes to: what it has cost so far, plus everything running in it now at its current rate until the month ends, plus what you ask for, which is a new service's rate or the difference a new size makes. A database's data is counted at its size now. Paid work that would take that past the organization's limit is refused.

The projection only refuses new work. What stops running services is the month to date: once what the organization has been charged this month, Used so far, reaches its limit, Cloud stops its paid services at once, until the next month begins or the limit is raised above it, as Stopped for billing describes. A database that keeps growing is the usual way there, since its data is charged by the GB. When what an organization's month comes to reaches 80% of its limit, Cloud emails you that the month is on course to reach it, naming the organization, once that month. While the month is projected past the limit, Billing reads This month is at this organization's limit. To raise an organization's limit, write to support with its name or its Organization ID, from Settings, Organization.

If a card charge fails, its statement reads Payment failed, Cloud emails you, Billing reads A past month is unpaid, and new paid work in that organization is refused until it is paid. Press Pay now on the statement: a Payment page opens in the console with Paddle's form beside the amount owed, where you can pay with the same card or another. It reads "Paddle has the payment. Marking the month paid." once Paddle takes it. An invoice past its due date reads Overdue and refuses new paid work in its organization the same way until it is paid through its link.

A month left unpaid stops the organization's paid services once its grace period ends, on the date Cloud emails you, and a month that closes with no card works the same way, as Stopped for billing describes. A stop that lasts archives them (Archived for billing). Cahaves may also suspend an account whose payment stays unpaid, which stops the services of all its organizations, as Suspended by Cahaves describes. Payments covers the messages each step can show.

Cloud stops an organization's paid services, the ones it charges for, when one of these holds for that organization:

• A month stays unpaid past its grace period. A card charge that failed, a month that closed with no card, or an invoice past its due date starts a grace period: from the failure, from the close, or from the end of the due date by the calendar in Jakarta. Cloud emails you the date and time it ends, in UTC, naming the organization: "Paid services in Kopi Tiga stop on 13 December 2026 at 12:00 UTC unless the month is paid". Billing shows the same date. Go by that date: pay before it, and nothing stops. A charge that is tried again and fails keeps its first date. When the stop is already due as Cloud finds the month unpaid, there is no warning, only the email that it has stopped.

• Paid services run with no card on file. An organization billed by card that runs a paid service, one running, failing or held stopped by Cloud, with no card on file starts the same grace period, from the first time Cloud saw it so. Cloud emails you the date: "Add a card to Kopi Tiga by 13 December 2026 at 12:00 UTC, or its paid services stop". Billing shows it too. Add a card before then and nothing stops. The date holds until the cause clears, and comes back as a new grace period only if the cause returns later.

• The month to date reaches the monthly limit. Once what the organization has been charged this month reaches its limit, its paid services stop at once, right after the hourly count that took it there. What the month is projected to come to does not stop anything; it refuses new paid work, as The monthly limit describes.

The stop is the organization's alone. Your other organizations carry on, and your free application and free database keep running in whichever organization they are, this one included. While it lasts nothing is deleted: volumes, databases and backups stay. A stop for an unpaid month or for no card that lasts 30 days has its paid services archived, as Archived for billing describes; a stop for the limit alone never does. Cloud records which paid services were running and stops them, and the console marks each one Stopped for billing. A database in the middle of a backup stops once the backup finishes. A deployment of a paid service still queued or building, whoever started it, is cancelled with "Deployment cancelled because paid services in this organization are stopped for billing." Stopped services cost nothing, so the month to date stops growing, apart from a free database's data past its free amount.

Cloud emails you when the stop happens, "Paid services in Kopi Tiga are stopped for billing", saying why and what clears it, and for an unpaid month or no card, the date Cloud archives the paid services if they stay stopped.

Each cause clears on its own, and the services come back once every one has:

About a minute after the last cause clears, Cloud starts again exactly what it stopped, each service at its own replicas, and once they are all back it emails you "Paid services in Kopi Tiga are starting again". A service you had stopped yourself before the stop stays stopped. Cahaves never lifts a stop by hand: support clears its cause, by marking an invoice paid or raising the limit.

Stopping a service that is stopped for billing changes nothing, so one you no longer need comes back with the rest: stop it once it is running again.

While the organization is stopped, the paid work What needs a card lists is refused with a sentence that names the cause and what clears it, and so is starting a service stopped for billing:

With more than one cause, the sentence names each, and what clears each. The organization's name, the month and the limit in these sentences are its own. Work that costs less, such as a smaller size or fewer replicas, and anything on the free application or the free database, is never refused for the stop.

A stop for billing is separate from a suspension by Cahaves, which holds every organization you own (Suspended by Cahaves). When both hold a service, it starts again only once neither does.

A stop for an unpaid month or for no card that lasts 30 days archives the organization's paid services: Cloud takes a final backup of each one's data, then deletes the service. The date is set once, when the stop for that cause begins, and it does not move. The email that the services stopped gives it, and so do Billing and the dashboard: "If the paid services stay stopped, Cloud archives them on 12 January 2027 at 12:00 UTC: it keeps a final backup of their data for 30 days, then deletes it." Go by the dates in Cloud's emails, which are in UTC.

A stop for the limit alone is never archived, since it lifts with the month. Your free application and free database are never archived, in any organization, and neither is anything in your other organizations.

Clear every cause before the archive date, as What brings them back lists, and nothing is archived: the stop lifts and the services start again as usual. A cause that clears while Cloud is still taking a service's final backups also keeps that service, and the backups already taken stay as its ordinary backups. Once a service is deleted, paying does not bring it back.

From the archive date, within the hour, Cloud archives each paid service in the organization:

1. A final backup of its data, to the same platform backup storage your backups use (Backups): a database dump of a PostgreSQL, MySQL, MariaDB or MongoDB database, and an archive of each volume of an application. A database stopped for billing is started briefly for its dump. An application with no volume, a Redis database, a compose stack and a service that never ran have nothing Cloud backs up, so they are deleted with no final backup.

2. Then the service is deleted, only once every final backup of it has finished, the way you would delete it yourself: its domains, its backup schedules and its volumes first, then the service. If a final backup fails, the service is not deleted, and Cloud tries again a day later.

When the services are archived, Cloud emails you which ones, and until when their final backups can be downloaded. Archiving settles nothing that is owed: an unpaid month stays unpaid until it is paid, and new paid work in the organization is refused until its cause clears, as before.

The final backups are kept for 30 days from archiving. Until then, Storage has an Archived tab beside Backups, listing each archived service with its project, when it was archived and the date its backups are kept until, and each final backup with Download: a database dump as a gzip file, a volume as a tar file. A backup can be downloaded once Cloud has verified its stored file, usually within the hour. Cloud emails you a reminder 7 days before the date, and deletes them on the date. The archived service stays on the tab with the date its backups were deleted, and no download.

Paying after the services were archived keeps their final backups until the same date, and restores nothing: Cloud does not rebuild an archived service. Download the backups and create the service again, and support can help you rebuild it.

Each goes to your account's email, names the organization, and gives every date in UTC:

A service archived with no final backup is named in the email at archiving, and not again.

The Usage chart draws what the organization was charged as columns, one per period, in UTC:

The last column is the period in progress. Hover a column, or move between columns with the arrow keys, to read its period and its amount. Beside the tabs, a chip with an arrow compares the last finished period with the one before it, as a percentage; it is absent when there is nothing to compare or no change.

With nothing charged yet, the card reads: "Nothing charged in the last 30 days. Running services are metered once an hour, so a service started in this hour is not on the chart yet."

Cloud emails your account's address, the one you sign in with, when an organization's month is on course to reach its limit, when its card charge fails, when its month closes with no card, when an unpaid month's or a missing card's grace period starts, with the date its paid services stop, when they stop for billing, when they start again, and at each step of an archive, as The emails at each step lists, whatever notification channels you have set up. Each email names the organization it is about, and its link opens that organization's billing, or for an archive's final backups its Storage, moving the console to it first. Notifications calls them Automatic account emails. Paddle sends its own receipt for a card charge, and an invoice comes from Cahaves' invoicing service, so Cloud does not repeat either.

Cahaves can suspend an account itself, for example when a payment stays unpaid or the terms, external link are broken. A suspension is the account's, so it holds every organization you own. Billing then reads This account is suspended: "Cahaves suspended this account and all its organizations, and only Cahaves can lift the suspension." Every running service, in every organization, is stopped, and changes are refused with "This account is suspended by Cahaves. Contact support to have the suspension lifted." Your stored data is kept. Contact support. When Cahaves lifts the suspension, the services the suspension stopped start again. Until the account is active again, changes are refused with "This account is starting again. Try again in a minute."

A banned account is different again: it cannot sign in at all (Sign-in problems).

Until 05:00 UTC on 14 October 2026, Cloud was prepaid: you added credit with top-ups, one credit to a US cent, and each hour came off the balance. Top-ups ended there, an hour ahead of the switch itself, so the last one had time to settle first. At 06:00 UTC monthly billing started: credit you had paid for and not spent was refunded through Paddle, and the signup credit and credit Cahaves had added lapsed. Paddle's receipts for your top-ups stay your record of them, and the refund policy, external link covers what changed.

The first monthly close after the switch is scheduled for 1 November 2026. For organizations that moved from prepaid, the first monthly period runs from 06:00 UTC on 14 October through 31 October. An organization already billed by invoice keeps its earlier start date.

The switch retired balance-based billing. A ban or an operator's suspension stayed in place until Cahaves lifted it.