Repository navigation
docs: split workload isolation into two - #604
Open
authzed-catherine wants to merge 2 commits into
Open
authzed-catherine wants to merge 2 commits into
authzed-catherine wants to merge 2 commits into
Conversation
…olation The workload isolation page said every deployment gets hardware only you use, and listed Cloud. Cloud SpiceDB pods run on a node pool shared with other Cloud customers; they get reserved CPU and memory, not their own machines. Dedicated runs in a cloud account and cluster dedicated to the customer, and production permission systems get node pools of their own. - Rename the page to "Workload Isolation and QoS" (same URL) and describe both levels, with anchors for each. - Split the Picking a Product matrix row into Workload QoS (Cloud and Dedicated) and Full Workload Isolation (Dedicated only). - Correct the Deployments page, which said Cloud runs on hardware dedicated to your organization. Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: Catherine Chambers <[email protected]>
Contributor
|
Preview deployment status for this pull request.
|
jzelinskie
reviewed
Nov 12, 2026
| SpiceDB also runs on nodes that are separate from AuthZed's own platform services (see [Control Plane](#control-plane)), so management and monitoring work never competes with your permission checks. | ||
|
|
||
| On AuthZed Cloud, SpiceDB nodes are shared with other Cloud customers' deployments. | ||
| Your CPU and memory are reserved, but other resources on a node, such as CPU caches, memory bandwidth and network bandwidth, are shared. |
Member
There was a problem hiding this comment.
I think it'd help to clarify that the CPU cores themselves are pinned to the workload.
Contributor
Author
There was a problem hiding this comment.
Claude pushed an update that says each Cloud SpiceDB pod is pinned to its own whole CPU cores. Is that what you hand in mind @jzelinskie ?
Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: Catherine Chambers <[email protected]>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The workload isolation page said every deployment gets hardware only you use, and listed Cloud. Cloud SpiceDB pods run on a node pool shared with other Cloud customers; they get reserved CPU and memory, not their own machines. Dedicated runs in a cloud account and cluster dedicated to the customer, and production permission systems get node pools of their own.
Description
Testing
References