OEC.sh
SaaS Plan — $249/mo flat

Sell Odoo as your own SaaS product

A storefront and a client portal ready to install on your Odoo. Billing built in. Tenants live on your servers in about a minute and a half. One flat $249/mo — no per-user tax, no per-tenant markup. Your brand, your price, your customers.

Start with SaaS Plan →See all plans

Odoo Community · Your customers never see OEC.sh

Why Odoo.sh does not fit a SaaS reseller

Odoo.sh charges per user of every tenant, plus a required Enterprise licence on each. Your cost scales with your success in a way you cannot pass through cleanly, and every invoice you send has a per-seat line item under it.

100 tenants, 5 users each — a rough comparison

On Odoo.sh

  • · Enterprise licence, 100 × 5 × $24.90: $12,450/mo
  • · Workers, storage, staging: ~$3,000/mo
  • · And you still have to pass that per-seat cost through

~$15,450/mo hard floor

On OEC.sh SaaS

  • · OEC.sh platform: $249/mo flat
  • · Your servers, say four mid-range Hetzner boxes at ~30 tenants each: ~$180/mo
  • · No licence fee (Community Edition)

~$429/mo total

Illustrative. Your server sizing depends on workload. The point is the shape: a flat fee plus the cloud cost you already pay, versus a per-user tax you cannot escape.

What is in the box

Everything you would otherwise be building yourself.

A storefront your customers use

Plan catalog, sign-up, payment, verification. Styled with your brand. Refuses new customers before charging them when you are already at capacity.

A portal your customers live in

They see their instance, their invoices, their backups. They request a plan change. They are told plainly what happened, when it happened, and why.

Billing that does the work

Stripe is in the box. Subscriptions, plan changes, reminders, suspension for non-payment, reactivation when the invoice clears. Everything reversible until you say otherwise.

A tenant that just works

About 90 seconds from checkout to a live Odoo. Backups on a schedule you choose. A suspended tenant stops costing you compute. A restored one comes back with the same people signed in.

What your customer sees

Five moments. Everything between them runs itself.

  1. Step 1
    Sign up
    On your storefront, in your brand
  2. Step 2
    Pay
    Stripe (or your gateway)
  3. Step 3
    Provision
    ~90 seconds, automatic, on your server
  4. Step 4
    Live Odoo
    Ready to use — the moment it truly is
  5. Step 5
    Ongoing
    Portal, invoices, backups, quiet renewals
Your customer does thisRuns on its own

Yours to shape

The storefront, portal and control panel are Odoo modules on your own Odoo — the same tools your team already builds in. Add a field, change a flow, restyle a page, drop in your own emails. Your dev team can do it, or the OEC.sh team can do it for you by arrangement — either way, it stays your product, not ours.

What stays yours

The customer relationship. OEC.sh is not a reseller of your product. We do not talk to your customers.

  • ✓Your brand — your customers never see OEC.sh
  • ✓Your prices — set per plan, changed when you want
  • ✓Your servers — any cloud, any region
  • ✓Your payment account (Stripe now, other gateways on request)
  • ✓Your customer support — they talk to you
  • ✓Your data — full exports on demand
  • ✓Your commercial terms — trials, discounts, invoices
  • ✓Your storefront copy — you write it

How it goes

Step 1

You set up once

Attach your servers, publish your plans, style the storefront. A short day of work with an onboarding call.

Step 2

Customers show up

They sign up on the storefront, they pay, they land in their own Odoo about a minute and a half later. You do not touch it.

Step 3

You do not run infrastructure

Suspensions, restarts, backups, reminders — all handled. Your day-to-day is signing new customers and doing the work you were selling.

Versus the alternatives

 OEC.sh SaaSOdoo.shBuild it yourself
Per-user costNone — flat $249/moCharged on every user of every tenantNone
Storefront + portalIn the boxNot providedWeeks to write
Billing lifecycleIn the boxNot providedMonths to get right
Where tenants runYour serversOdoo's data centresYour servers
Community-only tenantsFineNot the modelFine
Time to first paying customerDaysDays — but per-user cost hits day oneWeeks to months

SaaS Plan

$249/mo

Flat. Not per-user, not per-tenant. Annual is $2390/yr (save $598).

Start with SaaS Plan →Compare all plans

SaaS reseller FAQ

A ready-to-use Odoo storefront and client portal, the control panel that runs the whole thing, and billing that already knows how to charge, remind, suspend and reactivate a customer. You install it on your Odoo, attach your servers, publish your plans. That is the day-to-day.
No. It ships. Your customers browse plans, sign up, pay, and land in their own Odoo — without you touching anything after publish. If you want it to look and behave a specific way, everything is Odoo modules on your own Odoo, so you extend and restyle it the way you would any other Odoo app. Your dev team, or the OEC.sh team by arrangement.
Stripe is in the box: subscriptions, plan changes, reminders, suspension for non-payment, and reactivation when the invoice clears. If you need a local payment gateway instead (Razorpay, Paystack, and so on) you can build the integration with your own team, or talk to the OEC.sh team about a bespoke integration.
On your own cloud servers. Any cloud, any region. You point us at the servers you already have or spin up — DigitalOcean, Hetzner, AWS, GCP, Azure, and the rest.
Around 90 seconds from checkout. Your storefront reports ready the moment the tenant actually is — nothing sits waiting on a minute-timer.
You do not have to think about it. The system reminds them, suspends when the grace period runs out (nothing gets deleted), and reactivates cleanly when the invoice clears. Three emails to your customer along the way — overdue, suspended, restored.
No. Your customers are yours. We do not see who they are, we do not bill them, we never write to them. The $249/mo is between you and OEC.sh, and that is the whole relationship.
Odoo Community. Enterprise-edition resale needs a separate Partner arrangement with Odoo S.A. that OEC.sh is not part of.
Odoo.sh charges per user, on every tenant, forever. That kills SaaS-reseller margins the moment you get any traction. Here you pay one flat fee and there is no per-user tax — your tenants run Community on your own servers.
Building it yourself means writing and then maintaining a storefront, a portal, a billing state machine, a suspension flow, backups, restores, and reliable email — and keeping it all working across Odoo version upgrades. Here that whole stack ships as one thing, and it is updated with the platform.