Ten websites on your own dedicated Odoo database — full data isolation from other tenants.
- 10 websites, 10 custom domains
- Dedicated Odoo DB on shared cluster — own filestore, own container
- 60 GB storage · ~600,000 page-views / month
- White-label login with custom logo
- Audit log for admin actions
- Nightly database dump at 02:30 and a separate off-site copy at 03:30 held with a different provider; write-ahead-log archiving on the primary gives local point-in-time recovery covering the period since 23 July 2026, 15:03. Until 24 July 2026 the dump covered the database only — attachments and uploaded documents were not included; the fix is deployed and the first backup containing documents is the run of the night of 24–25 July 2026
- Retention target 30 daily / 4 weekly / 6 monthly / 2 yearly locally, 14 daily / 8 weekly / 12 monthly / 2 yearly off-site — with the copies for 21, 22 and 23 July 2026 missing after a disk-full incident, so the daily target has a three-day gap. Backups travel over TLS and are not encrypted at rest
- Fleet restore drill on a weekly timer, Sundays 03:30 — client databases restored into throwaway copies, database records only, not one drill per customer; every result published pass or fail, with the dates and figures on the proof page. The first drill was started by hand on 24 July 2026 and passed. A separate full-stack drill, Sundays 05:00, restores the whole cluster and boots a tenant; its first scheduled run failed and its attempts are published too
- No uptime percentage published — we publish the restore drill instead
- E-mail support, one working day, from the engineer who built it — 4 engineering hours a month