
# Medplum Self-Hosted

Open-source FHIR healthcare backend, clinical application and automation platform deployed in customer cloud infrastructure.

Canonical page: https://launchinyourcloud.com/directory/medplum-self-hosted/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## Medplum Self-Hosted

Open-source FHIR healthcare backend, clinical application and automation platform deployed in customer cloud infrastructure.

- Listing: https://launchinyourcloud.com/directory/medplum-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: hybrid
- License: Apache-2.0 Community software; an optional commercial Enterprise Self-Hosted support plan is separate.
- Licensing model: open-source
- Installation: AWS CDK, or Terraform and Helm on Azure AKS or Google GKE
- Architecture: Containerized API and web application with PostgreSQL, cache, object storage, secrets and load-balancing or CDN services
- Operations: Customer operates the cloud infrastructure and application lifecycle; Medplum offers an Enterprise Self-Hosted support plan.
- Product website: https://www.medplum.com/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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.

The Community software is Apache-2.0; Enterprise Self-Hosted support is a separate commercial service.

The deployment combines customer Kubernetes or container compute with managed database, cache, storage, secrets and network services.


### 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.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.medplum.com/docs/self-hosting/install-on-azure (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.medplum.com/docs/self-hosting/install-on-gcp (checked 2026-11-19). 


### Cloud deployment evidence

- Complete Medplum installation in a customer AWS account (aws): https://www.medplum.com/docs/self-hosting/install-on-aws
  Medplum describes a complete production-ready installation in the customer's AWS environment and deploys the application and supporting AWS resources with CDK.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Production-validated Medplum deployment on Azure (azure): https://www.medplum.com/docs/self-hosting/install-on-azure
  The official Terraform and Helm workflow deploys Medplum into the customer's Azure subscription with AKS, PostgreSQL, Redis, storage, gateway and frontend resources.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Production-validated Medplum deployment on Google Cloud (gcp): https://www.medplum.com/docs/self-hosting/install-on-gcp
  The official Terraform and Helm workflow deploys Medplum into the customer's Google Cloud project with GKE, Cloud SQL, Redis, storage and frontend resources.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and 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.

Reviewed 2026-11-19.

- Upstream contributor history: https://github.com/medplum/medplum/graphs/contributors

- Reviewed upstream application release: https://github.com/medplum/medplum/releases/tag/v5.2.17

### Sources

- Medplum production installation on AWS: https://www.medplum.com/docs/self-hosting/install-on-aws

- Medplum production installation on Azure: https://www.medplum.com/docs/self-hosting/install-on-azure

- Medplum production installation on Google Cloud: https://www.medplum.com/docs/self-hosting/install-on-gcp

- Medplum open-source terms: https://www.medplum.com/open-source

- Medplum self-hosted support plans: https://www.medplum.com/pricing

- Reviewed deployment artifact reference: https://github.com/medplum/medplum/tree/v5.2.17/packages/cdk

- Buyer evidence: release: https://github.com/medplum/medplum/releases/tag/v5.2.17

- Upstream contributor history: https://github.com/medplum/medplum/graphs/contributors

### Licensing sources

- https://www.medplum.com/open-source

- https://www.medplum.com/pricing

### Infrastructure sources

- https://www.medplum.com/docs/self-hosting/install-on-aws

- https://www.medplum.com/docs/self-hosting/install-on-azure

- https://www.medplum.com/docs/self-hosting/install-on-gcp


### Buyer diligence


Research coverage: 12/12 fields (100%); 4 documented, 8 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Sources checked — unresolved. 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. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- Cloud commitment eligibility: Sources checked — unresolved. 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. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- Single sign-on: Sources checked — unresolved. 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. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- SCIM provisioning: Sources checked — unresolved. 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. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- Compliance attestations: Sources checked — unresolved. 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. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- Security controls: Edition-dependent. 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. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- Air-gapped operation: Sources checked — unresolved. 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. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- Deployment artifact / IaC: Documented. 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. Scope: Medplum Community AWS IaC source, independently versioned from other deployment components. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19). Deployment artifact: https://github.com/medplum/medplum/tree/v5.2.17/packages/cdk. Artifact reference: @medplum/cdk 5.2.17 at upstream tag v5.2.17.

- Minimum footprint / sizing: Sources checked — unresolved. 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. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- License pricing: Documented. 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. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/open-source (reviewed 2026-11-19). Supporting source: Commercial support plans — https://www.medplum.com/pricing.

- Operating cost estimate: Sources checked — unresolved. 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. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- Release snapshot / cadence: Documented. 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. Scope: Medplum Self-Hosted upstream application, independently versioned from provider packages. Source: https://github.com/medplum/medplum/releases/tag/v5.2.17 (reviewed 2026-11-19).




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Medplum 5.2.17 authentication and delegation hardening (security-advisory): 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. Conditions: 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. Source: https://github.com/medplum/medplum/releases/tag/v5.2.17; reviewed 2026-11-19.



