Products
Two products. Two licenses. Neither is a rebrand of the other.
Payer work lives on cloudhealthoffice.com. Practice work lives on clouddental.io. This page is only the index.
Health plans · BSL 1.1
Cloud Health Office
A payer claims platform that deploys beside QNXT, Facets, or HealthEdge. Meet CMS-0057-F without replacing the core.
- CMS-0057-F FHIR APIs beside the existing core admin system
- Claims, eligibility, prior auth, payments — progressive modernization
- Runs in the plan’s Azure, AWS, or GCP. PHI stays in the plan’s boundary
- Source-available under BSL 1.1 so a security team can read the code
Not a clearinghouse. Not a hosted black box that takes PHI out of the plan’s boundary by default.
Dental practices · Apache 2.0
Cloud Dental Office
The system of record for a dental practice. Scheduling, patients, claims, eligibility, and ERAs in one inspectable platform.
- One calendar. Practice websites and marketplace partners read availability
- Partners submit booking intent. They never become the calendar. They never see PHI
- 837D claims, 270/271 eligibility, 835 ERAs
- Apache 2.0. Clone it. Read the isolation boundary
Not a second calendar bolted onto a website. The practice remains the authority.
How they relate
Cloud Dental Office can submit claims to Cloud Health Office. Intelligence comes back through a practice-facing API. That meeting point is optional. A plan can run Cloud Health Office beside Facets or QNXT with no dental surface. A practice can run Cloud Dental Office without buying payer infrastructure.
We do not sell a suite, a “platform family,” or a combined SKU from this site. If you are evaluating a deployment, use the product site that matches the job.