One framework. Three paths.
Real SaaS.
Tiger is a complete application platform — not a page builder, not a vibe-coding toy, not a plugin maze. Whether you're designing a website, prompting an AI to build your app, or writing enterprise code, it's the same real framework underneath.
Three ways in. One platform underneath.
Start wherever you are — the framework is the same, so you never migrate or rebuild to grow.
= $p[1] ?>
= $p[3] ?>
- = $b ?>
Included — not bolted on
Everything below ships with Tiger. No plugins, no third-party services, no per-feature pricing.
| Tiger | WordPress | Vibe platforms | |
|---|---|---|---|
| = $row[0] ?> | = $row[1] ?> | = $row[2] ?> | = $row[3] ?> |
N-Tier Architecture
Not opinionated. Structured.
The Backend's Separation of Concerns.
Four clean tiers, each with one job and one neighbour. A request flows down through them and the response flows back up — so there's exactly one place for everything, and your AI always knows where to look.
And the view tier itself? Everything is a partial.
The presentation layer uses one clean composition model — just different roles in the hierarchy, all stored in one table, all rendered the same way, all introspectable by AI. The builder edits blocks; the framework controls partials; you never break the structure by editing content.
And the frontend? Just the web platform.
The heavy frontend frameworks were invented
to assist human programmers manage the UI/UX and paper over what browsers couldn't do a decade
ago. But we don't live in that era anymore, so Tiger renders on the platform itself: semantic HTML,
Bootstrap for mobile-first, with CSS variables, and vanilla JavaScript. No build step, no bundler,
no node_modules. Bring a framework if you really want one; but in the modern era, you
don't need it.
Everything you need for a world-class scalable app, and nothing you don't.
Not a feature. The architecture.
Your app is a directory and a database. TigerBackup is the whole migration story:
Runs on any box with PHP and MariaDB — a $5 VPS, a TigerDen instance, a Raspberry Pi, a Docker container on your laptop. It doesn't phone home. It doesn't need four vendors to agree to serve a page. That's real portability — not "export to GitHub and pray."
The vibe-coding stack vs. Tiger
| Vibe-coding stack | Tiger | |
|---|---|---|
| = $row[0] ?> | = $row[1] ?> | = $row[2] ?> |
WordPress vs. Tiger
| WordPress | Tiger | |
|---|---|---|
| = $row[0] ?> | = $row[1] ?> | = $row[2] ?> |
Every path gets you the same platform
Same features, same architecture, same portability — pick your on-ramp.
TigerDen
Your own instance on AWS, Tiger pre-installed — TigerSSL, TigerShield, TigerPASS included. No DevOps required.
TigerInstall
Already have hosting? One-click setup on any standard LAMP host.
Tiger + Composer
Tiger + Docker
No open-core bait-and-switch. No surprises.
Tiger is free, open-source software under BSD-3. No "community edition" missing half the features, no relicensing threats. Build what you want, deploy where you want, keep everything you build.