SaaS · NestJS
Multi-tenant SaaS for Matrimony & E-commerce
A multi-tenant SaaS platform where per-tenant isolated databases are provisioned on approval, an entitlements layer controls feature access, and a Puck-based CMS lets each tenant customize their experience — without touching code.
The challenge
Multiple verticals on one platform, zero rebuilds
Starting with matrimony and expanding into e-commerce on the same platform. Each tenant gets their own isolated PostgreSQL schema, an entitlements layer that controls which modules are enabled, and a Puck CMS so they can manage content without engineering. New verticals are a config decision, not a rebuild.
What we delivered
- Per-tenant isolation with automated provisioning
- Entitlements + CMS without engineering involvement
- Matrimony and e-commerce on one codebase
- New tenants onboarded in minutes, not days
- Versioned REST API for custom frontends
- Zero-downtime feature toggles per tenant
Features
What we built
Six core capabilities that make the product what it is.
Per-tenant Database Isolation
Each tenant gets a dedicated PostgreSQL schema, provisioned automatically on approval. Data isolated at database level, not just application level.
Entitlements Layer
Feature flags and module entitlements per tenant, managed through an admin. Enable or disable features without a deployment — zero downtime.
Puck CMS Integration
A visual, block-based CMS that tenants use to manage content, layouts, and copy without engineering involvement — publish in minutes.
Tenant Onboarding Workflow
Automated approval, database provisioning, entitlement assignment, and welcome onboarding in a single workflow. New tenants live in minutes.
Multi-vertical Support
Matrimony and e-commerce share the same platform core. Vertical-specific modules enabled per tenant by entitlement — no separate deployments.
API-first Architecture
Every feature exposed via a versioned REST API, so tenants can build their own frontends or integrations on top of the platform.
Stack
Built with the right tools
No dogma about tools. We assessed what the product needed, then chose the stack that delivers fastest and stays maintainable long-term.
Ready when you are
Build something like this?
Tell us what you're working on. We'll map the right approach and stack for your context.