Plesk’s new “AI-generated site” option is basically Sitejet Builder’s AI Website Generator, running as a hosted service (ai.sitehub.io) that’s bundled with your Plesk license and does not require your own API key.
What it is under the hood
- Plesk integrated Sitejet Builder’s AI Website Generator directly into the panel (new domain wizard, dashboard banner, and inside Sitejet itself).
- When you pick “AI-generated site” on subscription creation, Plesk hands your basic business info (name, industry, etc.) to Sitejet’s backend, which then generates a complete, responsive, SEO-ready site with layout, text, and images.
- The ai.sitehub.io URL you see is Sitejet’s hosted creation/editing flow, which then saves the result back into the Sitejet Builder instance tied to your Plesk.
How they’re doing the AI part
- Plesk/Sitejet are using their own integrated AI stack behind the scenes; they do not rely on your personal Gemini/OpenAI API key, which is why it works even though you never configured an API.
- The flow is: you input a short paragraph / business details → their AI models generate structure (pages/sections), placeholder images, and SEO-style copy → you land in the Sitejet drag‑and‑drop editor to tweak everything.
- They also use AI for ongoing text/SEO generation inside Sitejet (AI text generator, SEO helpers, translations), again provided as part of the extension.
Pricing / will they charge you?
- Sitejet Builder (including the AI Website Generator) is marketed as included “free with any Plesk license”—it’s part of the Sitejet Builder extension, not a separate per‑site AI add‑on.
- Plesk’s public materials and launch posts emphasize that the AI generator is “included free with Sitejet Builder” and “free with Sitejet Builder for Plesk,” i.e., as long as your Plesk license includes/permits the Sitejet Builder extension, you can use it without an extra AI fee.
- There’s no indication of a hidden, later-on per-site AI charge from ai.sitehub.io for Plesk users; it’s positioned as part of the hosting/control‑panel value rather than pay‑per‑generation.
That said, if your provider resells Plesk, they could always add their own markup or limits (e.g., only on certain plans), but nothing in Plesk’s own docs suggests you’ll hit a surprise charge just for finishing or publishing that generated site.
What happens to the generated site
- Once AI generation is done, the site is fully editable in Sitejet Builder: drag‑and‑drop layout, change colors, upload your logo, replace text/images, add forms, and tweak SEO.
- The steps you’re seeing now (logo, color palette, etc.) are part of Sitejet’s standard “complete the generation steps to fully customize your site” flow.
- When you publish from within Plesk/Sitejet, the files and configuration are deployed to your hosting just like any other Sitejet-built site.
Quick reassurance for your current use
- The ai.sitehub.io wizard you’re on is the official Sitejet/Plesk AI creator, not some third‑party upsell.
- You shouldn’t be asked for a separate AI subscription just to complete and publish this site, as long as your existing
- Plesk license covers Sitejet Builder.
With Web Host Max, Sitejet Builder (including the AI Website Generator you’re using) is included for all domains where the service plan has “Access to Sitejet Builder” enabled, so you’re not in some separate trial just by using that ai.sitehub.io flow.
What “included” means for you
- Plesk’s own Sitejet Builder page says it is “included free with any Plesk license,” which covers Web Host / Web Host Max editions like yours.
- As long as your service plans in Plesk have the Sitejet permission turned on, every domain dashboard can use Sitejet and the new AI Website Generator without an extra Plesk-side fee.
AI generator specifically
- The AI Website Generator is part of Sitejet Builder for Plesk, not a separate billed add-on; it’s advertised as a built-in feature of Sitejet (“New AI Website Generator feature”).
- The fact that you can click it from each domain dashboard is exactly how Plesk intends hosts on Web Host/Max to offer it—no need for per-domain AI licensing on your side.
What to watch for (if anything)
- In a self-licensed Web Host Max setup, you can safely keep going in that wizard and publish; it should behave like any other Sitejet site, just auto-generated instead of starting from a template.
There’s no real chatter about Sitejet-built sites being a common hacking target; if anything, they tend to be seen as lower-maintenance and less exposed than DIY CMS stacks like WordPress.
What’s known about Sitejet security
- Sitejet publishes that their hosting stack is redundant, monitored, and protected with DDoS mitigation, spam protections (rate limiting, honeypots, captchas), and an internal disaster-recovery plan.
- They explicitly avoid sharing implementation details publicly, which is standard practice, but their uptime/security doc and status page indicate stable operation rather than recurring compromise incidents.
“Hacked sites” chatter (or lack of it)
- Public Sitejet community/news threads talk about availability, email deliverability issues, and occasional incidents, but not about systemic “all our sites got hacked” type events.
- Blog posts comparing Sitejet vs WordPress frame Sitejet’s managed updates and automatic SSL as a way to reduce vulnerabilities compared with plugin-heavy WordPress sites, which are well-known hack magnets if not maintained.
Your specific risk profile on Plesk
- Because the Sitejet project is generated and managed inside the builder, you’re not running a big PHP app with third‑party plugins that you or customers keep updating (and breaking), which removes a ton of typical exploit surface.
- Your actual attack surface is more about Plesk server hygiene (patching, firewall, strong auth, Imunify/Fail2Ban, etc.) than about Sitejet’s templates themselves; standard Plesk hardening guidance still applies.
Practical hardening steps for these sites
- Keep Plesk and extensions updated, enforce strong passwords and MFA on Plesk, and make sure the site is always served over HTTPS.
- Use an existing stack (Imunify360, firewall, Fail2Ban) to watch for anomalies, and treat the Sitejet-generated site like any other virtual host from a server-security perspective.