SQLPage
Self-HostedBuild web apps using only SQL queries—no frontend code required
Overview
SQLPage lets developers and data analysts create interactive web apps directly from SQL databases without writing HTML/CSS/JS. It supports PostgreSQL, SQLite, MySQL, and MariaDB, with built-in UI components (tables, charts, forms, buttons). Deployment is simple: use a standalone binary (no dependencies) or Docker container. Ideal for internal tools, dashboards, or quick prototypes, it focuses on data logic over frontend complexity. Open-source under MIT License, it’s perfect for self-hosted, SQL-first solutions.
Self-Hosting Resources
Below is a reference structure for docker-compose.yml.
⚠️ Do NOT run blindly. Replace placeholders with official values.
version: '3'
services:
sqlpage:
image: <OFFICIAL_IMAGE_NAME>:latest
container_name: sqlpage
ports:
- "8080:<APP_INTERNAL_PORT>"
volumes:
- ./data:/app/data
restart: unless-stopped Key Features
- Build web apps with only SQL (no frontend code)
- Supports PostgreSQL, SQLite, MySQL, MariaDB
- Built-in UI components (tables, charts, forms)
- Standalone binary or Docker deployment
Frequently Asked Questions
? Is SQLPage hard to install?
No—SQLPage can be installed as a standalone binary (download and run, no dependencies) or via Docker with a simple command. It takes minutes to set up and connect to your database.
? Is it a good alternative to Retool?
Yes, for SQL-savvy teams. SQLPage is open-source and self-hosted (avoiding Retool’s subscription costs), but Retool offers more visual customization for non-SQL users.
? Is SQLPage completely free?
Yes! SQLPage is licensed under MIT, so it’s free to use, modify, and self-host with no paid plans or hidden fees.
Top Alternatives
People Also Ask about SQLPage
Tool Info
Pros
- ⊕ No frontend skills needed (SQL-only workflow)
- ⊕ Fast prototyping for internal tools/dashboards
- ⊕ Self-hosted (data stays on-premises)
- ⊕ Zero dependencies for binary installation
Cons
- ⊖ Requires SQL knowledge to use effectively
- ⊖ Limited UI customization for complex apps
- ⊖ Not ideal for public-facing apps with advanced frontend needs