Lessons from building a multi-tenant Laravel app

Multi-tenancy looks like a database problem and turns out to be a discipline problem. The hard part isn't isolating data; it's making sure every query, job, cache key and file path remembers which tenant it belongs to.

If I started again I'd decide three things on day one: how a request finds its tenant, how background jobs inherit it, and how roles and permissions are scoped per tenant. Retrofitting any of these later is painful and risky.

I'd also write the onboarding path early. Creating a new tenant with sensible defaults, roles included, should be one command. If it takes a checklist, you'll forget a step the first time a customer is waiting.