Medplum Self-Hosted
Open-source FHIR healthcare backend, clinical application and automation platform deployed in customer cloud infrastructure.
8 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
Medplum 5.2.17 authentication and delegation hardening
The v5.2.17 release strips ClientApplication secrets from auth/me responses and changes on-behalf-of identity and delegation handling.
Scope: The authentication/me and delegation paths named in the v5.2.17 release; no universal affected-version range or CVE is asserted.
Applicability depends on the installed server build and use of the affected authentication/delegation endpoints.
Action: Upgrade a compatible server/application bundle to v5.2.17 or later and test identity/delegation flows. Assess whether application secrets were exposed and rotate them where appropriate.
Primary source · Reviewed 2026-11-19
What lands where
Supplied by
Vendor or project
AWS CDK, or Terraform and Helm on Azure AKS or Google GKE
Runs in
Documented customer environment
Containerized API and web application with PostgreSQL, cache, object storage, secrets and load-balancing or CDN services
- AWS: Customer cloud account
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- AWS
- Azure
- Google Cloud
Hybrid
Operated by
Your team
Customer operates the cloud infrastructure and application lifecycle; Medplum offers an Enterprise Self-Hosted support plan.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Complete Medplum installation in a customer AWS account ↗ · Source checked 2026-11-19
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Production-validated Medplum deployment on Azure ↗ · Source checked 2026-11-19
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Production-validated Medplum deployment on Google Cloud ↗ · Source checked 2026-11-19
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | AWS CDK, or Terraform and Helm on Azure AKS or Google GKE |
|---|---|
| Infrastructure | Hybrid The deployment combines customer Kubernetes or container compute with managed database, cache, storage, secrets and network services. |
| Licensing model | Open Source / Open Core The Community software is Apache-2.0; Enterprise Self-Hosted support is a separate commercial service. |
| License | Apache-2.0 Community software; an optional commercial Enterprise Self-Hosted support plan is separate. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
12 of 12 fields researched (100%) · 4 documented · 8 unresolved. Evidence coverage is not a feature score.
- Marketplace delivery
Not confirmedEvidence and scope for Marketplace delivery
The reviewed deployment and licensing sources did not establish a public cloud-marketplace offer that unambiguously entitles the selected self-hosted edition. Obtain the exact offer ID, seller, delivery artifact and edition terms before treating marketplace procurement as available.
Medplum Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-19
Sources checked — unresolved · Editor reviewed.
- Cloud commitment eligibility
Not confirmedEvidence and scope for Cloud commitment eligibility
Customer-cloud deployment or marketplace delivery does not by itself establish cloud-spend commitment eligibility. Confirm the exact offer, billed dimensions, private-offer terms and buyer agreement.
Medplum Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-19
Sources checked — unresolved · Editor reviewed.
- Single sign-on
Not confirmedEvidence and scope for Single sign-on
The reviewed installation and edition sources did not establish the exact SSO protocols, identity-provider support and entitlement for this selected edition. Confirm authentication, role mapping and break-glass access before deployment.
Medplum Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-19
Sources checked — unresolved · Editor reviewed.
- SCIM provisioning
Not confirmedEvidence and scope for SCIM provisioning
The reviewed sources did not establish a SCIM endpoint or automated user and group lifecycle for this selected edition. SSO, directory authentication or just-in-time account creation would not by themselves establish SCIM.
Medplum Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-19
Sources checked — unresolved · Editor reviewed.
- Compliance attestations
Not confirmedEvidence and scope for Compliance attestations
The reviewed product and deployment sources did not establish an independent compliance attestation whose assessed scope covers this customer-operated edition and its local infrastructure. Obtain the current report and map customer responsibilities.
Medplum Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-19
Sources checked — unresolved · Editor reviewed.
- Security controls
Edition-dependentEvidence and scope for Security controls
The production guides deploy secrets, TLS termination, identity and private data services within the customer's cloud environment. Healthcare compliance still depends on the buyer's configuration, agreements, audit controls and operating procedures.
Medplum Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-19
Edition-dependent · Editor reviewed.
- Air-gapped operation
Not confirmedEvidence and scope for Air-gapped operation
The reviewed sources did not establish a fully disconnected installation, update and license workflow for this selected edition. Identify required registries, package repositories, telemetry, identity, activation and support endpoints before claiming air-gapped operation.
Medplum Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-19
Sources checked — unresolved · Editor reviewed.
- Deployment artifact / IaC
AvailableEvidence and scope for Deployment artifact / IaC
The tagged @medplum/cdk 5.2.17 source supplies the AWS CDK application used by the installation guide. The CLI, server image, frontend build and Azure/GCP Terraform/Helm packages remain separately selected artifacts; one CDK tag does not pin the whole stack.
Medplum Community AWS IaC source, independently versioned from other deployment components · Source ↗ · Deployment artifact ↗ (@medplum/cdk 5.2.17 at upstream tag v5.2.17) · Reviewed 2026-11-19
Documented · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
The reviewed sources describe the deployment components but do not provide one complete production sizing model for the buyer's users, data volume, traffic, retention and availability target. Size every application and managed-service dependency.
Medplum Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-19
Sources checked — unresolved · Editor reviewed.
- License pricing
AvailableEvidence and scope for License pricing
Medplum Community is Apache-2.0 and can be self-hosted without a software license fee; the Enterprise Self-Hosted support plan is separately commercial. Infrastructure, support and healthcare compliance work are separate.
Medplum Self-Hosted: selected customer-operated edition · Source ↗ · Commercial support plans ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
- Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate
No complete dated operating-cost estimate is established. Define provider and region, workload, availability, retention, storage growth, network transfer, support, software entitlement and operating labor before estimating total cost.
Medplum Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-19
Sources checked — unresolved · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
The reviewed upstream v5.2.17 release was published 2026-11-11. Provider images and installer/component packages can differ; this snapshot does not promise a support window or future cadence. It includes authentication-response secret removal and on-behalf-of delegation hardening.
Medplum Self-Hosted upstream application, independently versioned from provider packages · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Scope & considerations
The official AWS, Azure and GCP guides deploy both backend and frontend components. Enterprise support is optional and does not change the Apache-2.0 classification of the selected Community software; validate healthcare compliance scope and local operating controls separately. The v5.2.17 release strips ClientApplication secrets from auth/me responses and changes on-behalf-of identity and delegation handling. Upgrade a compatible server/application bundle to v5.2.17 or later and test identity/delegation flows. Assess whether application secrets were exposed and rotate them where appropriate.
Community & maintenance
The reviewed upstream contributor history includes codyebberson, mattwiller, ThatOneBro, with sustained contributions alongside the dated application release and public installation history. This establishes maintained community participation, not a commercial support, compliance or capacity guarantee.
Category fit
- Backend platforms
- Provides a FHIR datastore, APIs, OAuth identity, application SDKs and clinical backend services on customer infrastructure.
- Workflow automation
- Medplum Bots, cron jobs, subscriptions and triggers automate clinical and operational workflows.
Compare within Backend platforms
- Appwrite Self-HostedSelf-hosted backend services for authentication, databases, storage, functions and messaging.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Gravitee API Management Self-HostedOpen-source and commercial self-hosted API management platform with documented EKS, AKS and GKE deployment paths.
- AWS
- Azure
- Google Cloud
- HashiCorp Consul EnterpriseCommercial service networking, discovery and service-mesh platform deployed into customer cloud infrastructure.
- AWS
- Azure
- Google Cloud
- Hasura GraphQL Engine v2GraphQL API engine that exposes connected databases through permission-aware application APIs.
- Azure
- Google Cloud
- KeystoneJS (Keystone 6)Self-hosted content backend with a configurable GraphQL API and administration interface.
- Northflank
- Kong Gateway Self-ManagedOpen-source and commercial self-managed API gateway with supported AWS, Azure and Google Cloud deployment platforms.
- AWS
- Azure
- Google Cloud
- Parse ServerNode.js application backend for data APIs, users, permissions and server-side application logic.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Heroku
- Red Hat OpenShift Container PlatformCommercial self-managed Kubernetes application platform installed and operated in customer cloud accounts.
- AWS
- Azure
- Google Cloud
- Alibaba Cloud
- IBM Cloud
Showing 8 of 11 other listings in Backend platforms. These products address related workflows; read their category-fit notes before comparing scope. See all of Backend platforms →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Medplum production installation on AWS ↗www.medplum.com
- Medplum production installation on Azure ↗www.medplum.com
- Medplum production installation on Google Cloud ↗www.medplum.com
- Medplum open-source terms ↗www.medplum.com
- Medplum self-hosted support plans ↗www.medplum.com
- Reviewed deployment artifact reference ↗github.com
- Buyer evidence: release ↗github.com
- Upstream contributor history ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Complete Medplum installation in a customer AWS account ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Medplum describes a complete production-ready installation in the customer's AWS environment and deploys the application and supporting AWS resources with CDK.
- Production-validated Medplum deployment on Azure ↗ · Azure
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
The official Terraform and Helm workflow deploys Medplum into the customer's Azure subscription with AKS, PostgreSQL, Redis, storage, gateway and frontend resources.
- Production-validated Medplum deployment on Google Cloud ↗ · Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
The official Terraform and Helm workflow deploys Medplum into the customer's Google Cloud project with GKE, Cloud SQL, Redis, storage and frontend resources.
- Complete Medplum installation in a customer AWS account ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Upstream contributor history ↗github.com
- Reviewed upstream application release ↗github.com