Skip to main content
Deploy  ·  Your cloud or local eval

How Cloud Health Office runs.

You deploy in your own cloud. PHI never leaves your boundary. Evaluate and run locally for free; license a production deployment when you are ready.

Evaluate locally — free

Clone the repo and run it on local Docker Desktop Kubernetes. Read the source, walk the First Claim journey, and reproduce the Million Claim Challenge. No license required for evaluation.

Local quickstart →

Production — in your cloud

Deploy in your own Azure, AWS, or GCP subscription. Your team owns the environment and the data permanently; there is no black-box vendor access to member data. Private endpoints, network isolation, full audit evidence.

Trust & security →

Managed tenant — optional

Prefer us to operate it? A managed tenant is available. Either way you start at Layer 1 (CMS-0057-F compliance) beside your core and expand only when you choose.

See the layers →

License

Source-available under BSL 1.1. Evaluate and run locally for free. Production use requires a license. Deploy in your cloud or as a managed tenant.

The CMS-0057-F API implementations ship in the repo. Implementation, core mapping, prior-auth workflow, and Platform Engagement (claims / payments / core replacement) are paid.

Commercial licensing →

Stage

What “production” means today

Cloud Health Office is ready to deploy in your cloud as a compliance layer beside QNXT, Facets, or HealthEdge. The first production tenant is under discussion; the evidence and source are already public.

First production deployment terms

Terms for an early production tenant

A production Layer 1 deploy in your cloud is a low-friction entry. For an early production tenant, license terms can be waived — in exchange for engineering partnership and a reference.

Waived platform license

Platform license terms can be waived for the first production tenant. You still own your cloud environment and your data permanently.

Direct engineer access

Work side-by-side with the engineers building the platform while you deploy the CMS-0057-F surface and map it to your core.

Reference partnership

In return, we ask to reference the deployment. Implementation, core mapping, and Platform Engagement remain scoped, paid work.

Talk about a deployment → Get the evaluator pack →