RunDock is in limited beta.

Tunnels that speak Docker.

Turn a local port — or a whole Docker Compose service — into a public HTTPS URL, and see every request that hits it.

Join the beta Read the docs

Localhost is a dead end

Webhooks can’t reach localhost

Stripe, GitHub, and Telegram deliver to public HTTPS endpoints. Your laptop isn’t one.

Showing work means shipping it

A work-in-progress demo shouldn’t need a push, a build, and a deploy. It should be a link.

Compose services are trapped

Your app already runs in Docker with its ports mapped. Getting one service onto the internet by hand still means proxies and TLS certificates.

From compose file to first webhook

RunDock reads your compose file. Expose a service by name, watch the webhook arrive, replay it until your handler works.

POST /webhooks/stripe 200

Stripe-Signature:: t=1719840000,v1=5257a86…
Content-Type:: application/json

{
  "type": "payment_intent.succeeded",
  "data": {
    "object": {
      "id": "pi_3PQ…",
      "amount": 2000,
      "currency": "usd"
    }
  }
}

How it works

1. Run

rundock tunnel 3000

2. Get a public URL

https://bright-fox.rundock.dev

3. Inspect & replay

Every request lands in the inspector — replay it as curl.

What you get

Tunnels

Public tunnels

Public HTTPS URL for any local port in one command.

Random subdomains

Every tunnel gets a memorable name like bright-fox.rundock.dev.

Inspect & replay

Request inspector

See method, headers, and body of every request that hits your tunnel.

Replay as curl

Re-send any captured request as a ready-to-run curl command.

Docker

Compose detection

RunDock reads your compose file so you expose services by name.

Stack mode

One command opens a tunnel per exposable service — databases are skipped.

Safety

Safe links

Password-protect a tunnel or set it to expire after a duration.

Webhook presets

Send realistic sample payloads from common providers to test handlers early.

Made for the terminal

Three ways teams use RunDock

Debug Stripe webhooks locally

Watch the exact payload arrive and replay it until the signature check passes.

$ rundock webhook stripe 3000

Show work in progress

Send a link instead of shipping a build — password-protected, self-expiring.

$ rundock tunnel 3000 --password --expires 2h

Put your stack online

One tunnel per exposable Compose service; databases stay private.

$ rundock expose stack

More than a URL

Generic tunnels

You get a URL for a port. Debugging the webhook that just hit it — and wiring up your Compose stack — is your problem.

RunDock

A URL for a service. Compose-aware expose, a request inspector, and one-command replay — built for webhook development in Docker.

RunDock covers local development tunnels and webhook testing. Its sibling product HookWatch covers production webhook reliability — monitoring, alerts, audit. Separate tools; a future integration will connect them.

Try RunDock

The beta is open by invite. Redeem a code or request one — setup is a single curl.

Join the beta