Arc Launchpad

A self-hosted web UI for Arc — the high-performance columnar analytical database.

Arc Launchpad connects to one or more existing Arc instances and gives you a browser-based interface for running SQL, exploring schemas, browsing logs, managing tokens and retention policies, setting up alerts and continuous queries, and inviting teammates into shared organizations.

It does not provision or host databases. You point it at Arc instances you already run (by endpoint URL + admin token), and it stores only those connection details plus your accounts/teams in a local SQLite database.

Features

• SQL console with schema explorer, query history, and multi-tab editing
• Logs viewer with pattern detection and trace extraction
• Token management and retention policies for your Arc instances
• Alerts and continuous queries
• Organizations & teams — invite users, assign roles
• Local auth — email/password with optional MFA (TOTP) and passkeys (WebAuthn)

Tech stack

• Runtime: SvelteKit + Node.js (adapter-node)
• Storage: SQLite (accounts, teams, connection records)
• Auth: session JWTs, bcrypt password hashing, optional TOTP MFA + WebAuthn passkeys

Quick start (local)

Requires Node.js 20+.

npm install
cp .env.example .env        # then edit .env — set LAUNCHPAD_JWT_SECRET at minimum
npm run dev                 # http://localhost:5173

The first account you create becomes the admin. After that, self-service signup is closed — additional users join by admin invitation only.

Configuration

All configuration is via environment variables. See .env.example for the full annotated list. The only strictly required variable is:

Variable	Purpose
LAUNCHPAD_JWT_SECRET	Secret used to sign session tokens. The app refuses to start in production without it. Generate one with openssl rand -hex 32.

Email (Mailgun), signup CAPTCHA (Cloudflare Turnstile), ops alerting (Google Chat), and GitHub/Google OAuth are all optional — without them, those features are simply skipped (e.g. emails print to the console instead of being sent).

Production build

npm run build
LAUNCHPAD_JWT_SECRET=$(openssl rand -hex 32) node build

The server listens on $PORT (default 3000).

Docker

Use the published image (latest, or pin a version tag from the releases):

docker run -p 3000:3000 \
  -e LAUNCHPAD_JWT_SECRET=$(openssl rand -hex 32) \
  -v launchpad-data:/app/data \
  ghcr.io/basekick-labs/launchpad:latest

The SQLite database is written to /app/data/launchpad.db — mount a volume there to persist it.

Docker Compose

curl -O https://raw.githubusercontent.com/basekick-labs/launchpad/main/docker-compose.yml
LAUNCHPAD_JWT_SECRET=$(openssl rand -hex 32) docker compose up -d

The compose file uses ghcr.io/basekick-labs/launchpad:latest and a named volume for the data.

Helm

helm install launchpad oci://ghcr.io/basekick-labs/charts/launchpad \
  --set jwtSecret=$(openssl rand -hex 32) \
  --set baseUrl=https://launchpad.example.com

Or from a release chart archive:

# grab launchpad-<version>.tgz from the latest GitHub Release
helm install launchpad ./launchpad-*.tgz --set jwtSecret=$(openssl rand -hex 32)

Common values (see helm/launchpad/values.yaml for the full list):

Value	Default	Purpose
jwtSecret	""	Required unless existingSecret is set. Signs session tokens.
existingSecret	""	Name of a pre-created Secret holding LAUNCHPAD_JWT_SECRET instead.
baseUrl	http://localhost:3000	Public URL (email links + passkey origin).
persistence.size	1Gi	PVC size for the SQLite database.
ingress.enabled	false	Enable to expose via an Ingress.

Connecting to an Arc instance

After signing in, add a connection with your Arc instance's endpoint URL (e.g. http://localhost:8000) and an admin token. Arc Launchpad verifies the connection and then lets you query and manage that instance.

License

Apache-2.0.