A studio platform engineered in Copenhagen.
Class Booking is built and operated by Nahbo ApS, an independent Danish software company. The team that designs and engineers the product also answers support — there is no outsourced layer between you and the people who own the code.
Known as Holdstyring in Denmark
Class Booking and Holdstyring are the same platform, built by the same company, Nahbo ApS (CVR 45880583). Holdstyring is our Danish brand at holdstyring.dk, where studios rate it 4.3 on Trustpilot. Choosing Class Booking, you get exactly that software, in English.
How the product came to exist
The company — Nahbo ApS, CVR 45880583 — was founded in Copenhagen in 2024. Independent, profitable from day one, no outside funding.
The first version shipped as Holdstyring, in Danish, for Danish yoga and fitness studios. It ran in daily production through 2025; the platform deepened with every studio that joined. In Denmark the platform is still sold as Holdstyring today: same product, same team, same company (Nahbo ApS).
Class Booking — the international product — launched in 2026 because studios outside Denmark kept asking for the same engine in English. Same codebase, same database, same team; the interface, currency and tax rules switch by tenant. The platform runs in EUR, GBP, USD, DKK, SEK or NOK, in any country Stripe operates in.
The platform runs in the EU, on servers in Germany — which means GDPR-grade privacy by default for studios anywhere, not because someone bolted a privacy badge on later, but because that's where the company lives and where the engineering decisions are made. A few sub-processors handle data outside the EU — Stripe for payments and Anthropic for the AI assistant — under the EU Commission's Standard Contractual Clauses and the EU-US Data Privacy Framework; the full list is in our privacy policy.
Why we built it
The class-booking market offered two kinds of options. Local European systems served their home markets, often in a single language. The global platforms — Mindbody among them — were designed for large US operators, with pricing and contracts to match. We saw room for a platform in between: one that handles payments across jurisdictions and bookings that cover more than one person.
We wanted to give independent studios on both sides of the Atlantic a platform built for them — modern stack, multi-currency, multi-jurisdiction, fair pricing, no sales call. So we built one.
The engineering tradition we sit in
Scandinavian, in the sense that matters
Klarna, Spotify, Vipps, Linear, Bambora — Nordic software at its best is precise, current, and built to last. Class Booking sits in that tradition. Not a personality, an engineering discipline.
Depth before surface
The interesting work is in the data model — per-participant VAT, fixed-seat seasons, multi-currency settlement, real-time event propagation. The surface is direct because the engine underneath is doing the heavy lifting.
International by architecture
Multi-currency Stripe Connect, country-aware tax rules, per-participant invoicing, GDPR-grade privacy — built into the data model, not bolted on through configuration screens. Operate in any market without architectural detours.
Defaults that ship the same day
A new studio can sign up, add a class and take a booking the same afternoon — without a setup specialist. The defaults are deliberate; the configuration surface is there when you need it.
Pricing as commitment
The price on the pricing page is the price on the invoice. No transaction skim, no per-booking commission, no annual lock-in, no "contact sales" tier. Independent and profitable means we can keep it that way.
Boring choices where boring wins
PostgreSQL, Stripe, Next.js — the same building blocks the rest of the industry runs in production. We pick novel where novelty makes the product better, and boring where reliability matters.
Owned, not assembled
The team that designs the product writes the code and answers support. No outsourced tier between you and the people who can fix what is broken or build what you need.
The team
A focused product team, in Copenhagen. The people who designed and built the platform still work on it every day. Support requests go to engineers, not to a tier-1 routing layer.
The structure is deliberate. When something breaks, the person fixing it usually wrote the code. When you propose a feature, the person reading the request can tell you precisely how it would fit — or why it wouldn't — without forwarding anything internally.
Independent and profitable
Independent and profitable. We answer to studios, not investors — so the roadmap follows what helps you run the place.
Where the platform runs
Studios in Denmark, Sweden and the UK use the platform daily, with a growing footprint across the rest of Europe and into North America. We don't publish a customer count — that number would be a marketing exercise rather than a technical fact. If you want to speak to a studio already on the platform, write in and we'll make the introduction.
How we work, and how to reach us
Email lands with a person on the team and is answered within a working day. There's no phone hotline; the live chat inside the admin reaches the same engineers who write the code. Beta features ship to opt-in studios first. Breaking changes are announced with notice — never silently rolled into a release.
Support
For existing customers.
Live chat is also available inside your admin dashboard.
CVR 45880583
Copenhagen, Denmark