The database enforces tenant isolation.
Every business is its own tenant and every query is scoped to it, with PostgreSQL row-level security underneath. One forgotten filter in application code shouldn't be able to expose another business's data.
How Saroh is built, down to the code.
Most companies describe their engineering. Ours is public. This is the architecture of a multi-tenant product we run in production.
- Code
- Public
- Language
- TypeScript
- Tenancy
- Row-level
- Browser tests
- Playwright
The system.
Several Next.js apps, one API, one database. Each business connects its own payment and email accounts.
Next.js 16 and React 19 · Cloudflare Workers through OpenNext
Marketing sitesaroh.in
Workspaceapp.saroh.in
Business sitessaroh.app
Accountsaccounts.saroh.in
Help and docshelp · docs
One APINestJS · shipped as a Docker image
PostgreSQLPrisma 7 · row-level security
PaymentsThe business's Razorpay or Cashfree
EmailThe business's Resend, SendGrid or SMTP
Decisions we'd defend.
One API for every surface.
The web apps share one NestJS API, so the business rules live in one place. A future mobile app can use the same rules instead of a second copy of them.
Modules a business can switch off.
Each of the nine parts is a module. A bakery and a clinic share one product, and the workspace changes shape to match the business you are in.
The business keeps its own accounts.
Payments land in the business's own Razorpay or Cashfree account, and email goes out from its own address. Their money and their reputation stay theirs.
Don't take our word for it. Read the code.
Saroh is source-available. Have your own engineer review how we work before you ever call us.
saroh.in/ ├─ apps/ │ ├─ api.saroh.in │ ├─ app.saroh.in │ ├─ accounts.saroh.in │ ├─ saroh.app │ └─ saroh.in ├─ packages/ │ ├─ auth database emails │ ├─ integrations object-storage │ └─ site-blocks ui └─ e2e/
Need this kind of engineering?
We build custom websites, web apps and mobile apps. Tell us what you're working on.