Pricing
You pay for published interpretations. Nothing else.
Free
2 analysed studies
2 analysed studies at no cost, with no payment details and no expiry.
- No card details. Access is requested, not bought: the request asks for an email address and nothing that could be charged.
- No expiry. A free allowance that lapses is a coupon; this one is there when you come back.
- Your own workspace. You become its administrator when your request is approved, and nobody outside your organisation can see its records.
Access is granted by a person rather than by a form: a request is reviewed, and an approval sends a single-use link that creates your organisation.
Clinic
₹2,999.00 per period
200 analysed studies for 30 days. One payment, not a recurring mandate.
- 200 analysed studies, drawn from the moment the period opens.
- Valid for 30 days. The allowance does not roll over when the period ends.
- Every clinical act around an analysis stays free. Review, override, sign, export and transmit are never metered, even after the allowance is spent.
- Bought through the hospital administrator. One role holds the permission to spend the organisation’s money, and it is not a clinical role.
The figures above are this deployment’s configured list price, read from the same configuration the checkout uses — so the page cannot advertise a price the payment screen would not charge. Prices are held as whole minor units to avoid rounding, and the currency is INR.
The meter
What is counted, and what is never counted.
Counted
One unit per published interpretation
When the engine produces an interpretation and it is stored against the study, one unit is drawn. That is the only event that consumes allowance.
Re-analysis of a new recording is a new unit
A different recording is different work, and is counted as such.
Never counted
- A recording that fails quality validation. Nothing was interpreted and nothing was published, so charging for it would be charging for a refusal.
- Re-analysing a study that has already been counted — for example after an approved engine upgrade. The same recording is not charged twice.
- Viewing a waveform, at any point, by any role.
- Recording a clinical review, a disagreement or an override.
- Signing an interpretation.
- Generating, reading or exporting a report.
- Transmitting a signed study over FHIR or HL7.
- Acknowledging or closing an alert.
- Reading the audit trail, the analytics or the governance register.
- Everything an administrator does: users, roles, devices, thresholds, integrations.
Why the quality gate is free
A recording that fails quality validation is not counted, and that is a deliberate commercial decision as well as a clinical one. If refining lead placement cost money, the incentive would run the wrong way: a department would be discouraged from repeating a poor recording at the very moment repeating it is the correct clinical action. The meter therefore runs on published interpretations, and a refusal costs nothing.
Payment
A payment activates a period. A redirect never does.
The order is created server-side from the server’s own price list. A caller cannot choose what they pay: the amount is looked up from the same configuration shown above, and the stored order records the amount it was created with.
The payment is verified twice. The provider’s signature is checked, and the payment is then read back from the provider’s API. A signed callback that names a payment which does not exist, or which was not captured, opens nothing.
Closing the tab after paying does not lose the purchase. A signed webhook opens the period as well, so a customer who pays and then closes the window still gets what they bought on their next sign-in.
A purchase can also be granted by a person. An operator can open a period by hand for an account — a pilot, a replacement, a departmental arrangement — and doing so requires a written reason that is recorded. There is deliberately no way to reset or top up an account silently.
No card details reach this application. The checkout runs in the provider’s own interface; this system stores the provider’s identifiers for an order and never a card number.
Not included
What this build genuinely does not do.
Nothing renews automatically
A period is a single purchase for a fixed term. It does not repeat, it cannot take a second payment on its own, and it expires quietly — which is the safe direction for a hospital budget, but it does mean somebody has to buy the next period deliberately.
No email, SMS or pager is ever sent
There is no message transport in this build, so no receipt, no expiry reminder and no address verification is delivered. Alerts are raised and tracked inside the system, and they are escalating on a screen rather than to a device.
No invoices and no automated refunds
The payment provider issues its own receipt for the transaction. This application does not generate a tax invoice, and a refund is a manual action at the provider rather than something the software can perform.
Regulatory position
What this is not
This is a demonstration-grade clinical system. It is not a medical device, it holds no regulatory clearance anywhere, and it has not been validated against a clinical dataset.
It does not diagnose and it does not replace clinical assessment. Every interpretation is decision support for a qualified professional, who reviews, overrides and signs it — and the record shows which professional.
No sensitivity, specificity, agreement or accuracy figure appears on this site, because none has been established for this build. Any such figure would be invented. Read the full position.
See it on your own recordings.
Send a request, and a person reviews it. If it is approved you get a link that creates your own organisation, with the first 2 analysed studies included and no card details — and you are its administrator from the moment you set your password.