Run a solo practice from your own devices

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.

Solo syncs like every edition: your desktop, laptop and phone share one record, every entry is sealed on our server the moment it is written — a copy we cannot read — and your devices keep working on the seat they learned at sign-in, even offline. Nothing of ours is load-bearing for the day's work.

How a solo week actually runs

Patients book by phone or, if you later move to Practice, 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.

A server that cannot read a word

Every SaaS practice system quietly makes your Tuesday depend on someone else's uptime and leaves your records readable in someone else's database. Solo removes both: an outage on our side cannot stop clinical work, because the app writes to your device and queues whatever the server has not received; and the copy on our server is sealed — we hold no key to it. 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 later is a seat change, not a data migration — and adding a laptop or a phone is just a sign-in. The Practice edition adds seats for the people you work with and the patient portal on top of the record 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.