Expose local.
Debug faster.
Binboi gives your localhost a stable public URL, captures every inbound request, and surfaces webhook failures before you touch a redeploy.
Full request visibility from public webhook to local response.
Active focus: HTTP Routing. Fast public exposure without hiding the forwarding path.
Public URL
miransas-dev.binboi.link
Stable enough for providers to call back into local development.
Tunnel state
ACTIVE
Handshake, attach, and proxy lifecycle surfaced instead of hidden.
Debugging clue
Signature mismatch
Headers, raw body, status, and response timing stay close together.
Reserve subdomain
Allocated stripe-dev.binboi.link
Forward to localhost
Sent POST /webhooks/stripe to 127.0.0.1:3000
Live relay terminal
HTTP Routing
operator@binboi:~$ tail -f relay.log
Public URL reserved: https://stripe-dev.binboi.link
> Matched host and active tunnel session
> Forwarded request to localhost:3000/webhooks/stripe
Delivery completed with 200 OK in 38ms
What Binboi
Unlocks Fast
Not growth hacks. Not fluff.
Just ingress, visibility, and safer sharing.
Fast Public
URLs
Request
Visibility
Traffic Clarity
Before Guesswork
Webhook Flows
That Stay Legible
Access Control
That Scales
From install to live in 60 seconds.
No port-forwarding. No firewall changes. Just a token and a command.
Install the CLI
One command, no dependencies.
$ npm install -g @binboi/cliAuthenticate
Paste your access token from the dashboard.
$ binboi login --token <your-token>Expose your port
A stable public URL appears instantly.
$ binboi http 3000 my-appWhat is Binboi?
A self-hosted tunnel platform built for developers who want request visibility without a managed SaaS dependency.
Open source
MIT licensed
Self-hosted
Your infra only
TLS always
End-to-end encrypted
Webhooks
First-class support
Binboi is a self-hosted alternative to ngrok. It creates a secure tunnel from a public HTTPS URL to a port on your local machine—giving providers like Stripe, GitHub, and Clerk a stable endpoint to call, even during local development.
Yes. Binboi is open source and free to self-host. You bring your own server, your own domain, and pay nothing to Miransas. A managed cloud option may follow later.
Traffic is TLS-terminated at the Caddy edge. Your server is the only machine that can read plaintext—Miransas never sees your data. Access tokens are stored as bcrypt hashes and scoped per machine.
Yes. Point a wildcard DNS record (*.yourdomain.com) at your server and configure Caddy with DNS-01 for wildcard TLS. Every tunnel then gets a subdomain like my-app.yourdomain.com.
The CLI agent reconnects automatically with exponential backoff. The public URL stays reserved as long as the session is associated with your token—no manual re-registration needed.
Start tunneling
in 60 seconds.
Deploy Binboi on your own server, create an access token, and expose your first local port—all before your coffee cools.
$ npm install -g @binboi/cli
$ binboi login --token ••••••••
$ binboi http 3000 my-app
✓ Tunnel live → https://my-app.binboi.miransas.com