Eukairon
A multi-tenant SaaS booking platform for small businesses â hair salons, auto shops, veterinary clinics. Built with Laravel, Inertia.js + React, MySQL, Redis & Docker.
Overview
Eukairon lets small businesses accept bookings 24/7 â no phone calls, no missed appointments. Each business (workspace) gets its own professionals, services, schedules, customers, and bookings, with complete data isolation between tenants.
Customers book through the business's own public booking page â no account needed â and get SMS reminders before their appointment. Owners run everything from one dashboard: statistics, live calendar, services, professionals, opening hours and exceptions, plus their subscription through Stripe. Fully bilingual (Greek / English), with each business's timezone and daylight-saving changes handled server-side.
Key Features
Multi-tenant & Role-based Access
Data isolation enforced in middleware, request authorization, route binding, and an explicit workspace filter on every query. Owner, admin, member, and viewer roles per workspace.
Real-time Booking Engine
Customers pick a service, professional, date, and time from live availability. Conflict detection, past-slot refusal, and calendar updates pushed over WebSockets (Reverb).
Automated Reminders
SMS reminders queued on Redis for 24h and 2h before each appointment, each with a one-tap cancellation link.
Stripe Billing
Solo / Pro / Business flat-priced plans, a 30-day Solo trial with no card, VAT applied at checkout, and an admin plan override for special cases.
REST API
Versioned API with scoped read/write keys, per-key rate limiting, and plan gating â so a business can push bookings from its own systems.
Automated Tests
3,200+ Pest tests (feature + Playwright browser) and 1,100+ Vitest tests, run in parallel as a merge gate. Security fixes are proven to fail against the broken code first.
Technical Challenges
Tenant isolation at every layer
A simple where('workspace_id', ...) is not enough. Isolation had to be enforced at middleware, FormRequest authorize(), controller writes, route model binding, and queue jobs. A dangling pointer in current_workspace_id could open access to a removed workspace. Solved with defense-in-depth: scopeBindings(), role gates, plan gates, and feature flags â each layer refusing independently.
Refusal shape consistency (403 vs 404)
Some endpoints answered 403 for a workspace the user does not belong to â which confirms that the workspace exists â while their siblings answered 404. That difference is an enumeration oracle. Normalized to 404 for any foreign workspace, with tests pinning the response shape route by route.
Stripe integration with plan override
Beyond standard Stripe subscriptions, an admin plan_override feature grants free Pro/Business without Stripe. The plan gate reads from one authoritative source (config/billing.php) â not hardcoded strings. API access is checked on the credential itself, so a downgraded workspace's keys stop working the moment its plan changes.
Booking times across timezones
The app runs in UTC, while every booking is wall-clock time in its business's own timezone. The booking engine (laraveljutsu/zap) compared date strings, so a slot from the business's yesterday slipped through for about three hours a day, and an offset-carrying timestamp saved without ->utc() landed hours off. Fixed by comparing instants, refusing past starts on every write path (admin, API, public), requiring an explicit offset on the API, and filtering the slot list in one place so no screen offers a slot another one refuses.
Queue observability & data leaks
Notifications were synchronous. Moving to a queue improved latency but created a new problem: if the worker failed, delivery logs weren't written, and historical rows leaked through notification read paths after feature retirement. Solved with centralized visibility (User::visibleNotifications()) called from all read paths and export jobs.
Test infrastructure robustness
phpunit.xml <env> entries were inert â container .env took precedence, so tests pushed real jobs to dev Redis (271K failed_jobs). Baseline drift happened 4 times from manual bumps. Fixed with an executable baseline (baseline.json, ±5 tolerance) checked on every merge, per-database locks so parallel sessions never share a test DB, and a 4-process parallel gate that runs the full suite in about a minute.
Owner Dashboard
Everything a business owner needs at a glance: revenue, monthly bookings, occupancy, and no-show rate against the previous month, the day's and upcoming schedule, top customers, and revenue per day. A separate statistics page covers this month, the last 3 or the last 12 months: revenue, online booking share, cancellations and no-shows, new vs returning customers, occupancy per professional, services, booking sources and peak hours. Each workspace sees only its own data.
- Month-over-month KPIs
- Today's & upcoming schedule
- Top customers & revenue per day
- Statistics for 1, 3 or 12 months
Need something similar?
I build multi-tenant SaaS platforms, REST APIs, and complex integrations from scratch. Let's talk about your project.
Get in touch