2600 stars · MIT (named in the About sidebar) · v0.47.0 (2026-10-16), read from /releases/latest as '16 Oct' and dated by the run · Track this in Scout
A single-executable web server that turns SQL query results into real web pages, forms and charts.
Radar check
What we found when we opened it. Every bar is one fact, with its date.
Last code pushed 24 Oct 2026, one day before this check.
Latest release v0.47.0 on 16 Oct 2026.
Public since July 2022, a little over 4 years.
2,579 stars and 177 forks.
156 commits and 30 new issues in the last 90 days.
53 contributors. 131 pull requests merged in 90 days.
A security policy says how to report a problem. 1 published security advisory.
How the bars are scored
- Alive. Days since the last code push: a week or less 100, a month 90, three months 70, six months 50, a year 30, eighteen months 15, older 0.
- Releases. Age of the latest GitHub release, on a similar scale; no bar when the project publishes no releases.
- Maturity. Age of the project: eight years 100, five 90, three 70, two 55, one 40, six months 25, younger 10.
- Adoption. Stars on a log scale: 100,000 stars is 100, 10,000 is 80, 1,000 is 60, 100 is 40.
- Activity. Commits in the last 90 days: 300 or more 100, 100 85, 30 65, 10 45, any 25.
- Community. People who have contributed: 100 or more 100, 30 80, 10 60, 5 40, 2 25, one 10.
- Security. A published security policy 80, none 40; published advisories are listed, not scored.
Checked by Repo Radar on 26 Oct 2026 from the repository on GitHub. Covered in Edition 62.
▶Repo detailsthe review · specs · pros & cons · install
What it does
You create files ending in .sql. Each file holds queries, and each query names a component — text, list, grid, chart, form, table — in its first column. SQLPage runs the file against the database when someone asks for that address and renders the components in order. Forms post back to another .sql file, which can run an INSERT or an UPDATE, so the pages write as well as read. It ships as one executable with HTTPS and HTTP/2 built in, and it connects to SQLite, PostgreSQL, MySQL, Microsoft SQL Server, and anything reachable through an ODBC driver, which covers ClickHouse, DuckDB, Snowflake and BigQuery. It is a web server and not a database, and not a desktop application either: it connects to a database that already exists somewhere else.
Why it matters
Who it suits. Anyone who knows SQL well and web development barely at all, and needs a page that other people can use. Internal dashboards, data entry screens for a small team, a report a manager can open without asking anyone. It also suits a developer who simply does not want to build a frontend for a tool five people will use. Skip it if the thing being built is a public product with its own design, because the components are deliberately fixed and you will spend longer fighting them than writing the page.
Verdict. The most interesting thing in today's edition, and the one most likely to save a reader a week. Version 0.47.0 was released on 16 October 2026 under the MIT licence, and it is at 2,600 stars, which is far less attention than it deserves. The honest limits are worth stating. Release binaries cover Linux and Windows on Intel and AMD processors and macOS on Apple silicon; an Intel Mac means Homebrew or building from source. ODBC connections need the database's own driver installed separately, so the long list of supported engines is not all equally easy. And the fixed component set is a real ceiling, not a temporary one. Against that, the comparison is instructive: simonw/datasette publishes and explores data, where SQLPage builds an application that writes back.
- A working web page from SQL alone. No JavaScript, no build step, no second language.
- One executable, with HTTPS and HTTP/2 included.
- Forms write back to the database, so these are real tools and not just reports.
- Fixed components. The look is what it is, and that is a hard limit for anything public-facing.
- No release binary for Intel Macs, so those need Homebrew or a build from source.
- ODBC databases need their own driver installed, which is more work than the supported list suggests.
simonw/datasette11.4k stars, Apache-2.0; publishes an existing database as a browsable site with an interface for other programs. Read-only, where SQLPage writes.
Track this in Scout
evidence-dev/evidence7.0k stars, MIT; reports written as SQL inside Markdown, built into a static site. Better-looking output, no forms and no live writes.
Track this in Scout
mkdir mysite && cd mysite
mkdir sqlpage
echo '{ "database_url": "sqlite://./data.db?mode=rwc" }' > sqlpage/sqlpage.json
printf "select 'text' as component, 'It works.' as contents;\n" > index.sql
./sqlpage
