ABDM v3 · M1–M4 implemented
Sandbox keys, issued on signup

Pricing

Priced per hospital, not per patient

You pay for the hospitals you onboard. Not per patient, not per record, not per ABHA created. A group with eleven facilities pays eleven times the listed price, on one contract.

Start on the sandbox Talk to us

01 Plans

Per hospital, per month

Every account starts on the sandbox, which is for testing and costs nothing. You pay at the point you go live with real patients, for the number of hospitals you actually run — one clinic pays for one. Wondering how that compares with building it or buying a new HMIS? The comparison, with the market’s own figures. No developer on hand? We integrate it for you, quoted per scope on top of the subscription.

Sandbox — for testing, included with every account

Synthetic data against ABDM's sandbox gateway: two facilities, 50,000 API calls a month, and every milestone from M1 to M4. No card, no expiry. It is where you build and test, not where you treat patients — but it is the same API you will call in production, so nothing you build here has to be rewritten later.

Create an account
Most chosen

Growth

Go live with one clinic or hospital

₹2,999

per hospital, per month

or ₹29,990 a year — save ₹5,998

  • 50,000 API calls a month
  • 1200/min burst rate
  • 10 connected systems (HMIS, LIMS, apps)
  • 15 team members
  • 200 practitioners per hospital
  • Every ABDM milestone: M1 to M4
  • Email support, next business day
Choose Growth

Scale

Run a group, a network or a health-tech product

₹4,999

per hospital, per month

or ₹49,990 a year — save ₹9,998

Everything in Growth, plus:

  • 2,00,000 API calls a month
  • 6000/min burst rate
  • Unlimited connected systems
  • Unlimited team members
  • Unlimited practitioners
  • Priority support with a named contact
Choose Scale

Running one clinic or one small hospital? Growth is priced for exactly that — a single hospital, at the listed price. Prices are per hospital, per billing period, exclusive of GST. Payment is taken by Razorpay — card details never touch this site. Add or remove hospitals whenever you like; Razorpay prorates the difference. Running more than a few dozen facilities? Talk to us rather than buying seats one at a time.

02 Value

What you are actually paying for

One integration instead of one per hospital, and the parts of ABDM that are easy to get quietly wrong.

Secrets

The credentials stay here

Your production ABDM client_secret does not end up on a hundred hospital servers. One place to rotate it, one place to track ABDM's changes.

Consent

Enforced, not assumed

Every record release is checked against the artefact's hi-types, date range and expiry at transfer time. Treating a granted consent as a boolean is the failure this is built to prevent.

Crypto

Fidelius, implemented once

Curve25519 ECDH, HKDF-SHA256 and AES-256-GCM, transcribed from NHA's own reference rather than from a blog post — several of which are wrong about the gateway base URL alone.

FHIR

Validated on the way in

Bundles are checked against NRCeS profiles when you send them. A bundle rejected here is one you can fix; one rejected at transfer time is a gap in a citizen's record nobody notices for weeks.

FAQ Common questions

Frequently asked questions

How much does ABDM integration cost?
From Rs 2,999 per hospital per month. You pay for the hospitals you onboard, not for patients, records or API calls beyond the plan's quota. A hospital group with eleven facilities pays eleven times the listed price on one contract.
Is there a free plan?
Yes. Sandbox access is free and needs no card: sign up, verify your email and you are building against ABDM's sandbox the same day, with two facilities and 50,000 API calls a month. You only pay when you go to production.
What counts as a hospital?
One facility registered in ABDM's Health Facility Registry, with its own HIP or HIU identity. A single hospital with several departments is one facility; two buildings with two HFR registrations are two.
Can I change how many hospitals I pay for?
Yes, at any time. Adding a hospital takes effect immediately and Razorpay prorates the difference. Reducing below the number you already run is refused -- remove the facility first.
Do I need my own ABDM credentials?
No. The connector holds the ABDM client credentials and speaks ABDM v3 on your behalf. You authenticate to us; your facilities keep their own HFR identities.

Start on the sandbox

No card. Two hospitals, every milestone, and the same API you will use in production — nothing you build in sandbox has to change.

Create an account Read the API