Packstub Tenancy — Documentation
Multi-database tenancy for Filament v5 panels, powered by stancl/tenancy v4. One database per tenant or shared databases with tenant_id scoping — your choice per app, even per tenant — across any number of database servers.
- Website: packstub.dev
- Support: support@packstub.dev
- Customer portal (licenses, tokens, invoices): packstub.dev/customer
Guides
| Guide | What it covers |
|---|---|
| Quickstart | Fresh Laravel app to your first provisioned tenant in ~10 minutes |
| Installation | Composer repository setup, the interactive installer, subdomain vs. path identification |
| Configuration | Complete reference: the annotated config file and the fluent TenancyPlugin API |
| Database strategies | Dedicated (database-per-tenant), shared (tenant_id, shards, optional PostgreSQL RLS), and hybrid data separation |
| Custom domains | Tenant-owned domains: DNS verification, cross-domain sign-in handoff, logout-everywhere |
| Customizing the UI | Publishing views and translations: restyle the waiting room, add a locale |
| Horizontal scaling | The database pool: spreading tenant databases across multiple servers |
| Resource syncing | Keeping central and tenant copies of a resource in sync |
| Testing | Test helpers and patterns for tenant-aware test suites |
| Production | Queues, Octane, backups, and operational checklists |
| Troubleshooting | Common failure modes and how to recover them |
This repository is a read-only mirror of the docs/ directory in the Packstub Tenancy package, published for evaluation and reference. It is updated automatically — please report documentation issues via support@packstub.dev.