Not add-ons, and nothing extra to buy. These come with the line you are looking at.
Wayback restore
Buy an expired domain and put its old site back on it — pages, images, styling and internal links, at the addresses they had. Pick any date the public web archive holds, not just the last one, and we rebuild it as static HTML or as a WordPress site you can keep writing on.
See how it works
The web editor
On every site we host on our own fleet — a site you deploy elsewhere is edited there — open a full editor in your browser from the site's page and work on its real files, with git built in and the whole editor inside the same isolated jail as your SFTP access. Nothing to install, and it edits the live site: a file you save is public the moment it is written, though a static file may keep serving from the CDN cache for up to four hours.
See how it works
Zinnector®, the developer CLI
Free and MIT-licensed. Scaffold a WordPress site, run it on your own machine, pre-flight it against the slot you are about to deploy to, then deploy. Built on the same public API our dashboard uses, and it needs Node 24 or newer.
See how it works
MCP server for your AI
Connect the AI you already use — Claude, Cursor, ChatGPT — to your hosting over one Model Context Protocol server, and it can work on your sites through the same API and the same permissions the dashboard uses. Read-only by default — a tool that can change something has to be enabled for you first, so an agent cannot widen its own reach.
See how it works
Per-site developer access
Invite a developer by email address and fence them to one site. They sign in as themselves with a viewer, editor or manager role, every other site answers 404, and the account owner can revoke it in one click.
See how it works
Brute-force login protection
Bots that hammer your WordPress login or XML-RPC are throttled and shut out at the web server, before they can guess a password or slow your site down.
See how it works
Origin lock and locked-down servers
Your site answers only through our CDN — attackers cannot go round it to your server's IP address — and the servers' admin ports open only to our own systems.
See how it works
Website email that arrives
Password resets, contact forms and shop receipts are signed with SPF and DKIM so they land in the inbox, and queued and retried if a mail server is briefly down.
See how it works
Send through your own mail service
Prefer Google Workspace, Microsoft 365 or your own SMTP server? Connect it and your website sends through it — tested before it is used, with automatic fallback.
See how it works
Virus and spam filtering on every mailbox
Every message is scanned for viruses and checked against live spam blocklists, and forwarded mail stays trusted with SRS and ARC.
See how it works
A backup mail server
If the main mail server is ever down, a second one holds your mail until it is back — nothing is lost, and made-up addresses are refused so you are not used to spread spam.
See how it works
Mail apps set themselves up
Outlook, Apple Mail and phones find your mail settings automatically — type the address and password, and it works.
See how it works