SQLpage is an SQL-only webapp builder. It is meant for data scientists, analysts, and business intelligence teams to build powerful data-centric applications quickly, without worrying about any of the traditional web programming languages and concepts.

With SQLPage, you write simple .sql files containing queries to your database to select, group, update, insert, and delete your data, and you get good-looking clean webpages displaying your data as text, lists, grids, plots, and forms.

SELECT 
    'list' as component,
    'Popular websites' as title;
SELECT 
    name as title,
    url as link,
    CASE type
      WHEN 1 THEN 'blue'
      ELSE 'red'
    END as color,
    description, icon, active
FROM website;

SELECT
  'chart' as component,
  'Quarterly Revenue' as title,
  'area' as type;

SELECT
    quarter AS x,
    SUM(revenue) AS y
FROM finances
GROUP BY quarter

SELECT
    'form' as component,
    'User' as title,
    'Create new user' as validate;

SELECT
    name, type, placeholder,
    required, description
FROM user_form;

INSERT INTO user
SELECT $first_name, $last_name, $birth_date
WHERE $first_name IS NOT NULL;

select 'tab' as component, true as center;
select 'Show all cards' as title, '?' as link,
  $tab is null as active;
select
  format('Show %s cards', color) as title,
  format('?tab=%s', color) as link,
  $tab=color as active
from tab_example_cards
group by color; 


select 'card' as component;
select
  title, description, color
  image_url as top_image, link
from tab_example_cards
where $tab is null or $tab = color;

select
  'text' as component,
  sqlpage.read_file_as_text('footer.md') as contents_md

• SQLite, including the ability to load extensions such as Spatialite.
• PostgreSQL, and other compatible databases such as YugabyteDB, CockroachDB and Aurora.
• MySQL, and other compatible databases such as MariaDB and TiDB.
• Microsoft SQL Server, and all compatible databases and providers such as Azure SQL and Amazon RDS.

SQLPage is a web server written in rust and distributed as a single executable file. When it receives a request to a URL ending in .sql, it finds the corresponding SQL file, runs it on the database, passing it information from the web request as SQL statement parameters. When the database starts returning rows for the query, SQLPage maps each piece of information in the row to a parameter in one of its pre-defined components' templates, and streams the result back to the user's browser.

Read the official get started guide on SQLPage's website.

The easiest way to get started is to download the latest release from the releases page.

• Download the binary that corresponds to your operating system (linux, macos, or windows).
• Uncompress it: tar -xzf sqlpage-*.tgz
• Run it: ./sqlpage.bin

To run on a server, you can use the docker image:

• Install docker
• In a terminal, run the following command:
  • docker run -it --name sqlpage -p 8080:8080 --volume "$(pwd):/var/www" --rm lovasoa/sqlpage
  • ("$(pwd):/var/www" allows sqlpage to run sql files from your current working directory)
• Create a file called index.sql with the contents from this example
• Open https://localhost:8080 in your browser
• Optionally, you can also mount a directory containing sqlpage's configuration file, custom components, and migrations (see configuration.md) to /etc/sqlpage in the container.
  • For instance, you can use:
    • docker run -it --name sqlpage -p 8080:8080 --volume "$(pwd)/source:/var/www" --volume "$(pwd)/configuration:/etc/sqlpage:ro" --rm lovasoa/sqlpage
  • And place your website in a folder named source and your sqlpage.json in a folder named configuration.
• If you want to build your own docker image, taking the raw sqlpage image as a base is not recommended, since it is extremely stripped down and probably won't contain the dependencies you need. Instead, you can take debian as a base and simply copy the sqlpage binary from the official image to your own image:

  • FROM debian:stable-slim
    COPY --from=lovasoa/sqlpage:main /usr/local/bin/sqlpage /usr/local/bin/sqlpage

We provide compiled binaries only for the x86_64 architecture, but provide docker images for other architectures, including arm64 and armv7. If you want to run SQLPage on a Raspberry Pi or a cheaper ARM cloud instance, using the docker image is the easiest way to do it.

An alternative for Mac OS users is to use SQLPage's homebrew package.

• Install homebrew
• In a terminal, run the following commands:
  • brew install sqlpage

• TODO list: a simple todo list application, illustrating how to create a basic CRUD application with SQLPage.
• Plots, Tables, forms, and interactivity: a short well-commented demo showing how to use plots, tables, forms, and interactivity to filter data based on an URL parameter.
• Tiny splitwise clone: a shared expense tracker app
• Corporate Conundrum: a board game implemented in SQL
• Master-Detail Forms: shows how to implement a simple set of forms to insert data into database tables that have a one-to-many relationship.
• SQLPage's own official website and documentation: The SQL source code for the project's official site, https://sql.ophir.dev
• Image gallery: An image gallery where users can log in and upload images. Illustrates the implementation of a user authentication system using session cookies, and the handling of file uploads.
• User Management: An authentication demo with user registration, log in, log out, and confidential pages. Uses PostgreSQL.
• Making a JSON API and integrating React components in the frontend: Shows how to integrate a react component in a SQLPage website, and how to easily build a REST API with SQLPage.
• Handling file uploads: An image gallery where authenticated users can publish new images via an upload form.
• Bulk data import from CSV files : A simple form letting users import CSV files to fill a database table.
• Advanced authentication example using PostgreSQL stored procedures
• Complex web application in SQLite with user management, file uploads, plots, maps, tables, menus, ...
• Single sign-on: An example of how to implement OAuth and OpenID Connect (OIDC) authentication in SQLPage. The demo also includes a CAS (Central Authentication Service) client.
• Dark theme : demonstrates how to let the user toggle between a light theme and a dark theme, and store the user's preference.

You can try all the examples online without installing anything on your computer using SQLPage's online demo on replit.

SQLPage can be configured through either a configuration file placed in sqlpage/sqlpage.json or environment variables such as DATABASE_URL or LISTEN_ON.

For more information, read configuration.md.

Additionally, custom components can be created by placing .handlebars files in sqlpage/templates. Example.

SQLPage supports HTTP/2 and HTTPS natively and transparently. Just set SQLPAGE_HTTPS_DOMAIN=example.com, and SQLPage will automatically request a trusted certificate and start encrypting all your user's traffic with it. No tedious manual configuration for you, and no annoying "Connection is Not Secure" messages for your users !

You can run SQLpage serverless by compiling it to an AWS Lambda function. An easy way to do so is using the provided docker image:

 docker build -t sqlpage-lambda-builder . -f lambda.Dockerfile --target builder
 docker run sqlpage-lambda-builder cat deploy.zip > sqlpage-aws-lambda.zip

You can then just add your own SQL files to sqlpage-aws-lambda.zip, and upload it to AWS Lambda, selecting Custom runtime on Amazon Linux 2 as a runtime.

When running serverless, you can include the SQL files directly in the image that you are deploying. But if you want to be able to update your sql files on the fly without creating a new image, you can store the files directly inside the database, in a table that has the following structure:

CREATE TABLE sqlpage_files(
  path VARCHAR(255) NOT NULL PRIMARY KEY,
  contents BLOB,
  last_modified TIMESTAMP DEFAULT CURRENT_TIMESTAMP
);

Make sure to update last_modified every time you update the contents of a file (or do it inside a TRIGGER). SQLPage will re-parse a file from the database only when it has been modified.

• actix web handles HTTP requests at an incredible speed,
• tabler handles the styling for professional-looking clean components,
• tabler icons is a large set of icons you can select directly from your SQL,
• handlebars render HTML pages from readable templates for each component.

Why would I want to write SQL instead of a real programming language? SQL is not even Turing-complete!

• You are probably worrying about the wrong thing. If you can express your application in a purely declarative manner, you should propably do it, even if you are using a traditional programming language. It will be much more concise, readable, easy to reason about and to debug than any imperative code you could write.
• SQL is much more simple than traditional programming languages. It is often readable even by non-programmers, and yet it is very powerful.
• If you really want to make your website more complicated than it needs to be, please note that SQL is actually Turing-complete.
• Even if it wasn't (if it didn't have recursive queries), a sequence of SQL statement executions driven by an user, like SQLPage allows you to do, would still be Turing-complete. You could build a sql website representing a Turing machine where the user would have to click "next" repeatedly to compute the next state of the machine.

Just Because You Can Doesn’t Mean You Should...

— someone being mean on reddit

Life's too short to always play it safe. Where's the fun in should? I think SQLPage has some real value to offer, despite its unconventional approach ! SQLPage isn't intended to replace traditional web development frameworks or discourage their usage. Instead, it caters to a specific group of people who want to leverage their SQL skills to rapidly build web applications, without spending months learning all of the technologies involved in traditional web development, and then weeks using them to build a simple CRUD application.

Is this the same as Microsoft Access?

The goal is the same: make it easy to create simple data-centric applications. But the tools are very different:

• SQLPage is a web server, not a desktop application.
• SQLPage is not a database, it connects to real battle-tested databases. Microsoft Access tries to be a database, and it's not very good at it.
• Microsoft Access is an expensive proprietary software, SQLPage is open-source.
• Microsoft Access is a zombie that will stab you in the back, SQLPage won't.
• SQLPage will not tortue you with Visual Basic for Applications.

Is the name a reference to Microsoft Frontpage ?

Frontpage was a visual static website building software popular in the late 90s. I had never heard of it before someone asked me this question.

I like CSS, I want to design websites, not write SQL.

Are you human ? Human beings hate CSS.

The take of SQLPage is that you should not spend time designing the border radius of your buttons until you have a working prototype. We provide a set of components that look decent out of the box, so that you can focus on your data model instead.

However, if you really want to write your own HTML and CSS, you can do it by creating your own components. Just create a .handlebars file in sqlpage/templates and write your HTML and CSS in it. (example)