Skip to main content
Trust

Trust starts with clear boundaries.

Cloud Dental Office is source-available practice infrastructure, not a certification claim. This page states what is in the repository, what IntakeService cannot do, and what we do not put on a badge.

Source visibleIsolation, booking flow, and availability engine are in the public repository.
Disabled by defaultPublic booking returns 404 until PublicBooking:Enabled is true.
No PHI read pathIntakeService cannot read patient, clinical, or scheduling databases.
No borrowed badgesWe do not claim SOC 2, HITRUST, or a certified Zocdoc partnership.
Current assurance status

What is public, what is configurable, what is not claimed.

Public & implemented

Intake isolation

API key compared in constant time. Rate limit 5/min per IP. Isolated inbox. BookingRequestedEvent over Service Bus. Token revalidation with 409 on stale slots.

Reference architecture

Private network for PHI

Portal, YARP, and every PHI-bearing service stay private. Only IntakeService is designed to face the internet.

Not currently claimed

Aurelianware certifications

This site does not claim that Aurelianware or Cloud Dental Office currently holds SOC 2 Type II or HITRUST certification.

Pilot · October 2026

Zocdoc

Built on Zocdoc’s scheduling API. Zocdoc has agreed to a pilot starting in October 2026.

Contractual

BAA, SLA, support

PHI processing, support coverage, and incident terms are defined per engagement. Visitor-submitted intake data must still be handled as sensitive healthcare information.

Customer-operated

Production effectiveness

Identity, networks, keys, logging, and recovery must be verified in the target environment. A repository is not a production control.

Intake boundary

What IntakeService is allowed to do.

ActionAllowedNotes
Accept name, phone, optional email, preferredStartYesMinimum necessary for appointment intake.
Publish BookingRequestedEventYes202 only after the event is on the bus.
Expose free/bookable slots + availabilityTokenYesSlugs, practice timezone, no PHI.
Read patient / clinical / scheduling databasesNoNo connection. Isolated inbox only.
Write an AppointmentNoStaff create the appointment after review.
Return 202 when Service Bus is downNoReturns 503 so the website can fall back.
Vulnerability reporting

Report privately. Do not file PHI in public issues.

Do not disclose suspected vulnerabilities, PHI, credentials, or tenant data through public GitHub issues. Email [email protected] with the component, steps, and redacted evidence. The product SECURITY.md is in the repository.

License

Source-available under BSL 1.1. Free to run your own practice.

Cloud Dental Office is licensed under the Business Source License 1.1, the same license as Cloud Health Office. You can read, copy, modify, and redistribute the code, and use it outside production.

Production use is free for your own dental practice, or practices under common ownership, including self-hosted. Offering Cloud Dental Office or a derivative to third parties as a hosted, managed, or embedded product that competes with Aurelianware's paid versions requires a commercial license.

Each version converts to Apache 2.0 four years after its first public release. Code at or before the apache-2.0-final tag remains under Apache 2.0.

This is a summary. The LICENSE file is the governing text; LICENSING.md explains it. Commercial licensing: [email protected].

Bring the architecture team. We will walk the isolation boundary in source.

No badges we have not earned.

Founding-practice pilot starts October 2026.

Join the pilot → How it works