Apache 2.0 Licensed · 560+ Tests · Production-Ready Core

The Open Source Practice Management System for Dental

A complete, cloud-native PMS that DSOs can self-host, software companies can sell as SaaS, and developers can build on. Built-in patient record portability, open third-party integrations, and multi-tenant deployment.

79
Data Models
22
API Collections
560+
Tests Passing
21
Imaging Bridges
6
Repositories
HOW PATIENT PORTABILITY WORKS

Records Move With the Patient, Not the Vendor

A patient at Office A (powered by Vendor X) can transfer their full clinical history to Office B (powered by Vendor Y) — instantly, with consent.

🏗

Office A

Powered by Vendor X
Has patient records
Hash lookup
🌐

Chairside Foundation

Zero-knowledge registry
Stores only SHA-256 hashes
Zero PHI

Hash lookup
🏢

Office B

Powered by Vendor Y
Needs patient records
Office A
FHIR R4 Bundle
RSA-signed consent • Direct transfer
Office B

Foundation facilitates the lookup but never sees the clinical data. The transfer is direct between offices, encrypted, and requires patient consent.

Learn more about patient portability →

HOW OPEN INTEGRATIONS WORK

Practices Choose Their Own Tools

Third-party developers register once on Foundation. Any practice on any vendor’s Chairside deployment can authorize their app.

🧠
AI Diagnostics

Cavity detection

📈
Analytics

Production reports

💬
Patient Comms

Reminders & recalls

💰
Insurance

Eligibility checks

Register once

🌐 Chairside Foundation

Developer Portal • App Registry • Secret Verification

OAuth2 + Graph API
Practice authorizes ↓
🏗
Practice A

Vendor X

🏢
Practice B

Vendor Y

🏘
Practice C

Self-hosted DSO

👥
Patients

22 collections

📅
Appointments

via Graph API

💵
Billing

Scoped by practice

📋
Clinical

Notes, charts, plans

Developers register once. Practices authorize directly — no vendor approval needed. Each app only accesses the data the practice consented to, scoped to that practice only.

Build on the Chairside API →

WHAT MAKES CHAIRSIDE DIFFERENT

Built Different From the Ground Up

Three capabilities designed into the core of Chairside that set it apart.

PATIENT PORTABILITY

Patient records move with the patient

Chairside includes a built-in patient portability registry. When a patient visits a new office, their complete clinical history — X-rays, treatment plans, notes, medications — transfers instantly via FHIR R4. No faxes. No phone calls. Cross-vendor, cross-state, with patient consent.

FHIR R4
Standard transfers
0
PHI on registry
How patient portability works →
Dental office with modern technology
Analytics dashboard showing practice data
OPEN INTEGRATIONS

Practices connect any third-party app they choose

Chairside ships with an OAuth2 authorization server and a Graph API covering 22 data collections. Practices authorize third-party apps directly — AI diagnostics, analytics, patient communication, insurance tools, marketing platforms. The ecosystem is open by design.

22
API collections
OAuth2
Standard auth
Explore the Graph API →
COST & CONTROL

Deploy on your own terms, at your own scale

-500/month per provider. A 30-location DSO with 3 providers each spends over K annually on PMS licenses — for software they can’t modify, can’t migrate from, and don’t control the roadmap of.

K
30-loc DSO/year
/bin/zsh
Chairside license
Deploy or sell as SaaS →
Cloud server infrastructure

Full PMS Feature Set

Everything a dental office needs to operate — from patient intake to insurance claim submission.

Patient demographics & history
Tooth charting & perio exams
SOAP clinical notes
Treatment planning
Prescriptions
Multi-provider scheduling
Insurance claims (X12 837D)
Ledger billing & aging reports
Stripe Connect payments
Patient portal & online booking
E-signatures & audit certificates
21 imaging software bridges
Multi-location group practices
OAuth2 + Graph API (22 collections)
FHIR R4 patient transfers
30+ plan feature toggles
Subscription billing (Stripe)
AWS SES email & Twilio SMS
Role-based access control
Docker & Lambda deployment

Who Deploys Chairside

Chairside is built for technical teams in dental organizations — not end users browsing for software.

🏗

DSO Tech Teams

Deploy on your own AWS/GCP account. Run all your locations on one platform with shared patient records, zero per-provider licensing, and full control over the data and infrastructure.

Self-host Chairside →
🏢

Software Vendors

White-label Chairside as your own SaaS product. Multi-tenant vendor platform with Stripe billing, credential management, subscription plan builder, and 30+ feature toggles per plan.

Sell as SaaS →
💻

Integration Developers

Build against a real dental API. OAuth2 authorization, 22 Graph API collections, standard scopes. No vendor approval needed. Practices authorize your app directly.

Start building →

Apache 2.0 with Two Ecosystem Protections

Fork it, sell it, white-label it, modify it. Two things you cannot do:

  1. Remove patient portability. Every deployment must participate in the Foundation registry and process record transfers. Patients own their data.
  2. Block third-party integrations. Vendors cannot restrict access to the OAuth API. The practice decides which apps connect — not the vendor.

Full license details →

Get Started with Chairside

Six repositories, full documentation, 560+ tests. Get a working PMS in minutes.