Plans

A plan decides what a project's production runs on. Environments beyond production — staging, development and feature branches — are add-ons on either plan, bought with the project or added later under Commercial terms.

Every price is on the public price list, with the machines grouped the way the configurator groups them, cheapest first.

Plan	What it is
Dedicated	Single project. Every topology is available. Ideal for medium to large projects.
Shared	Multiple projects on a single machine dedicated to your sites. Ideal for smaller projects.

#Shared

Several of your small sites packed onto one machine. The word shared is about the machine being shared between your own projects — not between customers. Nobody else's site runs on it.

What that buys you is the cost of one machine across several sites. What it costs you is flexibility:

• One machine for production, always. You can see how a site is laid out, but nothing can be moved onto a second machine and no worker or extra can be added — those are machines of their own, and a shared plan buys none. Additional environments, if you add them, share one machine of their own beside it, the same as on a dedicated plan.
• No uptime promise. One machine that reboots is a site that is down, and there is nothing to fail over to. The console shows this as No uptime SLA and will not let you change it, because changing it would be selling a promise nothing can keep.

This is the right plan for a brochure site, a small shop, a landing page — the sites where an hour of downtime during a kernel upgrade is an inconvenience rather than an incident.

#Dedicated

Your own machines, and every option is open: any shape, and an uptime promise that means something because there is more than one machine to keep the promise with.

#Backups

Every production environment is backed up nightly and kept a week, on either plan, with two copies offsite on different providers. How long a series reaches back is not something the plan decides — it is bought for production, and changed whenever you like. Thirty days instead of a week catches "this has been wrong since before the last release and nobody noticed", which is the restore people actually need and the one a week does not cover.

The database can also be backed up every four hours rather than nightly — an add-on on either plan, and included on the Dedicated shape. Staging and development are not copied offsite. See Backups.

#Non-production environments

Production is included. Everything beyond it — staging, development, feature branches — shares one machine, and that machine is the purchase. You pick it when you set the project up, from a short list named for how many environments each one carries (VC-PRE-E3-0 suits three, VC-PRE-E7-0 seven), and resize it afterwards from its own page like any other machine.

How many environments you run on it is a separate lever, and a free one: the count divides the machine rather than buying anything. Staging takes two shares to a feature branch's one, so at three environments staging has half the machine and the other two a quarter each. Run more and each gets less; run fewer, or buy a bigger machine, and each gets more. Both are changed later under Commercial terms on the project's configuration page, and adding an environment past the count opens that dialog rather than failing.

Sold in bands — 2, 4, 6, 8, 10, 15, 20, 25 — so seven environments are bought as eight and the spare one is yours to start whenever. On a shared plan the ceiling is twenty-five, which is one non-production environment for each site the plan can carry.

The machine is built in production's own datacentre wherever one suitable is sold there, and in the nearest that has one otherwise; the configurator says which before you buy.

#Traffic

Origin bandwidth is what leaves your machines — to visitors directly, or to the CDN in front of them. Every machine that faces the internet includes some each month. How much depends on the machine and where it runs, and the configurator shows the figure beside each one as you choose and the total under Edge — so the allowance you are buying is on the screen rather than in a table here that would be right for some machines and wrong for others.

The figure shown is yours to spend. Like cores, memory and disk, traffic is quoted after the platform's own share has been taken out of it. Your backups leave the machine on the same connection your visitors arrive on, and so do your shipped logs, the container images pulled on every deploy, and the agent talking to the control plane — none of which appear in any log you can see. The allowance beside a machine is what is left once all of that is paid for, with room kept back for the month nobody plans: a crawler that finds a faceted search, a fortnight of retries against a webhook that broke quietly.

So the number is smaller than the one the underlying provider advertises, and it is the only one we will quote you. There is no larger figure to go looking for.

A site that will send more buys extra bandwidth by the terabyte a month, at the same price whatever the machine or datacentre, when the project is set up or later under Commercial terms.

Requests are not limited. Nothing is capped or charged per request, at the origin or at the edge: a page served a million times costs its bandwidth and nothing else.

#CDN

Serving your site from datacentres near your visitors, bought by the terabyte a month. The platform runs the pull zone, attaches your domains and gets the certificates; your application can clear the cache without holding a credential. Full details.

#Domains

Two of your own domains on a project are included — the name the site answers on, and the one somebody always wants beside it. More are bought in two bands, up to nine and up to twenty-five, under Commercial terms.

#People

The first person on a project is free; everybody after that is charged per project. See Teams.

#Changing any of it later

Support, the uptime promise, the environment count, extra bandwidth, the CDN, domains and production's backup schedule are all changed from Commercial terms on the project's configuration page. Taking more is immediate and prorated — you are charged for the part of the period you use it. Giving something back takes effect from your next invoice and is not credited for the rest of the period you already bought. Resizing a machine is the exception, credited both ways; a disk cannot be removed. See Billing.

The billing period is the one thing that does not move mid-term. It is what you agreed to and have been invoiced under, so it changes at renewal; the dialog shows it and refuses it rather than leaving you to wonder where it went.

#Choosing

Start with the question of whether one machine is enough for production. If an hour of downtime during a kernel upgrade is an inconvenience rather than an incident, shared is enough. If it is an incident, you need dedicated — that is the line, and it is a harder line than machine size or traffic.

You cannot move a project between plans. They are different machines, not a setting on the same one, so switching means creating the new project and migrating to it. Choosing dedicated for a site that turns out not to need it costs money; choosing shared for a site that turns out to need a second machine costs a migration.

#Next

Shapes covers how many machines an environment runs on, which is the choice inside a dedicated plan. Billing covers how any of this is actually charged — the period, what changing something mid-term costs, and what happens if an invoice goes unpaid.