Start with Cloudpepper Odoo Hosting

Getting started with Cloudpepper is fast. This guide walks through creating a server, deploying your first Odoo instance, connecting your modules, and the essentials around DNS and backups.

Create your first server

Cloudpepper gives you the freedom to host Odoo wherever you like. Use servers from AWS, Vultr, Hetzner, DigitalOcean, or on-premises — or pick a Cloudpepper-managed server straight from your dashboard for a fast start.

If you’re not sure how to size things, the Server Sizing Guide picks the right plan based on your expected number of users and modules. The deploy guides cover each provider in detail — self-host on your own infra is the most flexible starting point.

Create your first Odoo instance

Once your server is connected, create your first Odoo instance from the Cloudpepper dashboard. Each instance is fully isolated, so you can run one or many on the same server without them interfering with each other.

Pick the Odoo version, set a name, choose Community or Enterprise, and Cloudpepper handles the provisioning — Postgres tuning, Nginx config, workers, SSL — and gives you a free *.cloudpepper.site subdomain so it works immediately.

Migrating an existing instance

Already running Odoo somewhere else? You can migrate from Odoo.sh, Odoo Online, or an on-premises server. Migrations work by importing your database dump and filestore into a fresh Cloudpepper instance, then flipping DNS at your convenience — no surprise downtime.

Tip

Run a staging migration first. It’s a free dry-run — you import the dump, click around, and find the surprises before your users do.

Adding your custom modules

You can add custom modules in three ways:

• Upload a .zip — fastest for one-offs and experiments.
• Connect GitHub — sync repositories directly. Push to a branch, Cloudpepper rebuilds. Auto-deploy on push and auto-upgrade are toggles.
• Any Git provider — GitLab, Bitbucket, self-hosted Gitea, anything that speaks SSH.

DNS and your own domain

Point your domain at your Odoo instance so users access it under your brand. The short version:

1. Add an A record on your DNS provider pointing to the IP shown in your dashboard.
2. Add the domain in your Cloudpepper instance settings.
3. Cloudpepper auto-issues an A+ SSL certificate; renewal is automatic.

Until DNS is set up, your free *.cloudpepper.site subdomain works as the canonical URL — useful for trials, demos, or client previews.

Automated backups

Backups are configured per instance. Choose the frequency (hourly to monthly), set retention or keep backups forever, and pick the storage destination — Cloudpepper Managed Backup Storage (encrypted at rest, stored in OVH France) or your own S3 / SFTP target. Multiple parallel schedules are supported, e.g. hourly for the last 24 hours plus daily retained for 30 days plus monthly retained indefinitely.

Cloudpepper also makes recovery practical during outages. If a server has a major issue, you can restore a backup to a new server from the dashboard, so a recent successful backup can become a fast path back online instead of a manual rebuild.

See the SLA’s backup & disaster-recovery section for the RPO/RTO guarantees that go with each setup.

Next steps

Once your first instance is running and backups are scheduled, the next hour or so is best spent on:

• Creating a staging instance so you can test changes safely before promoting them.
• Locking down server access with an IP allowlist if your team works from known networks.
• Connecting your module Git repository for push-to-deploy.
• Browsing the rest of the documentation, or chatting with us if something looks off.