Self-host SQLPad with Levelrail

Web based SQL editor for running queries against many databases, with saved queries, charts and sharing. The admin account is created from the install form.

  • Authorsqlpad
  • LicenceMIT
  • Memory256 MiB
  • Services1

How to self-host SQLPad

  1. Pull the images

    One image is pulled on your server.

    Show images
    • sqlpad/sqlpad:7.5.7
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 3000.

  3. Fill in the secrets

    1 secret is generated and stored encrypted, 3 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

After the first start

  • Sign in with the admin email and the generated password shown in the deployment variables, then add a connection to your database.

SQLPad requirements

Memory
About 256 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
3000
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
MIT, permissive license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then SQLPad. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the SQLPad docs page.

Deploy SQLPad your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy SQLPad from the CLI

Add --domain SERVICE=HOST to serve a service on your own domain, for example --domain sqlpad=app.example.com.

levelrail-cli templates install sqlpad --name my-sqlpad

Deploy SQLPad with the API

Create a token in the dashboard first. Name, env and domains are the request fields.

curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  https://levelrail.example.com/api/v1/service-templates/sqlpad/install \
  -d '{
    "name": "my-sqlpad"
  }'

SQLPad configuration

SQLPad services

ServiceImagePortsVolumes
sqlpad sqlpad/sqlpad:7.5.7 3000 data -> /var/lib/sqlpad

SQLPad environment variables

VariableServiceValue
SQLPAD_ADMIN sqlpad Preset by the template
SQLPAD_ADMIN_PASSWORD sqlpad Generated at deploy
SQLPAD_APP_LOG_LEVEL sqlpad Preset by the template
SQLPAD_DB_PATH sqlpad Preset by the template

Ports and volumes

Ports
3000
Volumes
1 named mount: data -> /var/lib/sqlpad

SQLPad FAQ

How much memory does SQLPad need?

The catalog lists about 256 MiB of memory for SQLPad.

Does SQLPad run on arm64?

For SQLPad, arm64 support is not confirmed; amd64 is unknown.

What licence is SQLPad under?

SQLPad is licensed under MIT, which is permissive, with few conditions on reuse.

Does SQLPad need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which ports does SQLPad use?

SQLPad listens on port 3000 inside the stack.

Where does SQLPad keep its data?

In a named volume: data mounted at /var/lib/sqlpad.

Can I deploy SQLPad on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for SQLPad, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image sqlpad/sqlpad:7.5.7 is what you deploy there.

levelrail-cli templates install sqlpad --name my-sqlpad