Admin: OHC identity seed

2026-07-04T23:07:40Z

OHC identity seed

New page

{{Doc header
|type=guide
|domain=deployment
|title=Deploying Care
|order=1
}}

Care is self-hostable. You can run your own instance end to end, from the database and object store to the backend workers and the web frontend.

This section is written for '''operators and SREs''' standing up and running their own Care instance — people comfortable on the command line and with a cloud console. It is not an end-user or clinician guide.

== Two ways to deploy ==

There are two complementary paths through this section. Pick the one that matches how you want to run Care.

{| class="wikitable"
|-
! Path
! Best when
! What you get
|-
| **[[Index
| Cloud provider guides]]**
| You are deploying onto one cloud and want a concrete, click-through recipe using that provider's managed services.
|-
| **[[Deployment/Kubernetes/Reference architecture
| Kubernetes reference deployment]]**
| You want a provider-agnostic, self-managed production setup, or you run your own hardware.
|}

The two are not mutually exclusive — the provider guides show how Care maps onto a single cloud's managed services, while the Kubernetes reference is the portable, fuller-featured production setup that OHC runs itself.

== What gets deployed ==

However you deploy it, a Care instance brings up the Care '''backend''' (web workers, Celery workers, and a scheduler), the Care '''frontend''' served as static assets, and the infrastructure they depend on: '''PostgreSQL''', '''Redis''', an '''S3-compatible object store''', and — for a full production setup — '''OpenSearch/Elasticsearch''', ingress with TLS termination, an image registry, and monitoring. The platform components '''Odoo''' and '''Metabase''' are commonly deployed alongside Care.

The cloud guides provision these from each provider's managed services; the Kubernetes reference runs them in-cluster from Helm charts.

== What this section covers ==

=== Cloud provider guides ===

* '''[[Index|Overview & infrastructure requirements]]''' — the components a production deployment needs, and how to choose a provider.
* '''[[Index|AWS]]''' — deploy on ECS Fargate with a GitHub Actions pipeline.
* '''[[Index|Google Cloud]]''' — deploy on GKE with Cloud Build, or host the frontend as a static site on GCS with Cloud CDN.
* '''[[Deployment/Providers/Deploying Care on DigitalOcean|DigitalOcean]]''' — deploy on the App Platform with managed Postgres and Spaces.

=== Kubernetes reference deployment ===

* '''[[Deployment/Kubernetes/Requirements|Requirements]]''' — workload components, storage and backup expectations, and the tooling you need on your workstation.
* '''[[Deployment/Kubernetes/Reference architecture|Reference architecture]]''' — the shape of the reference cluster: nodes, networking, ingress, storage, and supporting services.
* '''[[Deployment/Kubernetes/Provisioning the cluster|Provisioning the cluster]]''' — bringing up the Kubernetes cluster with kubeadm, the CNI, and storage.
* '''[[Deployment/Kubernetes/Deploying Care onto the cluster|Deploying Care]]''' — applying the application modules with the <code>deployer.py</code> workflow.
* '''[[Deployment/Kubernetes/Day-2 operations|Day-2 operations]]''' — backups, restores, monitoring, and routine maintenance.

=== Security & privacy ===

Applies to every deployment, however you host it:

* '''[[Deployment/Security/Data security|Data security]]''' — the standard security practices to enable at the edge, network, transport, data, and operational layers.
* '''[[Deployment/Security/Privacy and data protection|Privacy & data protection]]''' — handling patient data responsibly and meeting your regulatory obligations.

{{Tip|title=Looking to contribute instead?|1=If you want to run Care locally to develop against it rather than operate a production instance, see the [[Contributing|Contributor's Guide]].}}

{{Related}}

Deployment - Revision history

Admin: OHC identity seed