Clinic OS is a cloud platform for dental, aesthetic, and private medical clinics. It combines CRM, finance, marketing, compliance, and AI intelligence in one place.

Is this an EMR or a CRM?

It is neither a generic CRM nor a full hospital EMR. It is purpose-built for clinic revenue operations, leads, bookings, patients, billing, and growth.

Do you support Arabic?

Yes. The admin panel and public clinic website support English and Arabic with full RTL layout for Arabic.

How does the free plan work?

Free is a forever-free Clinic OS tier for solo dentists, not a time-limited trial. Run CRM, scheduling, website, online booking, and a capped AI assistant within published limits. Upgrade to Starter when you need finance, portal, or higher volume.

Can I upgrade or downgrade later?

Yes. Move Free → Starter → Growth → Scale as your clinic matures. Feature access and limits adjust automatically from your billing dashboard.

How is my clinic data secured?

Clinic OS runs on encrypted cloud infrastructure with role-based access, audit trails, and clinic-scoped data isolation. Backups and access controls are built in, your patient and financial data stays within your workspace permissions.

Can you migrate data from our current system?

Yes. We help Starter, Pro, and Enterprise clinics import patients, appointments, and key records from spreadsheets or common clinic tools. Share what you use today during onboarding and we will map a practical migration plan.

What support is included?

All plans include email support and help-center guides. Starter adds priority email support. Pro and Enterprise include faster response targets and onboarding assistance, Enterprise adds a dedicated success contact for multi-location teams.

Developers

Build on Clinic OS integrations

API, webhooks, SDKs, and OpenAPI guidance for technical teams connecting external systems.

API
Webhooks
SDKs
OpenAPI

API Reference

Public API

Authenticated machine access for clinic-scoped reads and controlled writes.

Clinic-scoped tokens

API access is bound to clinic context and operator-approved credentials.

Core resources

Patients, appointments, and related operational resources for integration partners.

Fail-closed auth

Missing or invalid credentials are rejected — no cross-clinic leakage.

Webhooks

Event delivery

Push clinic events to your systems with signed payloads and replay tooling.

Signed deliveries

Verify authenticity before accepting inbound webhook events.

Outbox & replay

Operators can inspect sync health and replay failed deliveries from admin.

Connector hub

Installations, providers, and webhook events live under Platform → Integrations.

SDKs

Client libraries

Use HTTP first; official SDKs expand as partner demand solidifies.

HTTP-first

Any language can integrate with the documented REST endpoints and auth headers.

Partner kits

Example payloads and collections are shared during technical onboarding.

OpenAPI

Machine-readable contract

OpenAPI descriptions support codegen and contract review for partner builds.

Contract-driven

Schemas describe available operations for clinic integrations.

Versioned carefully

Breaking changes are communicated through release notes and partner channels.

Request API access or OpenAPI artifacts during a technical walkthrough with the product team.

Need credentials or a sandbox?

Book a technical session — we scope API access to your clinic and use case.

Contact product team