What SGEN is
The 60-second answer. SGEN is one CMS platform that replaces the WordPress + page-builder + plugin stack — operated entirely in the browser across five surfaces: SG-Core (the essentials — pages, media, users, templates), SG-Modules (first-party features that replace plugins — forms, SEO, ecommerce, and more), SG-Dashboard (see and run every site in your account), SG-Admin (run one site day to day), and SG-Builder (drag-and-drop visual layout). No installs, no plugin sprawl, no update fragility. If you've outgrown WordPress + Elementor + a plugin pile, SGEN is the consolidated alternative.
It's one operating system with distinct surfaces, not a bundle of disconnected tools — and it's browser-first: the operator surfaces are URLs, not installs.
Where to go next: The five surfaces · What it replaces · Is SGEN right for you? · Surface-to-task lookup
The five surfaces
Every SGEN site is composed from the same five surfaces. This page names them; the Platform overview walks each one section by section.
| Surface | What it owns | Coming from WordPress |
|---|---|---|
| SG-Core | Pages, posts, media, users, menus, templates, custom objects, fields | "WordPress core", consolidated and governed |
| SG-Modules | First-party features — forms, SEO, ecommerce, redirects, attribution, events, and more | Your whole plugin pile, replaced |
| SG-Dashboard | Account view — every site, billing, cross-site analytics, backups, reports | Multi-site management plugins, native |
| SG-Admin | Single-site shell — publish, settings, environments, run modules, open the builder | WP-Admin, quieter and governed |
| SG-Builder | Drag-and-drop visual page composition with clean, semantic output | Elementor / page builders |
They share one data layer. A page lives in SG-Core, gets its layout in SG-Builder, is published in SG-Admin, and shows its analytics in SG-Dashboard — the same record moving through each surface. That's why no single surface is "the platform"; the platform is how they cooperate.
pick a site
manage records
visual compose
live
What it replaces
SGEN keeps the familiar patterns — pages, posts, menus, media, templates — and removes the dependency sprawl, update fragility, and performance overhead of a stitched-together stack. The structural mapping:
| Legacy stack | SGEN |
|---|---|
| WordPress core | SG-Core |
| Elementor / page builders | SG-Builder |
| Plugin pile (forms, SEO, attribution, popups...) | SG-Modules (first-party) |
| Multi-site management plugins | SG-Dashboard (native) |
| WP-Admin | SG-Admin (consolidated, governed) |
Full reasoning and the migration framing: How SGEN replaces your WordPress stack · How SGEN is different · Why SGEN exists.
Is SGEN right for you?
SGEN is built for operators who run sites — agencies, in-house teams, founder-operators, designers, and developers. It's a strong fit if you publish and maintain content sites, run one site or a portfolio, and want your features built in rather than bolted on.
It's a weaker fit for pure CDN-edge static publishing with no CMS layer, single-purpose web apps unrelated to content, or workflows that hinge on one specific WordPress plugin with no SGEN equivalent yet.
Pick the path for your role: For your role routes founders, marketers, designers, developers, agencies, and ecommerce managers to a tailored start.
Surface-to-task lookup
| You want to | Surface |
|---|---|
| Add or edit a page | SG-Builder (in the admin) |
| Manage users for one site | SG-Core → Users |
| Add a contact form | SG-Modules → Forms |
| See traffic across all sites | SG-Dashboard → Live Analytics |
| Run a backup | SG-Dashboard → Backups |
| Configure SEO for a page | SG-Modules → SEO |
| Set up a redirect | SG-Modules → Redirects |
| Edit a template | SG-Core → Templates (or Theme Editor) |
| Add custom CSS site-wide | Custom CSS surface (in the admin) |
| Switch staging to live | the admin → Stage & Live |
A starting point — open the relevant section landing for the full feature docs.
Where to find it
- The platform —
dashboard.sgen.com(SG-Dashboard) and inside each site (SG-Admin / SG-Builder). - The docs —
docs.sgen.com(this surface). - The marketing site —
sgen.comfor buyer-facing positioning and pricing.
Related reading
- Platform overview — the five surfaces, in depth.
- How SGEN replaces your WordPress stack — the structural migration.
- Why SGEN exists — the problem statement.
- How this documentation works — reading model.
- Documentation map — the full IA.
Surface-to-task lookup
| You want to | Surface |
|---|---|
| Add or edit a page | SG-Builder (in the admin) |
| Manage users for one site | SG-Core → Users |
| Add a contact form | SG-Modules → Forms |
| See traffic across all sites | SG-Dashboard → Live Analytics |
| Run a backup | SG-Dashboard → Backups |
| Configure SEO for a page | SG-Modules → SEO |
| Set up a redirect | SG-Modules → Redirects |
| Edit a template | SG-Core → Templates (or Theme Editor) |
| Add custom CSS site-wide | Custom CSS surface (in the admin) |
| Switch staging to live | the admin → Stage & Live |
