Deployment scope
Pilot, single-site, multi-site, or system-wide. Pilot deployments typically run at a reduced rate; system-wide deployments invoke volume considerations.
PricingInstitutional
Institutional pricing, scoped to your deployment.
ChironAI is sold to institutions, not seat-by-seat to individuals. Pricing reflects the deployment scope and the institutional commitments that come with it — BAA, integration, residency, regulatory framework. The factors that shape a quote are transparent. The number is not on this page; it is on the Statement of Work signed after the conversation with your team.
Nine pricing factors
What shapes a quote.
Clinician headcount
Number of licensed clinicians using ChironAI. Pricing scales with usage; quoted on a per-clinician basis for most institutional deployments.
Edition mix
ChironAI CDS, ChironAI OM, or both. Bundled-edition deployments are quoted with bundle consideration.
Specialty depth
Core clinical reasoning is included in the base. Specialty-depth LoRA adapters (radiology, OM regulatory, future specialty packs) are quoted incrementally where the workload warrants them.
EHR integration depth
Read-only document export, structured-data sync, bidirectional HL7/FHIR integration, single-sign-on via Microsoft Entra ID. Pricing reflects the integration surface contracted.
Regulated workflow scope
For ChironAI OM: California-only, multi-state, or national framework. Adapter packs and regulatory-reasoning calibration are scoped per jurisdiction.
BAA terms and data residency
Standard BAA template covers most US institutional customers. Customer-managed key (BYOK) deployments, per-tenant compute isolation, and non-standard data-residency commitments are scoped separately.
Deployment region
US-primary deployments are the default. EU, UK, APAC, and other regional deployments are scoped per jurisdiction and per Azure region selection.
Implementation support
Onboarding, workflow integration, AI literacy training, ongoing operational partnership. Implementation packages are scoped per institutional Statement of Work.
How conversations go
From first contact to signed Statement of Work.
- 01.
Discovery call
Forty-five minutes with our clinical and engineering team. We confirm the use-case fit, walk through the architecture, and answer procurement questions.
- 02.
Procurement diligence
Trust Center documentation walk-through, security questionnaire response, counsel coordination, BAA review. Typically two to four weeks depending on the institutional process.
- 03.
Scoped pilot
A focused initial deployment to validate fit, latency, and clinical workflow alignment in your environment. Pilot pricing is below the production rate by arrangement.
- 04.
Production Statement of Work
Multi-year institutional commitment with the BAA, the data-residency commitments, and the per-clinician pricing scoped to your deployment. The quote is on the SOW.
A note to the reader