Skip to main content
Open console

Plans

What differs between shared and dedicated, and which one your site needs.

6 min read

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 as the configurator groups them, cheapest first. To compare configurations in a conversation, see Ask an assistant.

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 on one machine. The machine is shared between your own projects, not between customers.

  • 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. Additional environments share one machine of their own beside it, the same as on a dedicated plan.
  • Standard uptime only. 99.9% a month, committed, with service credits when it is missed, the same as every project. Advanced and Premium are sold on a dedicated plan.

It suits a brochure site, a small shop or a landing page: sites where an hour of downtime during a kernel upgrade is an inconvenience, not an incident.

Dedicated

Your own machines, and every option is open: any shape, and the Advanced and Premium uptime promises.

Backups

Every production environment is backed up nightly and kept four days, on either plan, with two copies offsite on different providers. Add-ons, on either plan:

  • Thirty days instead of four, for production. Change it whenever you like.
  • Database backups every four hours instead of nightly, on either shape.

With point-in-time recovery, production's database can be restored to any moment of the last seven days. Staging and development are not copied offsite. See Backups.

Non-production environments

Production is included. Everything beyond it shares one machine, and that machine is the purchase.

  • The machine. 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). Resize it afterwards from its own page like any other machine.
  • The count. It is free: it divides the machine. 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.
  • Bands. Sold in bands: 2, 4, 6, 8, 10, 15, 20, 25. Seven environments are bought as eight, and the spare one is yours to start whenever. On a shared plan the ceiling is twenty-five: one non-production environment for each site the plan can carry.
  • Location. The machine is built in production's own datacentre where a suitable one is sold there, otherwise in the nearest that has one. The configurator says which before you buy.

Change the machine and the count later under Commercial terms on the project's configuration page. Adding an environment past the count opens that dialog; it does not fail.

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. The amount depends on the machine and where it runs: the configurator shows the figure beside each machine and the total under Edge.

The figure shown is yours to spend. Like cores, memory and disk, it is quoted after the platform's own share: backups, shipped logs, container images pulled on every deploy, and the agent talking to the control plane. None of these appear in any log you can see, and some room is kept back as well. The figure is therefore smaller than the one the underlying provider advertises, and it is the only one we quote.

Extra bandwidth is bought by the terabyte a month, from €5 a terabyte. The price follows what the machine's provider charges for traffic in that datacentre and is shown beside the counter, when the project is set up or later under Commercial terms.

A bare-metal server is different: its traffic is not metered. It is listed as unmetered with the speed of its port, and the port is the only limit. There is no bandwidth to buy by the terabyte for it; where a faster port is sold for the server, you buy that instead. See bare metal.

Requests are not limited. Nothing is capped or charged per request, at the origin or at the edge.

CDN

Your site served 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. More are bought in three bands (up to ten, twenty-five and a hundred) under Commercial terms.

Included on every project

The Basic WAF and bot management at the edge and log forwarding to your own collector are add-ons every project has, at no cost. They appear on the invoice at nothing.

Restricted server access

An SSH allow list: only the addresses you list, such as your office or your developer's VPN, can get into the project's servers. The site stays open to visitors as usual. €9 a month per project while the list holds an address, prorated both ways. Add it when you configure the project, under Security, or later on its Configuration page. See Keeping the port to your addresses.

Single sign-on

Your identity provider in front of the team (Entra ID, Okta, Google Workspace, anything that speaks OpenID Connect or SAML): €49 a month per team, whatever it runs. It is a subscription of the team's own, not a line on a project, and the team's Owner takes it out on the team's settings page. See Single sign-on.

People

The first person on a project is included; past that, a project is in a band of up to three, ten or thirty people. 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.

Change Effect
Taking more Immediate and prorated: you are charged for the part of the period you use it.
Giving something back From your next invoice; not credited for the rest of the period you already bought.
Resizing a machine Credited both ways. A disk cannot be removed.
The billing period Not changed mid-term: it changes at renewal. The dialog shows it and refuses the change.

See Billing.

Choosing

Ask whether one machine is enough for production. If an hour of downtime during a kernel upgrade is an inconvenience, shared is enough. If it is an incident, you need dedicated.

You cannot move a project between shared and dedicated. Switching means creating the new project and migrating to it.

Next

  • Shapes: how many machines an environment runs on, the choice inside a dedicated plan.
  • Billing: the period, what a mid-term change costs, and what happens if an invoice goes unpaid.