Skip to content
TesseraQL

The five-minute demo

One command boots a complete, seeded, browsable app with Studio open (roadmap Phase 47).

One command

Section titled “One command”
Terminal window
tesseraql serve --app examples/inventory-app --embedded-db

No database, no compose: an embedded PostgreSQL starts inside the process, the app’s migrations create and seed the schema, and every route serves immediately. Any gallery app works the same way (purchase-request-app, helpdesk-app, scaffold-demo-app).

Or as one container:

Terminal window
docker build -f deploy/Dockerfile.demo -t tesseraql-demo .
docker run --rm -p 8080:8080 tesseraql-demo

The Studio tour

Section titled “The Studio tour”

Open http://localhost:8080/_tesseraql/studio and walk the loop the framework is built around — every stop is live against the seeded data:

  1. Explorer — every route, view, job and workflow the app serves, straight from the files on disk. Open web/products/get.yml: the whole page is one YAML document and one 2-way SQL file.
  2. Data browser — the seeded rows (opt-in via tesseraql.studio.dataBrowser.enabled). Filter, sort, export CSV; with the row editor enabled, fix a value under audit + confirm.
  3. The instant loop — edit the SQL in the source editor, apply, and the running page changes; scaffold a CRUD slice from a table and its pages serve immediately; create a migration and press Migrate now. No restart anywhere.
  4. Tests — open a route and run its declarative suite in the sandbox; record a new case from the API console with one click.
  5. Docs portal — the generated documentation: routes, schema, coverage, the release diff. tesseraql admission --app . is the bar a shared app must clear.
  6. Dashboards — /products/dashboard renders stats, a chart and a low-stock table from three SQL files and one view: dashboard document. No HTML anywhere in the app.

Milestone M12 — the low-code loop, closed

Section titled “Milestone M12 — the low-code loop, closed”

The demo walks the milestone end to end: a semi-technical author adds a column and its screen behavior entirely in Studio — migration (created and applied with Migrate now, Phase 42), view (a declarative document, Phase 39), recorded test (the API console’s one click, Phase 43) — writing no HTML and never restarting; the change promotes through a release diff (Phase 46); and the route’s latency shows up on a scraped dashboard (Phase 45, deploy/grafana/tesseraql-dashboard.json). Each leg is held green by an integration test: the zero-restart M7 loop, the Studio test recorder, the release diff engine, and the Prometheus exposition.