How to install and configure Tenancy for Laravel from scratch?

Install via Composer and follow the version-specific documentation (e.g., v4.tenancyforlaravel.com) for setup steps, which include configuring tenancy middleware and database connections. Expect to adjust environment files and service providers.

Tenancy for Laravel vs using separate databases per tenant manually

This package automates database switching and isolation without manual connection changes, reducing errors and development time. Manual approaches offer more control but require extensive boilerplate code and careful management.

Can I use subdomain identification with Tenancy for Laravel?

Yes, it supports subdomain-based identification out of the box, including second-level domains. Configure the hostname identification in the tenancy config file to map domains to tenants seamlessly.

What happens to Laravel queues and jobs in a multi-tenant setup with this package?

Tenancy for Laravel can integrate with queues by automatically scoping jobs to tenants, but it requires additional configuration like tenant-aware job middleware to prevent cross-tenant data mixing.

How to handle tenant-specific files and storage in Tenancy for Laravel?

It uses Laravel's native Storage with automatic tenant isolation, but you must configure disk prefixes or separate directories per tenant in the storage settings to avoid file overlap.

Is Tenancy for Laravel compatible with Laravel Octane or other performance optimizations?

Compatibility exists but may need testing, as automatic tenant switching in long-lived processes like Octane can lead to state leakage; refer to the documentation for best practices on resetting tenancy between requests.

Open-Awesome

tenancy

MITPHPv3.10.0

Automatic multi-tenancy for Laravel applications without requiring code changes.

Visit Website GitHub

4.3k stars487 forks0 contributors

What is tenancy?

Tenancy for Laravel is a package that provides automatic multi-tenancy for Laravel applications, enabling developers to serve multiple tenants from a single codebase without modifying existing code. It handles tenant identification, data isolation, and integration with Laravel's core components seamlessly, solving the complexity of building SaaS platforms.

Target Audience

Laravel developers building SaaS applications, multi-tenant platforms, or any system that needs to serve multiple organizations or customers from a single installation.

Value Proposition

Developers choose Tenancy for Laravel because it requires zero code changes, integrates natively with Laravel's architecture, and provides automatic tenant isolation, reducing development time and complexity compared to manual multi-tenancy implementations.

Overview

Automatic multi-tenancy for Laravel. No code changes needed.

Use Cases

Best For

Building SaaS applications with multiple tenants
Creating multi-tenant platforms in Laravel
Implementing automatic tenant data isolation
Serving multiple organizations from a single Laravel codebase
Handling hostname-based tenant identification
Reducing multi-tenancy development complexity in Laravel

Not Ideal For

Projects requiring manual, fine-grained control over database connections and tenant isolation logic
Applications that identify tenants via non-hostname methods (e.g., URL paths or custom headers) without built-in support
Teams preferring explicit, trait-based approaches for clear tenant management in code
Legacy Laravel systems with highly customized architectures that may conflict with automatic tenancy

Pros & Cons

Pros

Zero Code Changes

Eliminates the need to modify existing Laravel models or classes, as the README emphasizes no model traits or replacement of core classes.

Native Laravel Integration

Uses built-in Laravel components like Cache and Storage without tenancy-aware alternatives, ensuring seamless compatibility and reduced maintenance.

Automatic Tenant Identification

Built-in hostname-based identification, including second-level domains, simplifies tenant detection without additional coding effort.

Effortless Data Isolation

Automatically handles tenant data separation, lowering the risk of data leaks and saving time on manual management for SaaS applications.

Cons

Configuration Complexity

Initial setup can be intricate, requiring a deep understanding of multi-tenancy concepts and Laravel's service container, despite the no-code-change promise.

Hostname Dependency

Primarily designed for hostname-based identification, which may not suit all use cases without custom extensions or additional development work.

Limited Flexibility for Advanced Scenarios

The automatic nature restricts fine-grained control, such as custom tenant switching logic or mixed tenancy models, which might be needed in complex applications.

Frequently Asked Questions

Related Projects

LiveWire

A full-stack framework for Laravel that takes the pain out of building dynamic UIs.

Debugbar for Laravel (Integrates PHP Debug Bar)

Stars19,179

Forks1,607

Last commit2 days ago

IDE Helper

IDE Helper for Laravel

Stars14,891

Forks1,188

Last commit23 days ago

Intervention Image

PHP Image Processing

Stars14,330

Forks1,491

Last commit5 days ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub