Oxaa
Sign inDownload
  1. Localhost. Online. Without opening your network.
  2. Expose localhost securely

Secure public endpoints for local development

Expose localhost securely

Expose localhost securely: practical workflow, product behavior, limits, evidence and the exact next step with Oxaa.

Fast answer

Expose exactly one selected local service with a managed HTTPS URL, without opening an inbound router or firewall port. The route remains reachable only while the enrolled device and current authenticated route are live.

From local service to a real external request

  1. Install the approved signed Oxaa package and verify the release.
  2. Run oxaa login and enroll the device.
  3. Start and health-check the selected local service.
  4. Run oxaa http <port> and wait for edge readiness.
  5. Send a request from a provider sandbox, remote browser, phone or second network.
  6. Confirm the request and response in the local application and Inspector.
  7. Stop the route and remove callbacks, captures and test credentials when finished.

Technical details

  • Managed HTTPS endpoint and public TLS termination.
  • Outbound device session with QUIC preference and TCP/443 WebSocket fallback after testing.
  • Exact-host routing and short-lived route generation.
  • Local Inspector with explicit bounded capture, redaction, deletion and replay limits.
  • HTTP, WebSocket and SSE behavior within published limits.

How traffic and Inspector data are handled

Oxaa's public edge terminates public HTTPS so it can resolve the exact hostname, identify the current authenticated route and forward the request. The session between the enrolled device and Oxaa is encrypted; the selected local service receives the request through that session.

Oxaa retains bounded account, route, usage, security, billing, support and diagnostic metadata required to operate and protect the service. Inspector body capture is a separate, explicit debugging action: the bounded request or response body copy shown by the local Inspector remains on the developer device and can be redacted, deleted or allowed to expire. Public traffic still has to be processed by the edge, so the accurate claim is local Inspector copies-not “Oxaa cannot see traffic.”

Route identity and the selected-service boundary

The enrolled device initiates the connection. Locally generated device identity, proof of possession, short-lived route generations and exact-host matching bind the hostname to the current route. Unknown, malformed, revoked or stale ownership fails closed instead of being forwarded to an uncertain destination.

Oxaa publishes only the configured local target. Private-network destinations require explicit authorization, while public, metadata, link-local, multicast and other unsafe destination classes remain blocked by policy.

Troubleshooting

Start with the local process, port and scheme. Then check authentication and clock, DNS, UDP/443, TCP/443 fallback, corporate proxy or TLS interception, route ownership and edge readiness. Use oxaa routes list, oxaa diagnose --network and stable error IDs; review diagnostic output before sharing it and remove secrets, bodies and private paths.

Cleanup and production handoff

Remove the external callback, preview URL or DNS binding; rotate test credentials; delete local captures; stop the route; and revoke the device or session when appropriate. Move production traffic to the deployed application, production ingress or event-delivery platform designed for that job.

What Oxaa is - and is not

Oxaa is development connectivity for a selected local HTTP or HTTPS service while the enrolled device and authenticated route are live. It is not application hosting, a general VPN, a forward proxy, permanent production deployment, raw TCP/UDP tunneling, arbitrary TLS passthrough, a CDN/WAF replacement or a production webhook delivery platform.

Frequently asked questions

Does Oxaa deploy my application?

No. The application continues to run on the enrolled device. Oxaa forwards requests to the selected local service only while the authenticated route is live.

Do I need to open an inbound port?

Normally no. The enrolled device initiates the session. A restrictive network can still block DNS, UDP/443, TCP/443 or intercept TLS, so diagnostics remain important.

Where do Inspector body copies live?

When bounded capture is explicitly enabled, the copy displayed by the local Inspector remains on the developer device. Oxaa still processes public traffic and retains bounded operational metadata.

Is this production hosting?

No. Use a deployed application, production ingress or event-delivery platform for production traffic.