Skip to main content
Open console

Billing

How a subscription is charged, when changes take effect, and what happens when an invoice goes unpaid.

10 min read

Everything a project runs is on one subscription, billed to the team that owns it. The team's Billing page lists the subscriptions, what the period running now has come to, the statements and the card.

The period

Monthly, quarterly or yearly, chosen when the project is set up.

Period Paid ahead Notice to cancel
Monthly — 3 days
Quarterly 5% off 10 days
Yearly 15% off 45 days

The period is fixed for the term. On a card subscription it changes at renewal, not mid-term. The Commercial terms cards show it and refuse the change.

Premium support and the Advanced uptime SLA are sold on a quarterly or yearly period. The Premium uptime SLA is sold on a yearly one. A project on a shorter period is shown them and told why they are not available until the period changes.

Changing something mid-term

Everything except the period can change at any time: support, the uptime promise, the environment count, extra bandwidth, the CDN and its network, the number of domains, how many people are on a project, and production's backup schedule. Resizing a machine or buying a disk counts too.

Taking more is always immediate and always prorated. You are charged for the part of the period you use it.

A reduction applies from your next invoice, with one exception: resizing a machine. Until then you keep what you are giving up, and keep being billed for it.

Change Takes effect Credited now?
Resize a machine, up or down Immediately Yes, both ways
Buy a disk, or grow one Immediately n/a
A disk you already have Not removable —
Add environments, traffic, CDN, domains, people Immediately n/a
Reduce environments, traffic, CDN, domains, people Next invoice No
Move the CDN to the cheaper network Next invoice No
Lower support or the uptime SLA Next invoice No
  • Not every machine can be resized down. See Resizing a machine.
  • You can lower a number at any time. It is recorded, and raising it again before the next invoice cancels the reduction.
  • Deleting an environment costs nothing and refunds nothing. The slot stays yours for the next one. Lowering the count is what changes the price.
  • A disk cannot be given back. Storage is grown, never shrunk.
  • A machine that cannot be built is not charged for. It comes off your bill when its build is given up, with the disk bought for it. The rest of the period is credited. The environment's page and the project's Machines notifications say so. If it is built later, it is charged from then.

Adjustments appear on the next invoice, not as a separate charge.

Resizing a machine

Which way a machine can move depends on its disk. See Machines for the two kinds.

Cloud native compute Regular compute
The disk Its own. A resize changes CPU and memory and leaves the disk alone Part of the machine type. Moving up grows the disk with it
Growing Without taking the site down where the provider allows it The machine is always stopped, moved and started again
Shrinking The machine is always stopped, moved down and started again Not possible. Storage cannot be shrunk, so the list offers only the size it is on and larger
On the bill Credited both ways Charged prorated from the day you take it

Choose cloud native compute when a site is busier in December than in February. Before you confirm a resize there, you are told whether the machine keeps serving or is stopped.

Growing the disk grows the filesystem on it too, so the room is there when the machine comes back.

Preview environments share one machine: staging, development and every feature branch. That machine is what is resized, and resizing it gives every environment on it more at once.

It can move only to a machine on the short VC-PRE-… list:

  • Several machines carry the same number of environments, twenty for example. They differ in how much each environment gets, and every option says both.
  • The name is the count, then which of that size's machines it is, cheapest first. VC-PRE-E20-0 is the cheapest machine carrying twenty, VC-PRE-E20-1 the next one up.
  • Pick further down the list when the environments are rehearsing a large site, and at the top when they are not.
  • It can move to a smaller machine, but not to one that carries fewer environments than are running on it.

Paying

Pay by card, or by bank transfer where invoice terms have been granted. You cannot switch invoice terms on yourself.

Card details are entered at the payment provider and never reach this platform. Manage at Stripe on the billing page opens their portal, where the card, the receipts and the past invoices live.

By invoice, a period is billed when it ends. The statement for it is raised on the last day of the period and is due that many days later: a month from 13 November to 13 December on 30-day terms is due on 12 January.

Usage this period on the billing page shows what the period running now has come to so far, and what its statement will come to if nothing changes: each machine and add-on for the days it has run, the period's discount, and the days a machine spent autoscaled, and VAT. A credit for an outage is worked out when the statement is raised.

Statements are this platform's record of each period, with what was paid against it. The invoice itself is sent by email.

Free trial

Paying by card, a project whose machines come to €30 a month or less before tax starts with three days free. The configurator marks the machines that qualify, and its summary says whether the whole order does. Add-ons such as support, uptime or extra environments are not counted towards the €30. A promotion code can give a trial on other terms, longer or on larger machines. It says so when it is applied at checkout.

  • The card is taken at checkout and charged when the trial ends. Cancel the project before then and nothing is charged. It runs until the trial ends, and is then deleted with its data and backups.
  • One trial per person, and per card. Whoever orders, and every owner of the team, must not have had one before, from a code or not. A card or bank account that has already paid for a trial, under any account, ends the new one as soon as checkout completes. The site keeps running, and the first payment is taken straight away.
  • The project runs as ordered until the first payment. Nothing that raises the price can be changed during the trial: resizing a machine, growing a disk, moving a service onto a machine of its own, adding machines, or raising the commercial terms. Giving something back is allowed.
  • If the first payment does not arrive, the site is taken offline a couple of hours after the trial ends and shows your offline page. Pay within three days, by updating the card in the billing portal, and it comes back on its own.
  • After three days unpaid, the data and backups are deleted. The project is cancelled and its machines are removed straight away. Unlike an ordinary cancellation, nothing is kept for thirty days.

Paying by invoice there is no trial: the terms are agreed with us.

Tax

Prices in the console are shown and stored net. The public price list shows them with Croatian VAT included.

Tax is worked out at checkout from the billing address on your team:

Billing address Tax
Within Croatia, and EU consumers 25%
A business elsewhere in the EU with a verified VAT id Reverse charged, and labelled as such
Outside the EU Zero

The billing address belongs to the team: two people buying for one team cannot put two different companies on two invoices. Changing it applies to the next invoice and never to one already raised.

An invoice that goes unpaid

Nothing is destroyed, and nothing stops serving.

Paying by invoice. The team's owner is mailed a couple of days before an invoice falls due, again when it passes its due date, and weekly after that. Three days past the due date the team is suspended. After a week it also opens a ticket on our side. The suspension is lifted when the invoice is paid.

Paying by card. If the payment provider's retries fail and the subscription ends unpaid, the team is suspended seven days after the subscription ended. The suspension is lifted once the team has a way of paying again: a live subscription, or invoice terms we have granted.

On a suspended team everybody is capped to Viewer. The sites keep serving and the backups keep running. Deploys, provisioning and configuration stop.

Cancelling

Cancel from the project, giving the notice its period asks for. The dialog quotes the date before you agree to it.

  • With more notice than that, the subscription ends at the end of the current period.
  • Inside the notice window, it ends at the end of the next one.

By invoice, the last period is billed when it ends, as every period is.

Your site keeps running until that date. Then:

When What happens
On the date quoted Billing stops. A bare-metal server is destroyed that day, not a day later
A day after it The machines are destroyed and the hostnames stop resolving
Thirty days after the subscription ends The backups are deleted from our storage

The project, its environments, their domains and the release history stay as they are. Until the backups are deleted the site can be brought back: see Backups. A copy in your own storage is not deleted.

Worked examples

Assume a monthly subscription that renews on the 1st.

Day You What happens
Checkout Configure production, add one extra environment and a CDN commitment, and pay The first invoice covers the whole first period. The subscription then renews on the 1st of each month for the same lines
10th Raise the environment count from 1 to 2 in Commercial terms Two-thirds of a month is charged for the new slot, and it appears on the 1st. You can set the environment up immediately
12th to 15th Create an environment in the slot you already have, and delete it three days later Nothing is charged and nothing is credited
14th and 20th Resize a production machine on cloud native compute up, then down Both are prorated. The invoice on the 1st shows the charge for six days at the larger size and the credit for the rest of the month at the smaller one
16th Move a production machine on regular compute up Half a month is charged for the difference. The new size comes with a bigger disk, so there is no way back below it
18th Drop support from Premium to Standard Recorded, and applied on the 1st. You keep Premium response times until then
20th Delete an environment and lower the count from 2 to 1 Its machine is destroyed there and then. The count stays at 2 until the 1st, when the lower price takes over. The rest of that month is not credited. Raising it back to 2 on the 27th cancels the reduction entirely
22nd Buy a 50 GB disk A third of a month is charged for it on the 1st. It cannot be removed later, only grown
25th Cancel Three days' notice, so it lands at the end of the month you are in. Billing stops on the 1st, the site keeps serving until then, and the machines go a day later. The backups are there for thirty days after the 1st

Next

  • Plans — what is bought, and what each part is
  • Teams — who is billed, and how people are counted