Skip to content
NEXORA Gateway

Beta

Govern every model call. Install nothing.

NEXORA Gateway is a hosted door in front of your model provider. Your apps call one endpoint with one key. Every request is authenticated, limited, and logged, and there is no package to install, patch, or trust inside your own stack.

Your first governed call
curl https://api.onenexora.com/v1/chat \
  -H "Authorization: Bearer nx_live_..." \
  -H "Content-Type: application/json" \
  -d '{"messages":[{"role":"user","content":"Hello"}]}'

Why a hosted gateway

Self-hosted gateways become part of your attack surface.

An open-source proxy you run holds your provider keys and sees every prompt. When one of its releases is compromised, so is everything that trusted it. With Gateway there is nothing of ours inside your build.

You can't govern what you can't see.

Teams share provider keys and have no record of who sent what. Gateway gives every app its own key, limits, and an audit log, so you can see usage and shut a key off in one click.

Key. Call. Govern.

  1. 01

    Key

    Create a Gateway key in the dashboard. It is shown once and stored only as a hash.

  2. 02

    Call

    Send a chat request to one endpoint. Same shape whichever provider sits behind it.

  3. 03

    Govern

    Every call is authenticated, rate limited and checked against your quota. Calls that go through are written to your audit log.

What is real today

On the roadmap

Questions

Do you store my prompts?
No. We store a hash of each prompt with the model, token counts, latency, and decision. See Data handling.
Which providers can I use?
Anthropic and OpenAI, with your own key or the shared one. Routing rules across providers are on the roadmap.
What does it cost?
Free and Starter plans are live. See Pricing.
Does it stream?
Yes. Set stream to true and read the response as server-sent events.

Make your first call in minutes.