stancl/tenancy

Features

• Database-Level Tenant Isolations - Assigns each tenant to a dedicated database schema to ensure complete physical separation of data.
• SaaS Application Architectures - Provides a comprehensive architectural foundation for building SaaS applications with isolated data, filesystems, and caches.
• Tenant-Scoped Job Executions - Initializes the tenant context automatically for background jobs to ensure they process data using correct resources.
• Multi-Tenant Domain Managers - Maps incoming requests from subdomains or custom domains to the corresponding tenant account.
• Tenant Resource Switching - Reconfigures database connections, cache prefixes, and filesystem paths at runtime to match the identified tenant.
• Automated Tenant Migrations - Runs database schema updates across tenant databases using configurable default parameters.
• Connection Configurations - Defines unique database names, credentials, and connection settings for each tenant via the tenant record.
• Data Tenant Isolators - Provides query-level scoping via traits to restrict data access within a shared database environment.
• Automated Database Provisioners - Automates the provisioning, migration, and isolation of dedicated databases for individual tenants.
• Database Schema Migrations - Implements automated database migrations and seeding across all tenant-specific databases from the command line.
• Tenant Lifecycle Managers - Provides an integrated administration interface to manage the creation, listing, and deletion of tenant records.
• Request-Based Tenant Detectors - Determines the active tenant by analyzing domains, subdomains, or URL paths during the incoming HTTP request.
• Tenant Identification Strategies - Resolves the active tenant by analyzing domains, subdomains, URL paths, or HTTP headers in the request.
• Multi-Tenant Resource Isolation - Scopes caches, filesystems, and Redis stores to ensure complete resource isolation between tenants.
• Tenant Configurations - Maps tenant-specific database attributes directly into the application configuration to allow per-tenant behavior overrides.
• Tenant Path Isolation - Modifies storage paths and asset helpers to ensure files are stored in tenant-specific directories.
• Tenant Storage Separation - Separates stored files and assets by tenant to ensure users only access their own resources.
• Tenant Database Provisioning - Triggers the automatic creation of a dedicated database immediately after a new tenant is registered.
• Tenant Context Propagation - Injects the tenant identifier into queued job payloads and restores the tenant context during background processing.
• Tenant Lifecycle Hooks - Uses an event-based architecture to modify bootstrapping and post-creation workflows via custom listeners.
• Session Isolations - Prevents session data from being shared across tenants by scoping storage to tenant-specific databases or Redis.
• URL Path Identifications - Provides the capability to resolve tenant identity by parsing specific segments of the incoming request URL path.
• Tenant Environment Bootstrappers - Uses custom bootstrapper classes to modify application state and configuration upon tenant initialization.
• Multi-Tenancy Frameworks - A complete framework for implementing multi-tenancy in Laravel with support for multiple isolation strategies.
• Tenant Cache Isolation - Isolates cached data by tenant to prevent cross-tenant information leakage in shared memory stores.
• Tenant Context Propagation - Injects tenant identifiers into queued job payloads to restore the correct environment during background processing.
• Tenant Environment Switching - Dynamically reconfigures database connections, caches, filesystems, and queues to the identified tenant's environment.
• Tenant State Retrievals - Provides helper functions and dependency injection to access the active tenant's model and attributes.
• Tenant Route Definitions - Registers routes that automatically apply identification middleware to isolate requests by tenant.
• Tenant-Specific Invalidations - Enables removing cached data for specific tenants using unique tags for isolated cache clearing.
• Cache Data Segmentations - Provides strict data isolation within Redis stores to prevent cross-tenant data leakage.
• Session Partitioning - Blocks attempts to manipulate session cookies across tenant domains by validating the session scope.
• Database Seeding Tools - Populates tenant databases with initial or test data using configurable seeding parameters.
• Flexible Metadata Stores - Saves arbitrary key-value pairs into a serialized column to avoid dedicated schema changes for every attribute.
• Cross-Tenant Query Federations - Bypasses tenant-specific scoping to retrieve data across all tenants for central administration purposes.
• Key Prefixing Isolations - Ensures key-value data isolation by dynamically changing the Redis prefix for each tenant.
• Per-Tenant Override APIs - Maps tenant-specific database attributes to application configuration keys for customized per-tenant settings.
• Tenant-Scoped Model Filtering - Filters database queries using shared model traits to restrict data access in single-database environments.
• Tenant Bootstrappers - Allows the implementation of custom bootstrapper classes to define component behavior during tenant initialization.
• Tenant Initialization Extensions - Provides mechanisms to add custom bootstrapping logic to modify tenant-specific environment initialization.
• Domain-Based Routing - Separates routes into central and tenant groups to ensure pages are only accessible on respective domains.
• Tenant Authentication Isolation - Manages separate OAuth clients and encryption keys for each tenant to ensure authentication isolation.
• Domain Access Restrictions - Validates that requests to tenant routes originate from tenant domains to block central route access.
• Multi-Tenant Administration - Provides administrative tools to manage tenant configurations and accounts from a central application context.
• Active Tenant State Tracking - Maintains the identity of the active tenant throughout the application lifecycle for manual resource isolation.
• Multi-Tenant Isolation - Secures sensitive tenant data by storing attributes in custom columns with encryption casts.
• Tenant-Scoped Token Isolation - Isolates authentication tokens and cookies across multiple tenants to ensure users remain within their specific context.
• Event-Driven Hooks - Triggers custom business logic during tenant creation, updating, or deletion using an event-driven system.
• Global Context Background Jobs - Runs background tasks in a global context using dedicated queue connections to prevent state leakage.
• Manual Tenancy Initializations - Provides a way to programmatically trigger the tenant boot process to isolate resources when middleware is not applicable.
• Tenant-Scoped Tagging - Adds tenant identifiers as tags to cache calls to scope data by tenant for selective clearing.
• Tenant Command Execution - Provides a command-line interface to execute administrative tasks across all tenants or specific tenant subsets.
• Tenant Context Executions - Allows running specific logic or commands within a tenant's environment before returning to the central context.
• Tenant Lookup Caches - Stores tenant identification results in a local cache to avoid repeated expensive queries to the central database.
• Central Route Isolations - Restricts specific routes to central domains so they cannot be reached via tenant domains.
• General Utilities - Automates multi-tenancy implementation.

Star-Verlauf