Booking SaaS

bkg.dk: a booking platform for salons and clinics that we built and run ourselves

bkg.dk is our multi-tenant booking SaaS for salons and clinics: deposits, no-show protection, reminders, three languages. Live since 14.09.2026.

The problem

Before writing any code we read what salon owners actually complain about. In August 2026 we went through 392 negative reviews of five large booking tools: Vagaro, Booksy, Fresha, GlossGenius and Acuity. Missing features were rarely the problem. The largest groups were outages (40 reviews), poor support (31) and fees (27). One complaint kept coming back: when a client disputes a card payment, the professional has no proof that the cancellation terms were ever shown.

Our competitor study from July pointed the same way. The biggest platforms earn money as a marketplace and a payment provider, so the salon's client list and payments become part of someone else's business model. Several Danish tools charge per staff member, which adds up quickly for a salon with five chairs. And none of the tools in the comparison had a Ukrainian interface.

For a small salon the problems are concrete: empty slots after no-shows, clients who do not come back, and a system that has to work on the busiest day of the week.

What we built

bkg.dk is one application serving many salons. Every database read and write goes through a repository layer that filters by salon, so one business's clients and bookings cannot leak to another. From the research we deliberately took three things: operational depth, protection against no-shows, and features that bring clients back. Just as deliberately we left out a marketplace, fees on new clients, our own payment provider and automatic payouts.

Money runs through Stripe Connect. Each salon connects its own Stripe account, and bkg.dk only treats it as connected once Stripe allows charges. A service can require a fixed or percentage deposit, and with a card on file the salon can later charge a no-show or late-cancellation fee. The cancellation policy is shown before the client confirms. Where a fee can be charged, the server refuses the booking without consent, and the exact text, time and IP address are stored so the salon has evidence if a payment is disputed.

Around the calendar we added what a salon uses every day: email and SMS reminders (SMS through our own gateway), a waitlist where a freed slot can be claimed with one click, resource limits so three chairs never receive four bookings, per-employee prices and special working days, gift cards, punch cards, memberships and loyalty tiers, an occupancy report, and a payroll report that the salon hands to its accountant. The booking page can be embedded on the salon's own website. Client pages, emails and the admin are available in Danish, English and Ukrainian, and every email goes out in the client's language.

Facts and results

14.09.2026Live in production at bkg.dk
4,621automated tests passed in the release gate on 16.11.2026 (1,057 when CI first went green on 02.10)
3 languagesDanish, English and Ukrainian in the admin, client pages and emails
12 of 12modules with an API also have a working admin screen
392negative reviews of five competitors analysed before the design
Per salonfixed price per salon, not per staff member
Nightlybackups, checked with a restore drill

Stack

Python 3.12 with FastAPI, SQLAlchemy 2 and Alembic migrations; MySQL 8 in production; Redis for rate limits, one-time codes and a short-lived cache of free slots; Celery for reminders, webhooks and background jobs; Stripe and Stripe Connect for subscriptions, deposits and fees; reportlab for PDF invoices. Everything runs in Docker Compose on our own server, with nightly backups that we restore into a throwaway container to prove they work.

What we learned

Four serious faults only showed up in production after launch. Every Stripe webhook was rejected because of one wrong method call. Confirmation emails were sent before the booking was committed, so none went out. Duplicated email templates made a salon send nothing at all. And background jobs failed roughly every other run because the database pool was bound to the wrong event loop. No test caught any of them. Before launch the interface had surprises too: design mock-ups were registered ahead of the real pages, so signing up was impossible, and the create buttons on six admin pages did nothing. Since then we walk the real interface in a browser before each release, a self-check endpoint watches for unsent notifications and stuck payments, and Stripe events are deduplicated in the same database transaction as the change they cause.

Need something like this for your business?

Describe the task in the form. After a free scoping talk we send a plan and a quote, and we tell you which parts of these products we can reuse for you.

Get Started Today