diff --git a/docs/enterprise.md b/docs/enterprise.md index f126e283..105f9113 100644 --- a/docs/enterprise.md +++ b/docs/enterprise.md @@ -111,14 +111,21 @@ We run the proxy; you focus on your product. Included with every enterprise license: a dedicated Slack/Teams channel with our engineering team for integration, deployment, and provider troubleshooting. -| Severity | Response SLA | -|---|---| -| **Sev 0** — 100% production traffic failing | 1 hour | -| **Sev 1** — partial production impact | 6 hours | -| **Sev 2–3** — setup issues, non-urgent bugs | 24 hours (7am–7pm PT, Mon–Sat) | -| **Security patches** | 72 hours | - -Custom SLAs available on request. +### Supported Versions + +We provide enterprise support for the **last 4 stable releases** (approximately the most recent month of `v1.x.x:main-stable` releases). Stable releases come out weekly — see the [Release Cycle](./proxy/release_cycle.md) for details on how releases are cut and promoted. + +If you are running an older release, we recommend upgrading to a release within the supported window before opening a support request. + +### Response SLAs + +:::info + +Our response SLAs are currently being updated. We will publish revised SLA details here once they are finalized. + +For time-sensitive issues, please reach out via your dedicated support channel or [book a call](https://enterprise.litellm.ai/demo) — custom SLAs are available on request. + +::: --- diff --git a/docs/proxy/release_cycle.md b/docs/proxy/release_cycle.md index b3e056b0..1d90e12b 100644 --- a/docs/proxy/release_cycle.md +++ b/docs/proxy/release_cycle.md @@ -26,6 +26,11 @@ Stable releases come out every week (typically Sunday) ### Enterprise Support +:::info + +This section is being updated. We are currently re-defining what our enterprise support SLAs look like and will publish updated details here soon. + +In the meantime, please [reach out](https://enterprise.litellm.ai/demo) if you have questions about enterprise support for a specific release. + +::: -- Stable releases come out every week. Once a new one is available, we no longer provide support for an older one. -- If there is a MAJOR change (according to semvar conventions - e.g. 1.x.x -> 2.x.x), we can provide support for upto 90 days on the prior stable image.