Use cases
Three ways teams use RunDock
Every scenario below runs on the shipped CLI — commands are copy-pasteable.
Debug Stripe webhooks locally
Point Stripe at a public URL, watch the exact payload arrive, and replay it against your handler until the signature check passes — no redeploys between attempts.
$ - Realistic payment_intent.succeeded sample payload to test before Stripe ever calls.
- Raw body preserved — signature verification works.
- Replay any captured delivery as curl.
Show work in progress without deploying
Send a link instead of shipping a build. Password-protect it and let it expire when the meeting ends.
- Password gate on the public URL.
- Tunnel closes itself after --expires.
- --once for links that die after the first visit.
Put your Compose stack online in one command
RunDock reads docker-compose.yml, skips databases, and opens a tunnel per exposable service.
$ - Services by name, not port numbers.
- Datastores are private by default.
- One URL per service, opened concurrently.
Your scenario, your app
The beta is open by invite — bring the app you’re working on right now.