One business. One live dataset.
ServeFlow runs the restaurant on one live dataset. Menu, orders and riders share the same state, and every status change of every order appends to an order history that is never edited or removed. Delivery and pickup follow their own fixed flows, and a cancelled order never counts as revenue.
Roles & security
Two roles, enforced on the server — not just hidden in the interface.
| Admin | Staff |
| 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 Staff account (staff@serveflow.local) runs the service day — orders, menu availability and riders — but cannot delete records or open Settings.
SCRYPT hashed passwords
SERVER-SIDE auth on every endpoint
429 sign-in flood limit
STATUS LOG append-only order history
Why ServeFlow
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 ServeFlow live, right now.
No signup, no install — the demo is the product.
Admin — admin@serveflow.local ·
Staff — staff@serveflow.local
Tap an account on the sign-in screen and the password fills in.