Self-host QuestDB with Levelrail

A fast time series database with SQL, a web console, the PostgreSQL wire protocol on 8812 and InfluxDB line protocol ingestion on 9009. The console and the PostgreSQL port share one generated password. Only the console is offered a domain.

  • Authorquestdb
  • LicenceApache-2.0
  • Memory1 GiB
  • Services1

How to self-host QuestDB

  1. Pull the images

    One image is pulled on your server.

    Show images
    • questdb/questdb:10.1.0
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on ports 9000, 8812, 9009.

  3. Fill in the secrets

    2 secrets are 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

  • Open the console. Queries ask for the user below and the generated password from the app secrets.

QuestDB requirements

Memory
About 1 GiB
Architectures
amd64 unknown, arm64 unknown
Ports
9000, 8812, 9009
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
Apache-2.0, 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 QuestDB. 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 QuestDB docs page.

Deploy QuestDB your way

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

Deploy QuestDB from the CLI

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

levelrail-cli templates install questdb --name my-questdb

Deploy QuestDB 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/questdb/install \
  -d '{
    "name": "my-questdb"
  }'

QuestDB configuration

QuestDB services

ServiceImagePortsVolumes
questdb questdb/questdb:10.1.0 9000, 8812, 9009 questdb_data -> /var/lib/questdb

QuestDB environment variables

VariableServiceValue
QDB_HTTP_PASSWORD questdb Generated at deploy
QDB_HTTP_USER questdb Preset by the template
QDB_PG_PASSWORD questdb Generated at deploy
QDB_PG_USER questdb Preset by the template
QDB_TELEMETRY_ENABLED questdb Preset by the template

Ports and volumes

Ports
9000, 8812, 9009
Volumes
1 named mount: questdb_data -> /var/lib/questdb

QuestDB FAQ

How much memory does QuestDB need?

The catalog lists about 1 GiB of memory for QuestDB.

Does QuestDB run on arm64?

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

What licence is QuestDB under?

QuestDB is licensed under Apache-2.0, which is permissive, with few conditions on reuse.

Does QuestDB need configuration before it starts?

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

Which ports does QuestDB use?

QuestDB listens on ports 9000, 8812 and 9009 inside the stack.

Where does QuestDB keep its data?

In a named volume: questdb_data mounted at /var/lib/questdb.

Can I deploy QuestDB 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 QuestDB, 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 questdb/questdb:10.1.0 is what you deploy there.

levelrail-cli templates install questdb --name my-questdb