Multitenant Bundle Laravel Package

Product Decisions This Supports

• SaaS Platform Expansion: Enables rapid development of multi-tenant architectures for subscription-based products (e.g., B2B SaaS, marketplaces, or shared-resource platforms).
• Cost Efficiency: Avoids building a custom multi-tenancy solution from scratch, reducing development time and technical debt.
• Scalability Roadmap: Supports future-proofing for horizontal scaling (e.g., tenant isolation, database sharding) by providing a modular foundation.
• Build vs. Buy: Justifies "buy" for teams lacking PHP/Symfony expertise in multi-tenancy patterns, while still allowing customization.
• Use Cases:
  • Shared Database Multi-Tenancy: Ideal for SaaS apps where tenants share a single database but require data isolation (e.g., CRM, analytics tools).
  • Hybrid Tenancy Models: Supports scenarios where users can own or belong to multiple tenants (e.g., agencies managing client accounts).
  • Dynamic Tenant Switching: Useful for admin dashboards or APIs requiring tenant context (e.g., switching between customer accounts).

When to Consider This Package

Adopt if:

• Your Symfony 2.4+ app requires shared-database multi-tenancy with minimal overhead.
• You prioritize quick integration over cutting-edge features (e.g., no need for schema-per-tenant or microservices).
• Your team lacks deep expertise in SQL filtering or tenant context management but needs a battle-tested foundation.
• You’re using FOSUserBundle or a similar auth system and need to layer multi-tenancy on top.

Look elsewhere if:

• You need schema-per-tenant or database-per-tenant isolation (consider Laravel’s tenancy package or custom solutions).
• Your app requires real-time tenant switching (e.g., subdomains) beyond URL parameters or helper methods.
• The 2016 release date is a blocker; the package lacks recent maintenance (evaluate forks or alternatives like Stof/StofDoctrineExtendsBundle for modern Symfony).
• You’re using Symfony 5/6 or PHP 7.4+ and need compatibility (check forks or alternatives).
• Your use case demands advanced features like tenant-specific configurations, billing integration, or complex role hierarchies (consider Spatie’s Laravel packages for inspiration).

How to Pitch It (Stakeholders)

For Executives: "This bundle lets us launch a multi-tenant SaaS product 30–50% faster by leveraging a pre-built solution for tenant isolation in Symfony. It handles the heavy lifting of SQL filtering and context switching, so our team can focus on core features like user onboarding and tenant-specific workflows. The trade-off is minimal maintenance risk (last updated in 2016), but the cost savings and speed-to-market outweigh the risks for our shared-database model. We’ll pair it with FOSUserBundle for auth and monitor for forks if we need long-term support."

For Engineering: *"This is a lightweight, opinionated way to add multi-tenancy to Symfony without reinventing the wheel. Key benefits:

• Automatic tenant filtering on entities (no manual WHERE tenant_id = X in queries).
• Traits for entities to enforce tenant ownership (e.g., use TenantAwareTrait).
• Dynamic tenant switching via URL params or a helper (e.g., /dashboard?tenant=123).
• Works with FOSUserBundle out of the box for user-tenant relationships.

Risks:

• No active maintenance; we’ll need to vet forks or patch issues internally.
• Limited to shared-database tenancy (no schema isolation).
• Symfony 2.4+ only (but we’re already on 5.x, so we’d need a fork or polyfill).

Recommendation: Use this for MVP, then evaluate migrating to a modern alternative (e.g., a Symfony 6-compatible fork or a Laravel package) if we scale beyond shared-database tenancy."*