Readyset Docs

Web UI

Start a local HTTP server that backs the RDST web client: a browser-based alternative to the CLI.

rdst web serves RDST's interface in a local browser. Use it for Continuous monitoring when you can't install the desktop app. Keep the server running to collect readings; a browser tab is only required for browser notifications.

The CLI and desktop app share targets, saved queries, and analyses under the same operating system user. Run one monitoring backend for a data directory to avoid duplicate background checks.

Start the server

# Default: 127.0.0.1:8787
rdst web

Then open http://localhost:8787/ in your browser.

Other binding options

# Different port
rdst web --port 9000

# Bind to all interfaces (for remote access, see warning below)
rdst web --host 0.0.0.0 --port 8787

# Also answer to a DNS name for this machine
rdst web --host 0.0.0.0 --port 8787 --allowed-host rdst.internal

The server binds to 127.0.0.1 by default so only your local browser can reach it. If you pass --host 0.0.0.0, the server is reachable from your whole network. The server has no authentication of its own, so make sure the port is not exposed to untrusted networks.

The server answers only to localhost, loopback addresses, the --host address, and the IP address a request arrived on. To open it by a host name, such as http://rdst.internal:8787/, pass that name with --allowed-host (repeatable) or list names, comma-separated, in RDST_WEB_ALLOWED_HOSTS. Requests for any other name get HTTP 421 with a message naming the rejected host, and the server logs a warning. This also applies to names a reverse proxy or tunnel forwards: allow the public name the browser uses. Inside a GitHub Codespace, RDST allows its forwarded *.app.github.dev address automatically. SSH and VS Code port forwards that you open on localhost need no extra flag.

RDST Agent in the browser

  1. Open the local URL printed by rdst web.
  2. Connect a database.
  3. Sign in to Readyset for AI monitoring.
  4. Open Database and turn on monitoring.

The browser has the same Database, Inbox, Agent activity, Ask, and report pages as the desktop app. It has no desktop tray or start-at-login controls. To get pop-ups, enable Browser notifications and keep a tab open.

When your account's AI usage limit is reached, AI monitoring stops gracefully. Local monitoring keeps running, and the app asks you to contact us.

Shared data and startup

The default data directory is ~/.rdst. Use RDST_DATA_DIR to select another one. The first startup after an upgrade may take longer while files migrate. Keep the installed CLI and desktop versions compatible.

Deployment patterns

For local development the default 127.0.0.1:8787 binding is exactly what you want. For shared team use, a few common patterns:

Run rdst web on a bastion host and forward the port over SSH:

# On the bastion, in a tmux session or similar:
rdst web --host 127.0.0.1 --port 8787

# On your laptop:
ssh -L 8787:localhost:8787 bastion.example.com
# Then open http://localhost:8787/

Forwarding keeps authentication at the SSH layer, so the web server doesn't need to be exposed publicly.

rdst web can run inside a container if you bind to 0.0.0.0 and map the port. Keep the container on a private network.

docker run --rm -it \
    -p 127.0.0.1:8787:8787 \
    -e ANTHROPIC_API_KEY \
    -e PROD_ORDERS_PASSWORD \
    -v $HOME/.rdst:/root/.rdst \
    rdst:latest web --host 0.0.0.0 --port 8787

For a persistent install on a dedicated diagnostic host, run rdst web as a systemd service. Put a reverse proxy (nginx, Caddy) in front if you need TLS or auth, and pass the name the proxy serves with --allowed-host.

# /etc/systemd/system/rdst-web.service
[Unit]
Description=RDST web server
After=network.target

[Service]
User=rdst
Environment=ANTHROPIC_API_KEY=...
Environment=PROD_ORDERS_PASSWORD=...
ExecStart=/usr/local/bin/rdst web --host 127.0.0.1 --port 8787 --allowed-host rdst.example.com
Restart=on-failure

[Install]
WantedBy=multi-user.target

A matching Caddy site forwards the browser's Host header unchanged:

rdst.example.com {
    reverse_proxy 127.0.0.1:8787
}

With nginx, set proxy_set_header Host $host; and proxy_set_header X-Forwarded-Proto $scheme;, and allow the same name. If a rejected name shows up in journalctl -u rdst-web, add it to --allowed-host.

Flags reference

FlagPurpose
-p, --port <N>Port to listen on (default 8787)
--host <ip>Host to bind to (default 127.0.0.1)
--allowed-host <name>Extra host name the server answers to (repeatable)

See also

  • Claude Code integration: MCP-based CLI-style access instead of a browser
  • Data Agents: scoped, guarded HTTP API for external consumers (different from rdst web, which exposes the full RDST surface)