Deploy OpenMetadata in Production
Are you looking to do POC? It won't get easier than following our Quickstart guide!
OpenMetadata Deployment Architecture

OpenMetadata requires 4 components
- OpenMetadata Server, pick the latest release from our (GitHub releases)[https://github.com/open-metadata/OpenMetadata/releases]
- OpenMetadata Server stores the metadata in a relational database. We support MySQL or Postgres. Any Cloud provider such as AWS or GCP's provided MySQL/Postgres services will work as well
- MySQL Version 8.0.0 or Greater
- Postgres Version 12.0 or Greater
- Search Engine (ElasticSearch, OpenSearch)
- We support ElasticSearch 7.16 to 7.17
- OpenSearch 1.3
- Workflow Orchestration Tools OpenMetadata requires connectors to be scheduled to periodically fetch the metadata, or you can use the OpenMetadata APIs to push the metadata as well
- OpenMetadata Ingestion Framework is flexible to run on any orchestrator. However, we built an ability to deploy and manage connectors as pipelines from the UI. This requires the Airflow container we ship
- If your team prefers to run on any other orchestrator such as prefect, dagster or even GitHub workflows. Please refer to our recent webinar on How Ingestion Framework works
The Dependencies must be deployed before installing OpenMetadata Application. With Docker and Kubernetes deployment, we package these together as part of quickstart.
For production deployment, we recommend you to bring up MySQL/Postgres, Elastic/OpenSearch, Scheduler (like airflow) as an external service and do not rely on quickstart packages.
Deployment Options
We support following deployment options
Deploy on Docker
Deploy OpenMetadata with Docker
Deploy on Bare MetalDeploy OpenMetadata directly using the binaries.
Deploy on KubernetesDeploy and scale with Kubernetes
Security
Secure your OpenMetadata deployment
Upgrade
Learn how to move from version to version: