Fast answer
Integration guides hub gives the visitor a direct answer, the exact product behavior, the limits that affect the decision and a practical path to verification.
Choose only a provider guide that has an owned sandbox, a reproducible event, current official-source review and a maintenance owner. A logo or keyword is not enough to justify a page.
Planned provider portfolio
- Stripe
- GitHub
- Shopify
- Slack
- Twilio
- Telegram
- PayPal
- Mercado Pago
- Pix
- LINE
- Auth0
- Okta
- Clerk
- Discord
- n8n
- Zapier
- Pipedream
- Supabase
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.”
Availability and commercial eligibility
Language preference, account country, billing country, service region, payment eligibility and support language are separate values. Show the current result before signup or checkout and never infer commercial availability from the page language alone.
Complete the next real step
Continue with Start free when the current product, plan and country support that action. Use Open the exact documentation to review the exact technical, trust or support path before committing.
oxaa login
oxaa http 3000