Platform Architecture Overview
A public-safe overview of how SGEN uses a shared platform foundation to serve many sites while preserving site-level separation and controlled operations.
Architecture layer
The platform can be understood through a small set of system-level layers. Each one explains how SGEN serves multiple sites from one governed platform while keeping site behavior separated and controlled.
One governed application foundation serves multiple sites.
Incoming domains are used to identify the intended site context.
The platform loads the correct content and configuration for the active site.
Site content and settings remain separated even though the platform foundation is shared.
Environments and release handling reduce risk before live rollout.
What this page covers
This page explains the platform at the system level. It describes how SGEN is organized, how sites are served, how environments are separated, and how the platform supports scale, performance, and controlled change.
What SGEN is
SGEN is a shared platform for building, operating, and managing websites from one governed application foundation. Each site uses the same platform codebase, but site content and configuration are separated so that one site does not behave as another.
How the platform works
Every request reaches the platform through a controlled routing layer. The incoming domain determines which site configuration should be used. From there, SGEN loads the correct site context and serves the appropriate content, assets, and operational behavior for that site.
Why this architecture exists
This model is designed to reduce infrastructure duplication, improve operating efficiency, support faster onboarding of new sites, and make change management more consistent across the platform. SGEN is built to support many sites from one platform foundation instead of treating each site as a separate standalone stack.
What this architecture is designed to support
Public boundary
This page is intentionally public-safe. It does not expose private infrastructure details, internal credentials, exact network topology, unpublished operational controls, or protected service identifiers.