Run a solo practice from one machine

Complete on day one

Solo is not a teaser tier. It carries the full clinical core — structured notes, the calendar, billing, outcome measures, the in-office kiosk, audit and compliance — plus on-device AI, which is never edition-gated.

What Solo deliberately lacks is infrastructure: no relay, no server component, no account with us that your practice depends on. One machine, one encrypted database, one licence key verified offline after activation.

How a solo week actually runs

Patients book by phone or, if you later add Portal, book themselves. Sessions run off the day sheet; notes draft by dictation or assistant and are signed before the kettle boils; invoices raise from the chart and track to paid. Sunday admin is the practice overview plus a .cfbak backup to your own drive — fifteen minutes, not an evening.

No server is a feature, not a gap

Every SaaS practice system quietly makes your Tuesday depend on someone else's uptime and your records depend on someone else's database. Solo removes both dependencies: an outage on our side cannot stop clinical work, and there is no vendor copy of your records anywhere. The wider argument for that posture lives on the privacy-first page; Solo simply gives it to you by default.

Growing out of Solo, without a migration

Hiring an associate or adding a laptop later is a licence change, not a data migration. The Practice edition adds zero-knowledge sync on top of the database you already have; nothing is exported, imported or re-entered. The pricing page shows the ladder, and the 30-day evaluation covers the top of it, so you can test the future before paying for it.