Explainable routing
Records selected, skipped, fallback, budget, and compatibility evidence so every model choice is traceable.
SIFTGATE OSS
SiftGate
A self-hosted AI gateway for apps, coding agents, MCP tools, provider keys, routing, budgets, cache, and evidence.
SiftGate is an MIT open-source data plane. It keeps provider keys, gateway keys, routing policy, budgets, cache, audit, and dashboard evidence inside your infrastructure, with metadata-only operations by default.
MIT
open source license
50+
provider metadata profiles
7
localized doc entrypoints
v2.11.3
current OSS release
OSS DATA PLANE
Not just a proxy. A governed AI traffic layer.
SiftGate puts model routing, provider credential pools, agent profiles, MCP, budgets, and dashboard evidence into one self-hosted runtime.
Provider key isolation
Clients use Gateway API keys while upstream provider keys stay in SiftGate nodes, env vars, or secret references.
Coding agent gateway
Gives Codex, Claude Code, Cursor, Cline, Roo Code, Continue, and similar tools one governed ingress.
MCP tool governance
Proxies MCP tool traffic behind Gateway API keys, namespace allow-lists, and rate limits.
Cost and cache evidence
Tracks tokens, estimated cost, provider-cache savings, budget scopes, and chargeback metadata.
Metadata-only by default
Does not store prompts, responses, raw headers, provider keys, tool payloads, media, source code, or diffs by default.
REQUEST PATH
Govern the request before it leaves your infrastructure
Clients never touch upstream provider keys directly. SiftGate applies gateway keys, policy, budget, compatibility, routing, and credential-pool decisions before forwarding.
Apps / SDKs
Coding Agents
MCP Tools
SiftGate Data Plane
Model Providers
Who can call which model?
Gateway API keys, workspaces, teams, policy namespaces, endpoint/model/node limits, rate limits, and budgets.
Where should traffic go now?
Compatibility filters, tiered routing, fallback chains, circuit state, cache-aware cost, and route explanation.
Which upstream key is working?
Credential pools support least-in-flight, weighted round-robin, sticky affinity, cooldown, and retry failover.
What evidence remains after a request?
Metadata-only call logs, route traces, provider health, cache savings, cost estimates, session timelines, and audit.
PUBLIC EVIDENCE
Evidence lives in the open-source repo
Provider smoke matrices, benchmark reports, and agent+MCP demos come from the OSS documentation assets for self-hosted evaluation.
Provider coverage evidence
Local overhead benchmark
Agent + MCP flow
DASHBOARD
Open-source dashboard screenshots
These captures are from the SiftGate open-source dashboard: local setup, configuration, observability, and cost evidence live in one operating surface.
01
Gateway Overview
From setup to health, guardrails, cost metrics, and cache hits, one screen shows the open-source data plane in motion.
02
Provider Catalog
Maintains provider metadata, pricing sources, active profiles, and custom providers so node setup is evidence-backed.
03
Usage Analytics
Tracks calls, tokens, spend, cache impact, and provider usage, turning AI traffic into operational data.
