1Context
One supplier, hundreds of business customers
Orders, documents and account changes arrived by email. Each new client meant a custom setup in a legacy admin panel, and support couldn't see what the customer saw.
2Challenge
Every client was a snowflake
- Onboarding took weeks of manual configuration.
- No shared view between customer, sales and support.
- Data from different clients lived in one database with no isolation guarantees.
- Compliance asked for a full history of who changed what.
3What we build
A multi-tenant portal on one codebase
- Per-tenant branding, roles and SSO (SAML/OIDC) with row-level data isolation.
- Self-service onboarding: a new tenant is live in minutes, not weeks.
- Shared "customer view" for support, with impersonation under audit.
- Event-sourced audit trail and export for compliance.
- # stack · models · guardrails
- tenant_isolation: Postgres row-level security + tenant-scoped connection context
- identity: OIDC / SAML via Keycloak, role model per tenant
- audit_trail: event-sourced domain events, append-only, exportable
- onboarding: declarative tenant config, no per-client deploys
- support_view: audited impersonation with scoped read tokens
- caching: tenant-aware cache keys, per-tenant rate limits
4Outcome
Onboarding became a click, not a project
Setup time collapsed from weeks to minutes, support tickets about "what do you see" disappeared, and the same platform now serves new customer segments without code changes.
15min
to onboard a new tenant
1codebase
for every tenant
row-level isolation
0deploys
per new client
100%
of changes in the audit trail
who · what · when
−60%
onboarding cost per client
no engineering hours per setup
<9mo
payback on the platform
vs. legacy admin + manual ops