CloudPepper alternative
A panel manages your server, you run it. A platform rents you workers. An operator carries the outage.
An honest comparison, including the section on when CloudPepper is the better choice.
A feature list says little about what happens when things go wrong. Six cases. The CloudPepper column quotes the published documents verbatim, not our summary - including where CloudPepper comes out ahead of us.
| Case | CloudPepper | erpdock |
|---|---|---|
| The server dies | Replacement server and restore: "Provisioning a replacement server - typically completed within 20 minutes", then "Restoring the most recent successful backup from your designated storage destination". The target is "RTO target: under 1 hour" for small and medium instances. The data state is the last backup: "Your RPO is determined by the most recent successful backup" (CloudPepper SLA). | Your VM starts automatically on another node of the cluster. The data is unchanged. Read it in the SLA. |
| Ransomware runs inside your instance | Backups run on the schedule you configure. They are stored either in CloudPepper Managed Backup Storage - "backups stored in OVH data centers in France, geographically and operationally independent from your production server" - or on "any SFTP server or S3-compatible object storage you control". Whether they can actually be restored is your job to check: the customer responsibilities list "Periodically verifying that backups are restorable (we recommend quarterly)" (CloudPepper SLA). | Backups are taken below the VM, at hypervisor level, not from inside the instance, with database dumps on top. Malware running inside the VM cannot reach them. Operations sit with us, not with you. |
| Data is lost | "Subscriber is solely responsible for the preservation of Subscriber's data saved onto its virtual server" and "Cloudpepper shall have no liability for any lost Data". Liability is capped at what you paid in the preceding six months: "limited to the amount paid, if any, by you to Cloudpepper during the six (6) month period prior to any cause of action" (CloudPepper ToS). | For data loss we are liable to the extent the data can be restored from the last proper backup. The liability cap is the higher of your annual fee and the cover of our liability insurance, which we maintain at a minimum of EUR 1,000,000 per claim for the term of the contract (terms, section 10). |
| Your customer asks for a DPA and a subprocessor list | Annex A of the CloudPepper data processing agreement lists seven subprocessors: Amazon Web Services EMEA SARL, Google Cloud EMEA Limited, OVH SAS (OVHcloud), UpCloud Ltd, The Constant Company, LLC (Vultr), Cloudflare, Inc. and Crisp IM SAS. For Vultr and UpCloud the location reads "EEA (Customer-selected region; non-EEA available on request)", for Cloudflare "Global edge; primary processing EU/US". That choice of region is an advantage if you need to host outside the EU. | Exactly one subprocessor: Xenox IT & Kommunikations GmbH, processing location Vienna, Austria. We do not offer a choice of region (DPA). |
| The end customer calls | "Cloudpepper does not provide technical support to customers' customers" (CloudPepper ToS). Support itself runs on "Business hours are 09:00-18:00 Brussels time, Monday to Friday, excluding Belgian public holidays", with a "1 business hour" first response for P1, and "Support is provided in English, French, Dutch and Spanish" (CloudPepper SLA). Round-the-clock cover exists only as a separate enterprise arrangement. | German-speaking support, Monday to Friday 08:00 to 18:00 Vienna time, Austrian public holidays excepted. First response within 4 business hours (Starter, Standard) and 1 business hour for a total outage of the instance (Pro, Enterprise). The definitions are in the SLA. |
| You need proof of availability | 99.9 % for High Performance, 99.99 % for Dedicated Performance, "as measured by Cloudpepper monitoring from external probe locations". Service credits of 5 %, 10 % and 25 %, with "Total credits are capped at 100% of the monthly fee for the affected instance per calendar month". The commitment only covers CloudPepper servers: "Service credits apply only to instances deployed on Cloudpepper-provided infrastructure" (CloudPepper SLA). Those percentages are higher than ours. | 99.5 % for Starter and Standard, 99.9 % for Pro, measured per instance and per calendar month instead of averaged across the platform. Service credits of 10 %, 25 % and 50 % of the monthly fee of the affected instance. Nominally fewer nines: the difference sits in row 1 and row 3 of this table (SLA). |
CloudPepper sources: SLA (dated 26 April 2026 in the document), Terms of Service (6 October 2025), GDPR Data Processing Agreement (4 June 2026), Pricing and Partners. erpdock sources: SLA, terms, DPA, pricing. All retrieved on 14 September 2026.
Two numbers, each from the respective pricing page. What they include differs - so that is written next to them instead of a verdict.
The "Pro" plan at EUR 49/mo plus a Dedicated Performance server with 2 cores, 4 GB and 50 GB at EUR 30/mo. The pricing page shows this combination as "79/mo total with Pro".
Paid annually, net; paid monthly it is EUR 83/mo. The term is always 12 months. The price is per production instance - a second instance costs another plan.
If you run many small instances, a flat plan fee plus a server per instance adds up differently than one plan per instance.
Both models work. They simply distribute work and return differently, and here they sit side by side.
You buy the plan and set your own end-customer prices: "Set your own client pricing - keep the hosting margin". The partner page works that through for ten clients with "You keep 85.4%", on the cost basis "Pro 49 fixed fee + 12/client". CloudPepper does not describe a commission program of its own - the margin is the return.
In exchange, operations, backup strategy and the support of your end customers sit with you: "Cloudpepper does not provide technical support to customers' customers" (ToS), and verifying that backups are restorable is your job (SLA).
You earn 10 %, 15 % or 20 % commission on the hosting MRR of your customers, tiered by active instances, lifetime and uncapped. The customer stays yours, the hosting contract runs through us.
Operations, backups, monitoring and the response times from the SLA sit with us. The tiers and the worked example are on the partner page.
If you have the operating hours and want to spend them, you earn more at CloudPepper. If you do not have them, you pay for them at CloudPepper with your nights.
If none of that applies, and the sentence "when the server dies, your customer calls you" describes your risk: then we are the answer.
CloudPepper is primarily a management platform for Odoo instances and sells servers alongside it. Per Annex A of the CloudPepper data processing agreement, the hosting infrastructure comes from third parties: The Constant Company, LLC (Vultr) for the High Performance tier and UpCloud Ltd for Dedicated Performance, plus AWS and Google Cloud for the management platform, OVH for backup storage, Cloudflare and Crisp. Alternatively you bring your own cloud account. At erpdock the infrastructure runs through exactly one subprocessor, in Vienna.
At CloudPepper, "Dedicated Performance" is a separate server tier you add to your plan: the advertised configuration with 2 cores and 4 GB costs an extra EUR 30/mo, listed as "79/mo total with Pro". The CloudPepper SLA commits to 99.99 % on that tier and 99.9 % on the High Performance tier. At erpdock the dedicated VM is the default on every plan, from Starter up, at no surcharge.
Yes. We handle the move including a test migration on staging. If your instance is not running within 48 hours of starting, we keep working for free until it is.
Because we commit to the number we can hold per instance. CloudPepper states 99.9 % for High Performance and 99.99 % for Dedicated Performance; we state 99.5 % for Starter and Standard and 99.9 % for Pro. That is nominally less, and we write it down. The difference is not the percentage but what happens on a hardware failure - continuing on another node instead of a replacement server plus restore - and the liability for lost data.
Yes. Our SLA attaches to the production instance, not to the role of the contracting party: availability is measured per instance and per calendar month, and the service credit is calculated on the monthly fee of the affected instance. If you bring customers to us as a partner, every one of those instances carries the same commitment as a direct customer instance.
Related: the comparison with odoo.sh and the move with a 48-hour guarantee.