Problem
Booking flows get complex quickly when resources, times, roles, and tenants share the same system. The public guest needs a simple flow, while the business needs control behind the scenes.
Solution
I built a Laravel platform with public guest booking, admin and staff views, tenant isolation, role-based access, and transaction-safe conflict checks.
Technical decisions
Tenant isolation to keep business data separated.Policies/Gates to make permissions explicit in code.PostgreSQL through Supabase for relational data and practical operations.Render deployment to get the app live without unnecessary operational complexity.
What it shows
The project shows my ability to build business-facing systems where data model, user flow, permissions, and deployment need to work together.
Tech
Laravel 11PHP 8.3PostgreSQLSupabaseBladeTailwindAlpine.jsRender