Drag in any direction to rotate the 3D model. Scroll the page to turn the scene. Use arrow keys to rotate, Shift with left or right to roll, plus and minus to zoom, and Home to reset. On a touch screen, swipe sideways to start rotating, swipe up or down to scroll the page, and pinch to zoom the page.
SQLPage

SELECTa websiteFROM sql;

Turn your database into tools
you can share.

Run it
select 'list' as component; select 'chart' as component; select 'table' as component; select 'card' as component;

-- real SQLPage components, a few lines each

Data,
but clickable

-- pick a component

Actually rendered by
SQLPage, live 

select 'text' as component, 'Customers' as title;
select 'table' as component, 'landing-customers' as id,
    true as sort, true as search, 'status' as markdown;
select name, plan, status, seats, lower(status) as _sqlpage_css_class
from customers
order by id;

Explore the table component

-- Suspiciously few files.
Yes, that's the app.

-- Low maintenance, on purpose.

A useful tool for them.
A manageable
application for you.

You need a webapp,
but you don't want to maintain a webapp. Build it, or let your coding agent do it. Don't maintain 1000 lines of code.

An unshaved yak

-- The yak stays unshaved.
-- App maintenance is not a hobby.

-- What do you have to maintain?

  • Frontend to update
  • Build tooling to keep working
  • API server to patch
  • Session and state to keep in sync
  • Database you already own this

-- 5 layers, all yours.

10× fewer lines

Forms, tables and charts are components you call, not code you write and keep alive.

DROP the busywork;

Stateless

All state lives in the database. Scale by adding servers, deploy by copying files, restart whenever you like.

Agent-friendly

Small, declarative SQL files are easy for a coding agent to write and easy for you to review. Robots welcome. Humans too.

Bring your own robot.Agent not included.You're still the boss.

The database is the job

You already back it up, secure it and keep it healthy. That is the maintenance. The app just reads and writes.

-- Your files. Your deployment.

No frontend
to build.

-- read, edit, and act.
-- forms, tables, charts, and navigation.
-- Tables with manners. CRUD, but polite.

Instant by default.

HTML streams to the browser while the database is still working.

sql-page.com/performance

typical app (illustrative)

SQLPage

rendered on the server+ interactive in the browser

SELECT * FROM your_database;

Keep your
database. Add
the app.

We're seeing other databases. A healthy relationship model.

SQLite-- built in PostgreSQL-- native driver MySQL-- native driver MariaDB-- native driver SQL Server-- native driver Oracle-- through ODBC ClickHouse-- ODBC + pg protocol Snowflake-- through ODBC BigQuery-- through ODBC Databricks-- through ODBC DuckDB-- quack 🦆 👍 Db2-- yes, but why ?

-- A tool for them. Not a second job for you.

Small team.
Serious tools;

COMMIT; start with a query

DELETE busy;
-- NULL drama.