Project Config (up / down)

Define your project's tunnels once in an otterkit.toml and bring them all up with a single command. Each profile runs as a background daemon, so status, inspect, replay, and stop work on them like any other daemon.

toml

# otterkit.toml
[tunnels.web]
port = 3000
subdomain = "myapp"          # stable URL (optional)
auth = "admin:s3cret"        # HTTP Basic auth (optional)
log = true                   # capture requests (optional)
ttl = "8h"                   # auto-stop (optional, default 24h)

[tunnels.hooks]
webhook = true               # capture-only endpoint, no local server
subdomain = "myapp-hooks"
respond = 200                # custom auto-response (optional)
respond_body = '{"ok":true}'

bash

npx otterkit up          # Start everything
npx otterkit up --json   # Machine-readable results for agents
npx otterkit down        # Stop the daemons started from the config

up is idempotent — profiles that are already running are skipped and reported as already_running, so agents can run it repeatedly without double-provisioning. Use --config <path> to point at a different file.

Pricing is unchanged: each profile is a normal daemon at 1 credit per connected hour, capped at 10 credits/day. up with two profiles provisions two tunnels.

Daemon Mode Webhook