Skip to main content
Your SaaS Gateway needs almost no management — Guardway runs and upgrades it. This page explains the two actions you can take and, precisely, what happens to your data with each.

Statuses at a glance

Redeploy — reset without losing anything

Redeploy rebuilds your gateway from a clean state on the current platform version. Use it if the gateway looks unhealthy, or after support suggests it.
  • Your configuration (providers, API keys, guardrails, budgets) is reapplied automatically — you don’t re-enter anything.
  • Your dashboard history (logs, usage, spend) is untouched.
  • Requests fail for a few minutes while the gateway rebuilds; the card shows Provisioning, then Online.

Delete — and what a later Setup restores

Delete deprovisions the gateway entirely:
  • Your API keys stop routing within about 30 seconds — calls to the endpoint return 401.
  • Teardown takes a few minutes; the card shows Deleting, and Setup becomes available again once it completes.
  • Setting up again later creates a new gateway — and your configuration (providers, guardrails, MCP servers, application policies) carries over to it automatically.

What happens to your data

The platform is the source of truth. Nothing you configured in the dashboard is ever lost by a Redeploy or Delete — the gateway instance is disposable by design, and everything it needs is restored from your organization’s configuration.

Limits and behavior worth knowing

  • One SaaS Gateway per organization. Need more? Talk to us.
  • 6 MB maximum request size — larger requests are rejected immediately with 413 rather than hanging.
  • Streaming responses (SSE) are fully supported end to end.
  • Region: United States.
  • During Beta, platform upgrades are applied by Guardway and may briefly restart your gateway; your configuration and history are unaffected.