Skip to main content
Start here to choose the right Admin9 Labs documentation path before jumping into product setup, admin operations, or repository exploration.

​
Pick your path

Admin9 variants

Compare the single-tenant admin9 product with the multi-tenant admin9-tenancy variant and see which docs are shared.

Shared docs

Use the main Admin9 docs for installation, architecture, guides, and release work shared by both variants.

Tenancy supplement

Read the multi-tenant addendum when tenant scoping, provisioning, or tenant-level operations matter.

Open source portfolio

Explore the public repositories, starters, and reusable packages maintained by Admin9 Labs.

​
Documentation structure

This site is organized into three primary documentation areas:
  • docs for shared product setup, development, architecture, guides, and release workflows
  • admin docs for operator-facing panel workflows
  • open source docs for public repositories and reusable packages
Within the main docs, admin9 is the single-tenant variant and admin9-tenancy is the multi-tenant variant. Most pages are shared; multi-tenant-only differences are collected in the tenancy supplement.

​
What the main Admin9 docs cover

  • launch a subscription SaaS with an admin panel and user dashboard
  • manage products, plans, pricing, discounts, invoices, and transactions
  • support Stripe, Paddle, Lemon Squeezy, or offline payment flows
  • ship authentication, verification, and social login flows for customer-facing products
  • ship localized, themeable frontend pages with built-in operational tooling

​
Fast path

Review variants

Decide whether you are working in the single-tenant or multi-tenant product before applying the shared guides.

Install the product

Set up the shared Admin9 stack from source with the current Laravel, Livewire, and Filament stack.

Run locally

Bring up MySQL, Redis, Vite, queues, and the main application surfaces.

Read tenancy notes

Apply the multi-tenant differences where tenant boundaries affect architecture or operations.

​
Current stack

The current codebase depends on:
  • PHP 8.2+
  • Laravel 12
  • Livewire 4
  • Filament 5
  • Tailwind CSS 4
  • DaisyUI 5
  • Vite 7
  • Laravel Sanctum for API tokens
  • Laravel Horizon for Redis-backed queues

​
What the shared Admin9 platform includes

  • Admin panel at /admin for product, content, revenue, and settings management
  • User dashboard at /dashboard
  • Subscription checkout and one-time purchase checkout
  • Stripe, Paddle, Lemon Squeezy, and offline payment flows
  • OAuth social login providers
  • Two-factor authentication
  • Role and permission management
  • Blog, roadmap, announcement, FAQ, and legal page support
  • Multi-language frontend routing with localized URLs
  • Theme switching with DaisyUI themes and Filament synchronization
  1. Start with Admin9 Product Variants to identify whether you are working on the single-tenant or multi-tenant product.
  2. Continue with Installation and Local Development.
  3. Read Architecture Overview and the shared guides.
  4. If you are on admin9-tenancy, add Admin9 Tenancy Supplement anywhere tenant concerns affect the implementation.
  5. Use Commands and Endpoints and Release Checklist before shipping.
If you work primarily in /admin, switch to the Admin Overview after the installation flow. If you are reviewing the public repository portfolio rather than deploying an Admin9 product, switch to Open Source Overview.

​
Core guides

If prose and product behavior ever disagree, treat the relevant product repository as authoritative.