This document discusses building multi-tenant SaaS applications with Laravel using separated databases. It begins by defining what multi-tenancy and SaaS are. It then covers database layouts for single, shared, and separated databases. The main sections cover setting up tenant connections, calling models from tenant and shared databases, handling inter-database relations, firing tenant events, and other considerations like caching and queues. Pros of the approach include backups and scalability per tenant, while cons include added complexity for built-in Laravel functions. Server layout and existing Laravel packages for multi-tenancy are also mentioned.