Skip to content

Pricing

No pricing table,
and here's why.

We could put three columns and some numbers here. You'd read them, we'd meet, and the real figure would depend on your departments, your volume, and what you're migrating off — the way it always does. So let's skip that step.

Clinic

Clinic rollout

One clinic, a handful of doctors, and the parts that eat the day: booking, Aira intake, live queues, the consultation, reports, payments, and the patient app.

  • Aira voice intake
  • Booking, scheduling, and live queue
  • Doctor consultation workspace
  • Patient mobile app
  • Razorpay payments
  • Guided setup, and a human to ask
Discuss a clinic

Hospital

Hospital deployment

Multiple departments reading one record: operations visibility, the investigation lifecycle, radiologist-owned reporting, payments, and facility-scoped access.

  • Everything in the clinic rollout
  • Multi-department configuration
  • Radiology review and release controls
  • Investigation lifecycle tracking
  • Facility-scoped roles and admin controls
  • Append-only clinical audit trail
Request a proposal

Group

Group or integration

Several sites, an existing HMIS that isn't going anywhere, a migration with real history in it, and a compliance team who will want to read the schema.

  • Everything in the hospital deployment
  • Multi-site rollout planning
  • External HMIS integration scoping
  • FHIR R4 export and data migration
  • Security and compliance review
  • SLA and support planning
Plan an integration

Questions

The ones you'd ask on the call.

Why isn't there a price on this page?

Because the honest number depends on things we don't know yet: how many departments are live, how many people touch it, whether radiology is in scope, what you're migrating off, and how much of the rollout you want us in the room for. A public tier would be a guess dressed up as a policy — you'd discover the real figure on a call anyway, having wasted a week.

Are you cheaper than what we run now?

Usually, and we'd rather you didn't buy on that. The system you're replacing has years of institutional muscle memory around it, and switching costs are real. If price is the only thing moving you, the migration will hurt more than the saving is worth.

Can we pilot one department first?

That's the way we'd prefer it. One clinic, one department, or one workflow, run properly for long enough to see where it rubs — then expand. A pilot that goes badly is information; a hospital-wide rollout that goes badly is your reputation.

What actually moves the number?

Active departments, user roles and headcount, patient app rollout, whether radiology is in scope, payment hooks, data migration volume, external integrations, training depth, and the support level you want. Those are the levers, and we'll show you which one your quote is sitting on.

How do we pay?

UPI, bank transfer, major cards, or wire, depending on the contract structure. Payments inside the product run through Razorpay.

Do you work with government or public hospitals?

Yes, scoped separately around procurement, compliance, and deployment constraints. Tell us the procurement route you're bound by early — it changes the shape of the whole engagement.

Next step

Tell us the shape of it and we'll price it.

Hospital type, departments, rough volume, what you're running today, and the workflow that hurts most. That's a proposal, not a discovery process.