There's no artisan schema:show, so I built one

Update: Truss now has a dedicated docs site and a public roadmap. See the notes at the end of this post for what’s changed since publishing.

Update: Truss 1.5 adds truss:doctor, a deterministic, structure-only review of your schema across thirteen rules, runnable from the terminal, CI, or the dashboard. Read more in The schema doctor is in.

You join a project. Forty tables, half of them undocumented, and a posts table that somehow relates to three other tables you’ve never heard of. Where do you start?

php artisan db gets you an interactive shell, and from there you’re back to whatever dialect your database speaks: .schema on SQLite, DESCRIBE on MySQL, \d on Postgres. Laravel’s own db:show and db:table commands are a step up, an overview of your tables or one table’s columns, indexes, and foreign keys, printed straight to the terminal. But they’re still one table at a time, in text. Nothing shows you the shape of the thing: which tables actually connect, and how, across the whole schema. So you end up either opening a DB client through an SSH tunnel, or drawing the diagram yourself on a whiteboard from memory, which is exactly as reliable as it sounds.

And that’s the easy case, when you have shell access at all. On staging or production, where you actually need this the most because that’s where the real schema drifted from the migrations, you often don’t have a shell. Some organisations block SSH outright for compliance, which is exactly the situation I wrote about replacing with AWS Systems Manager for running Artisan commands. Even with a Run Command session in hand, that gets you a shell again, not a diagram.

So I built Truss.

What it does

Truss is a live database structure viewer for Laravel. It scans your actual schema, not your migration files, and renders it as a scrollable, zoomable ER diagram right inside your app.

• Live ER diagram, rendered with Mermaid, of every table and how it connects.
• Focus mode: click a table to isolate it and its foreign-key neighbours, centred and highlighted, so you’re not staring at forty tables to understand one.
• Filter by table name, and toggle native column types against Laravel-style labels.
• Map-style pan and zoom, with auto-fit.
• Structure only, always. Truss reads tables, columns, keys, and indexes. It never queries a single row, which is the whole point of being able to run it somewhere that matters.
• Self-contained: Mermaid and fonts are vendored and served from the package, so it works offline and under a strict CSP. No CDN, nothing phoning home.
• Cached and automatic: the snapshot rebuilds after migrations, so the diagram never goes stale.
• Export the whole diagram as PNG or SVG, exactly as it’s currently filtered and focused, so it drops straight into a design doc or a PR description instead of a screenshot. Per-table exports as JSON or CSV are also available from each table’s menu, and the whole schema can be saved as a Markdown data dictionary or a DBML file.

Install it, visit /truss, and you get the diagram. No config, no separate service to run.

composer require albertoarena/laravel-truss

By default it’s only enabled locally. To use it on staging or production you explicitly enable it and gate access behind a viewTruss authorization gate, so “safe to run in prod” doesn’t mean “wide open in prod”.

From the command line, too

db:show and db:table get you close, but they’re still one table at a time, in text. php artisan truss:show prints that same cached, exclusion-filtered snapshot the diagram uses, as a table: one row per database table, with its column count and foreign-key count, the whole schema at once instead of one piece of it.

php artisan truss:show   # the whole schema as a table, in your terminal
php artisan truss:open   # or jump straight to the diagram

php artisan truss:open opens the dashboard in your default browser, honouring the route prefix and app URL. It prints the URL regardless, so it still works over a forwarded port on a headless host with no browser for it to open.

Both commands live under a truss: namespace rather than schema:. A package squatting Laravel’s own schema: namespace is asking for a collision if the framework ever ships a schema:show of its own, which is the joke in this post’s title.

Trying it without installing anything

If you want to poke at it before adding it to a project, there’s a live demo running against a fictional schema, right in your browser. Pan, zoom, filter, focus a table, no install required.

How it’s held up

I’ve dropped Truss into a few of my own Laravel projects since building it, including ones I hadn’t touched in a while, and it’s the fastest I’ve re-oriented myself in a schema I half-remembered. Clicking through foreign keys in focus mode beats reconstructing the relationships from migration file names, every time.

Get started

The documentation covers installation, the quick start, and authorization for non-local environments in more detail. It requires PHP 8.3+ and Laravel 12+. There’s also a public roadmap: schema diff, seeing what changed since the last migration, is next up.

Feedback welcome, as always.

Notes

On July 29, 2026, Truss reached v1.3.1: a data dictionary and DBML export shipped in v1.3.0, and v1.3.1 scoped schema introspection to the connection’s own database so a shared server no longer leaks tables from other databases. Docs also moved to a dedicated site, trussphp.com, with a public roadmap.

On July 31, 2026, Truss reached v1.5.0, adding truss:doctor: a deterministic, structure-only review of your schema across thirteen rules spanning integrity, indexes, and types, runnable from the terminal, CI, or the dashboard’s new Health panel. See The schema doctor is in.