Kernel-level isolation (CloudLinux LVE)
Per-site caps on CPU, RAM, IO, IOPS, processes and entry-processes. A runaway or attacked site is throttled inside its own cage — one site can never take down the rest.
Multisite hosting
Run dozens or hundreds of sites on one platform without them looking like one operation. Every site gets kernel-level isolation, its own delivery path and clean IP space — so no single site can slow, expose or blocklist its neighbours. Availability: per-site database throttling is in active development and not yet available. Everything else described here is live today.
Managing many sites in one place usually means a trade-off: convenience in the panel, but a shared footprint underneath — one IP range, one account, one bad neighbour dragging everyone down. Multisite hosting from Zinn Digital® removes that trade-off. You get a single control plane for the whole portfolio, while each site is isolated at the kernel and delivered independently.
The same footprint-free technology that runs behind our largest networks powers every plan here — built for density and separation from day one, whether you host ten sites or a thousand.
Every site is separated at the layers that matter, then served over its own path.
Per-site caps on CPU, RAM, IO, IOPS, processes and entry-processes. A runaway or attacked site is throttled inside its own cage — one site can never take down the rest.
Each site gets its own filesystem view. It cannot see other sites, other tenants, or sensitive system files — breaches are contained, not spread.
Add your own Cloudflare and CDN accounts alongside ours, and choose which account each site deploys to. Delivery is spread, not stacked behind one shared edge.
No bad-neighbourhood IPs. Sites are balanced across accounts and separated at the edge, so one compromised site's reputation problem stays its own.
Separation isn't cosmetic — it protects every site's availability, security and reputation.
Portfolio and agency work is repetitive by nature — so the platform is designed to do it once, across many.
Deploy, update and manage many sites at once, in a single action instead of one site at a time.
LSCache full-page cache and per-site Redis object cache keep every site fast, with coordinated purge from the panel or from inside WordPress.
Bring your existing portfolio across at no cost. We move the sites; you keep working.
Bring your own CDN and DNS accounts, keep ownership of your infrastructure, and leave whenever you like — nothing here is a trap.
What makes running dozens or hundreds of sites here different from a conventional multisite install.
Each site gets its own containment boundary rather than a shared install — one compromise cannot become all of them.
See isolation & containment →Sites are distributed across multi-account CDN and DNS pools, so a shared edge account is never the thread that ties your portfolio together.
See the CDN account pool →Run a large estate on subdomains without collapsing it into one install and one fingerprint.
See subdomains →Give a client or a contractor access to exactly the sites they need, with every privileged action audit-logged.
See delegated access →Daily backups with 30-day retention across every site, restorable individually in one click.
See backups & DR →Bulk operations, a web IDE and database maintenance across the whole estate rather than one dashboard login at a time.
See site tools →A multisite is many sites behind one install, so the add-ons that pay off are the ones that scale across all of them.
Updates
One bad plugin release reaches every site in a network at once. Updates are applied to a copy and checked before they touch the live install.
Read about AI Update Guard →Backups
A copy of the whole install kept somewhere that is not us, so a restore does not depend on the platform holding the original.
Read about external backups →Moving in
We take the network off your old host, put it up here, and check it works before anything is pointed at it.
Read about managed migration →Everything else
Monitoring, SEO data and expert services, bought per site and billed on the invoice you already receive. Migrations are free.
Read about the whole add-on catalogue →WordPress Multisite runs many sites from one shared codebase, database and installation — a genuinely shared fate. Our multisite hosting keeps every site fully separate: its own isolated filesystem, its own resource limits, its own delivery path. You manage them together, but nothing is shared underneath.
From a handful to several hundred on one account. The platform is built for density and scale, and we host over 700,000 sites worldwide today, so growing your portfolio doesn't mean re-platforming.
No. CloudLinux LVE caps each site's CPU, memory and IO inside its own cage, CageFS isolates the filesystem, and MySQL Governor throttles per-site database load. A site under attack or running away is contained to itself.
Only if you want them to. You can add your own Cloudflare and CDN accounts and pick which account each site deploys to, so delivery is spread across accounts rather than stacked behind one shared edge.
Yes. Migrations are free, and you can start on a card-free 14-day trial with a 30-day money-back guarantee, so you can move a few sites and confirm it fits before committing the whole portfolio.
Isolated per site, managed as one. Start free in minutes — no card, free migrations, 30-day money-back guarantee.
Start freeNot add-ons, and nothing extra to buy. These come with the line you are looking at.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Every message is scanned for viruses and checked against live spam blocklists, and forwarded mail stays trusted with SRS and ARC.
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.
Outlook, Apple Mail and phones find your mail settings automatically — type the address and password, and it works.
Every WordPress site we host on our own servers comes with these plugins installed and activated, at no extra cost. Pro editions are optional paid upgrades.
A free page cache and Redis object cache for WordPress on any server, that purges only what changed.
Works with AI agents (MCP): 18 actions
Zinn® Cache Pro is an optional paid upgrade, from $49.00 a year, with a 14-day free trial. Start the free trial →
A free AI live chat and help desk for WordPress: an assistant that answers from your own pages, live chat for your team and support tickets, all in your own database.
Works with AI agents (MCP): 36 actions
Zinn® Chat Pro is an optional paid upgrade, from $189.00 a year, with a 14-day free trial. Start the free trial →
A smaller WordPress fingerprint, and SEO crawlers denied while search engines are never blocked.
Multilingual WordPress done properly: one real post per language, translated addresses, multilingual SEO, and AI agents that can translate for you.
Works with AI agents (MCP): 74 actions
Tranzly™ Pro is an optional paid upgrade, from $89.00 a year, with a 14-day free trial. Start the free trial →
Hosting customers also get 50% off the first payment of every Zinn® Pro plugin. See the Pro plugins discount →
Every plan comes with it. There is no support tier to buy, no per-incident charge and no ticket allowance — and the desk is open 24 hours a day.
Support is part of hosting, not an upsell. It is the same support on the smallest plan as on the largest, and nothing about it is counted or capped per incident.
Whatever hour you are working and whatever time zone you are in, the desk is staffed. You are not writing into an inbox that opens in the morning.
Write your ticket in the language you actually think in — we translate it for our team and answer you in yours, with the original always one click away. We sell in all 58.
Our assistant answers instantly from the knowledge base, but it never closes a ticket for you. A ticket is picked up and answered by somebody who can act on it.