Skip to content
Youssef Alouani
← Osoul platform

Deep dive · Osoul · live

Osoul deep-dive: multi-tenant platform with owned provisioning

Custom onboarding and Osoul-owned tenant provisioning, with full isolation of data, identity and configuration between restaurant groups.

Part of the Osoul platform case study.

Problem

Osoul serves restaurant groups that compete with each other. Each group has its own venues, staff, menus, guests and revenue data, and none of it may ever be visible to another group, by a bug, a mis-scoped query or a misconfigured token. At the same time, onboarding a new group has to be fast and repeatable: a restaurant should not wait weeks to go live.

Constraints

  • Full isolation: data, identities, configuration and secrets are separated per tenant, not just filtered in the UI.
  • Custom onboarding: each group brings its own venues, floors, menus, POS/PMS and brand, so onboarding is guided rather than self-serve.
  • Owned provisioning: Osoul provisions tenants itself, through internal-only tooling, so every tenant is created the same way and can be audited.
  • One codebase: isolation must come from the platform, not from forking the product per client.

Architecture

Osoul tenant provisioning and isolationAn Osoul operator runs custom onboarding, which calls the provisioning service. Provisioning creates the tenant's identity realm, its isolated data, and its configuration. At runtime, every request carries a token scoped to one tenant, and the API resolves the tenant before touching data.OnboardingCustom onboardingvenues · floors · menus · POSProvisioning serviceowned by OsoulPer tenantIdentityKeycloak realm / orgDataisolated in PostgreSQLConfig & secretsintegrations · brandingRuntimeTenant-scoped tokenTenant resolutionbefore any queryPortal · Guest · Waiter apps

Each tenant gets its own database, Keycloak realm, storage bucket and caching layer.

Multi-tenant SaaS diagram: tenants A, B and C each with their own isolated data stores on a shared core application, middleware and hardware; users reach only their tenant, a user can belong to tenants B and C, tenant C has an admin, and the SaaS provider operates the core
The model: isolated tenant data on one shared platform. A user can belong to several tenants, each tenant has its own admins, and Osoul as the provider owns provisioning.
Osoul Portal dashboard for one venue: revenue, orders, average check, seat occupancy and guest visits, with the venue switcher blurred
Every Portal screen is scoped to one tenant and one venue. Personal data blurred.

Key decisions

  1. Provisioning is a product, not a script. Creating a tenant goes through one service that sets up identity, data and configuration together, so a tenant is never half-created.
  2. Isolation is enforced below the application code. The tenant is resolved from the request itself, from its origin and CSRF token, before any query runs, so a missing filter cannot leak another group’s data.
  3. Onboarding stays guided. Fine-dining groups need their floors, menus and integrations right on day one; a guided onboarding beats a sign-up form for that.

Results

Numbers to come.

Stack and links