Cardinal | The Secure Backend For Health-Tech.

Pay based on your actual usage

Whether you're building for a single practitioner or managing a network of hospital beds, our flexible pricing adapts to your business model.

Configure your pricing plan

What is your project stage?

Testing / POC

Production application

Large-scale deployment

What level of support do you need?

Community

Ticketing

Direct contact

Custom offer

How do you want to pay?

Per Patient

Per Device or Institution Bed

Per Healthcare Professional (HCP)

You pay based on how many patients use your product.

⭐Recommended for you

Best for PoC/MVP

Free

For building Proofs of Concept and MVPs, ready for deployment with real patients, HCPs, hospitals, and healthcare institutions.

€0,00

per patient / month · excl. taxes€0,00 / year

Max 10 patients

50 MB combined storage per patient

2 tenants

Best for production

Flexible

For production applications that need usage-based pricing without a minimum commitment.

€0,13

per patient / month · excl. taxes€1,56 / year

No minimum engagement

2 MB structured storage per patient

50 MB file storage per patient

Unlimited tenants

Swiss hosting option

Best for Large Deployment

Enterprise

For large-scale healthcare deployments with volume pricing, dedicated support, and custom terms.

€0,08

per patient / month · excl. taxes€0,96 / year

Min 30 000 patients

2 MB structured storage per patient

50 MB file storage per patient

Unlimited tenants

Swiss hosting option

Custom contract

⚡ Being invoiced in Swiss Francs gives you the choice to be hosted in Switzerland.

⚠️ Pricing models are not combined — you only pay according to the selected billing model. Choosing "Per HCP" means you do not also pay per patient or per device.

Per PatientYou pay based on how many patients use your product. Each active patient counts as one billing unit — regardless of how often they interact with the app.Patient-facing applications where value scales with the number of people receiving care.Patient portal, Remote monitoring app, Digital therapeutics, Care pathway app

Per HCPYou pay based on how many healthcare professionals use your product. HCP stands for Healthcare Professional. Billing is based on the number of licensed care providers with access — not on the number of patients they manage.Professional tools where value scales with the number of clinicians or care team members.EHR system, Clinical dashboard, Care coordination tool, Professional workflow app

Per Device / BedYou pay based on how many connected devices or institution beds your product manages. Billing is tied to the number of active devices or beds in scope, independent of how many patients or professionals interact with them.Device or infrastructure products where value scales with physical deployment size.Connected device platform, Hospital deployment, Bed-based monitoring, Medical equipment integration

CommunityGitHub ticketsBest effort

TicketingCommunity + Jira ticketing2 working days

Direct contactTicketing + direct contact1 working day

Custom supportCustom support package — contact@icure.comPersonalised offer

No. Pricing models are not additive. You choose the model that best matches your product, and pricing is based only on that selected model.

Choose the unit that best represents how your product is used or monetized. Patient-facing apps usually use the patient model. Medical device or hospital infrastructure products usually use the device or bed model. Professional tools usually use the HCP model.

Yes. The Free tier is designed for testing, prototypes, and proof-of-concepts.

Enterprise is best for large-scale deployments, custom contracts, advanced support needs, or specific hosting and compliance requirements.

A tenant is an isolated workspace or deployment unit within your Cardinal environment. It can represent a customer, organization, institution, or separated application context, depending on your setup.

Community is usually enough for testing and proof-of-concepts. Ticketing is recommended for production teams that need structured support. Direct contact is better for production teams that need faster responses. Custom support is for organizations that need a personalised SLA.