Platform
Build the core once. Sell the modules independently.
Every hospital runs on the same secure, multi-tenant platform. What changes per hospital is which modules are turned on, how many branches exist, and how each one is configured.
Multi-tenant by design
Every hospital is a fully isolated tenant. Data never crosses the boundary, and isolation is enforced in the database, not the application.
Modular and independently sellable
Each module installs and bills on its own. Enable one module or the full set per hospital, all from the same deployed platform.
Multi-branch
Unlimited branches per tenant, each with its own doctors, inventory, and billing, rolled up to central corporate visibility.
Configurable without forks
Feature flags per tenant let a single-doctor clinic stay simple while a hospital chain runs the full configuration, from one codebase.
Entitlements, not forks.
A module is switched on for a hospital as an entitlement. Enforcement is automatic from the first request: the server checks that the tenant is entitled, then that the user is permitted, before any data is touched.
- Patient ManagementEnabled
- AppointmentsEnabled
- PharmacyEnabled
- LaboratoryEnabled
- Radiology & PACSOff
- Operation TheaterOff
Isolated per tenant
PostgreSQL row-level security keeps one hospital's data unreachable from another. Tested on every module, not assumed.
India-resident by design
Built to run on India-resident cloud infrastructure, with health data kept in-region.
Auditable by design
An append-only audit trail records every change and security event, and is kept for 180 days and queryable.
Encryption and least privilege
TLS 1.2 or later on every connection, stored credentials encrypted with AES-256, and a least-privilege architecture.
Included with every plan
The platform core, in every hospital.
These are never a line item. Whatever modules a hospital turns on, they sit on the same secure, multi-tenant foundation.
Tenant & branch isolation
Every hospital's data is isolated at the database layer with PostgreSQL row-level security. Unlimited branches per tenant.
Role-based access control
Fine-grained permissions per role, per-user overrides, and time-bound grants. Explicit deny always wins.
Module entitlements
Turn modules on per hospital as entitlements, not forks. Entitlement and user access are separate levers.
Immutable audit trail
Every change and security event is written to an append-only log that the application never deletes.
Notifications
One communication service for email, SMS and WhatsApp, with idempotency on every send. Patient SMS and WhatsApp go through your hospital’s own accounts and approved templates.
Financial infrastructure
Invoice, payment, tax, and receipt primitives live in one place; every billing module builds on them.
See it running with your own workflows.
Book a walkthrough and we will map your clinic or hospital onto the platform, module by module.