Is SBproxy a reverse proxy, an AI gateway, or a model server?

All three, from one binary. It terminates TLS and handles HTTP/1.1, HTTP/2, WebSocket, and gRPC like nginx or Envoy. It routes LLM traffic to 200+ hosted models across 72 providers with guardrails, budgets, and MCP federation. And it serves open-weight models on your own GPUs by supervising vLLM or llama.cpp underneath. One config file drives all of it, and the AI features sit on a runtime that was already a production-grade proxy.

SBproxy is the open-source enterprise gateway for API, MCP, and AI model traffic. Outbound, it routes to 200+ hosted models across 72 providers through one OpenAI-compatible endpoint, picking models by prompt difficulty and rerouting on live cost-per-success, and serves open-weight models on your own GPUs. Inbound, it gates the crawlers, signed agents, and MCP clients that hit your APIs, with controls like Pay Per Crawl and Web Bot Auth. Both directions share one policy of virtual keys, budgets, and guardrails. Underneath sits a production-grade reverse proxy running auth, TLS, WAF, rate limiting, transforms, and caching. Single static binary, Apache License 2.0.

Can SBproxy serve models on my own GPUs?

Yes, on any GPU. A provider whose entire body is a serve: block boots to a first token: SBproxy resolves the weights, fits an engine and quantization to your card (bigger cards take FP8, smaller ones fall back to an int4 GGUF), runs vLLM or llama.cpp as a supervised subprocess, and routes to it. Run sbproxy doctor first and it reports what the host can serve. Every governance plane, meaning virtual keys, budgets, guardrails, and the usage ledger, applies to the local model unchanged, and a hosted provider placed after the local lane catches overflow under policy.

How is SBproxy different from vLLM or Ollama?

vLLM and Ollama serve a model. SBproxy stands up the environment around it: the governed OpenAI-compatible endpoint, virtual keys, budgets, guardrails on prompt and response, failover to hosted providers, and a verifiable usage ledger. It runs vLLM or llama.cpp underneath as supervised engines, so you keep the engine and gain the gateway.

How is SBproxy different from Cloudflare Pay Per Crawl?

Cloudflare runs at its own edge. SBproxy runs in your VPC, region, Kubernetes cluster, or air-gapped environment. Pricing is tier-aware, per route, per shape, and per agent rather than domain-wide. Inbound monetization, agent identity, content negotiation, and outbound AI governance live on one policy graph instead of separate Cloudflare products. Settlement supports both x402 and Stripe MPP, and you can act as your own Merchant of Record.

How is SBproxy different from other AI gateways like LiteLLM, Helicone, Portkey, or Kong AI Gateway?

Most AI gateways stop at routing calls to hosted providers. SBproxy also serves the weights: the same binary runs open models on your GPUs and applies the same keys, budgets, and guardrails to local and hosted traffic alike. It is also a real reverse proxy underneath, so auth, WAF, and rate limiting ride along instead of needing a second gateway. Helicone is excellent for LLM observability. LiteLLM is a Python library that grew a server, and sbproxy config import-litellm converts its config in an afternoon. Kong is a traditional API gateway with AI bolt-ons. None of them serve the model.

Where does SBproxy sit in my stack?

At the network hop between your apps or agents and the models they call, and between inbound AI traffic and your APIs. SDK gateways live inside one app's code, hosted edges govern from someone else's network, and agent platforms ask you to build on them; SBproxy is standalone infrastructure that deploys like nginx, works under any agent framework or platform, and fronts any hosted provider or your own GPUs. It terminates TLS with certificates it issues and renews from Let's Encrypt, so the governed endpoint can face the public internet behind virtual keys you mint and revoke at runtime.

How does SBproxy handle API keys and state across a fleet of instances?

SBproxy ships a dynamic key plane. Mint, rotate, and revoke virtual keys at runtime through the admin API with no reload, and a revoke takes effect on the next request. Keys are hashed at rest with HMAC-SHA256 and a server pepper, and upstream provider credentials are sealed with AES-256-GCM. Across a fleet of replicas, a built-in mesh keeps the keys, budgets, and per-key rate counters coherent using SWIM gossip and CRDT counters, so the cluster coordinates itself without an external Redis. LiteLLM and most AI gateways need a separate Redis to share that state across instances.

Where does SBproxy deploy?

Single binary on a server, Kubernetes operator on a fleet, or air-gapped install on a regulated network. Same policy graph in every shape. No phone-home. No SaaS edge. Bring your own Stripe, your own SSO, your own observability, and your own audit sink. Suitable for EU, India, Saudi Arabia, US public sector, defense, healthcare, and finance workloads with sovereignty requirements.

Is SBproxy open source?

SBproxy is open source under the Apache License 2.0. Free for any use, including production and commercial, with no field-of-use restriction. Read every line on GitHub. Verify every binary.

What is Pay Per Crawl and how does SBproxy support it?

Pay Per Crawl is the pattern of charging AI crawlers for access to content using HTTP 402 Payment Required. SBproxy ships the ai_crawl_control policy: AI crawlers that arrive without a valid payment token receive a 402 response with a JSON challenge. The crawler retries with the issued token and the proxy validates it through a pluggable ledger. Settlement supports x402 stablecoin and Stripe MPP. Tokens can be priced per route, per shape, and per agent.

What is Web Bot Auth and how does SBproxy verify AI agents?

Web Bot Auth is the IETF pattern for verifying signed AI crawlers and agents. SBproxy implements it through the bot_auth provider. Agents sign each request with an Ed25519 key under RFC 9421 HTTP Message Signatures and advertise their key id in the Signature-Input header. The gateway looks up the matching public key in its directory and verifies the signature. Agents that pass come through. Everything else gets 401.

Does SBproxy support MCP?

Yes. SBproxy ships an MCP gateway that federates internal tools under one identity model. Authentication supports OAuth2 with DPoP, PKCE, and DCR. Federated servers can be wrapped from any OpenAPI service, with per-server prefix and RBAC. The same policy graph that governs API and AI traffic also governs MCP tool invocations.

What does SBproxy replace?

A hosted model router (OpenRouter), an LLM proxy (LiteLLM, Portkey, Helicone), the hand-rolled shim in front of vLLM or Ollama, a traditional API gateway (Kong, nginx, Envoy), a guardrails service, a bot management product, and a payment rail for crawlers (TollBit, Skyfire). One runtime instead of six vendors stitched together, one policy plane instead of six control planes, one audit log instead of six disconnected feeds.

How many AI providers does SBproxy support?

SBproxy reaches 200+ models behind one OpenAI-compatible API through 72 native providers, including OpenAI, Anthropic, Google Gemini, AWS Bedrock, Azure OpenAI, Azure AI Foundry, Groq, Mistral, Cohere, Together AI, Fireworks, xAI Grok, OpenRouter, Cerebras, NVIDIA NIM, Databricks, Snowflake Cortex, IBM watsonx, and Oracle GenAI, plus the models it serves itself on your GPUs via vLLM or llama.cpp and external self-hosted runtimes like Ollama and TGI. Routing supports fallback chains, weighted, round-robin, latency-based, cost-optimized, and outcome-aware strategies.

Is SBproxy safe to run in front of production traffic?

SBproxy ships as a single static Rust binary. Releases are cut from tagged commits in a public repository on GitHub. Dependencies are pinned and checksummed in Cargo.lock. The runtime does not fetch code from a public package registry when it starts. The deployment shape matches nginx, HAProxy, and Envoy. Hot reload is supported without dropping connections.

Storage

The storage action serves objects from S3, GCS, Azure, or local disk, plus the map of where the gateway persists its own state

Storage means two things in SBproxy, and this page covers both. The storage action serves files out of an object store, the way a static-site origin or a bucket-backed CDN path would. Separately, the gateway itself persists state (certificates, cache entries, payment ledgers, config history), and knowing which backend holds what tells you what to back up, what is safe to lose, and where Redis actually becomes a requirement.

The `storage` action

The storage action serves objects from S3, Google Cloud Storage, Azure Blob Storage, or the local filesystem. All four run through one codepath: the backend is constructed once at config load, and each request translates the inbound path into an object key, fetches or HEADs it, and streams the bytes back with Content-Type, Content-Length, ETag, and Last-Modified from the object metadata.

origins:
  "static.example.com":
    action:
      type: storage
      backend: s3
      bucket: my-static-site
      prefix: public
      region: us-east-1
      index_file: index.html

Field	Type	Default	Description
`backend`	string	required	`s3`, `gcs`, `azure`, or `local`. Anything else is refused at config load.
`bucket`	string	unset	Bucket or container name. Required for the three cloud backends.
`path`	string	unset	Local filesystem root. Required for `local`; canonicalized at build time, so symlinks in the configured path resolve to their real target before the store is rooted there.
`prefix`	string	unset	Key prefix prepended to every request path.
`index_file`	string	unset	Object served for paths ending in `/` (for example `index.html`).
`region`	string	env	Region override, `s3` only.
`endpoint`	string	unset	Endpoint override for S3-compatible stores (MinIO, Cloudflare R2).

What it serves: GET and HEAD, with byte-range support (Range in, 206 Partial Content and Content-Range out). Any other method gets 405. A missing object is 404; a transient backend error is 502. path, prefix, and index_file all refuse traversal sequences at config load.

Credentials come from the environment, using each provider's standard discovery: AWS_* for s3, GOOGLE_* for gcs, AZURE_* for azure. There is no credential field in the action config, so nothing secret lands in sb.yml; set the variables before process start, through your platform's secret mechanism.

Because a storage origin is a normal origin, everything in the pipeline applies: authentication, policies, transforms, and the response cache compose with it the same way they do with a proxy origin.

Runnable at examples/storage-action/, which uses the local backend so it runs with no cloud account, and shows the range, index-file, and 404 behavior with captured output.

Where the gateway keeps its own state

The house rule for the gateway's own persistence: redb for embedded key-value state, SQLite for relational state, and memory / file / memcached / redis for the response cache. Nothing requires an external database; the embedded defaults carry a single node, and Redis enters only where state must be shared across replicas.

Surface	Backends	Configured by	Reference
Response cache	`memory` (default), `file`, `memcached`, `redis`	`proxy.response_cache_store`	configuration.md
Cache reserve (cold tier)	`memory`, `filesystem`, `redis`	the `cache_reserve` block	cache-reserve.md
Shared counters (exact cluster-wide rate limits)	`redis` (the only implemented driver)	`proxy.l2_cache_settings`	configuration.md
ACME certificate store	`redb` (default), `sqlite`, `file`, `redis`, `s3`, `gcs`, `azure`, `memory`	`acme.storage_backend` + `acme.storage_path`	configuration.md
Payment settlement ledger and single-serve nonce ledger	SQLite, one shared database	`proxy.payments`	payment-settlement.md
Config history (durable ring of applied configs)	content-addressed files in a local directory	`proxy.config_history`	configuration.md
AI compression session state	`local` (embedded redb), `redis`, or the replicated mesh	the compression `state` block	ai-context-compression.md
Admin prompt persistence	redb, optionally sealed with AES-256-GCM	`prompt_persistence_path` + `prompt_persistence_encryption`	configuration.md
Cluster state (sessions, handoff)	the replicated mesh substrate	`proxy.cluster`	mesh-replication.md

Three properties worth knowing before you plan an installation around this table:

The response cache can seal entries at rest. The optional encryption block under response_cache_store encrypts headers and bodies with AES-256-GCM before they reach the backing store, which matters once entries land on disk (file) or in a shared store (memcached, redis) that outlives the request. An entry no configured key can open is evicted and reported as a miss, so rotation heals rather than breaks.
Local storage paths are subscriber-owned. proxy.compression_state and proxy.config_history name directories on the node's own disk, so a config authority cannot set them for a fleet; a distributed payload naming either is rejected whole. See configuration.md.
What to back up. The ACME store (or you re-issue on restore), the payments database (it is the proof of settlement), and the config-history ring if you rely on it for rollback. Cache tiers are rebuildable by definition and need no backup.

Storage

The storage action

Where the gateway keeps its own state

See also

The `storage` action