Oxaa
Sign inDownload
  1. Localhost. Online. Without opening your network.
  2. Security overview
  3. Trust center

Secure public endpoints for local development

Trust center

Trust center: practical workflow, product behavior, limits, evidence and the exact next step with Oxaa.

Fast answer

Trust center answers a trust question with architecture, controls, failure behavior and evidence. It does not rely on a badge, an adjective or a future certification.

Technical details

  • security overview
  • data handling
  • signed software and supply chain
  • vulnerability disclosure
  • status and incident history
  • subprocessors and data locations
  • DPA and procurement
  • acceptable use and country availability

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.

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.