Skip to content

docs: split workload isolation into two - #604

Open
authzed-catherine wants to merge 2 commits into
mainfrom
workload-qos-docs
Open

authzed-catherine wants to merge 2 commits into
mainfrom
workload-qos-docs

Conversation

@authzed-catherine

Copy link
Copy Markdown
Contributor

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.

Description

Testing

References

…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]>
@github-actions

github-actions Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Preview deployment status for this pull request.

Name Status Preview Updated (UTC)
docs 🟢 Ready Visit Preview Nov 10, 2026 08:04pm

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.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it'd help to clarify that the CPU cores themselves are pinned to the workload.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

1 active (outdated) deployment
Preview (GitHub Actions) — 72c0eb6d Deployed Nov 10, 2026 by github-actions[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants