Enterprise SaaS · 2024
Operon Cloud
Launched a multi-tenant admin dashboard with secure authentication, reporting, and API integration infrastructure.
Context
Operon Cloud productized internal admin tooling into a multi-tenant SaaS offering for enterprise customers with strict isolation expectations. Early tenants were already live; any tenancy redesign had to migrate data without maintenance windows that violated customer contracts. Corexel embedded with platform engineering to define tenant boundaries, auth flows, and reporting SLAs before feature velocity resumed.
Challenge
Row-level isolation had to hold under analyst-written queries, integration webhooks, and background jobs—not just HTTP requests. Auth0 flows needed step-up patterns for privileged actions without fragmenting the admin UX. Reporting pipelines had to stay fresh for 28+ tenants while API integrations multiplied. SOC-aligned reviews could not be a terminal phase; they were gates in CI.
Architecture
PostgreSQL row-level security policies enforce tenant_id on every path, backed by middleware that rejects ambiguous context. Auth middleware maps roles to policy bundles; Stripe billing hooks stay outside the tenancy critical path. A reporting warehouse decouples heavy aggregates from OLTP, with integration gateway rate limits and signed webhook verification. Next.js admin modules share a design system tuned for dense operational tables, not marketing chrome.
Delivery
Foundation sprint shipped tenancy, auth, and migration tooling; feature modules followed in two-week increments with tenant canaries. Security reviews ran per module. Zero critical auth incidents through launch window; report automation reached 100% for contracted tenants. Handoff included runbooks for tenant onboarding, key rotation, and incident escalation—Operon engineering leads retained pager ownership.
Engage
Share architecture constraints and success criteria. We respond with scope, risks, and an honest path forward.
