Without Roxy
http://localhost:3000Which service was this?http://localhost:8080Certificate warning again.http://localhost:5173OAuth callback mismatch.
Local development proxy
localhost behind.Give every project a memorable .roxy domain with trusted HTTPS. Route your stack, inspect its traffic, and keep moving.
One Rust binary · macOS & Linux · MIT licensed
terminal
# Install once
$ brew install rbas/roxy/roxy
$ sudo roxy install
# Give your app a real local domain
$ roxy register myapp.roxy \
--route "/=3000" \
--route "/api=8080"
✓ https://myapp.roxy
trusted HTTPS · ready to useA calmer local stack
Without Roxy
http://localhost:3000Which service was this?http://localhost:8080Certificate warning again.http://localhost:5173OAuth callback mismatch.With Roxy
https://shop.roxyFrontendhttps://shop.roxy/apiBackend APIhttps://admin.shop.roxyAdmin, trusted and clearEverything built in
Roxy creates and manages a local certificate authority so browsers trust every registered domain.
Send the frontend, API, admin, or static files to different targets behind one clean domain.
Develop multi-tenant apps locally with automatic certificates for every project subdomain.
Follow HTTP requests and WebSocket connections without adding another monitoring service.
Turn on integration once and let Roxy discover Docker Compose services as they start.
No nginx, dnsmasq, containers, or YAML. Roxy ships everything in one Rust binary.
Docker auto-discovery
name: myapp
services:
web:
build: .
ports:
- "3000:3000"
api:
image: myapp/api
ports:
- "8080:8080"Discovered from published ports
https://web.myapp.roxylocalhost:3000trustedhttps://api.myapp.roxylocalhost:8080trustedBuilt for real workflows
Use stable HTTPS callback URLs without tunnels or browser warnings.
https://shop.roxy/api/webhooksKeep every service under one domain with predictable path-based routes.
/ → 3000 /api → 3001Test tenant routing using wildcard subdomains and automatically issued certificates.
*.myapp.roxy → 3000
Ready when you are
brew install rbas/roxy/roxy↗