Plans and Extras

What you choose in the Infrastructure, Machine and Extras steps of the wizard, and what each choice actually changes.

note

Current prices are shown live in the wizard and on the pricing page — the price bar updates as you choose. They are deliberately not repeated here, because a number copied into documentation goes stale the first time it changes.

Infrastructure

Option	What it means
Premium Hosting	Zebroo's own hardware — faster machines, redundant cooling and power, managed by us. Costs more than the cloud tier for the same size
3rd Party Hosting	A cloud machine, provisioned on demand
Your own machine	You supply the server; zCloud installs and manages Odoo on it

Your own machine is the option to take when the hardware has to live somewhere specific — a customer's data centre, or a machine you are already paying for. You keep the box; you still get the provisioning, hardening and the project screen. If we may not sign in as root, the hardening stays with you (see Getting started).

Machine sizes

Five sizes, S through XXL, each roughly doubling the resources of the one below. The wizard shows cores, memory and disk for each.

The underlying server type is not something you choose or need to know — pick the size that fits the workload and zCloud maps it to hardware.

Sizing guidance, roughly:

• S — a single small company, light use, or a test system.
• M — the common starting point for a production Odoo with real users.
• L and above — many concurrent users, heavy reporting, or workloads doing significant background processing.

Moving up a size later is easier than recovering from a machine that has been undersized for months, but starting at XXL "to be safe" is money spent on headroom you may never use.

Odoo version and edition

• Versions 17, 18 and 19.
• Community or Enterprise.

Enterprise requires read access to Odoo's private enterprise repository. Your own GitHub token cannot read it, so zCloud uses a separate source token. If that token is missing, the interface tells you directly instead of showing an empty version list.

Source code

Option	Use when
New repository from template	Starting fresh — zCloud creates the repository for you
Existing repository	You already have addons in GitHub
None	Plain Odoo, no custom addons

A linked repository is cloned onto the machine during provisioning, and its addons/ directory is mounted into the Odoo container.

Extras

Some are selected by default as a recommendation — you can switch those off. Others are fixed parts of running a project and are folded into the base price rather than listed as optional, because something you cannot remove does not belong under "optional".

Available extras cover:

Extra	What it adds
Standard encrypted backup	Regular encrypted backups
Point-in-time recovery	Restore to a moment, not just to the last backup
Second location	Copies kept in a separate location
VPN connectivity	Reach the instance over a VPN
Staging instance	A second instance for testing changes. Included on larger sizes
Dedicated CPU	Cores that are not shared with other tenants
OCA connectors pre-installed	Common OCA modules already in the tree
zSYNC pre-installed	zSYNC installed and ready

Which are worth it

Point-in-time recovery is the one people underestimate. Standard backups get you back to last night; PITR gets you back to just before someone ran the import that broke everything. If the data is the business, take it.

Staging pays for itself the first time it catches a bad migration. If you deploy custom addons regularly, treat it as necessary rather than optional.

Dedicated CPU matters when performance has to be predictable — heavy reporting, or anything where a slow hour is a problem. For ordinary use, shared cores are fine.

Always included

Applied to every project, whatever you choose:

• Fail2Ban, installed and configured
• SSH password login disabled
• A firewall restricted to the needed ports
• Unattended security upgrades
• Automatic TLS certificates

See Architecture for how these are applied.