WORKBUSINESS SYSTEMSDEMO TENANT
Chhatrapati Online Service
A service business running its website, service catalogue, bookings and operations as a tenant on SevaDesk.
Chhatrapati Online Service — Tenant running its public site and operations on SevaDesk
- Next.js 14
- React 18
- TypeScript
- Prisma 5
- PostgreSQL
- Zod
- Tailwind CSS
- GSAP
System sketch — drawn from this build's own structure, not a screenshot.
About this build
Chhatrapati Online Service runs as a tenant on SevaDesk. The public site, the service catalogue, customer bookings, announcements and the back office are one deployment — which is the point: nothing about adding a second business is a new codebase.
It is a seeded tenant, not a live business. The platform's own content audit records its catalogue as placeholder — three seeded services, no logo, a `+91 90000 00000` phone, `(placeholder)` inside its descriptions — and its SEO fields are English while the page chrome is Marathi. So what this demonstrates is the tenancy model and the CMS surface a second business inherits, not a customer's finished website.
WHAT THIS IS FOR
- Shows a second business living on the same platform — public site, service catalogue, customer bookings, announcements and back office in one deployment.
- Demonstrates the tenancy model and the CMS surface any new business inherits when it is onboarded.
WHAT YOU GET FROM IT
- Adding a business is a tenant and its configuration, not a new project.
- The tenant's public pages and service catalogue are edited from the owner's own console, with a draft and a published version.
- Every surface shown here is a platform module switched on for this tenant — nothing in it is a bespoke build.
How it is structured
- Tenant provisioning — identity, branding, catalogue, roles
- Public site rendered from tenant-owned content
- Bookings written to the tenant's own records
- Public sections are stored per tenant as visible/hidden blocks, with a draft and a published version
- Plans carry feature and limit data; entitlements decide which modules a tenant can switch on
- Owner surface guarded per request — the tenant and the membership are both re-checked server-side
What it does
- Public business website
- Service catalogue with requirements
- Customer booking flow
- Announcements
- CRM and operations via SevaDesk
STATUS
In preparation
Screenshots are withheld because the ones on file show the tenant's placeholder content — literal `(placeholder)` text in the service cards, default platform branding instead of the business's own, and another centre's signboard in the hero. Real captures go up once the tenant's catalogue, logo and copy are authored and it is provisioned somewhere public.
No public tenant page. Chhatrapati exists as a seeded tenant on the platform's local development database, where its site renders at a tenant path. The platform has no production deployment with a tenant provisioned on it, so there is currently nothing to link to — a live URL is added the moment one exists.
One message — what happens today, and what you want instead. A straight answer within a day, including when it does not need building.
← All work