> ## Documentation Index
> Fetch the complete documentation index at: https://docs.guardway.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage

> What Redeploy and Delete actually do, what the statuses mean, and exactly what happens to your logs, usage, and configuration.

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

| Status           | Meaning                                                                  |
| ---------------- | ------------------------------------------------------------------------ |
| **Online**       | Healthy and serving requests.                                            |
| **Provisioning** | Being created or rebuilt — usually one to two minutes.                   |
| **Deleting**     | Being torn down after a Delete; Setup reappears when teardown completes. |
| **Attention**    | Something needs a look — try **Redeploy**, or contact support.           |

## 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

| Your data                                            | Where it lives                                           | Redeploy                             | Delete + later Setup                                                                            |
| ---------------------------------------------------- | -------------------------------------------------------- | ------------------------------------ | ----------------------------------------------------------------------------------------------- |
| Request logs (Logs view)                             | Guardway platform, 30-day retention                      | Kept, continuous                     | Kept until they age out; the new gateway starts its own log history                             |
| Usage & spend (graphs, totals)                       | Guardway platform                                        | Kept, continuous                     | **Organization-level totals stay continuous**; the new gateway's per-gateway charts start fresh |
| Configuration (providers, keys, guardrails, budgets) | Guardway platform (the dashboard is the source of truth) | Reapplied automatically              | Carried to the new gateway automatically                                                        |
| Data on the gateway instance itself                  | Your dedicated gateway only                              | Reset (that's the point of Redeploy) | Removed with the gateway                                                                        |

<Note>
  **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.
</Note>

## Limits and behavior worth knowing

* **One SaaS Gateway per organization.** Need more? [Talk to us](mailto:support@guardway.ai).
* **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.