RelayGate

What it is

Stop juggling provider keys. RelayGate is the open-source gateway between your apps and every LLM provider: virtual keys, programmable policy, cost caps, signed audit, and inline rewrites in one place. For solo devs juggling 4 provider keys · platform teams · compliance teams Point your apps at RelayGate instead of each model vendor directly. The gateway decides which provider to use, which prompts need redaction, when to fall back to a cheaper model, and which requests should be blocked or rerouted before the model ever sees them. This is the core RelayGate promise in motion: one request comes in, policy runs, a ContextWorker changes what needs changing, and the signed result moves on without the app needing to know which provider handled it. RelayGate translates every inbound format to a canonical ChatRequest before routing. Your code doesn't know or care which client protocol arrived. Switch providers without rewrites. Most gateways queue your request internally and hope. RelayGate returns 503 plus Retry-After. Your SDK's retry logic takes over. You stay in control of timing, budget, and fallback. CEL for routing decisions. CEL for policy gates. CEL for rate-limits and budget checks. Same engine, same syntax, one thing to learn. Type-checked expressions with predictable error messages. Pick from the gallery. Drop them into the request path in any order. The pipeline executes top-to-bottom, each worker can pass, mutate, enrich, block, or branch. Drag to reorder. The total overhead is the sum. RelayGate is designed to compose with R1, TrueCom, RelayOne, DeepTap, Veritize, Actium, CloudSwarm, and Heroa. The flows below are an illustrative walkthrough of the planned integrations — some hops are live today (TrueCom receipt emission), others are scaffolded and land progres

What to verify before adopting

• Confirm current pricing, usage limits, supported regions, and contract terms on the official website.
• Test integrations, export paths, access controls, and failure recovery with low-risk data first.
• Review privacy, data retention, security, and compliance requirements for your market.
• Keep a migration or rollback plan before making the product part of a critical workflow.