CHAPTER I·THE GATE

Every AI request.
One gate.

Gatewyse routes your traffic across every major AI provider with intelligent free-tier chaining, cryptographic audit trails, and a lifetime license you actually own.

See how routing worksRead the architecture

Own it for $2,499 →
EVERY MAJOR AI PROVIDER·One gate
OpenAIAnthropicGoogle GeminiAzure OpenAIxAIMistralCohereDeepSeekGroqTogether AIFireworksPerplexityCerebrasSambaNovaReplicateHuggingFaceAI21OllamavLLMLM StudioLocalAIllama.cppAssemblyAIElevenLabsWhisperComfyUIStability AIOpenAIAnthropicGoogle GeminiAzure OpenAIxAIMistralCohereDeepSeekGroqTogether AIFireworksPerplexityCerebrasSambaNovaReplicateHuggingFaceAI21OllamavLLMLM StudioLocalAIllama.cppAssemblyAIElevenLabsWhisperComfyUIStability AI

CHAPTER II·THE THREE PILLARS

What the gate stands on.

PILLAR I  ·  OWNERSHIP

Own it.

A lifetime license is $2,499. Host it on your cluster, your laptop, or an air-gapped VPC. Bring your own keys. Keep your own audit logs. We never sit between you and your data.

PILLAR II  ·  JUDGMENT

Route it.

Ten routing strategies, including free-tier chaining that exhausts every provider's free quota before touching a paid key, least-cost, least-latency, failover, weighted, and ML-driven task-optimized routing.

PILLAR III  ·  VIGILANCE

Audit it.

SHA-256 hash-chained immutable logs. Argon2id for passwords. AES-256-GCM with tenant-scoped AAD on every stored credential. PII guard. Prompt guard. SOC 2-ready by construction.

CHAPTER III·THE JUDGMENT

Ten strategies. One gate.

Every request walks the chain. Gatewyse checks health, cost, latency, and free-tier balance, then routes accordingly. When a provider's quota exhausts or its circuit opens, the gate passes judgment to the next candidate without dropping a packet.

CHAPTER IV·THE MODALITIES

Not just chat. Everything.

Eight modalities. One API key. Route by task, cost, latency, or free-tier balance — the gate decides.

POST /v1/chat/completions

OpenAI-compatible chat with streaming, tool use, and vision.

Providers

  • OpenAI
  • Anthropic
  • Gemini
  • Groq
  • Mistral
  • Together
  • …
curl https://api.gatewyse.com/v1/chat/completions \
  -H "Authorization: Bearer $GATEWYSE_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-4o",
    "messages": [{"role":"user","content":"Explain routing strategies in one line"}],
    "stream": true
  }'

CHAPTER V·THE VIGILANCE

Security as receipts, not adjectives.

Six laws of the gate. Each one verifiable in code, hardened against the threats that actually matter for an AI gateway: credential exfiltration, audit tampering, provider compromise, and cascading failure.

  1. Hash-chained audit

    Every log entry is sha256(entry ‖ previousHash). Tampering breaks the chain and is detectable with a single verify pass. Append-only. Sequence numbers prevent reordering. TTL indexes enforce 365-day retention by default.

  2. Argon2id

    The only password hash we accept. No bcrypt. No SHA-family. Memory-hard by design, resistant to GPU and ASIC attacks. Cost parameters per deployment; defaults exceed OWASP 2024 recommendations.

  3. AES-256-GCM with tenant AAD

    Provider API keys are encrypted at rest. The tenant ID is bound in as additional authenticated data, so a key intended for tenant A cannot be decrypted in tenant B's context. Ciphertext is version-prefixed for rotation.

  4. Prompt & response guard

    A configurable pipeline runs on every request and response. Built-in regex PII detectors (SSN, credit card, email, phone, IP, API key), LLM moderation callbacks, and custom guard plugins. Actions: block, redact, mask, or hash.

  5. OIDC + SAML single sign-on

    Okta, Microsoft Entra, Google, and any OIDC/SAML provider. Per-tenant identity isolation — identity providers never share sessions across tenants. Pre-configured templates for the common ones; generic IdP otherwise.

  6. Provider circuit breaker

    Each provider runs behind a per-instance state machine. After 5 consecutive failures, the circuit opens; routing skips it for 60 seconds; a half-open probe then closes it on success or re-opens on failure. No cascading failures under provider outages.

CHAPTER VII·THE SOVEREIGNTY

Buy it once. Or pay it off.

Most platforms rent their gate to you forever. Gatewyse gives you two honest options — own it outright, or amortize the license through a managed deployment and keep it when you're done.

LIFETIME LICENSE

$2,499once

  • Every future update, forever
  • Self-host anywhere — cluster, laptop, air-gapped VPC
  • Bring your own provider keys
  • Unlimited tenants, users, requests
  • Full source access
  • Priority support SLA
Buy lifetime

MANAGED  ·  DEDICATED

$99/mo

Single-node k3s deployment we run for you. Infrastructure and license amortized into one monthly bill.

See managed pricing

CHAPTER VIII·THE QUESTIONS

What you're about to ask.

Gatewyse tracks per-provider per-tenant daily free quotas in Redis. The free-tier-first strategy dispatches to providers with remaining free balance in priority order. When all free quotas exhaust (or circuit-open), it falls back to paid providers automatically. Zero manual fallback logic.
Feature parity. Self-hosted runs wherever you want (Docker, k8s, k3s, bare metal). Managed is our k3s deployment for teams that prefer not to operate it. Switching is a config change plus a data migration script we provide.
Not yet audited. The architecture is SOC 2-ready by construction: immutable audit log with hash chaining, TTL-based retention, Argon2id password hashing, AES-256-GCM at rest, tenant-scoped AAD, rate-limiter fail-closed behavior, full RBAC. We work with customers on the audit during onboarding.
Yes. Every provider config accepts tenant-scoped API keys, encrypted with AES-256-GCM using the tenant ID as additional authenticated data. Keys never leave your deployment on self-host; on managed they are encrypted with per-tenant rotation.
Audit logs default to 365-day retention via MongoDB TTL indexes, configurable per tenant. Request/response bodies are not logged by default; you enable that per route if you need it for compliance.
Each provider runs behind a circuit breaker (CLOSED → OPEN after 5 consecutive failures → HALF-OPEN after 60s). Routing skips OPEN providers automatically and probes them in HALF-OPEN. No request lands on a degraded provider.
Yes. It binds to the business entity, not the individual. Corporate acquisitions, spinoffs, and ownership changes are covered. Full terms in the license agreement.
Yes. After 36 months of Dedicated, the lifetime license transfers automatically. You can stay on managed, or take the license and self-host while continuing to use infrastructure support at reduced cost.

·EPILOGUE·

You've walked the gate.

Time to stand it up.

Get Gatewyse