Products

Own products and solutions

SaaS PlatformIn beta · from €29/month

Salonnare

The complete platform for beauty salons

Salonnare is an all-in-one multi-tenant SaaS platform built for beauty salons, hair salons, nail studios and barbers. From online appointments and POS to inventory and loyalty - everything in one user-friendly system, starting at €29 per month.

  • Online appointment management
  • Point of Sale (POS)
  • Inventory management
  • Customer management & CRM
  • Reports & insights
  • Automatic reminders

Built with Next.js, TypeScript, Node.js and MariaDB - multi-tenant SaaS

Why Salonnare exists

Salons across the Netherlands and Belgium often juggle disconnected tools: a separate booking system, a separate point of sale, a spreadsheet for inventory and WhatsApp for customer communication. That costs time, money and visibility.

Salonnare brings everything together in one platform. Every salon gets its own subdomain, its own branding and its own data - fully isolated from other salons thanks to a multi-tenant architecture. No juggling multiple logins or duplicated admin.

Who Salonnare is for

Three types of salons benefit most from an all-in-one platform.

Solo professionals

Freelance hairdressers, nail artists and beauty therapists who want a professional booking system with POS without paying for multiple subscriptions.

Teams of 2–10

Small to mid-sized salons with multiple staff members, inventory and customer records that need to be managed from one place.

Multi-location

Salon chains and franchise organisations with multiple locations that want per-location reporting while managing centrally.

Integrations

Salonnare works with the tools your salon already uses.

  • Stripe & Stripe Connect - online payments and platform splits
  • Mollie & Mollie Connect - iDEAL, Bancontact and OAuth platform splits
  • Google Reserve - bookings directly from Google Search and Maps
  • SMTP email - Resend or your own provider for notifications
  • WhatsApp Business - automated reminders
  • Cloudflare - SSL, DDoS protection and DNS

Under the hood

Salonnare runs on Next.js 14, TypeScript, Node.js and MariaDB, fully containerized with Docker and Docker Compose. The multi-tenant architecture isolates each salon at the database level through a tenant-scoped query wrapper, and the REST API uses 88 Drizzle ORM schemas. All sensitive operations are behind JWT authentication and rate limiting. Backups, monitoring and SSL are included by default - no self-hosting required.

Website Development

Custom-built websites

Besides Salonnare, I also build custom websites for businesses and entrepreneurs. Responsive, fast, SEO-optimized and modern.

Responsive on all devices

SEO-optimized

Lightning fast

Modern design

Proven in production

Hard numbers from Salonnare's production system - not a marketing pitch.

88

Drizzle ORM schemas

104

Idempotent SQL migrations

5

Supported languages (NL/EN/DE/FR/ES)

6

Live external integrations

100

Lighthouse SEO (Dyola case)

99.9%

Production uptime target

My old site was expensive and didn't work well. Within a week, Nick delivered something new that looks beautiful and lets my clients book effortlessly. A world of difference.
DyolaOwner, Dyola's Beauty Boutique (Tilburg)

Frequently asked questions about Salonnare

What does Salonnare cost?

During beta, Salonnare costs €29/month per salon including all modules (appointments, POS, inventory, CRM, reports) and integrations. Early adopters get the first year free.

Can I whitelabel Salonnare?

Yes. Each salon gets its own subdomain, branding, favicon and optional custom domain. There's also a whitelabel mode that hides 'Powered by Salonnare' for premium clients.

Where is my data stored?

All data is encrypted on EU servers. Each salon runs fully isolated thanks to multi-tenant database scoping - other salons never see your customers or revenue.

Can I migrate from another system?

Yes, I help migrate from Treatwell, Salonized, Mindbody and custom systems. CSV imports for clients, products and historical appointments are standard. More complex migrations are scoped as separate engagements.

Last updated: