A database for everything your website has to remember: appointments, enquiries, customer accounts. The servers sit in the EU, which keeps the data protection question simple from the start.
Appointments live on scraps of paper and in four people's heads. What's lost is lost.
Everything in one place, viewable any time, backed up daily.
- A real database, not a spreadsheet
Appointments, sign-ups and orders live in a PostgreSQL database — the same kind large companies run on.
- Rights live in the database itself
Who may see which row isn't decided in the page but one layer below. That can't be bypassed.
- Login comes with it
Customer accounts, password resets, signing in with Google — none of that has to be built.
- Files sit alongside
Images and documents are stored under the same rules as the data.
- Input on your site
- Supabase checks rights
- Database
- File storage
A rights check stands before every access. Someone without permission doesn't get through — not even knowing the address.
A PostgreSQL database with a ready-made interface, sign-in handling and file storage. Access isn't granted wholesale but row by row: a customer sees their own appointments and nothing else.
- Database
- PostgreSQL
- Location
- EU, Frankfurt
- Access
- governed per row
- Included
- sign-in and files
Appointment booking with slots that can't double-book
Collecting enquiries instead of losing them in an inbox
Protected areas only you can get into
A database needs upkeep and backups. For a site without appointments, accounts or orders it's dead weight — then I leave it out.
Not every site needs a database. As soon as appointments, accounts or orders appear, this is the foundation.