Skip to content
For vibe coders & SaaS founders

A secure MVP in minutes, not days.

Tiger hands you the boring-but-essential SaaS substrate — auth, orgs, roles, billing-ready multi-tenancy, i18n, and a clean /api — so you and your AI pair ship product from the first commit, on a stack that won't buckle when it works.

Start building Read the docs

Ship product, not plumbing

The unglamorous 80% every SaaS needs — already built, already secure. Spend your runway on the thing only you can build.

Auth that would take weeks

Passwords with policy + lockout, email codes, TOTP 2FA, password reset, DB sessions, and an audit log — wired, not a to-do.

Multi-tenant from commit one

Orgs, users, and memberships are the model, not a refactor you dread at 500 customers. Billing-ready when you are.

Roles & permissions

A deny-by-default ACL with roles on the membership. Gate a feature with a rule, not an if-branch you forget to write.

One clean /api

A single endpoint, the message says where it goes. Add a method and it's live — no route zoo, and it feeds a mobile app or SPA later for free.

Vibe-code that doesn't rot

Your AI reads the rules before it writes

Tiger ships an AGENTS.md and predictable, documented patterns your assistant ingests first — so "add a billing service" lands as a real service, with its ACL rule, its form, and its /api method, in the house style. Describe the feature; the conventions keep it clean.

  • Docs that live in the code — one obvious way to do each thing.
  • make:module scaffolds a live controller + service + ACL in seconds.
  • A generated API reference, straight from your docblocks.
# describe it to your AI, get a real, secured endpoint
$ vendor/bin/tiger make:module billing
→ Billing_Service_Invoice::create()  // validate → transaction
→ configs/acl.ini  // deny-by-default rule
→ POST /api {module:billing, service:invoice, method:create}

Enterprise-shaped MVP

Audit logging, per-tenant ACL, secure sessions, i18n, live config — the substrate that wins enterprise deals ships with your first commit, so your MVP is production-shaped, not a rewrite-in-waiting.

responds in
~10 ms

A lean core with no per-request framework bloat — steady at the median and the tail. Fast is the default, so a good launch-day spike doesn't become an outage.

runs on
a $5 host

Zero build step, tiny footprint — Tiger runs on cheap shared hosting the heavy frameworks can't even boot on. Keep the burn on your idea, not your infra bill.

~10 ms measured (single warm request, 2‑vCPU box, PHP 8 + OPcache) — not a controlled benchmark; results vary by workload and hardware.

From idea to a secure, running app today

One command scaffolds a running, themed, multi-tenant app — then vibe on.

$ composer create-project webtigers/tiger my-app
$ cd my-app && vendor/bin/tiger install:admin