Safe tunnels, simple pricing

Self-hosted means you run the NullBore server on your own infrastructure. You get all features, no limits, no cost — but you manage the server. Hosted means we run the infrastructure for you. You get a URL, dashboard, and API key instantly.

On Free, you get a random URL like a7f3bc.tunnel.nullbore.com that changes each session. On Dev, you claim an account subdomain like yourcompany.nullbore.com and create named tunnels under it — web.yourcompany.nullbore.com, api.yourcompany.nullbore.com, etc. On Pro, you can also bring your own domain.

Yes — it's one of our best use cases. Expose a local MCP server to a cloud-hosted agent, run your workflow, and the tunnel stays up as long as you need it. We have an OpenClaw skill and a Docker sidecar image that make integration seamless.

Yes. Changes take effect immediately. Downgrades prorate to the next billing cycle.

Persistent tunnels stay alive until you close them — no automatic expiry. Free tunnels expire after 2 hours. On Dev and Pro, the default TTL is persistent, but you can set a shorter TTL per tunnel if you prefer your tunnels to clean themselves up.

NullBore sends HTTP events to your URL when tunnels open, close, or expire — useful for automation, monitoring, and CI/CD integration. On Pro, webhooks include an HMAC signature so you can verify they came from NullBore.

This is different from testing incoming webhooks (e.g., Stripe → your local server), which works on every tier — it's just HTTP traffic through your tunnel.

All data relayed through the tunnel — both directions. If you're proxying a 1MB page load, that's ~1MB of bandwidth.

Not by default. We always track aggregate metadata (byte counts, request counts, timestamps) for billing and rate-limiting. Request inspection is off by default on every tunnel — you turn it on per tunnel from the dashboard when you want to debug. When enabled (Dev plan and up), we record the method, path, redacted headers, and the first 4KB of each request body, visible only to you. Toggle it off anytime; existing logs are kept until you delete the tunnel.

Absolutely — expose a local endpoint, point Stripe/GitHub/etc at the tunnel URL, test your integration, done. This works on every tier, including Free.

A lightweight container (ghcr.io/nullbore/tunnel:latest) that sits alongside your services in docker-compose and exposes them through tunnels — no published ports needed. See the Docker guide.