Skip to main content


For questions about pricing or to schedule a demo please reach out to us at

Cloud HostedSelf Hosted
PricingFree$2,000/mo$6,000/moContact usFreeContact us
Standard BAA✔️✔️✔️✔️
Standard MSA✔️✔️✔️✔️
FHIR Resources Stored750050,000250,000Contact usContact us
Bot Invocations8None5,000/mo25,000/moContact usContact us
Emails SentNone500/mo2500/moContact usContact us
Open OnboardingTesting only✔️✔️✔️✔️
Custom DomainsNone15Contact usContact us
UMLS Terminology✔️✔️
Dedicated InfrastructureContact us
Websocket Subscriptions11✔️✔️✔️
Concurrent Connections2000Contact UsContact Us
HL7 Integration Engine✔️✔️
Discord (SLA)
GitHub (SLA)
Private Slack
Contact usDiscord
Contact us
Shared Roadmap✔️✔️
Google Auth✔️✔️✔️✔️DIYContact us
Required Auth Methods9✔️✔️✔️DIY✔️
External Identity Providers1312Contact UsDIYContact Us
WAF Blocking✔️✔️✔️✔️DIY✔️
IP Address Restrictions✔️✔️DIY✔️
SCIM Administration✔️DIY✔️
Access PoliciesTesting only310Contact usDIYContact us
Log Streaming✔️DIY✔️
CISO Dashboard✔️✔️
SOC 2✔️✔️✔️✔️Contact us
CLIA/CAPContact usContact us
ONC✔️Contact usContact us
Audit Support12✔️✔️
Sign UpStart NowStart NowContact UsContact Us


  1. Free: recommended for prototyping or learning.
  2. Production: recommended for production use, e.g. treatment of patients or conducting research.
  3. Premium: recommended messaging heavy and integration heavy use cases.
  4. Enterprise: recommended for institutions with complex workflow, integration or data requirements. Read more details on our Enterprise offering page.
  5. Community: refers to self-hosting the Medplum application.
  6. Enterprise Self-Hosted: recommended for those who must host the application on their own cloud infrastructure.
  7. FHIR Resources Stored: Data usage refers to the creation of FHIR Resources. This figure is cumulative. For Premium, Communication resources that are generated as part of messaging are not included in the resource cap shown.
  8. Bot Invocations: refers to custom logic written by customers to execute their workflow. Automation documentation and integration are a good place to learn more.
  9. Required authentication methods: Organizations can require that all logins at their domain go through their identity provider of choice.
  10. Compliance: Many complex compliance scenarios can be supported with this infrastructure. You can read more on the compliance page.
  11. Websocket Subscriptions: maximal number of concurrent websocket subscriptions available.
  12. Audit Support: receive support during common audits common in health system and payor partnerships.
  13. External Identity Providers: connect your Okta, Azure SSO, Auth0 or other oAuth based identity provider.