Public demos show the proof model. Current hosted access is a 90-day design-partner pilot for one agreed staging endpoint, API route, or MCP tool. General self-serve production access is not the current offer.
Inspect the model before you discuss a pilot.
One governed workload, measured together.
Commercial scope follows accepted pilot evidence.
Standard MCP is an open tap for your API credits. SatGate adds the meter — and the shutoff valve.
| Capability | Standard MCP | SatGate-Enabled |
|---|---|---|
| Budget Enforcement | “Faith-based” — wait for the bill | Real-time hard caps at protocol level |
| Cost Attribution | Aggregate — one big API bill | Per-tool / per-agent granularity |
| Access Control | Static API keys — all or nothing | Attenuated macaroons — time/tool limited |
| Visibility | Post-mortem — look back at logs | Signed receipts + Evidence Pack export |
| Agent Loops | Potentially infinite spend | Automated kill-switch at threshold |
| Authentication | Basic / bearer tokens | Paid-rail context — L402/x402-aware governance |
Stop the $500 “hallucination loop” at $2. Automatically revoke access for idle or runaway agents.
Engineers stop acting as manual billing auditors. One proxy to govern all MCP servers.
Govern paid-rail context such as L402/x402 while SatGate proves agent authority, policy, and budget decisions.
SatGate is accepting design partners for one bounded staging endpoint, API route, or MCP tool. The public demos and Evidence Pack examples remain available without an account.
Most pilots start with a DNS, proxy, or MCP configuration change around one bounded endpoint or tool. We verify that path before expanding it.
No. General self-serve production access is not the current offer. Design partners start in an agreed staging or bounded pilot lane while SatGate verifies the buyer journey and operating controls.
The initial 90-day design-partner pilot has no charge or credit-card requirement. Any later commercial contract depends on the accepted scope, measured usage, and operating requirements.
We review the governed workload, policy outcomes, Evidence Pack use, support burden, and operating evidence together. Both sides then decide whether to expand, contract, or stop.
Dedicated deployment is evaluated during enterprise scoping. It is not currently advertised as a generally available tier or SLA-backed service.
Pick one staging endpoint or MCP tool, define the authority boundary, and measure the result before expanding.