Skip to Content

Platform overview

A control-plane approach to managed Odoo.

Elroi separates commercial packages, subscriptions, tenant inventory, release planning, support access, backups, and audit evidence so operations stay accountable.

Connected workflows

One operating spine for the work customers repeat every day.

Sales and CRM

Track leads, quotations, follow-up, and handoff into implementation.

Operations

Model branches, teams, workflows, and approvals before launch.

Inventory

Plan stock, branches, and reporting needs without overpromising unavailable modules.

Portals

Expose customer-facing access only where permissions and records are ready.

Integrations

Keep integration work typed, approved, and observable instead of ad hoc.

Finance roadmap

Finance flows are treated as configuration and validation work, not blanket compliance claims.

Managed operations

The service around the software is part of the product.

  • Onboarding cases and setup tasks keep launch responsibilities visible.
  • Tenant inventory records route, release, package, backup, and health state.
  • Desired-vs-actual drift is classified before risky changes continue.
  • Release channels and compatibility gates reduce surprise upgrades.

Security model

Tenant isolation and staff accountability stay separate from marketing copy.

Each tenant is designed for separate runtime, database role, filestore, secrets, backup scope, route, release assignment, and resource policy.

Staff permissions are role-based. High-risk approvals require a reason, reference, and a different approver. Audit events are append-only and exportable to external evidence.

Next step

Turn a business requirement into a reviewed launch plan.