SaaS · Rwasem

SaaS & Multi-Tenant Platform

An Odoo-based SaaS platform where new customers sign up, choose a plan and get their own isolated, pre-configured ERP instance in minutes, with subscription billing, custom domains and automated backups.

Client
Rwasem
Category
SaaS
Platform
Odoo 17 multi-tenant on Docker
Duration
16 weeks
Team
6 specialists

<0 min

to provision a tenant

0.0%

platform uptime

0%

lower hosting cost per tenant

The challenge

Rwasem wanted to sell its industry-specific Odoo solution as a subscription service. Every new customer was being set up manually: new server, database, modules, configuration and DNS, which took days of engineering time per customer.

They needed self-service onboarding, reliable tenant isolation and billing that scaled with the business.

The system

Self-service signup triggers automatic provisioning: database, modules, domain and SSL.

admin.saas-manager / tenants

Tenants

214 active
TenantPlanUsersHealth
tenant-0211Business48Healthy
tenant-0212Starter9Healthy
tenant-0213Enterprise212Healthy
tenant-0207Business61High load
trial-1192Trial3Healthy
tenant-0198Starter12Healthy
provisioner · new tenant

Starter

$49

96 tenants

Business

$149

82 tenants

Enterprise

Custom

36 tenants

Illustrative view with representative data.

Problems & solutions

Problem 1

Tenant isolation and data security

Customers' data had to be strictly separated, while shared infrastructure kept costs down.

How we fixed it

Each tenant gets its own PostgreSQL database and filestore, routed by domain through a reverse proxy, with per-tenant credentials and resource limits.

Problem 2

Provisioning took days

Installing modules and configuring each instance was manual and error-prone.

How we fixed it

We built a provisioning orchestrator that clones a pre-configured template database, applies plan-specific modules and issues SSL for custom domains, usually in under 3 minutes.

Problem 3

Upgrades across hundreds of databases

Rolling out a new module version to every tenant risked downtime.

How we fixed it

A staged upgrade pipeline tests on canary tenants first, then upgrades the rest in batches with automatic rollback on failure.

What we delivered

  • Self-service signup with plan selection and trial
  • Automated tenant provisioning from template databases
  • Subscription billing, usage limits and dunning
  • Custom domains with automatic SSL
  • Nightly per-tenant backups and point-in-time restore
  • Central admin console for tenants, plans and health

How the system flows

  1. 1Customer signs up
  2. 2Plan selected
  3. 3Tenant provisioned
  4. 4Domain & SSL issued
  5. 5Subscription billed
  6. 6Monitored & backed up
Impact

Key operating metrics before the project and after go-live.

Time to onboard a customer

-100%
Before72 hrs
After0.1 hrs

Hosting cost per tenant

-60%
BeforeBaseline
After40 vs 100

Tenants per engineer

+12x
Before15
After200

Tell us about your challenge. A solutions architect will reply within one business day with ideas, not a sales pitch.