Infrastructure and Environment Pages Added to SGEN Docs
SGEN now ships a complete set of architecture documentation covering infrastructure overview, environment model, deployment and release flow, performance and reliability, and security and isolation. These pages give anyone evaluating the platform a clear, public-safe picture of how SGEN is built and governed — without exposing internal controls or unpublished technical detail.
What was added
Five new pages expand the architecture section. Each is written for a public audience — focusing on how the system is organized and operated, not on internal controls or private identifiers.
Infrastructure
Infrastructure overview
A top-level map of how SGEN's platform is structured — hosting model, service layout, and the server-side rendering architecture the platform uses in production.
Environments
Environment model
How staging and live environments are separated, how changes move between them, and what isolation means for a site running on SGEN.
Deployment
Deployment and release overview
The flow from change to production — how releases are packaged, staged, and rolled out without disrupting sites already live on the platform.
Reliability
Performance and reliability
How the platform is operated to stay fast and available — delivery, caching posture, and the operational commitments behind uptime.
Security and isolation
How tenant data is isolated, what the access control boundary looks like, and the controls that govern how SGEN handles content and credentials — written to answer audit questions at a public-safe level.
Where it fits
These pages sit in the Architecture section of SGEN Docs. They are designed for platform evaluators — technical buyers, IT reviewers, and developers who want to understand how SGEN is built before committing to it. Legacy CMS platforms typically leave this picture as a black box, forcing readers to learn the environment model by breaking it. SGEN's architecture documentation closes that gap before the question gets asked.
Heads up Nothing to configure. These are reference pages only — no settings change, no migration step, and no action is needed on existing sites.