diff --git a/pages/authzed/concepts/management-dashboard.mdx b/pages/authzed/concepts/management-dashboard.mdx
index 1d7744f..1a62480 100644
--- a/pages/authzed/concepts/management-dashboard.mdx
+++ b/pages/authzed/concepts/management-dashboard.mdx
@@ -3,11 +3,10 @@
The Management Dashboard is a web-based application for organizations to manage SpiceDB deployments.
The dashboard is primarily targeting platform operators that want to configure and monitor the service.
-The Management Dashboard is exclusive to AuthZed [Dedicated], [Cloud], and [Serverless].
+The Management Dashboard is exclusive to AuthZed [Dedicated] and [Cloud].
In order to support a wider variety of environments, [Enterprise] customers configure [Extenders] directly instead of the Management Dashboard.
[Dedicated]: ../guides/picking-a-product#dedicated
[Cloud]: ../guides/picking-a-product#cloud
-[Serverless]: ../guides/picking-a-product#serverless
[Enterprise]: ../guides/picking-a-product#enterprise
[Extenders]: ./extenders
diff --git a/pages/authzed/concepts/restricted-api-access.mdx b/pages/authzed/concepts/restricted-api-access.mdx
index e75d39a..43bd380 100644
--- a/pages/authzed/concepts/restricted-api-access.mdx
+++ b/pages/authzed/concepts/restricted-api-access.mdx
@@ -43,7 +43,7 @@ Here's what an example Restricted API Access Token looks like.
sdbst_h256_thisisnotaverysecuresecret
```
-This is what you should forward in your API calls to your SpiceDB Dedicated cluster.
+This is what you should forward in your API calls to your AuthZed Dedicated cluster.
If you are using [static configuration] in your own SpiceDB Enterprise deployment, you'd need to
generate a token hash to be included in your configuration YAML.
diff --git a/pages/authzed/concepts/security-embargo.mdx b/pages/authzed/concepts/security-embargo.mdx
index 4473077..bc98b52 100644
--- a/pages/authzed/concepts/security-embargo.mdx
+++ b/pages/authzed/concepts/security-embargo.mdx
@@ -62,7 +62,7 @@ In the absense of a strict deadline, vulnerabilities are made public once every
## What actions must users under embargo take?
-Dedicated and Serverless Deployments running the latest release in any [Update Channel] are automatically upgraded to include embargoed security patches.
+Dedicated Deployments running the latest release in any [Update Channel] are automatically upgraded to include embargoed security patches.
Deployments with versions pinned to an older release and self-hosted users under embargo are given notice, but are ultimately responsible for updating their own software.
diff --git a/pages/authzed/guides/picking-a-product.mdx b/pages/authzed/guides/picking-a-product.mdx
index 0a737a4..1344d63 100644
--- a/pages/authzed/guides/picking-a-product.mdx
+++ b/pages/authzed/guides/picking-a-product.mdx
@@ -11,18 +11,18 @@ This document is designed to give a high-level overview so that you can effectiv
The following table maps functional requirements to their respective products:
-| Requirements | [Open Source] | [Serverless] | [Cloud] | [Dedicated] | [Enterprise] |
-| ---------------------- | :-----------: | :----------: | :-----: | :---------: | :----------: |
-| [Management Dashboard] | ❌ | ✅ | ✅ | ✅ | ❌ |
-| No-commit pricing | ✅ | ✅ | ✅ | ❌ | ❌ |
-| [Private Networking] | DIY | ❌ | ❌ | ✅ | DIY |
-| [Workload Isolation] | DIY | ❌ | ✅ | ✅ | DIY |
-| Self-Hosted | ✅ | ❌ | ❌ | ❌ | ✅ |
-| [Automated Updates] | DIY | ✅ | ✅ | ✅ | DIY |
-| [SOC2 Compliance] | DIY | ❌ | ❌ | ✅ | DIY |
-| [Audit Logging] | ❌ | ❌ | ✅ | ✅ | ✅ |
-| [Multi-Region] | DIY | ❌ | ❌ | ✅ | DIY |
-| [Security Embargo] | ❌ | ✅ | ✅ | ✅ | ✅ |
+| Requirements | [Open Source] | [Cloud] | [Dedicated] | [Enterprise] |
+| ---------------------- | :-----------: | :-----: | :---------: | :----------: |
+| [Management Dashboard] | ❌ | ✅ | ✅ | ❌ |
+| No-commit pricing | ✅ | ✅ | ❌ | ❌ |
+| [Private Networking] | DIY | ❌ | ✅ | DIY |
+| [Workload Isolation] | DIY | ✅ | ✅ | DIY |
+| Self-Hosted | ✅ | ❌ | ❌ | ✅ |
+| [Automated Updates] | DIY | ✅ | ✅ | DIY |
+| [SOC2 Compliance] | DIY | ❌ | ✅ | DIY |
+| [Audit Logging] | ❌ | ✅ | ✅ | ✅ |
+| [Multi-Region] | DIY | ❌ | ✅ | DIY |
+| [Security Embargo] | ❌ | ✅ | ✅ | ✅ |
[Cloud]: #cloud
[Dedicated]: #dedicated
@@ -95,44 +95,10 @@ Upcoming functionality includes:
- Deployments in more regions, including Europe
- Full SpiceDB API access: Watch API, HTTP API
- Enterprise features like Audit Logs, Restricted API Access
-- Removal of Serverless limitations: no rate-limits or prefixes required
AuthZed Cloud is built on the same foundation that's serving critical production workloads in AuthZed Dedicated.
During Early Access, the self-service control-plane functionality is considered experimental, but SpiceDB continues to operate with its existing level of reliability and performance.
-### Serverless
-
-[Serverless] is the Authzed product for self-service, shared-hardware SpiceDB clusters for evaluation purposes.
-
-- This is a fully managed service run by the experts at Authzed.
-- Clusters are autonomously configured and scaled without any configuration necessary.
-- Provision and manage permission systems and view real time metrics all from one place: our dashboard.
-
-
- **Warning:**
- Serverless is not an accurate representation of Dedicated/Cloud performance.
-
- Serverless lacks [Workload Isolation] and hardware configurations customized for your usage patterns.
-
- [Workload Isolation]: ../concepts/workload-isolation
-
-
-Serverless charges on a monthly billing period based on API usage.
-
-API usage is measured in two dimensions: operations (dispatches) and storage (relationships stored).
-
-The first 1 million of each are free.
-
-| Dimension | Price per Million |
-|-----------------------|-------------------|
-| Dispatched Operations | $1 |
-| Relationships Stored | $1 |
-
-To understand and calculate your workloads' dispatches, you can refer to the documentation on [debugging requests][debug].
-
-[Serverless]: https://app.authzed.com/?utm_source=docs&utm_content=spicedb+serverless
-[debug]: /spicedb/modeling/validation-testing-debugging
-
### Open Source
We understand that AuthZed's product suite will not satisfy all use cases and, for that reason, we've built and continue to invest in an open-source community around SpiceDB.
diff --git a/pages/authzed/links/_meta.json b/pages/authzed/links/_meta.json
index 1ff07fc..ae76352 100644
--- a/pages/authzed/links/_meta.json
+++ b/pages/authzed/links/_meta.json
@@ -15,7 +15,7 @@
"newWindow": true
},
"status": {
- "title": "Serverless Status Page",
+ "title": "Service Status Page",
"href": "https://status.authzed.com?utm_source=docs",
"newWindow": true
}
diff --git a/pages/spicedb/concepts/datastore-migrations.mdx b/pages/spicedb/concepts/datastore-migrations.mdx
index e580fe3..20e0557 100644
--- a/pages/spicedb/concepts/datastore-migrations.mdx
+++ b/pages/spicedb/concepts/datastore-migrations.mdx
@@ -72,13 +72,11 @@ More information on the use case/motivation is available in [this issue](https:/
## Recommendations
-### Managed services
+### Managed Service
Rather than handling updates yourself, SpiceDB is offered as a [managed service].
-Depending on the service, the update strategy varies:
-- SpiceDB Serverless upgrades seamlessly to track the latest release (and sometimes newer)
-- SpiceDB Dedicated users can select the desired version of SpiceDB
+- AuthZed Dedicated users can select the desired version of SpiceDB
No matter which service you select, zero-downtime migrations are always performed.
diff --git a/pages/spicedb/concepts/schema.mdx b/pages/spicedb/concepts/schema.mdx
index 2a5b214..0127234 100644
--- a/pages/spicedb/concepts/schema.mdx
+++ b/pages/spicedb/concepts/schema.mdx
@@ -37,12 +37,6 @@ caveat somecaveat(someparameter int) {
definition someobjecttype {}
```
-
- Note that the examples are unprefixed. You'll need to add the prefix from your
- permissions system if calling `WriteSchema` for a permissions system hosted in
- Serverless.
-
-
### Object Type Definitions
An Object Type definition is used to represent a new type of object.
diff --git a/pages/spicedb/getting-started/discovering-spicedb.mdx b/pages/spicedb/getting-started/discovering-spicedb.mdx
index df939b0..5848470 100644
--- a/pages/spicedb/getting-started/discovering-spicedb.mdx
+++ b/pages/spicedb/getting-started/discovering-spicedb.mdx
@@ -169,7 +169,7 @@ Even if you aren't interested in paid products, you can still schedule a call or
} title="Deploy the Operator on Kubernetes" href="/spicedb/ops/deploying-spicedb-operator" />
-} title="Deploy a SpiceDB cluster on Amazon EKS" href="/spicedb/ops/deploying-spicedb-on-eks" />
+} title="Install a SpiceDB cluster on Amazon EKS" href="/spicedb/getting-started/install/eks" />
} title="Schedule a call with AuthZed" href="https://authzed.com/call?utm_source=docs_discovering_spicedb" />
diff --git a/pages/spicedb/getting-started/install/eks.mdx b/pages/spicedb/getting-started/install/eks.mdx
index 5cb73eb..ef21f4f 100644
--- a/pages/spicedb/getting-started/install/eks.mdx
+++ b/pages/spicedb/getting-started/install/eks.mdx
@@ -157,7 +157,7 @@ SpiceDB [dispatches] work across instances in the same deployment via [gRPC].
We'll be securing this pod-to-pod communication with its own internal-only certificate:
[gRPC]: https://grpc.io
-[dispatches]: ../concepts/dispatch
+[dispatches]: ../../concepts/dispatch
```sh
kubectl apply --server-side -f - <