Anointed SaaS

What it is

Anointed SaaS is a public demo built to show how a multi-tenant SaaS product is put together, without a signup wall. Five seeded workspaces each hold their own customers, projects, members, billing, usage, API keys, webhooks, feature flags and audit history, and tenant isolation is enforced in the data layer rather than hidden in the UI. The product is explicit about its boundaries: authentication, payments and webhook transport are simulated and labelled as such on the site itself, and the database is IndexedDB running in the visitor's own browser rather than a server. Two integrations are genuinely live: an optional OpenAI copilot behind a server-only route with rate limits, and Resend for the lead capture emails. No payment SDK is installed and no card details are ever collected.

What is inside

• Multi-tenant data isolation enforced in the repository layer: every read and write requires a tenantId, and fetching another tenant's record by ID returns undefined instead of the row, the way a row-level security policy behaves
• Role-based access control with six system roles plus tenant-defined custom roles (a Growth and Scale plan entitlement), all routed through a single hasPermission check used by both the interface and the domain layer, with a user's role coming from their membership so the same person can be Admin in one workspace and Viewer in another
• Subscription lifecycle across four plans: entitlement gates, project and seat limits, downgrades blocked with the exact blockers listed, and a simulated proration invoice generated on upgrade
• Usage metering that sums real usage records over a rolling billing period, with API call usage firing in-app notifications plus a webhook event at 70, 90 and 100 percent of the plan limit
• Developer tooling with demo API keys generated via crypto.getRandomValues, stored only as a SHA-256 hash and shown once, an in-browser API explorer that rejects revoked keys and missing scopes, and webhook endpoints with simulated deliveries and retry timelines
• A separate Platform Admin back office across ten sections (overview, tenants, users, subscriptions, plans, usage, feature flags, support, audit, system) with MRR and ARR computed from the underlying subscription records rather than hardcoded
• Feature flag resolution combining per-tenant flags with platform rules that target all tenants, a plan, a single tenant or a percentage rollout, using a deterministic per-tenant hash so a tenant's bucket does not change between page loads
• An optional OpenAI copilot behind a server-only route with Zod-validated input, per-IP limits and a separate global hourly cap, plus Resend-backed lead capture protected by a honeypot field and its own rate limits

Built with