One business. One live dataset.
ClinicFlow runs the clinic day on one live dataset. The appointment book, patient register, visit records and billing share the same state — a booking must sit on the doctor's own grid inside working hours, a visit snapshots the fee the day it completes, and the invoice that follows is permanent.
Roles & security
Two roles, enforced on the server — not just hidden in the interface.
| Admin | Receptionist |
| Day-to-day work (create, edit, process) | ✓ Yes | ✓ Yes |
| Delete records | ✓ Yes | ✗ No — 403 |
| Settings & data controls | ✓ Yes | ✗ No — 403 |
| Sign in without a token | ✗ No — 401 for every role |
The Receptionist account (reception@clinicflow.local) runs the whole clinic day — patients, appointments, visit records, billing — but cannot delete records or open Settings.
SCRYPT hashed passwords
SERVER-SIDE auth on every endpoint
429 sign-in flood limit
PERMANENT invoices — never edited
Why ClinicFlow
Built to be owned, not rented.
No database serverNo database server, API keys or external services to manage.
Your data stays yoursData persists to a plain JSON file on your own server.
Runs anywhereShips with its own Node server — and the live demo runs the same backend as a serverless function.
Commercial licenceUse it in one end product, with full source code included.
Try ClinicFlow live, right now.
No signup, no install — the demo is the product.
Admin — admin@clinicflow.local ·
Receptionist — reception@clinicflow.local
Tap an account on the sign-in screen and the password fills in.