WEB APP · END-TO-END 2026 DEVICE INTEGRATION NEXT

SUMISURA

01/ THE BRIEF

The operating system for a private health center in Brussels.

Sumisura books sessions that depend on qualified staff, a specific room and specific machines being free at the same moment, sells memberships that draw down credits, and runs a shop. None of that survives a calendar plugin bolted to a website.

So it was scoped as one system: a Laravel backend owning the domain, and four frontends on top of it — the public site, a webshop, an admin panel, and a content studio. One stack, one database, one source of truth.

The work started with a capability assessment and a MoSCoW scope, then architecture and data model, before a line of feature code.

02/ WHAT WAS BUILT

01/ BOOKING ENGINE Real booking logic, not a calendar plugin. Each session type carries its own constraints: which staff are qualified, which room is required, which machines are involved and whether they are free. Availability rules, closures and waitlists are part of the model. Overlapping dependencies are resolved before a slot is ever shown.

02/ MEMBERSHIPS, CREDITS AND PAYMENTS Membership offers with subscription billing through Mollie, and credit balances that bookings draw down. Webhooks keep payment state truthful rather than optimistic. Consent and terms documents are versioned, because what a member agreed to matters later.

03/ ADMIN PANEL Full operational control for the team: members, sessions, products, rooms, staff scheduling. Built so the center runs from inside the system, with no manual step happening in a spreadsheet beside it.

04/ WEBSHOP A separate storefront sharing the same catalog, auth and payment rails as the rest of the platform. Its own app, not a second system: a product exists once, and a checkout uses the payment integration that already works.

05/ CMS AND CONTENT LAYER Sanity handles everything editable: site settings, SEO metadata, service descriptions, editorial copy, in Dutch and English. Fully typed schema with validated fields. The client edits content; the system keeps enforcing the rules.

03/ TECHNICAL HIGHLIGHTS

BOOKING CONSTRAINT-AWARE SCHEDULING Slot generation resolves three layers at once: staff qualification per session type, room availability, and equipment dependencies. A slot appears only when all three pass. Written from scratch against the actual operational model, because no plugin encodes this shape.

DOMAIN LARAVEL BACKEND, SERVICE-SHAPED Laravel 12 on PHP 8.2. The domain lives in services — booking, schedule, membership, payment, catalog, waitlist, staff — rather than in controllers, so the same rule holds whoever calls it. Sentry on the error path, JWT between the apps.

MONOREPO FOUR APPS, SHARED PACKAGES Website, webshop, admin panel and studio sit in one Turborepo over shared api, auth, ui, content and config packages. An API contract or a button exists once. Four apps that each reinvented those would have been four apps to fix every time.

PAYMENTS MOLLIE, WEBHOOK-DRIVEN Subscriptions and one-off purchases both settle through Mollie, with webhooks as the source of truth for payment state. Credit transactions are recorded as their own ledger, so a balance can always be explained rather than merely displayed.

IDENTITY TWO-TYPEFACE SYSTEM Su in Be Vietnam Pro Bold. Misura in Times New Roman Italic. The typographic split is the brand concept made visible, and every headline pairs the two. The design system is built around that split as its founding element.

STACK LARAVEL · ASTRO · REACT · SANITY · TS Laravel and PostgreSQL behind. Astro with React islands for the public site, React SPAs for the admin panel and webshop, GSAP for motion, Sanity for structured content, TypeScript across the front.

LARAVEL PHP 8.2 ASTRO REACT TYPESCRIPT TURBOREPO SANITY CMS MOLLIE BOOKING ENGINE WEBSHOP END-TO-END

04/ WHERE IT STANDS

Founding-members page is live. The platform is not, yet.

A standalone landing page runs at sumisura.be for early visibility, on its own repository and hosting. Behind it, booking, memberships and payments, the admin panel, the webshop and the CMS are built.

Ahead: platform testing, then connecting the center's machines so scan and session data flows into each member's account — credentials and APIs per device, which is its own piece of architecture. Then professional photography, a full feedback round, and launch.

Want to discuss a similar project? GET IN TOUCH →

DEVICE INTEGRATION NEXT