Panellicense

Enable and control Sitejet Builder in cPanel and WHM

Sitejet Builder ships free with cPanel 116+. Turn it on per package, hide it where you don't want it, understand the premium upsell, and avoid the document-root overwrite that eats live sites.

7 min readUpdated 2026-07-03cpanel · sitejet · website builder · feature manager
schema: HowToschema: FAQPage

Sitejet Builder is cPanel's built-in website builder — the drag-and-drop, AI-assisted tool that landed in the panel after cPanel's parent acquired Sitejet. It's bundled with your cPanel license at no extra per-account cost, so on any server running cPanel & WHM 116 or newer your users can spin up a templated site without WordPress, Softaculous, or an FTP client. Premium tiers exist, billed by Sitejet directly, but the core builder is free.

This is for the operator deciding whether to expose it, and how. You control Sitejet the same way you control every other cPanel tool: through feature lists. That means you can enable it on your shared plans, hide it on VPS or reseller plans where it's noise, and keep it off the packages where it would collide with existing sites.

Confirm your version

Sitejet Builder requires cPanel & WHM 116 or later. Check before you go looking for the feature:

/usr/local/cpanel/cpanel -V

If you're on an older LTS or a pinned tier, the feature won't appear in Feature Manager at all. Nothing to configure — upgrade first.

Enable it in a feature list

Sitejet is a standard cPanel feature, so it's governed by feature lists attached to your packages. In WHM go to Home » Packages » Feature Manager. Either edit an existing list or type a new list name and click Add Feature List, then in the feature grid find Sitejet Builder and tick it. Save.

Any package using that feature list now shows Sitejet Builder in the cPanel sidebar under the Domains/Software area. Existing accounts pick it up on their next login — no re-provisioning needed.

Feature lists are plain files under /var/cpanel/features/. If you're scripting a fleet, you can flip the flag directly and rebuild rather than clicking through WHM for every list:

grep -l sitejet /var/cpanel/features/*
# add or edit the line in the target list, then:
/usr/local/cpanel/scripts/rebuildfeaturecache

Hide it where you don't want it

You cannot uninstall Sitejet Builder — it's part of cPanel now, like Softaculous integration or the File Manager. What you can do is leave the feature unticked in a given feature list, and it vanishes from cPanel for every account on that plan. There's no server-wide "off" switch; control is entirely per feature list.

For resellers, the reseller only sees Sitejet in the plans you allow them to build from. If you don't want resellers offering it at all, keep it out of the feature lists exposed to their reseller ACLs and package set.

What "free" actually covers

The distinction that trips up buyers: the builder is free, some features inside it are not.

  • Included at no cost: the editor, 140-plus responsive templates, the AI site generator (layout, copy, colour and font suggestions), responsive preview, unlimited page publishing to the account's own domain.
  • Premium, billed by Sitejet: the higher-tier add-ons Sitejet upsells inside the interface — think advanced integrations and agency features. These are a direct relationship between the end user and Sitejet, not something that touches your cPanel bill or your reseller margin.

So your cost is zero and stays zero. If a customer buys a premium Sitejet feature, that transaction bypasses you entirely. Worth knowing before support gets a "why am I being charged" ticket — the answer is that they clicked an upsell, and it's Sitejet's charge, not yours.

The document-root gotcha

This is the one that causes real damage. When a user publishes a Sitejet site — the blue rocket icon in the editor — it writes the generated site into the domain's document root. If that docroot already holds a live site, publishing overwrites it.

The classic incident: a customer has a working WordPress install on example.com, opens Sitejet "just to look", builds something, and hits publish. WordPress is now buried under static Sitejet output and the site is down. Nothing is deleted maliciously — the files are just replaced in place — but for a non-technical user it reads as a total loss.

If you host a lot of WordPress, make sure your onboarding docs say this plainly, because the builder gives no loud warning at publish time. Users who want WordPress should go through Softaculous or the WordPress toolkit and leave Sitejet for greenfield domains.

Sitejet or WordPress — steer the customer right

Sitejet is a static-output builder: fast, no plugins, no database, nothing to patch. That's a genuine advantage for a brochure or small-business site — there's no WordPress update treadmill and no plugin attack surface for Imunify360 to worry about. It's the wrong tool the moment the customer needs a blog with real content workflows, WooCommerce, memberships, or any plugin ecosystem.

Rough rule for your support team: brochure site, portfolio, landing page, or "I just need a web presence" → Sitejet. Anything that says store, blog with contributors, or "an app my developer built" → WordPress on LiteSpeed with LSCache. Setting that expectation up front saves migrations later.

Next steps

Is Sitejet Builder free with cPanel?+
Yes. The core builder — editor, 140-plus templates, the AI site generator, and unlimited publishing — is included in your cPanel license at no extra per-account cost on cPanel & WHM 116 or newer. Only certain premium features cost extra, and those are billed by Sitejet directly to the end user.
How do I enable Sitejet Builder in WHM?+
Go to WHM » Packages » Feature Manager, edit or create a feature list, tick Sitejet Builder, and save. Every package using that feature list shows the tool in cPanel on the account's next login.
How do I disable or remove Sitejet Builder from cPanel?+
You can't uninstall it — it's part of cPanel. But you can hide it by leaving the Sitejet Builder feature unticked in a feature list. Accounts on that plan won't see it. Control is entirely per feature list; there is no server-wide off switch.
Does publishing a Sitejet site overwrite an existing website?+
Yes. Sitejet publishes into the domain's document root. If a live WordPress or other site already lives there, publishing overwrites it. Always publish to an empty docroot or a fresh subdomain, and back up first if the domain already has content.
What cPanel version do I need for Sitejet Builder?+
cPanel & WHM version 116 or later. On older versions the feature does not appear in Feature Manager. Check your version with /usr/local/cpanel/cpanel -V and upgrade if needed.
Should customers use Sitejet or WordPress?+
Sitejet suits brochure sites, portfolios, and landing pages — static output, no plugins to patch. WordPress is the right choice for blogs with content workflows, WooCommerce stores, memberships, or anything needing a plugin ecosystem.

Related articles

All tutorials & how-tos →
how to
Set up JetBackup 5 deduplication backups to cut storage cost
JetBackup 5.4 added a deduplication backup structure that fingerprints data in chunks and stores each unique chunk once — here's how it works, where it pays off, and how to turn it on.
6 min read
how to
Plesk 360 setup guide for centralized licenses and monitoring
Plesk 360 is the SaaS control plane for everyone running more than one Plesk box — license management, uptime monitoring, and SSO into every panel from one dashboard.
7 min read
how to
Use the Plesk REST API with reseller and customer accounts
Plesk Obsidian 18.0.79 opens the REST API to reseller and customer accounts and adds file, log, and impersonation endpoints — how to authenticate and use them.
7 min read
Switch in an afternoon

Switch from your current reseller — free.

We migrate active cPanel, Plesk, LiteSpeed and CloudLinux licenses from any reseller. We prorate the first month so you never pay twice, and your customers see zero downtime during the swap.