Add OpenHands Enterprise sizing guide [PLTF-3389] - #710
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
jpelletier1
self-requested a review
August 10, 2026 14:57
jpelletier1
approved these changes
Aug 10, 2026
mamoodi
approved these changes
Aug 10, 2026
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.
Summary of changes
"How big a box do I need?" is the first question on every Enterprise deployment call, and we had no answer in the docs — just a single trial-baseline VM spec buried in Quick Start, which says nothing about what happens at 50 or 500 concurrent users. This ports the internal sizing guide to the docsite so customers and CEs can size a deployment without a call.
The guide sizes on peak concurrent sandboxes rather than headcount, since sandboxes are the bulk of the footprint and one user can run several at once. Everything derives from one planning unit (0.5 vCPU / 4 GiB / 10 GiB node disk / 10 GiB volume per sandbox), with a table per install mode: Replicated embedded cluster on a single VM, and Replicated Helm into an existing cluster.
enterprise/sizing-guide.mdx— new page. Planning unit, VM sizing table (5–100 peak sandboxes with example GCP/AWS/Azure machine types and data disks), Helm sizing table (10–1,000 peak sandboxes with node pool min/max, platform nodes, volume storage, PostgreSQL sizing), and post-rollout adjustment guidance.docs.json— nav entry under Enterprise → OpenHands Enterprise, betweenenterprise-vs-ossandquick-start. It sits above both install paths because it applies to both and is a pre-install decision; nesting it under VM Install or K8s Install would hide it from half its audience.enterprise/quick-start.mdx— note framing the 16 vCPU / 64 GiB requirement as the trial baseline (~15 concurrent sandboxes), pointing here for larger rollouts.enterprise/k8s-install/index.mdx,enterprise/k8s-install/resource-limits.mdx,enterprise/index.mdx— cross-links from the places where sizing decisions actually get made.Verified with
mint devlocally: page and nav render, tables lay out correctly.mint broken-linkspasses clean.Note:
llms.txt/llms-full.txtare intentionally not regenerated here. They're already stale onmain, so running the generator pulls ~1,650 lines of unrelated drift into this diff. The weeklycheck-llms-filesworkflow will pick this page up.