OB E-Solutions Backup operations

Plans

Pick the isolation you actually need.

These are operated workspaces, not a dump-hosting SKU. S3 (or compatible storage) stays on your account. We run discovery, health, roles, and recovery access. Request a plan — there is no self-serve checkout.

Workspace

One client estate, operated properly.

A single company, or a first tenant while the rest of the estate is still being mapped.

$180/ month

Billed monthly. Annual invoice saves two months.

  • 1 tenant workspace with its own S3 target and prefix
  • Up to 5 Odoo databases discovered and indexed
  • Nightly metadata sync plus one on-demand refresh per day
  • Health windows (healthy / warning / critical) on every database
  • Presigned downloads that expire (default 15 minutes)
  • 1 administrator and 2 viewers
  • Email alert when a database goes critical
  • 30-day retention review of object age

Boundaries

  • No extra tenants without upgrading
  • Deletion disabled unless we enable it in writing
  • Standard onboarding of one existing bucket layout
Request Workspace

Most teams

Operations

Several tenants, one control plane.

Partners and operators who run more than one Odoo client and need isolation, roles, and an audit trail.

$490/ month

Most teams start here. Annual invoice saves two months.

  • Up to 5 isolated tenant workspaces
  • Up to 40 Odoo databases across those tenants
  • Sync every 6 hours, plus unlimited on-demand refresh
  • Full roles: Super Admin, Backup Admin, Viewer, Auditor
  • Optional TOTP for operators
  • Audit log of logins, downloads, deletes, and sync jobs
  • Multiple buckets or prefixes (one per tenant)
  • Email notifications for critical health and failed syncs
  • 30 / 60 / 90 day retention analysis
  • Assisted mapping of mixed folder / filename dump layouts

Boundaries

  • IAM design review included for the five tenants
  • Deletes remain confirm-and-audit; we enable them per workspace
Request Operations

Estate

The whole Odoo park, with named operators.

Groups, holdings, and hosts with many companies, custom discovery, and a need for stricter isolation.

Custom

Scoped after we see tenant count, dump size, and regions.

  • Unlimited tenant workspaces and databases
  • Per-tenant IAM / prefix review (no cross-tenant listing)
  • Custom discovery patterns and filename regexes
  • API access for inventory and health
  • Configurable health thresholds per tenant if needed
  • Deletion workflow with permission split and audit
  • Named operator coverage during agreed hours
  • Quarterly access and role review
  • Priority handling of new company folders after sync
  • Onboarding of existing multi-bucket estates

Boundaries

  • AWS and object-storage spend stays on your account
  • Odoo dump generation remains on your servers; we operate the index and recovery path
Talk about Estate

Side by side

Capability Workspace Operations Estate
Tenant workspaces 1 Up to 5 Unlimited
Odoo databases 5 40 Unlimited
Metadata sync Nightly Every 6 hours Agreed cadence
On-demand refresh 1 / day Unlimited Unlimited
Roles Admin + viewers Full RBAC Full RBAC + review
TOTP — Included Included
Audit log Basic Full Full + quarterly review
Health alerts Email, critical Email, health + sync Agreed channels
Retention analysis 30 days 30 / 60 / 90 Custom
Presigned downloads Yes Yes Yes, policy per tenant
API — — Included
Named operator — Shared desk Named coverage

Not included in any plan

  • Generating the dump on the Odoo server (filestore, pg_dump, or your existing job).
  • AWS account fees, bucket storage, and retrieval charges.
  • Restoring a dump onto a running Odoo instance (we hand over the object; you restore).
  • Public console access — live estates stay behind authentication we issue after onboarding.

Questions

What is a tenant?

A tenant is one client estate: its own S3 target, databases, people, and audit. Operators work in one workspace at a time. There is no shared dump pile across clients.

Do you store the backup files?

No. Amazon S3 (or compatible storage) stays the source of truth. We index metadata, health, and who may download. Bytes do not copy into our application database.

Is AWS usage in the plan price?

No. Storage, PUT/GET, and data transfer stay on the AWS (or MinIO) account that holds the dumps. The plan is the control plane: discovery, isolation, health, roles, and recovery access.

Who creates the Odoo dumps?

Your Odoo hosts (or existing backup jobs) still write dumps to S3. We connect that layout, keep the inventory current, and make last night’s file findable and downloadable by the right role.

Can we start on Workspace and move up?

Yes. We keep the same tenant and remap limits. You do not re-upload dumps; the bucket does not move unless you choose a new isolation design.

How do we pay?

Monthly invoice, or annual (two months included on Workspace and Operations). Estate is quoted after we see tenant count, regions, and dump size. Plans are requested on the contact form — they are not self-serve checkout.

Not sure which plan?

Send tenant count, Odoo versions, regions, and whether dumps already land in S3. We will map you to Workspace, Operations, or Estate.

Request a plan