Simple by branch

Pricing follows your branch count.

Every plan carries the same clinical spine. What changes is how many branches you run, how they are rolled out, and how deep the reporting goes.

Choose your starting point

A plan for the way you work now.

Prices are in Indian rupees and exclude applicable taxes. We confirm the scope and migration work before anything is switched on.

Plan

Single clinic

One branch, finding a better daily rhythm.

₹2,499/ month

  • One branch, the full clinical module set
  • Queue, charting, treatment, and GST billing
  • Owner, dentist, assistant, and front desk roles
  • Email support and documentation

Book a walkthrough

Tell us about your clinic.

Share the basics. We will reply with a suitable time and the details worth preparing.

Most chosen

Growing chain

Two to five branches working as one practice.

₹5,999/ month

  • Everything in Single clinic, across up to five branches
  • One patient history across every branch
  • Branch-level permissions and full reporting
  • Guided migration and priority support

Book a walkthrough

Tell us about your clinic.

Share the basics. We will reply with a suitable time and the details worth preparing.

Plan

Network

A network with its own operating rhythm.

Let’s talk

  • Rollout planned branch by branch
  • Managed migration, onboarding, and training
  • Custom roles, reporting, and retention
  • A named contact and a shared roadmap

Book a walkthrough

Tell us about your clinic.

Share the basics. We will reply with a suitable time and the details worth preparing.

We scope network pricing around branch count, existing records, migration and reporting requirements.

At a glance

What actually changes as you grow.

The clinical tools are the same in every plan. Branch count, rollout and support change as you grow.

CapabilitySingle clinicGrowing chainNetwork
Patients, appointments, live queueIncludedIncludedIncluded
Charting, perio, imaging, treatment plansIncludedIncludedIncluded
Prescriptions, lab orders, recallsIncludedIncludedIncluded
Billing, GST, and the day bookIncludedIncludedIncluded
Inventory, equipment, claims, payoutsIncludedIncludedIncluded
Branches1Up to 5Custom
Cross-branch patient history—IncludedIncluded
Roles and permissionsCore fourPer branchCustom
Reports and analyticsStandardFullCustom
Data migrationSelf-serveGuidedManaged
OnboardingDocumentationLive sessionsPlanned on site
SupportEmailPriorityNamed contact

The table scrolls sideways on a narrow screen.

Good questions

The ones worth asking before you sign.

Ask us anything that is missing here. GST and migration details are best settled before rollout.

Why is it not priced per dentist?
The cost that actually follows a chain is the number of places a patient can be treated, not the number of people glancing at the board. Charging per clinician punishes exactly the cross-branch visibility that makes a chain worth running.
Where does our data live?
Wherever you put it. Nothing in the code knows where it runs — the database, cache, object storage, and search index are all reached through a URL you provide, including the Docker secret-file convention, so it fits your own infrastructure and your own secret store.
Is dental treatment exempt from GST?
The treatment is, as exempt healthcare. Goods and cosmetic work are not, which is why a clinic bills two kinds of thing. The two are kept distinct, and place of supply is compared as a state code rather than as a name somebody typed.
What happens to our existing records?
We scope the migration before rollout, because importing rows is the easy part. A chart, an open treatment plan, and an outstanding balance travelling together as one patient is the actual work, and it is what we plan around.
How is one chain kept out of another’s records?
In the database, with row-level security enabled and forced, and verified by a cross-tenant probe on every route that fails the build if one is added without it. The full account is on the features page — we would rather you read it than take our word for it.
Can a patient get their data out?
Yes, and it is a permission on the catalog rather than a support ticket. A DPDP export is a workflow the team can run, not an incident they have to escalate to us.
How do you test this?
Against real infrastructure. The suite exercises tenant isolation, search, the queue stream, and file storage against actual Postgres, a search index, and object storage in containers. There are no database mocks, so a green run means the database refused what it was supposed to refuse.
Can we start with one branch?
Yes. A single clinic can begin with the whole clinical module set and add branches when the operating model is ready — the price follows the branch count, so nothing has to be undone later.

Tell us where the handoffs slow down.

How many branches, what software you are moving off, and which part of the day costs you the most time.

Book a walkthrough

Tell us about your clinic.

Share the basics. We will reply with a suitable time and the details worth preparing.