Cloud Start
Small production sites
$17.95 /mo*
*Indicative example pricing
- 2 vCPU / 4 GB RAM
- 80 GB replicated NVMe
- Auto-failover
- Daily snapshots
Resources drawn from a cluster rather than a single machine: better uptime, easier scaling, and a billing model worth reading twice.
Advertising disclosure. This article contains affiliate links. If you sign up with a hosting provider through one of them, RecordHosting.com may receive a commission at no extra cost to you. We only recommend services we would use ourselves, and compensation never buys a better rating. See our full affiliate disclosure and the FTC's Endorsement Guides: What People Are Asking.
Cloud hosting runs your site across multiple connected servers rather than one machine. Storage, compute and networking are pooled, so a hardware failure moves your workload somewhere else instead of taking you offline, and a traffic spike draws on the cluster instead of exhausting a single box. You pay for that resilience, and you usually pay partly by usage.
| Behaviour | Single server (shared or VPS) | Cloud cluster |
|---|---|---|
| Hardware failure | Site is down until restored | Workload restarts on another node |
| Traffic spike | Hits a hard ceiling | Draws from the pool, or auto-scales |
| Upgrading | Often a migration | Usually a slider and a reboot |
| Storage | Local disk | Replicated network storage |
| Billing | Flat monthly | Flat base plus usage, or hourly |
| Failure domain | One machine | One availability zone, sometimes one region |
A small brochure site on a resilient cloud cluster is still a small brochure site. If your traffic is flat and your uptime requirement is “please do not be down for a whole day”, cloud hosting buys you very little that a good shared plan with tested backups does not. Resilience is worth paying for when downtime has a price tag; otherwise it is an expensive comfort blanket.
Two questions cut through most cloud marketing: what is the failure domain (a node, a zone, a region?) and what is replicated synchronously (compute, storage, database, or only the file system?). Redundancy that stops at the disk layer will not save you from a zone outage.
Cloud pricing usually separates compute from storage from egress. Compute is predictable. Storage grows quietly. Egress — data leaving the platform — is the line that surprises people, especially for media-heavy sites and for record archives being exported in bulk. Before you migrate an archive in, check what it costs to get the whole thing out again; that number is also your exit cost.
Small production sites
$17.95 /mo*
*Indicative example pricing
Busy sites and stores
$49.95 /mo*
*Indicative example pricing
Long-term record storage
$0.021 /GB/mo*
*Indicative example pricing
Sponsored links. Prices are illustrative placeholders — swap in your provider's live pricing and affiliate URLs before publishing.
Cloud object storage with versioning and object lock is the closest thing most organisations will get to affordable write-once, read-many storage. Combined with lifecycle rules, it lets you set a retention period an administrator cannot shorten, which is exactly what a retention schedule asks for. Confirm that the lock is enforced at the platform level, that the region is contractually fixed, and that the provider will sign a data processing agreement naming it.
Compare current offers from the providers we work with, or tell us what you are hosting and we will point you at the right size of plan.
View current offers Ask us a question
Sponsored link. Indicative example pricing. Replace with your provider's live rates.
Tell us what you need to store, how long you need to keep it, and which standards you answer to. We will point you at the plan that fits — and say so if you do not need to spend as much as you thought.