← Platform grid
Nexus · scope loaded
AI gateway

Control every model call before it becomes operational reality.

Nexus is the governed AI gateway for enterprises that need routing, policy, audit, and cost intelligence across provider models and private inference.

Give developers one OpenAI-compatible edge while security, platform, and finance teams retain durable control.

Developer surface

Put a policy engine in front of every model call.

Nexus should feel like infrastructure because it changes almost nothing for app developers: keep the OpenAI client, move the base URL, and let the gateway own routing, policy, cost, and evidence.

ingress OpenAI API
decision policy trace
records tenant scoped
nexus — quickstart
~$ curl -H 'Authorization: Bearer $NEXUS_API_KEY' https://gateway.vortexaq.com/v1/chat/completions[ok] Resolving nexus contract...[ok] Bound signal: Governed edgeconst client = new OpenAI({ baseURL: process.env.NEXUS_URL, apiKey: process.env.NEXUS_API_KEY });const response = await client.chat.completions.create({  model: "gpt-5.5",  messages: [{ role: "user", content: "Summarize this incident packet." }],  metadata: { project: "claims-ops", policy: "regulated-pii" },});Artifacts: route decision log · provider key boundary · per-request cost event
Build path
  1. Point existing OpenAI clients at the Nexus base URL.
  2. Attach project, tenant, and policy metadata to each request.
  3. Route across provider or private models without leaking keys to app teams.
Evidence emitted
  • route decision log
  • provider key boundary
  • per-request cost event
Why this page exists

Give developers one OpenAI-compatible edge while security, platform, and finance teams retain durable control.

Deployment briefing ↗
Capability map

Primitives your teams ship against.

Concrete behaviors and interfaces so security, platform, and product teams share one operational picture.

01

Provider routing with bring-your-own-key and platform-managed key paths

02

Tenant-aware projects, API keys, and request attribution

03

Audit-ready traffic records with verifiable decision context

04

Cost, latency, and reliability signals for production operations