Get an overview of the 1upHealth single tenant / managed deployment infrastructure
1upHealth deploys it's entire networking, data, and application stack into a single tenant cloud vendor account or your cloud vendor's account as a managed deployment.

Type of Deployment

Prior to launching with 1up's platform, customers must pick which model to use.
Single vs managed tenant deployment models
Single Tenant A Single Tenant deployment means that 1upHealth's full FHIR Platform is deployed in its own physically isolated cloud account owned by 1upHealth. This environment is not shared at all with any other 1upHealth customers and can be branded to use the customer domains, logos, and messaging.
Managed Tenant A managed environment deployment is the full 1upHealth stack deployed in the customer's owned cloud account. This required additional coordination between 1up and the customer's IT team to ensure that VPC, CIDRs, and other core services do not overlap or conflict with pre-existing infrastructure.
Typically deployments are segmented into Baseline, Serverless, and Data Pipeline. This helps differentiate application/services and minimize software update time.


1upHealth deployments come with dev, stage, prod, & master accounts
Each deployment gets a dev, stage, prod, and master cloud account. The dev, stage, and prod accounts have the full 1up architecture deployed. The master account is only used for access controls, logging, and reporting. Usually, PHI is only contained on the prod accounts while dev and stage are used to ready data transformations for prod.