The SGEN all-in-one model

The 30-second answer. SGEN is one unified platform, not a stack of separate tools you assemble yourself. You do not buy a builder from one place, hosting from another, a security service from a third, and then spend your time making them talk to each other. With SGEN, the builder, the dashboard, and the infrastructure are one system with one login — and the infrastructure that runs every site (hosting, SSL, CDN, the web firewall, security patching, and the multi-site dashboard) is bundled into every plan, even the free Sandbox, as the Foundation Pack. On top of that base, you add Module Suites — Forms, Page Builder, SEO & Performance, Attributions, and more — for the capabilities your site needs. Build and test in the free Sandbox for as long as you like; choose a plan and the suites you need only when you go live.

On this page: One platform, not a plugin stack · What's bundled vs what you add · What the model still rules out · How plans and suites work together · The free Sandbox · Where to go next

This is an orientation page that explains the SGEN all-in-one model — what "all-in-one" means in practice, what is bundled, what you add as you need it, and why that changes the questions you have to ask. For exact plan names, prices, live-site counts, and the current Module Suites, see Choose your SGEN plan.

One platform, not a plugin stack

When you sign in to SGEN, you are not looking at a thin core waiting to be extended. The builder, the dashboard, and the infrastructure underneath are one system with one login. The "all-in-one" in the name is about the platform being a single, unified product — not a pile of separate tools you bolt together yourself.

This is the opposite of how many website setups work. The common pattern is a thin builder plus a shopping trip: a forms tool from one vendor, an SEO tool from another, a separate analytics product, hosting and security from somewhere else again — and then you spend real time making them play nicely together, and re-checking that they still do after every update. SGEN's answer is to be one platform whose parts are designed to work together because they are one system. The capabilities you turn on are first-party Module Suites that ship and update with the platform, not third-party add-ons from a marketplace you have to keep compatible.

What's bundled vs what you add

It helps to separate two things the all-in-one platform gives you: the infrastructure that comes with every plan, and the capabilities you add as your site needs them.

Bundled on every plan — the Foundation Pack. Every plan, including the free Sandbox, includes the infrastructure layer at no extra cost: managed hosting, an SSL certificate (the padlock and HTTPS in your visitor's browser, provisioned and renewed automatically), a CDN that speeds up loading for visitors anywhere, a web application firewall that filters known bad traffic, ongoing security patching, and the multi-site dashboard. You never buy these as separate products, and you never buy a "security plan" on top of your plan — they are part of what a site is on SGEN.

Added as you need them — Module Suites. The richer capabilities come as Module Suites you add à la carte: Forms, Page Builder, SEO & Performance, Attributions, and more. You pay only for the suites your site uses, each appears as its own line item on your invoice, and you can add or remove them from SG-Dashboard → Billing → Subscriptions. When a suite is active, its features appear inside SG-Admin for that site — no reinstall, no restart.

What the model still rules out

The all-in-one model removes real friction — just not by putting every feature on every plan. What it genuinely rules out:

• No plugin marketplace to assemble. Capabilities are first-party Module Suites that ship and update with the platform, not third-party plugins you install and keep compatible. Full detail: SG-Modules overview.
• No separate infrastructure bills. Hosting, SSL, CDN, the firewall, and security are bundled into every plan as the Foundation Pack. You do not source or budget them as separate line items.
• No integration glue. Because the surfaces share one data layer, a form, a page, and the dashboard all read the same records. There is nothing to connect, sync, or reconcile between tools.

The practical result: you still decide which capabilities your site needs — that is what Module Suites are for — but you never assemble a working platform from parts, and you never maintain the seams between separate products.

How plans and suites work together

Your cost on SGEN comes from two simple levers, and they are independent of each other:

• Your base plan sets how many live sites you can run. A live site is one published on a real domain and serving visitors. Building and testing in the free Sandbox costs nothing; the base plan you choose is the one that covers your live site (or sites).
• Module Suites set which capabilities your site has — Forms, Page Builder, SEO & Performance, Attributions, and more. You add the suites your site needs and skip the ones it does not.

Moving up a base plan raises how many live sites you can run; it does not, on its own, change what an existing site can do. To change what a site can do, you add or remove a Module Suite. The two levers are separate, so you adjust each as your needs change.

A quick reference for the questions new users ask most often:

For exact plan names, prices, live-site counts, and the current Module Suites, see Choose your SGEN plan.

Why this matters to you

The model is not just a billing detail — it changes how you work. Three practical things follow from it:

• The infrastructure is never your problem. Hosting, SSL, the CDN, the firewall, and security are bundled into every plan, so there is no hosting bill to chase, no certificate to renew, and no security service to wire up. You start every site with that layer already in place.
• There is nothing to keep compatible. Because the capabilities you add are first-party Module Suites, not third-party plugins, you are not maintaining a stack of add-ons that can drift out of sync after an update.
• Your choices stay separable. "How many sites do I run?" and "what does this site need to do?" are two independent questions — your base plan answers the first, Module Suites answer the second — and you can revisit either one later without disturbing your existing sites.

For a fuller comparison with how other platforms are put together, see How SGEN is different.

The free Sandbox sits underneath all of it

Every account starts with a free Sandbox. The Sandbox is a complete SGEN environment, with no time limit, where you build and test before anything goes live. The Foundation Pack — hosting, SSL, the CDN, the firewall, security, and the dashboard — is already there, so the Sandbox is the real platform, not a stripped-down demo. You build and test privately, and choose a base plan (and any Module Suites you need) only when you are ready to go live.

A few practical facts about the free Sandbox: it runs on an SGEN subdomain rather than your own custom domain, it is blocked from search engines so nothing you build there shows up in search results, and it allows up to 1,000 visits per month — plenty for building and sharing privately with a few people. A Sandbox that sits inactive is archived automatically after roughly 30 days, so if you are stepping away for a while, sign in occasionally to keep it active. When you are ready, you promote the Sandbox to a paid live site at any time.

Full detail: SGEN sandbox walkthrough.

Where to go next

• Choose your SGEN plan — actual plans, prices, and live-site counts.
• Plans, billing, and what every plan includes — billing detail and what each plan covers.
• SGEN platform overview — how the platform is organised.
• How SGEN is different — coming from another platform.