Manage Your Laravel Multi-Tenant SaaS From a Chat Widget (v1.3.1)

#laravel #saas #opensource #ai

If you run a multi-tenant Laravel SaaS, you already know the drill:

Open Filament → find the workspace
Check billing in another tab
Invite someone via API docs or a form

It works — but it's not how you want to feel your own product.

Laravel Tenant Kit v1.3.1 adds an in-app guided agent: a floating chat on the central domain that walks you through workspaces, usage, subscriptions, and team invites — step by step, with confirm/cancel for dangerous actions.

The brain behind it is api-operator — a separate Python package on PyPI. Tenant Kit stays PHP-only; the operator runs as a sidecar.

What the guided agent does

Flow	Example
Workspaces	List workspaces, create one (name → subdomain → confirm)
Billing	Usage and subscription for a workspace
Team	Invite a teammate (email → workspace → role → confirm)

Tokens stay server-side — the browser talks to Laravel (/api-operator/chat), Laravel talks to api-operator. No Sanctum token in the frontend.

Quick start with Docker (Windows)

git clone https://github.com/mohammedelkarsh/laravel-tenant-kit.git
cd laravel-tenant-kit
.\scripts\docker-setup.ps1

Open http://laravel-tenant-kit.test:8080/login

Login: admin@laravel-tenant-kit.test / password

Go to /dashboard → click the chat button (bottom-right).

Daily restart:

.\scripts\docker-up.ps1

Or use the CLI (api-operator on PyPI)

pip install api-operator==0.10.0
export TENANT_KIT_API_TOKEN="your-sanctum-token"

api-operator chat \
  --adapter yaml \
  --config integrations/api-operator/adapter.yaml \
  --base-url http://laravel-tenant-kit.test:8080

Full guide: docs/api-operator.md

Also in recent releases

v1.3.0 — usage-based billing meters (api_calls, team_seats)
v1.2.1 — API rate limiting, token abilities, workspace suspend, team invites API

Stack: Laravel 13 · PHP 8.4 · Filament 5 · Stancl Tenancy · Docker · 71 PHPUnit tests