SwitchGate for Enterprise

Run your own models on your own hardware behind the same governed gateway your teams already use for cloud models. Private inference, public-cloud breadth, one ledger, and controls your auditors will actually like.

Built for organizations

Everything the free tier has, plus the parts legal asked about

  • Private model hosting

    Serve your fine-tuned or open-weight models from your own GPUs through the SwitchGate Agent, in your catalog next to the cloud frontier.

  • SSO & SCIM

    SAML and OIDC single sign-on with directory sync, so keys assigned to users follow your identity provider, joiners and leavers included.

  • DPA, Loi 25 & GDPR

    Canadian hosting, a signed data-processing agreement, and pure-routing guarantees: no training on your data, no prompt retention by the gateway.

  • Volume fee tiers

    The 4.9% top-up fee steps down with committed volume; model usage stays at provider list price at every tier, and private inference bills 0 credits.

  • Org-wide governance

    Budgets, model locks and the kill switch applied per user, per team and per environment, with keys assigned to named people and audit-log export.

  • Priority support & SLA

    A named contact, an uptime SLA on the gateway, and migration help from whatever you route through today.

The device agent, in detail

Your own model, behind the same API

The Agent is not an AI: it's a device agent, a single static binary or container you install on your own server next to your inference runtime. It solves the hard part of private AI by opening a secure tunnel from your model to the gateway, so the model becomes usable through our API, on your website, by your teams, or by paying customers, without punching a hole in your firewall.

Your apps Gateway budgets · locks · ledger Anthropic OpenAI · Google · … YOUR VPC / DATACENTER SwitchGate Agent vLLM / Ollama your GPUs · your weights outbound mTLS tunnel opened by the Agent · no inbound ports

How it works

  1. Install next to your runtime

    One binary via curl, a Docker container, or a Helm chart into the same cluster as your vLLM or Ollama deployment. It needs outbound HTTPS and nothing else.

  2. The Agent dials out, never in

    It opens a persistent outbound mTLS tunnel to the gateway. No inbound ports, no public IP, no VPN appliance; it works from a datacenter, an office, or a workstation.

  3. Your models join the catalog

    Whatever the runtime serves is registered under private/your-org/<model>, visible only to your organization, callable through the standard endpoint.

  4. Governance applies automatically

    Per-user budgets, model locks, user-assigned keys and the kill switch treat private models exactly like cloud ones; the ledger records every call at $0.

  5. Route, mix and fail over

    Send sensitive traffic to private models and overflow to cloud, or seat your fine-tune on a review council. And once the marketplace opens, the same tunnel will let you charge for access (see below).

Deploy it your way

Kubernetes (Helm)
helm repo add switchgate https://charts.switchgate.ai
helm install sg-agent switchgate/agent \
  --set org=acme \
  --set runtime.url=http://vllm.internal:8000 \
  --set replicas=2   # HA: agents load-balance the tunnel
agent.yaml
org: acme
runtime:
  kind: vllm            # vllm | ollama | llamacpp | openai-compatible
  url: http://vllm.internal:8000
publish:
  - "private/acme/llama-4-maverick-ft"
  - "private/acme/legal-qwen-72b"
limits:
  max_concurrency: 32
  allowed_teams: ["platform", "legal-ai"]

Security posture

  • Data plane stays home. Prompts and completions for private models are processed inside your network; the control plane sees metadata only.
  • Outbound-only mTLS with pinned certificates and per-agent identities you can revoke individually.
  • High availability: run multiple agents; the gateway spreads traffic and routes around a lost tunnel in seconds.
  • Least privilege: publish only the models you list, to only the teams you name.
  • Full audit trail: every private call lands in the same exportable ledger as cloud traffic.

Model marketplace · on the roadmap

You'll be able to resell your model on SwitchGate

The same tunnel that serves your teams is built to serve paying customers next. When the marketplace opens, you'll flip a listing from private to public, set a per-token price, and your model will join the catalog next to the frontier: running on your hardware, billed by us, paid out to you. Here's how it will work.

  1. Publish the listing

    You'll promote private/acme/legal-qwen-72b to a public catalog entry with a name, description and your own model card.

  2. Set your price

    You'll choose the $/1M input and output token rates. Change them any time; buyers will always see the current list price, pass-through, like every other model here.

  3. We meter and bill

    Every buyer call will be metered by the gateway with the same exact-cost tracing you already use. Buyers will pay with their SwitchGate credits; you never handle billing.

  4. You get paid

    Monthly payouts of your earnings minus a marketplace share (rate to be announced; enterprise agreements will be able to negotiate it), with a revenue dashboard alongside.

  5. You stay in control

    You'll cap concurrency so buyers never starve your own teams, restrict listings by region, and unpublish instantly: the tunnel is yours, so the off switch is too.

Publish a listing (planned API, subject to change)
curl https://api.switchgate.ai/v1/marketplace/listings \
  -H "Authorization: Bearer sg-admin-…" \
  -d '{
    "model": "private/acme/legal-qwen-72b",
    "public_id": "acme/legal-qwen-72b",
    "price_per_m_input_usd": 0.40,
    "price_per_m_output_usd": 1.60,
    "max_buyer_concurrency": 16,
    "regions": ["ca", "eu"]
  }'
  • Buyers will never see your infrastructure. They'll call the public model ID; the gateway routes through your tunnel and returns the response.
  • Your weights will never move. Only tokens travel; the model stays on your server, under your control.
  • Same governance for buyers. Their budgets, locks and user keys will apply to your model like any other, which makes it easier to buy.
The marketplace opens after the console launch. Every device-agent tunnel set up today is marketplace-ready from day one, so connecting your model now means listing it later is one API call. Join the waitlist →

FAQ

Enterprise questions, answered

Will we be able to sell access to our model through SwitchGate?
Yes, that's on the roadmap. Once the marketplace opens, any model already tunneled in by the device agent will be publishable as a public listing with per-token prices you set; the gateway will meter buyer usage, bill their credits and pay you out monthly minus the marketplace share. Your weights and hardware stay entirely under your control, and unpublishing is instant. Tunnels set up today will be marketplace-ready.
Do prompts sent to our private models ever leave our network?
No. For models served through the Agent, inference happens entirely inside your VPC; requests reach it over an outbound mTLS tunnel the Agent opens, and responses return the same way. Only routing metadata (model name, token counts, latency, cost) reaches the SwitchGate control plane for the ledger.
Which runtimes does the SwitchGate Agent support?
vLLM, Ollama, llama.cpp and any OpenAI-compatible local server. The Agent registers whatever the runtime exposes and publishes it into your private catalog under the private/your-org/ namespace.
Can we mix private and cloud models in one workflow?
Yes. Private models are ordinary catalog entries, so a council workflow can draft on your fine-tuned private model and have cloud frontier models review it, or the reverse, with the same budgets, locks and per-user keys across all of it.
What does enterprise pricing look like?
Model usage stays at provider list price, private models bill 0 credits, and the top-up fee drops with volume from the standard 4.9%. Annual invoicing, a DPA and an uptime SLA are part of the enterprise agreement; email [email protected] for a quote.

Bring your model. Keep your perimeter.

Tell us about your runtime and your compliance constraints; a pilot Agent is usually live in a day.