# Zinn Digital® > AI-first, multi-tenant hosting and SEO platform. Two product lines on one engine: Footprint-Free hosting for bulk and PBN networks (footprint-aware CDN/DNS account pools, 106 managed footprints, static-HTML delivery), and mainstream managed WordPress, WooCommerce, reseller and agency hosting. Domains, an MCP server that connects any AI tool to your hosting, an AI assistant that performs real tasks, free repo-grade WordPress plugins, and a 14-day card-free trial. > Operated by Zinn Digital® LTD (company no. 16385785, VAT GB 526 5236 92), 71-75 Shelton Street, Covent Garden, London WC2H 9JQ, UK. This file is the full text of the public site, generated from source. --- # Every way to host — and everything a site needs to earn URL: https://zinndigital.com WordPress, WooCommerce, PHP, Node, Laravel, static sites and whole cloud servers, plus Footprint-Free hosting for PBNs. Deploy to our fleet, Netlify, Cloudflare Pages or GitHub Pages, track your rankings, buy and sell on our marketplace, and let AI build, write and watch your sites — in your language and currency. ## Not hosting with us? These work on any website Monitoring, project boards, live chat, AI answers, translation and backups — each one bought on its own with a free account, and pointed at sites hosted anywhere. - **Uptime checks for any URL** — Any address, hosted anywhere, checked from several locations — with three monitors free. - **Zinn® Boards** — Project boards your clients can see without an account — free for one board. - **Zinn® Chat** — A chat box for any website that answers from your own pages and hands over to you. Free to start. - **AI chat agent** — An assistant that answers visitors from your own pages, in their language, with a link to its source. - **Website translation** — Your WordPress site in 58 languages, each on its own indexable URL — wherever the site is hosted. - **Backups for any WordPress site** — Back up WordPress hosted anywhere to Cloudflare R2, and restore in one click. - **Domain monitoring** — Free expiry, registrar and nameserver alerts for any domain, at any registrar. - **Malware cleanup** — Expert removal and repair for a hacked site, whether or not you host with us. - **AI images** — Original images from a text prompt, on credit packs or your own provider key. - **Email campaigns** — Write, schedule and send through your own provider, with consent checked for every recipient. - **Private network** — An encrypted network for your team, with one dedicated static IP to allow-list. - **Domains** — Register, transfer or connect a domain, with WHOIS privacy, registrar lock and DNSSEC. - **Everything sold on its own** — Every product you can buy without hosting, with its starting price, on one page. ## Whatever you run, we host it Managed hosting for every stack, from a single WordPress site to an online store or a Laravel app — each with its own page and plans, and the same dashboard, API and support behind all of them. - **Managed WordPress** — LiteSpeed Enterprise with LSCache, a per-site Redis object cache, NVMe and HTTP/3. - **WooCommerce** — Your storefront served from cache, while cart, checkout and account pages always run live. - **Premium WordPress** — WordPress and WooCommerce on hardware we own and operate, with our own caching layer. - **PHP** — Managed PHP on a whole cloud server with root access and backups, in eight data centres. - **Node.js** — Managed Node.js on a whole cloud server with root access, sized from one core to forty-eight. - **Laravel** — One-click install, a managed plan with SSH, Git, Composer and cron, or a cloud server with root. - **Joomla** — One-click install, a managed plan with Joomla already running, or a cloud server with root. - **Magento** — Managed Magento on a whole cloud server, sized for a real catalogue. - **.NET** — .NET on Linux — one-click, fully managed, or a cloud server with the runtime you choose. - **Online courses** — WordPress with LearnDash or Tutor, or Moodle, with storage sized for video. - **Static sites** — Serve from our fleet, Cloudflare Pages or GitHub Pages — the backend is a per-site choice. - **Hosting for developers** — Deploy from GitHub or GitLab, branch a staging copy and push it live, and drive it all from an API, a CLI and an MCP server. - **Linux hosting** — One-click applications, MySQL databases, SSH, Git deploys and scheduled tasks — no database cap. - **Site portfolios** — Dozens or hundreds of sites with kernel-level isolation and no shared fingerprint. - **One-click applications** — Content management, ecommerce, frameworks, forums, CRM, learning and analytics — installed in one click. - **Find the right hosting** — Tell us about your site and the hosting finder recommends the plan that fits it. - **Which hosting is right for me?** — Every kind of hosting we sell in one table — what each is for, what it includes and where it starts. ## Servers, databases and AI infrastructure When a shared plan is not the right shape: whole machines, standalone databases, storage and inference — provisioned and managed from the same account. - **Managed cloud servers** — 1 to 48 vCPU cores and up to 128 GB of memory, tuned for your stack and run by us. - **Managed VPS** — 1 to 20 dedicated vCPU cores on NVMe storage, billed monthly or yearly. - **Private cloud machines** — Whole unmanaged machines with root SSH in six cities across three continents. - **Managed AWS** — Hosting on Amazon Web Services with published per-size prices and every control in our dashboard. - **Managed Google Cloud** — Hosting on Google Cloud with published per-size prices, tuned for your stack and run by us. - **Managed databases** — Standalone PostgreSQL and MySQL — no website required — with restores we verify. - **Object storage** — S3-compatible buckets with no egress fees, created from your dashboard or the API. - **AI inference hosting** — Serverless inference on open models — no GPU to rent and no idle capacity to pay for. - **Vector databases** — Managed pgvector for embeddings and semantic search, priced on storage and queries. - **Developer hosting** — Node.js, Python and Ruby apps deployed from Git, with one-click rollback and a preview for every branch. ## For agencies and resellers Run every client site from one place, or sell hosting as your own product — on the engine we built for our own fleet. - **Agency hosting** — Group client sites, give each person the right access, and present it all under your brand. - **Reseller hosting** — Sub-accounts, a white-label panel, per-client isolation and bulk provisioning. - **White-label** — Your brand on the panel, the emails and the invoices your clients receive. - **WHMCS and HostBill modules** — Free, open-source modules that provision and suspend real accounts from your own billing panel. - **Teams and single sign-on** — Owner, billing, developer and read-only roles, sub-accounts, SSO with passkeys and a full audit log. - **Delegated access** — Give a developer, an accountant or a client exactly the access they need — and nothing else. ## PBN hosting engineered to stay invisible Every site on its own CDN and its own nameservers, deployed as WordPress, static HTML, Joomla or a build pushed to Netlify — then run a thousand of them from one screen. 106 SEO footprints are removed automatically, at the server and in WordPress, and footprint-aware rotation spreads your sites across our CDN and DNS account pools or your own. It is the line this platform was built around, and it is priced by one thing only: how many sites. 42 tiers take you from 5 sites to 2,000, and every price is published. - 106 SEO footprints auto-managed on every deploy - Its own CDN and nameservers for every site - Block the backlink crawlers — never the search engines - Wayback Machine restore for expired domains - Our CDN and DNS account pools, or bring your own - 42 tiers, from 5 sites to 2,000 - **SEO footprint remover** — Strips the generator tag, version strings, discovery links, XML-RPC and pingbacks from every deploy. - **CDN and DNS account pools** — Balance is recomputed from live account state at every deploy, so distribution never drifts into a cluster. - **Crawler blocking** — Keep Ahrefs, Majestic, Semrush and Moz out of your network, per site, while search engines crawl freely. - **Wayback Machine restore** — Rebuild an expired domain's original site from the Internet Archive as clean static HTML or WordPress. - **Bring your own accounts** — Connect your own Cloudflare, CDN and DNS accounts and we drive them for your sites. - **42 published tiers** — Drag one slider to see the exact price of every tier, from 5 sites to 2,000. ## Our fleet, Netlify, Cloudflare Pages or GitHub Pages — your choice, per site Where a site is published from is a setting, not a migration. Deploy to our own managed fleet, to Cloudflare Pages, Netlify, GitHub Pages or GitLab Pages from our pooled accounts or your own, or push to a server you already pay for — and run every one of them from the same dashboard, API and MCP server. Connect the accounts you already use and we drive them for you. Every connection shows the permissions it needs, is checked when you add it, and is kept in a vault — never in code or a log. - Our fleet, Cloudflare Pages, Netlify, GitHub Pages and GitLab Pages - Your own server, from the same dashboard - Deploy from a GitHub or GitLab repository on every push - Bring your own Cloudflare, CDN and DNS accounts - **Cloudflare Pages** — A static site or a real edge application, with Pages Functions and bindings, managed from here. - **GitHub Pages** — We create the repository, push the build, wire the custom domain and roll back — one site or in bulk. - **Your CDN and DNS, per site** — Choose the CDN and DNS provider for each site at deploy, and change it from the dashboard or the MCP. ## Every product line, one place to run it Create a WordPress site, an application, a cloud server or a Footprint-Free network from the same screen — and then run all of it from one dashboard, in your language and currency. Bulk-add domains, install plugins across a portfolio, edit DNS, add mailboxes, take backups, open staging and hand a colleague exactly the access they need. Everything you can click, an agent can do through the same API. - One-click installers and every PHP version, per site - Reusable blueprints to redeploy a site in minutes - Bulk actions across hundreds of sites - Team roles, sub-accounts and single sign-on ## AI that builds, writes, answers and keeps watch Our AI is wired into the hosting, so it acts on your sites rather than describing them — on our credits or on your own provider key, on one meter you can see. - **AI site builder** — Describe the site you want and the AI builds it, then publishes it to any deploy target. Your first try is free. - **Zinn® Chat** — Live chat with an AI agent that answers your visitors first and hands over to a person when it cannot. - **Ask Zinn®** — Ask about plans, limits, prices or migrations and get a straight answer — no account needed. - **An assistant that does the work** — It can reset SSL, add disk, purge a cache or open a ticket — through the same actions you would click. - **AI content and images** — Write, illustrate and publish to your sites on a schedule, or generate an original image from a prompt. - **AI Webmaster** — Reviews your site against what only your host can see, every 30 days, and tells you what to fix. - **AI Update Guard** — Checks every plugin and theme update before it runs, instead of breaking your site on a schedule. - **AI visibility** — Find out every week whether ChatGPT, Claude, Gemini and Perplexity recommend you — or a competitor. - **Your site in 58 languages** — Every language on its own indexable URL with hreflang, and every language included. ## Your key or our credits — you choose, per provider Bring your own key for Anthropic, OpenAI, Google or xAI and those requests run on your account and cost you nothing here. Everything else comes out of your Zinn® AI credit, and the dashboard shows which is which, what each request cost and what is left. The same AI runs everywhere you work: in the dashboard, on your project boards, in the site builder and behind the chat on your site. - One meter for every AI feature - Your own provider key, per provider - The cost of every request, in your currency ## Built for developers — and for their AI agents Everything the dashboard does goes through the same public, versioned API, so an AI agent, our CLI, your scripts and our own screens all have the same powers. - **MCP server** — Connect Claude Code, Claude Desktop or Cursor once, and your agent can list your sites, read their logs, sync their files and deploy in plain language. - **Connect an AI agent in two minutes** — The exact config for Claude Code, Claude Desktop and Cursor, and every tool your agent can call — listed from the server itself. - **Zinnector® CLI** — Build WordPress locally with nothing but Node, pull a hosted site down to work on, and push it back — checked against the slot before you deploy. - **GitHub and GitLab** — Connect the account you already use and deploy straight from a repository — every push builds and deploys itself. - **Staging and push-to-live** — A staging copy in one click, and a database-aware sync back to live when you are ready. - **VS Code in the browser** — Open your site's real files in a full editor with git built in, inside the site's own isolated jail. - **SSH, wp-cli and phpMyAdmin** — A jailed shell, wp-cli, phpMyAdmin, a file manager, cron and environment variables for every site. - **Subdomains that are real sites** — Point app, shop or docs anywhere and get a genuinely isolated site behind each one. - **API and Terraform** — Spec-first, versioned and fully documented — the same API our own dashboard is built on. - **Webhooks** — Subscribe to platform events and receive them at your own endpoint. ## SEO tools built into your hosting Every site gets SEO Basics free — indexed status, Trust Flow and homepage Core Web Vitals. Go deeper with add-ons when you need them, or use the rank tracker on its own for any domain. - **Rank tracker** — A daily rank-tracking allowance comes with your hosting, paid keyword packs stack on top, and it works standalone for any domain — hosted with us or not. - **SEO Basics** — Indexed status, Trust Flow and homepage Core Web Vitals for every site, at no extra cost. - **Index monitoring** — Find out the day a page falls out of Google, not the month. - **Backlink monitoring** — Know when a link you paid for disappears — your profile is checked every week. - **Technical site audit** — Every page checked every month: broken links, missing titles and redirect chains. - **Competitor intelligence** — Track what your competitors rank for and what is being linked to, month by month. - **Keyword research** — Search volumes, related phrases and difficulty, for any market and any language. - **Domain authority** — Trust and citation scores for any domain, refreshed weekly and kept as a trend. - **SEO Pro** — Rank tracking, backlinks, competitor intel, a monthly health audit and the AI content assistant on one line of your invoice. ## Buy and sell links, sites and expertise — with the money held until it is delivered Guest posts, link building, SEO and AI services, web development, websites, domains and Shopify stores, all on one marketplace engine. Every order is held in escrow, and fulfilment is checked against live data before the seller is paid. Selling? List what you offer to the people already hosting with us, from the account you already have. - Escrow on every order - Fulfilment verified before funds are released - One checkout and one invoice for the whole platform ## Shopify stores, websites and domains — paid for only when the handover is done Your payment is held by us, a store or site is never accepted for you on a timer, and every sale carries a handover checklist. No listing fee for sellers. - **Shopify stores for sale** — Dropshipping, own-brand and print-on-demand stores, transferred to your own Shopify account. - **Websites for sale** — Content sites and online businesses, with the domain, files, analytics and Search Console handed over. - **Domains for sale** — Exact-match, brandable, aged and expired names, transferred to your registrar before the seller is paid. ## Browse by storefront - **Link building** — Backlinks, PBN placements, niche edits and GEO links. - **Guest posts** — Placements on real sites, filterable by niche and metrics. - **SEO services** — Audits, technical fixes, content strategy and consulting. - **AI and automation** — Agents, workflows and integrations that do the work. - **Web development** — Builds, migrations, fixes and ongoing development. - **Websites for sale** — Established sites, including ones not hosted with us. - **Domains for sale** — Names for sale, including ones not registered with us. - **Shopify stores for sale** — Live stores, sold with revenue disclosure. ## Just listed The newest listings across every storefront, live from the marketplace. ## Show your client the work, without giving them the keys Every other project tool makes you choose between a board your team can work on and a board your client is allowed to see. Zinn® Boards is one board with a visibility switch on every column, card and comment — your notes, your blockers and your internal estimates stay yours, while the client sees the stages, the work that is theirs to know about and the questions you have asked them. They open it from a link you paste into an email. No account, no invitation to accept, no seat to pay for — and the board sits beside the hosting it is about, in the same dashboard, so the work and the sites are not in two different tools. - A client view that hides your internal notes - Share by link — no account needed to look - AI that drafts cards, summarises a board and spots duplicates - Automations, two-way GitHub Projects sync, and full API and MCP access - Free for one board, and included with our Agency and Reseller plans ## Built in, not bolted on Each of these is part of the platform rather than an upsell — and each has a page explaining exactly how it works. - **Enterprise caching** — LiteSpeed full-page cache, a per-site Redis object cache and the CDN edge — most visits never reach PHP. - **AccelerateWP** — Object caching, critical CSS, deferred JavaScript and lazy-loaded images on every WordPress site. - **A free global CDN tier** — Serve pages from an edge close to your visitors, switched on in one click, on every plan. - **Per-site isolation** — Every site in its own kernel-level cage, so one compromised site cannot reach another. - **Malware scanning and WAF** — Malware scanning and a proactive firewall that blocks exploits before a patch exists. - **DDoS protection** — Floods absorbed at the edge and filtered upstream, so one attack stays one site's problem. - **Backups that survive the worst day** — Sites on our fleet get immutable, offsite backups kept apart from the servers they protect. - **A copy in storage you own** — Send every backup to your own S3-compatible bucket or SFTP server, encrypted before it leaves us — so a copy survives even us. - **Free migrations** — Bring one site or a whole portfolio across — files, database and all — at no charge. - **Email on your domains** — Real mailboxes, forwarders and autoresponders on the domains you host, managed beside the site. - **WordPress care, included** — Updates, backups, scanning, monitoring and a real person to ask — without a care-plan fee. - **Free Zinn® plugins** — Our cache and footprint plugins ship with every deploy, built to WordPress.org standards. ## Need something built? Our developers will quote it for free WordPress builds, custom plugins and themes, bug and error fixing on any site, and bespoke applications — by the engineers who built this platform, with more than 25 years of full-stack work behind them. Tell us what you need and we will send you a free quote. No retainer, and no obligation. - WordPress and WooCommerce builds - Custom plugins and themes - Bug and error fixing, on any site or CMS - Python, PHP, .NET and Node applications - **WordPress development** — Custom plugins, themes and blocks, WooCommerce, headless builds and rescue jobs. - **Python development** — Web apps, APIs, automation, data pipelines and AI integrations in production Python. - **Custom web development** — Complete applications in PHP, Python, .NET, JavaScript and Node, whatever the stack. ## Learn, ask and get help — in your language Answers in the knowledge base, guides on the blog, an assistant that answers from both, and people who reply. - **Knowledge base** — Step-by-step answers for hosting, domains, billing, plugins and more. - **Blog** — Guides and analysis on hosting, SEO and AI, written by the people who run the platform. - **Ask Zinn®** — A straight answer from our published knowledge base and live price list, and it says when it does not know. - **API reference** — Every endpoint, generated from the spec our own dashboard is built on. - **Help and support, included** — Free on every plan, open 24 hours a day, and you can write to us in your own language. Nothing here is behind a login. - **Why trust us** — A registered UK company with an owned fleet — who you are buying from, set out in full. ## Latest from the blog ## New in the knowledge base ## From signup to live sites No sales call, no onboarding queue, no card to start. 1. **Start your trial** — Create an account and get 14 days free with up to 5 sites — no card, no commitment. Pick your language and currency in the header; every price and receipt follows. 2. **Add domains and deploy** — Point a domain in, pick a stack and deploy — or let us migrate your existing sites for free, with the cache plugins already installed. 3. **Scale when you need to** — Move up or down a plan whenever you like. Upgrades apply instantly and downgrades credit back to your wallet, because billing and provisioning share one brain. ## Every price published — start free Every product on this page has a published price list, shown in your currency. Footprint-Free hosting has 42 tiers from 5 sites to 2,000 and you only choose how many sites; managed WordPress, cloud servers and the add-ons each have their own. Every Footprint-Free tier includes the whole stack: 106 managed SEO footprints, the CDN and DNS pools, free SSL and daily backups with 30-day retention. - 14-day free trial: no card, up to 5 sites - 30-day no-quibble money-back guarantee - Free migration of your existing sites ## How we compare The short version, across every line. See the full provider-by-provider tables on the hosting pages. | | Zinn Digital® | Typical PBN host | Typical mainstream host | | --- | --- | --- | --- | | Genuine Footprint-Free architecture | Yes | Partial support | No | | Footprint-Free AND mainstream lines | Yes | No | No | | Deploy to Netlify, Cloudflare Pages and GitHub Pages | Yes | No | No | | AI / MCP control of your hosting | Yes | No | No | | Rank tracker and SEO tools built in | Yes | Partial support | Partial support | | A marketplace with escrow on every order | Yes | No | No | | Same price on renewal (no hike) | Yes | Partial support | No | | 14-day free trial, no card | Yes | Partial support | No | | Free migrations | Yes | Partial support | Partial support | A high-level summary: the two “typical” columns generalise across the market and name no single provider, so there is nothing here to cite. The evidence behind them is the named, provider-by-provider tables on the Footprint-Free and WordPress hosting pages — every competitor figure there carries the provider’s own page it was read from and the day we read it (last verified 12 September 2026). ## Frequently asked questions **What can I host on Zinn Digital®?** WordPress, WooCommerce, PHP, Node.js, Laravel, Joomla, Magento, .NET, online-course platforms and static sites, plus managed cloud servers, VPS, standalone databases, object storage and AI inference — and Footprint-Free hosting for PBNs and SEO networks. Each has its own page and plans, and all of them run from one dashboard. **Can I deploy to Netlify, Cloudflare Pages or GitHub Pages?** Yes. Where a site is published from is a per-site choice: our own fleet, Cloudflare Pages, Netlify, GitHub Pages or GitLab Pages, from our pooled accounts or your own connected ones, or a server you already run. You manage all of them from the same dashboard, API and MCP server. **Is rank tracking included?** Yes. A daily rank-tracking allowance comes with your hosting, you can add paid keyword packs on top, and you can use the rank tracker on its own for any domain, hosted with us or not. SEO Basics — indexed status, Trust Flow and Core Web Vitals — is free on every site. **What is the Zinn® marketplace?** A marketplace for guest posts, link building, SEO and AI services, web development, websites, domains and Shopify stores. Every order is held in escrow and fulfilment is verified before the seller is paid, and you can sell from the same account you host with. **Can AI tools manage my hosting?** Yes. Our MCP server lets Claude, Cursor, ChatGPT and other MCP clients manage, build and deploy sites through one connection you authorise, scoped to what you grant and audit-logged. Our own AI also builds sites, writes content, reviews updates and answers your visitors — on our credits or your own provider key. **Do you build websites and plugins?** Yes. Our developers build WordPress sites, custom plugins and themes, fix bugs and errors on any site, and build custom applications. Every project is quoted for free: tell us what you need and we will price it. **Is there a free trial?** Yes. Footprint-Free hosting starts with a 14-day free trial for up to five sites, with no card. Every plan is also backed by a 30-day money-back guarantee. --- # About Zinn Digital® URL: https://zinndigital.com/about Zinn Digital® is an operator-run hosting company, not a reseller. We host more than 600,000 PBN sites worldwide, plus more than 100,000 money sites, and we build the AI-first platform that runs them — footprint-free hosting for bulk and SEO networks, and mainstream managed hosting for everything else. ## Who we are Zinn Digital® runs its own fleet. We are the operator, not a middleman reselling someone else's servers — the sites we host live on infrastructure we build, tune and own end to end. That is why more than 600,000 PBN sites worldwide — alongside more than 100,000 money sites — already run with us, and why the platform is engineered to scale far beyond that. The company is built on 25+ years of full-stack engineering under founder and CEO Neil Lock. Everything from the control plane to the cache layer to the footprint-aware CDN pools is bespoke and owned in-house, so nothing about your hosting is at the mercy of a third-party panel or a reseller margin. ## Founder: Neil Lock, technology entrepreneur and developer Zinn Digital® was founded, and is led, by Neil Lock: an English technology entrepreneur, developer and SEO scientist with more than 25 years in technology. A farmer's son who began by making games on the Commodore 64 and the ZX Spectrum, he turned that childhood passion into his profession at about twenty, and moved into SEO as Google arrived, coming through the Panda and Penguin updates that ended most SEOs' careers. He is an AI engineer who builds his own LLMs and the 24/7 AI support agent our customers use, and the founder behind pbn.ltd, the world's first AI hosting platform for SEOs, and the Zinn Hub® freelance marketplace. He leads from the front: the hosting depth, SEO science and applied AI in this platform are one person's discipline, engineered into the product you use. His own site, neillock.dev, tells the whole story, from the farm to the platform. - Technology entrepreneur and developer, with 25+ years in technology - Around 25 years of full-stack engineering — Laravel, Python, Django, WordPress and more - SEO scientist since the early days of Google - AI engineer — his own LLMs, automation and our 24/7 AI support agent - Founder of pbn.ltd and co-founder of Zinn Hub® ## How we're different Everything we ship is designed for scale, security and SEO from day one. - **Operator, not a reseller** — We own and run the fleet the 600,000+ PBN sites we host worldwide sit on. No white-labelled upstream, no shared-fate reseller account between you and your servers. - **AI-first by design** — The platform is built around an AI control plane and an MCP server, so you can manage sites, deploys and support from the tools you already use. - **Two product lines, one engine** — Footprint-free hosting for bulk and PBN networks — CDN account pools with footprint-aware rotation — plus mainstream managed WordPress, WooCommerce and PHP hosting. - **No vendor lock-in** — Free migrations in, and no contracts trapping you. Every part of the stack is built to swap, so you are never held hostage by a proprietary panel. ## What you get with us - Card-free 14-day trial — try the platform before you pay anything - 30-day money-back guarantee on paid plans - 99.99% uptime assurance, backed by an owned and monitored fleet - Free migrations — we move your sites in for you - Footprint-free hosting with footprint-aware CDN rotation for PBN and SEO networks - Mainstream managed WordPress, WooCommerce, PHP, static and Node hosting - No vendor lock-in — swap or leave whenever you choose ## The company Zinn Digital® LTD is registered in the United Kingdom, company number 16385785, at 71-75 Shelton Street, Covent Garden, London WC2H 9JQ. We build to enterprise standards — auditable, secure and SLA-ready — because we run a live, revenue-generating platform on the same infrastructure we sell. If you want to see how it is built, or talk to the team behind it, our development and contact pages are the next step. ## Frequently asked questions **Is Zinn Digital® a reseller?** No. Zinn Digital® is the operator. We build and run our own fleet in-house, and we already host more than 600,000 PBN sites worldwide on it — there is no reseller or white-labelled upstream between you and your servers. **What kinds of hosting do you offer?** Two product lines on one engine: footprint-free hosting for bulk and PBN networks, with CDN account pools and footprint-aware rotation, and mainstream managed hosting for WordPress, WooCommerce, PHP, static and Node sites. **Can I try it before paying?** Yes. We offer a card-free 14-day trial, so you can use the platform before committing. Paid plans are also covered by a 30-day money-back guarantee. **Will you migrate my existing sites?** Yes. Migrations are free — we move your sites in for you. There is no vendor lock-in, so you can leave just as freely as you arrive. **Who is behind Zinn Digital®?** Zinn Digital® is led by founder and CEO Neil Lock, with 25+ years of full-stack engineering behind the platform. The company is registered in the UK as Zinn Digital® LTD, company number 16385785. --- # Everything you can add to a site, and what each one actually does URL: https://zinndigital.com/add-ons Monitoring, SEO data, expert services and infrastructure — bought per site from your dashboard, on the invoice you already get. Every one has a page explaining it properly. ## How add-ons work here An add-on is something you switch on for one site rather than for your whole account, so you are never paying for rank tracking on the brochure site because you wanted it on the shop. They appear in your dashboard beside the site they belong to, and on the invoice you already receive. Everything here is monthly or one-off with no minimum term. Monthly add-ons stop at the end of the period you have paid for; one-off services are a single job with nothing recurring behind them. Where an add-on has a free tier or a plan-included allowance, its own page says so rather than leaving you to find out at checkout. ## How they are priced There is no add-on bundle and no tier you have to reach. Each one is priced on its own page, from the live catalogue rather than from copy somebody typed, so what you read is what you are charged. Monthly add-ons are a few pounds to a few tens of pounds a month; one-off expert services are priced per job by how much work they are. Several have a free tier or an allowance your plan already includes — three uptime monitors on any account, weekly index checks on every Footprint-Free plan, staging on every site. Where that is true the add-on's own page says so before it asks you for anything. ## Watch what happens to your site Things that take a reading on a schedule and tell you when it changes. All monthly, all cancellable, all work on a site hosted anywhere. - **Uptime and performance monitoring** — Checks from outside your hosting around the clock, with Core Web Vitals. Three monitors free on any account. - **Index monitoring** — Daily checks that your pages are still in Google, and named page targets for the ones that earn. - **Rank tracking** — Daily positions for twenty-five phrases, with history, and stackable packs for more. - **Domain monitoring** — Expiry, nameserver changes and WHOIS movement on the domains you care about. - **Reputation monitoring** — What the first page of search says about your brand, checked weekly and diffed. - **Local rankings** — Where your business sits on Google Maps, in the local 3-pack and in the ordinary results, town by town. - **Client reports** — Branded SEO reports for your clients, in their language, e-mailed on a schedule. - **Brand mentions** — Who on the web mentions your brand, in what tone, with an e-mail when new pages appear. - **AI visibility** — Whether ChatGPT, Claude, Gemini and Perplexity name you, who they name instead, and why. ## Understand where you stand Search and market data, collected for you on a schedule and kept as history so a change means something. - **Backlink monitoring** — New and lost links every week, with the authority behind each one and the date it went. - **Domain authority** — Trust and citation scores for any domain, weekly, as a trend rather than a single reading. - **Domain vetting** — Check a domain's links, spam signals, traffic and archived past before you buy it. - **Domain alerts** — Get one e-mail a day when a new aged domain matches your saved search. - **Competitor intelligence** — Other people's domains on the same screens as yours, in packs of five and twenty-five. - **Keyword research** — Search volumes, related phrases and difficulty in any market and language, with no per-query charge. - **Product price tracking** — Your products and your competitors' on Google Shopping and Amazon, weekly. - **Whole-site technical audit** — Every page crawled monthly for broken links, metadata, orphans and redirect chains, with a month-on-month diff. - **PBN footprint checker** — What publicly ties your sites together, scored, with the closest pairs and a plain fix for each link. ## Let the platform do the work Things that act on what they find, with you approving anything that changes your site. - **AI webmaster** — A review of your site built on facts only your host can see, with one-click fixes you approve. - **AI update guard** — Every plugin and theme checked against your actual PHP and WordPress versions before an update runs. - **AccelerateWP** — Object and page caching on every plan, with a setting-up service if you want it done for you. - **Database maintenance** — Revisions, transients and orphaned metadata cleared out as an automated job, with a backup taken first. - **Site translation** — Your site in more languages, translated and kept in step when the source changes. - **AI image generation** — Images generated in the dashboard from three providers, billed against your credit meter. ## Have somebody do it for you One-off jobs where an engineer does the work. Each has a response promise attached to the purchase rather than a target we aim at. - **Managed migration** — We move your site here — files, database, mail and DNS — and you decide when it goes live. - **Site speed optimisation** — A tuning pass on the site you already have, with measured before-and-after numbers. - **Performance Boost** — More CPU, memory and processes for one busy site, one to three tiers above its plan. - **Expert site speed-up** — The deeper engagement, priced by site size, for when tuning is not the answer. - **SEO and performance audit** — An engineer reads your site and writes you a prioritised plan, using server-level facts. - **Malware cleanup** — A hacked site cleaned, hardened and checked, by somebody who does it every week. - **Emergency support** — An engineer on your problem within four hours, worked to resolution, with a root-cause write-up. ## Infrastructure and capacity Things you add to an account rather than to a page — storage, networking, backups and destinations. - **Backups for sites hosted elsewhere** — Back up a site we do not host, on our storage, restorable without moving it here first. - **Offsite backups to your own storage** — An encrypted copy of every backup in your own S3 bucket or SFTP server, restorable in one click. - **Hourly backups** — A backup of a website every hour, the last 48 hours kept, on top of the nightly. - **Private network** — A private link between your sites and services, so internal traffic never crosses the public internet. - **Object storage** — S3-compatible storage on our own infrastructure, for media, backups and anything else. - **Managed databases** — A database as its own product, sized and looked after separately from any one site. - **Extra database for a website** — One more MySQL database for a website on a plan with a fixed number of databases. - **LiteSpeed Enterprise, managed** — The commercial web server our own hosting runs on, put on a server of yours — ordered, licensed, installed and handed back when you stop. - **External deploy targets** — Deploy from here to hosting you own elsewhere, in packs on top of what your plan includes. - **SSL setup** — A certificate installed and verified for you, including the awkward cases a one-click button cannot handle. ## For resellers and agencies Bought once for your account and applied across every client site, rather than per site. - **Reseller SEO data** — Authority, links and search data across up to two hundred client sites for one flat price, resold at your rate. - **Billing-panel modules** — Free WHMCS, HostBill and PHP modules so your own panel provisions real hosting accounts. - **Priority support** — Standing front-of-queue support, much cheaper per incident than buying an emergency callout each time. ## Frequently asked questions **Do I have to host with you to buy an add-on?** For most of them, no. Monitoring, SEO data and external backups all work on a site hosted anywhere — you need a free account and the domain added. The expert services and the infrastructure add-ons need the site to be here, because they act on the server. **Are add-ons per site or per account?** Most are per site, so you pay only where you need them. The reseller add-ons and a few account-wide ones are bought once and cover everything — each page says which it is. **Is there a minimum term?** No. Monthly add-ons run to the end of the period you have paid for and then stop if you cancel. One-off services are a single job. **Where do I actually buy one?** From your dashboard, on the add-ons tab, against the site you want it for. Every add-on there links back to the page explaining it, so you can read before you buy. **What happens if my account falls behind on payment?** Anything that costs money to run is paused while the account is not in good standing, and resumes on its own when it is — you do not have to ask. Nothing already collected is deleted, and you can still read it. **Do prices include tax?** No. Tax is worked out from your billing country and shown at checkout, so what you see there is what you pay. --- # Know when a link you paid for disappears URL: https://zinndigital.com/add-ons/backlink-monitoring Links are bought, earned and then quietly removed. We watch your profile every week and tell you what appeared, what vanished and what it was worth. ## What it is A backlink is the one part of your SEO that somebody else controls. It can be removed when a site is redesigned, when an editor changes, when a page is pruned, or when whoever placed it stops being paid — and nothing tells you. This add-on takes a reading of your link profile every week and keeps the difference. New links are recorded with where they came from; lost links are recorded with the date they went. That difference is the product. ## What you get The profile itself is easy to buy anywhere. The history of how it changed is what is worth having. - **New and lost, dated** — Every weekly reading is compared with the last one, so a link that disappeared has a date against it rather than being simply absent. - **Authority behind each link** — Not just how many, but from where — so one good link is not buried under fifty worthless ones in a count. - **Referring domains, not just URLs** — Fifty links from one site are one relationship. The reading counts both, because they mean different things. - **Anchor text** — What the link actually says, which is what determines much of what it does for you. - **Any domain** — Your site, a client's site, or — with competitor intelligence — somebody else's. - **Beside your rankings** — Link changes and ranking changes on the same screen, because one usually explains the other. ## How it works 1. **Add the domain** — Any domain you have added to your account, hosted with us or not. 2. **We read it weekly** — A full profile reading once a week, batched with everyone else's, which is what makes this affordable at this price. 3. **You see the difference** — Appeared, disappeared and changed — with dates, so you can connect a loss to a ranking drop. ## Why weekly is the right cadence A link profile does not change hourly, and pretending otherwise sells noise. A weekly reading is frequent enough that a removed link is noticed within days, and infrequent enough that what you see is signal. It is also what lets us price it the way we do. Readings are taken in bulk rather than one domain at a time, so adding a domain costs us almost nothing and we do not have to charge you as though it did. ## Frequently asked questions **How far back does the history go?** From the day you start monitoring. We cannot tell you when a link disappeared before we were watching — no one honestly can. **Will you tell me if a link is harmful?** We show you the authority and the source so you can judge. We do not publish a 'toxic' score, because those are opinions dressed as measurements. **Does this include disavow files?** No. This add-on measures; it does not act on your Search Console account. **Do I have to host with you to buy this?** No. Backlink monitoring works on any domain, wherever it is hosted. You need a Zinn Digital® account, which is free to create, and you add the domain you want watched. **Can I cancel whenever I want?** Yes. It is billed monthly with no minimum term, and cancelling stops the next charge. The history we have already collected for you stays readable for as long as your account is open. **What happens if my account is suspended or unpaid?** Checks stop while the account is not in good standing, and start again by themselves once it is — you do not have to ask. Everything already collected stays visible in the meantime, with its real age shown, so you are never looking at stale data that is pretending to be current. --- # Hear when the web talks about you URL: https://zinndigital.com/add-ons/brand-mentions Tell us the phrases that matter — your brand, a product, a person — and we find the news stories, blog posts and shop pages that mention them, show you whether each one reads positive or negative, and tell you when new ones appear. ## What it is People write about businesses in places the business never sees: a local news story, a comparison post, a forum-style review on somebody's blog, a reseller's product page. By the time a customer quotes one back to you it has been working on your reputation for weeks. Brand mentions listens for the phrases you choose across news, blogs, organisations' sites and online shops. Each check finds the newest pages that use the exact phrase, counts every page that does, and sorts them into positive, neutral and negative so the ones worth an answer are easy to find. ## What you get Built to find the pages that matter, not a pile of loose keyword matches. - **The exact phrase** — We search for your phrase as a phrase. A two-word brand is not matched on pages that merely contain both words somewhere. - **Every page, linked** — Each mention comes with its page, the site it is on, its headline, a short excerpt and the date it was published when the page gives one. - **Positive, neutral or negative** — Every page is read for tone, and the totals show how the whole conversation leans — so a negative story stands out the day it appears. - **The trend over time** — Every check adds a point, so you can see whether you are being talked about more or less than last month. - **Told when it is new** — When a check finds pages we had not seen before, we e-mail you a summary. A phrase's first check is your starting point and does not flood your inbox. - **Your schedule** — Check each phrase every day, every week or every month. Your plan includes a number of checks a month, and the screen shows exactly how many a schedule uses before you save it. ## How it works 1. **Add your phrases** — Your brand, your products, your key people — up to the number your plan includes, on any domain you watch with us. 2. **Choose how often** — Daily for the ones that matter most, weekly or monthly for the rest. 3. **Read and reply** — Open the list, filter it by tone, and go straight to the pages that need an answer. ## Frequently asked questions **Where do you look?** News sites, blogs, organisations' websites and online shops. We do not read private social-media accounts or anything behind a login. **How many pages do I see?** Each check shows the newest pages that mention a phrase — up to a hundred — beside the total number of pages that do. Pages we have found stay on your list after later checks. **What counts as one check?** One phrase, checked once. A phrase checked every week uses about four or five checks a month; checked every day it uses thirty. **Can I check now instead of waiting?** Yes. Check now re-reads every phrase that has not been checked in the last twenty hours, using your month's checks. There is no extra charge. **Will you remove a negative page?** No, and be wary of anyone who says they will. We tell you it is there, and how the conversation moves, so you can reply where it matters. --- # Branded SEO reports your clients can read URL: https://zinndigital.com/add-ons/client-reports Put the rankings, AI visibility, Google index status, site health and backlinks you already track for a client into one PDF under your own logo — written in their language, e-mailed weekly, monthly or quarterly, with a link they can open online. ## What it is Your clients pay you for results, and most of them will never open an SEO tool to see them. A report is how they see the work: where they rank, whether AI assistants mention them, whether Google has their pages, how healthy the site is and who links to it. Client reports gathers those figures from the tools you already use with us, for the domains you choose, puts them under your name and colours, and adds a plain summary of what changed since the last report. It is written in your client's language, sent as a PDF on the schedule you pick, and can also be read online through a link that expires. ## What you get A report your client understands, that never mentions us. - **Your brand, not ours** — Your logo, your colours, your agency name, your intro and your footer. Pro and Agency add more looks for more brands. - **In your client's language** — Choose the language per client and the whole report — headings, figures, dates and the covering e-mail — is written in it, right to left where the language needs it. - **What changed, in plain words** — Every figure is compared with the previous report, and the summary says what went up or down and whether that is good news. - **On a schedule, or now** — Weekly, monthly or quarterly reports are made and e-mailed on their own. You can also make one at any time. - **PDF and online** — The PDF is attached to the e-mail and ready to download. Each report also has a private link your client can open, which you can withdraw. - **Only what was measured** — A report reads the checks your tools already ran. A tool with no reading yet is left out rather than shown as zero. ## How it works 1. **Set up your look** — Upload your logo and choose your colours, an intro and a footer. 2. **Add a client** — Their domains, who receives the report, their language and how often. 3. **Send** — Reports go out on schedule, or make one now and preview it before it is sent. ## Frequently asked questions **Where do the figures come from?** From the SEO tools you already use with us — rankings, AI visibility, the index checker, site audits and backlinks. A report reads what those tools have measured, so making one costs nothing extra, and it shows only what was really checked: a tool with no reading yet is left out rather than shown as zero. **Does my client see your name?** Not in the report. It carries your logo, your colours and your name. With your own mail domain connected, the e-mail is sent from your domain too; without one it comes from our sending address on your behalf, and on Pro and Agency replies go to an address you have confirmed. **What does the 'what changed' section show?** Each report compares every figure with the client's previous report and says in plain words what went up or down and whether that is good news — for example, that phrases on page one went up from 5 to 7. **What counts as one report?** One report for one client, whether the schedule made it or you did. A report that fails on our side is not counted. Your monthly count resets on the 1st. **How long does a share link work?** 30 days on Client Reports, 60 on Pro and 90 on Agency. You can withdraw a link at any time, and it stops working at once. --- # Watch the sites you are actually competing with URL: https://zinndigital.com/add-ons/competitor-intelligence Track a competitor the way you track yourself: what they rank for, what is being linked to, and what changed this month. Five domains in a pack, stackable to as many as you need. ## What it is Your own numbers only tell you half the story. A ranking that has not moved in six months might mean your work is not landing, or it might mean three competitors are pushing hard and standing still is an achievement. You cannot tell the difference without watching them too. Competitor intelligence puts other people's domains on the same screens as your own — rankings, link profile, authority, and how each has moved — so a comparison takes a glance rather than an afternoon with three tabs and a spreadsheet. ## What you get The same readings we take for your sites, taken for theirs, and lined up beside each other. - **Domains in packs** — Add competitors in packs of five or twenty-five. The packs stack, so a big agency and a one-site business both pay for what they watch. - **Rankings side by side** — See where a competitor sits for the phrases you care about, not just where you sit. - **Link movement** — Who is linking to them that is not linking to you, and what has appeared or disappeared since last month. - **Authority over time** — A trend line rather than a single score, so you can see whether the gap is opening or closing. - **They do not need to be customers** — It is public search data. You can watch any domain — a competitor, a prospect, an acquisition target. - **Your own domains never count** — Sites in your account are watched anyway. The allowance is for external domains only. ## How it works 1. **Name the domains** — Type the competitors you want watched. The counter shows your allowance and what you have used. 2. **We collect weekly** — Readings are taken on a weekly cadence, which is the honest one for this data: link profiles and authority move on the timescale of link acquisition, so a daily figure would be noise sold as a feature. 3. **Compare on one screen** — Their numbers appear beside yours, with history, so you are comparing trends rather than snapshots. ## Why weekly and not daily We could check these every day and charge more for it, and it would tell you nothing extra. Backlink profiles and authority scores move on the timescale at which links are actually acquired — weeks, not hours — so a daily reading is mostly measurement noise presented as a trend. Weekly is the cadence at which a change in this data means something happened. Where a faster reading genuinely helps — your own rankings — we check daily, and that is a different add-on for that reason. ## Frequently asked questions **How many competitors can I track?** As many as you buy packs for. Five and twenty-five come as packs and they add together. **Do my own sites use up the allowance?** No. Sites in your account are watched as part of your own SEO data; the allowance is only for external domains. **What if I go over my allowance?** Nothing is deleted. We stop collecting for the domains past your allowance, oldest first, and pick them up again the moment there is room. **Can I watch a domain that is not a competitor?** Yes — a prospect, a client you are pitching, a site you are thinking of buying. It is public data about a domain, not a relationship. **Do I have to host with you to buy this?** No. Competitor tracking works on any domain, wherever it is hosted. You need a Zinn Digital® account, which is free to create, and you add the domain you want watched. **Can I cancel whenever I want?** Yes. It is billed monthly with no minimum term, and cancelling stops the next charge. The history we have already collected for you stays readable for as long as your account is open. **What happens if my account is suspended or unpaid?** Checks stop while the account is not in good standing, and start again by themselves once it is — you do not have to ask. Everything already collected stays visible in the meantime, with its real age shown, so you are never looking at stale data that is pretending to be current. --- # Hear about the right aged domain first URL: https://zinndigital.com/add-ons/domain-alerts Save a search of our aged-domain list — by rating, trust flow, referring domains, price, extension, language or topic — and we e-mail you once a day when a new domain matches it, or one you were told about gets at least 10% cheaper. ## What it is Good aged domains sell quickly. New stock is added to our aged-domain list every day, and the one that fits your project can be gone before you look again. Domain alerts watch the list for you. Set the filters you care about, save them, and each morning we check every new domain against your searches and send you one e-mail with the ones that match. ## What an alert does Your filters, checked against new stock every day. - **Every filter the list has** — Domain Rating, Domain Authority, Trust Flow, Citation Flow, referring domains, price, extension, language, topic, Google index status, Wikipedia and Google News — exactly the filters you saved. - **Only what is new** — Domains already on the list when you save a search are not e-mailed. You hear about each new match once. - **Price drops** — If a domain you were told about drops by 10% or more, it is flagged once at its new price. - **One e-mail a day** — All your searches in one message, each domain with its rating, trust flow, referring domains and price. - **Pause any time** — Pause a search and resume it later. A paused search keeps its history and does not count toward your allowance. - **Vet before you buy** — From each match, run a domain vetting report or order the domain in one step. ## How it works 1. **Filter the list** — Open Aged domains in your account and set the filters you want. 2. **Save it as an alert** — Press Save as alert and give it a name you will recognise in the e-mail. 3. **Get the matches** — Each day, new domains that match arrive in one e-mail, with links to vet or order them. ## Frequently asked questions **How often are searches checked?** Once a day, after the day's new domains are added to the list. **Will I be told about domains that were already listed?** No. When you save a search, everything already matching it is noted and not e-mailed. Only domains added afterwards, or that drop in price by 10% or more, are announced. **What happens if my plan ends?** Your oldest searches keep running up to your allowance and the newest are paused. Nothing is deleted — resume them when you have room again. **Do I need hosting with you?** No. Domain alerts work on any account. --- # One honest number for how much weight a domain carries URL: https://zinndigital.com/add-ons/domain-authority Trust and citation scores for any domain, refreshed weekly and kept as a trend. It is part of Domain Overview, which also reads your competitors — every reading of either uses one report from your month's allowance. ## What it is Authority scores are how the industry compares domains quickly. They are not a Google metric and nobody should pretend otherwise, but they are the best available shorthand for whether a domain has earned genuine links from places that themselves earned links. What makes a score useful is history. A domain sitting at the same score for two years and a domain that has climbed to it in six months look identical in a single reading and are completely different propositions. We keep the readings so you can see which one you are looking at. ## What you get The scores, the trend, and enough context that the number means something. - **Trust and citation, separately** — Two numbers rather than one blended score, because a domain with many links from poor sources and one with fewer from good ones are different, and one number hides that. - **A weekly trend line** — Every reading kept, so you see direction and not just position. - **Any domain you name** — A site you are buying, a site offering you a link, a competitor, or your own. - **Beside your link profile** — Authority and backlinks on the same screen, because the first is a summary of the second. - **Reports, not lookups** — Each reading uses one report. Starter includes 30 a month, Pro 100 and Agency 350, and packs of 30 add more. A domain read every week uses four or five a month. - **For resellers, across a whole book** — If you manage client sites, the reseller SEO-data add-on gives you this across all of them for one flat price. ## How it works 1. **Name a domain** — Yours, a client's, or one you are considering. 2. **Weekly readings** — Trust and citation are refreshed once a week and each reading is kept. Each reading uses one report from your month's allowance, which resets on the 1st. 3. **Read the direction** — The trend is the product. A rising score and a falling one tell you opposite things about the same number. ## What this is not It is not a Google ranking factor and we will not sell it as one. No third-party authority score is used by any search engine; they are estimates built from crawls of the public web. What they are good for is comparison and triage — deciding which of twenty link offers is worth answering, or whether a domain somebody wants to sell you has anything behind it. Used for that, they are one of the most useful cheap numbers in SEO. ## Frequently asked questions **Is this Google's PageRank?** No. Google has not published PageRank for domains since 2016. This is a third-party estimate built from a web-wide link crawl, and it is useful for comparison rather than as a prediction of ranking. **Can I check a domain before I buy it?** Yes, and it is one of the best uses of this. Add the domain, take a reading, and look at what the link profile behind the score actually is. **Why two scores instead of one?** Because volume and quality are different questions. A domain can have enormous citation and poor trust, which usually means a lot of links from places that do not matter. **Do I have to host with you to buy this?** No. Domain scoring works on any domain, wherever it is hosted. You need a Zinn Digital® account, which is free to create, and you add the domain you want watched. **Can I cancel whenever I want?** Yes. It is billed monthly, or yearly at a saving, with no minimum term, and cancelling stops the next charge. The history we have already collected for you stays readable for as long as your account is open. **What happens if my account is suspended or unpaid?** Checks stop while the account is not in good standing, and start again by themselves once it is — you do not have to ask. Everything already collected stays visible in the meantime, with its real age shown, so you are never looking at stale data that is pretending to be current. --- # Check a domain before you buy it URL: https://zinndigital.com/add-ons/domain-vetting One report reads a domain's backlinks, anchor texts, link history, spam signals, search traffic, Google index status and archived past — then tells you whether it looks clean, needs care or is high risk, with every reason shown. ## What it is An aged domain is bought for its past: the sites that link to it and the trust search engines have in it. That past can also be a liability — links bought from spam networks, years as a casino or pharmacy site, a penalty that took it out of Google. None of it shows on the domain's current home page. Domain vetting reads that history for you before you spend money on a domain or build a site on it. It scores what it finds out of 100, gives a verdict, and shows the evidence behind every point it took off. ## What a report reads Ten checks, each one shown to you, none of them a black box. - **Its link profile** — Referring domains, backlinks, how many networks they sit on and the spam score of the links pointing at it. - **Its anchor texts** — Whether the words other sites link with look natural, or like casino, pharmacy and loan spam — or a script it never used before. - **Its link history** — Referring domains month by month since 2019, so a collapse or a sudden burst of bought links stands out. - **Its rankings and traffic** — What it still ranks for, what it has lost, and its estimated search traffic over the last two years, in the market you choose. - **Its Google index status** — Whether Google lists it at all. Many links and no index is the classic sign of a penalised domain. - **Its archived past** — What its home page was over the years, read from the public web archive — and whether it was parked, redirected or changed language. ## How it works 1. **Enter a domain** — Paste a domain or a web address and choose the market its rankings are read for. 2. **We read its history** — The ten checks run together. Most reports are ready in under a minute. 3. **Read the verdict** — A score out of 100, a verdict and the reasons behind it, worst first, with the evidence underneath. ## Frequently asked questions **What happens if part of a report cannot be read?** The report says which part is missing and leaves it out of the score — it is never counted as clean. If nothing at all can be read, your credit is returned. **Is the score a guarantee?** No. It is a reading of the domain's public history, with every reason shown, so you can judge it for what you want to build. **Do I have to own the domain?** No. Vetting is for domains you are thinking of buying — at auction, from a marketplace or from a seller. **Do credits expire?** No. A credit stays on your account until you use it. **Which markets can I choose?** Twenty, including the United States, the United Kingdom, Canada, Australia, Germany, France, Spain, Italy, the Netherlands and Brazil. --- # Something is badly wrong and you need an engineer now URL: https://zinndigital.com/add-ons/emergency-support A one-off callout for a site that is down, hacked, or broken in a way nobody in your team can fix. An engineer picks it up and works it until it is resolved. ## What it is Most support requests are questions. This is for the other kind: the site is down in the middle of a campaign, a database is corrupt, a deployment went wrong at the worst moment, or something has clearly got in and you do not know how far it went. Buying it puts an engineer on your problem now rather than in the normal order of arrival, and keeps them on it until it is resolved. It is a one-off — there is no retainer to sign and nothing to cancel afterwards. ## What you get Somebody's undivided attention, and a written account of what happened. - **Straight to an engineer** — Not a first-line queue that escalates. The person who picks it up is the person who can fix it. - **Worked to resolution** — It is not a time box. The engineer stays with the problem until it is resolved or until we have told you honestly that it cannot be. - **Server-level access** — We host it, so there is no waiting for logs from a third party or guessing at what the server did. - **Recovery included** — If the answer is a restore, we do the restore. Getting you back is part of the job, not a second purchase. - **A root-cause write-up** — Afterwards you get what happened, why, and what would stop it recurring — so the money buys more than one fix. - **No retainer** — Buy it the day you need it. If you would rather have it standing, priority support is the ongoing version. ## How it works 1. **Buy it and describe the problem** — From your dashboard, against the affected site, with whatever you know so far. 2. **An engineer takes it** — It goes to somebody who can act, not into a general queue, and you are told who has it — within 4 hours of buying it. 3. **You get the write-up** — What was wrong, what was done, and what would prevent a repeat. ## When NOT to buy this If your site is down and you host with us, do not buy anything — tell us. An outage caused by our infrastructure is our problem and our cost, and we would rather you shouted at us than paid us. This is for the situations where the fault is in your site rather than in our platform: a bad plugin update, a compromised install, a deployment that went wrong, a database somebody dropped. Those are not covered by hosting and would normally wait their turn. ## Frequently asked questions **My site is down — should I buy this?** If you host with us and the outage is ours, no. Contact support and it costs you nothing. Buy this when the fault is inside your own site and you need it fixed now rather than in turn. **Is my site hacked, and will you clean it?** Malware cleanup is a separate, cheaper service built specifically for that. Buy this one if the compromise has gone further than the site files — into the database, into mail, or into other accounts. **What if you cannot fix it?** We tell you that plainly and quickly rather than billing you for a week of trying. Where the honest answer is a restore, we do the restore. **Do you offer this as a standing arrangement?** Yes — priority support is the ongoing version and is much cheaper per incident if you expect to need it more than occasionally. --- # Deploy to hosting that is not ours URL: https://zinndigital.com/add-ons/external-sites Push a site from here to a server, a static host or a platform you already pay for — and manage it from the same dashboard as everything else. Your plan includes some; these add more. ## What it is Not everything you look after is hosted with us, and pretending otherwise would make our dashboard useless to most agencies. An external deploy target is a destination you own somewhere else that we can build to and push to. Every plan includes a number of them. These packs add more when you have outgrown what your plan carries — one at a time, or five, and they stack so you never have to jump a whole plan tier to add a single site. ## What you get The same build, deploy and management flow, pointed somewhere else. - **One dashboard for everything** — Sites here and sites elsewhere in one list, rather than a spreadsheet and four control panels. - **Build here, deploy there** — The build runs on our infrastructure; the output goes to your destination. - **Static hosts and servers** — A platform like a static host, or a plain server you have SSH access to — you own the destination and its bill. - **Stackable one at a time** — A pack of one exists deliberately, so adding a single client site never costs a whole plan upgrade. - **On top of what your plan includes** — These add to your plan's allowance rather than replacing it. - **Nothing hidden about the limits** — Your allowance and what you have used are on the screen, so you find out before a deploy fails, not during one. ## How it works 1. **Check what your plan includes** — Every plan carries a number of external targets. The dashboard shows your allowance and your usage. 2. **Add packs if you need more** — One or five at a time, stacking on top of the plan allowance. 3. **Point a site at it and deploy** — The build happens here; the result is pushed to your destination on every deploy. ## Why we sell this at all It would be commercially tidier to make our dashboard work only for sites hosted with us. It would also make it useless to the agencies who are our best customers, because no agency has all its clients on one host and none ever will. So the dashboard manages sites wherever they are. If that eventually persuades somebody to move a site here because it is simpler, good — but the tool works either way, and that is the point. ## Frequently asked questions **How many targets does my plan include?** It varies by plan and the number is shown in your dashboard next to what you have used, so you never have to work it out from a table. **Why are these priced in pounds?** Because that is the price they were set at. Converting it into your currency and charging something slightly different would be a made-up number, so we show the real one. **What kinds of destination are supported?** Static hosting platforms and servers you have access to. You own the destination and its bill; we own the build and the push. **Do the packs stack?** Yes. Buy the pack of one five times, or the pack of five once — whichever matches how you grow. --- # One more database for a website URL: https://zinndigital.com/add-ons/extra-database Every website on our servers has its own MySQL database. On plans with a fixed number of databases, add another one to a website when it needs it, ready as soon as you pay. ## What it is Some plans include a fixed number of databases per website, for example PBN hosting and the plans that list 2 or 4 databases. When a website needs one more, for a second application, a separate shop or a copy of its data to test with, this add-on gives that website another MySQL database for a monthly charge. Plans that say “Unlimited databases”, such as WordPress hosting, never need it: create as many databases as you like there. This add-on is not offered on those plans. ## What you get A real database beside the website’s own, managed from the same card. - **Ready straight away** — Pay in the same window, type a short name and press Create database. The database exists as soon as the page answers. - **In your phpMyAdmin** — The website’s own database user can use the new database too, so the site’s one-click phpMyAdmin shows it beside the site’s database. - **Its own login** — Each extra database also has its own username and a password we show you once and do not store. - **Backed up before it is deleted** — Delete a database and we take a backup first and keep it for 30 days. If the backup cannot be made, nothing is deleted. ## How it works 1. **Open the website** — In your dashboard, choose the website and open its Databases card. 2. **Add a database** — When every included database is in use, buy one more and pay in the same window. 3. **Name it and use it** — Type a short name, copy the password we show once, and connect your application. ## Frequently asked questions **Can I add one on a WordPress plan?** There is no need. WordPress plans include unlimited databases, so you can create as many as you like. **How many extra databases can a website have?** Up to 10 extra databases per website, on top of the databases its plan includes. **Does an extra database count towards my database size?** Yes. The website’s database size limit covers its own database and every extra one together, and the usage meter adds them up. **What happens when I delete one?** We back it up first and keep the backup for 30 days. Ask support within that time if you need it back. **Can I use it for a website hosted somewhere else?** No. Extra databases are for websites on our own servers. For a database that is its own product, see managed databases. --- # A backup every hour for a website URL: https://zinndigital.com/add-ons/hourly-backups Every website we host is backed up every night. For a website that changes during the day, such as a shop taking orders, add hourly backups and go back to any hour of the last two days. ## What it is Your plan already backs up every website we host once a night and keeps those backups for as long as the plan says. If something goes wrong in the afternoon, the newest copy can be many hours old. Hourly backups add a backup of the website’s files and database every hour, for one website at a time. The last 48 hours are kept, so you can go back to any hour of the last two days. Your nightly backups are not changed. ## What you get Hourly restore points beside the nightly ones, in the same backup list. - **A backup every hour** — Files and database together, taken automatically every hour once you turn it on. Each one is labelled Hourly in the website’s backup list. - **The last 48 hours** — Hourly backups are kept for 48 hours and then removed on their own. They never take the place of a nightly backup. - **Restore in one step** — Press Restore beside the hour you want. We back up the website as it is first, so a restore can be undone. - **Stop when you like** — Stop renewing at any time. Hourly backups carry on to the end of the month you paid for, and nothing already backed up is removed early. ## How it works 1. **Open the website** — In your dashboard, choose the website and open its Backups page. 2. **Turn on hourly backups** — Press Turn on hourly backups and pay in the same window. 3. **Let it run** — The first hourly backup runs within the hour, and one more every hour after that. ## Frequently asked questions **Do I still get nightly backups?** Yes. Nightly backups carry on exactly as your plan says. Hourly backups are added on top and never replace a nightly one. **How far back can I go?** To any hourly backup from the last 48 hours, and to any nightly backup your plan keeps. **What happens if a payment is missed?** Hourly backups pause while a payment is overdue and start again on their own once it is paid. Nothing already backed up is deleted early. **Can I use it for a website hosted somewhere else?** No. Hourly backups are for websites we host whose hosting can be backed up. Websites hosted elsewhere have their own external backup plans. **Is it per website?** Yes. You turn it on for each website that needs it, and each one is charged separately. --- # Find out when a page falls out of Google, not months later URL: https://zinndigital.com/add-ons/index-monitoring A page that is not indexed earns nothing, and nothing tells you when one drops out. We check the pages you name every week and tell you when one leaves — 50, 250 or 1,000 pages depending on your plan. ## What it is Being in Google's index is the precondition for everything else in search. A page that has quietly dropped out cannot rank, cannot be found and cannot convert — and the usual way people discover it is by noticing that traffic has fallen, weeks later, and then going looking. This add-on removes the delay. We ask, every week, whether each page you have asked us to watch is still indexed, and we record the answer. When the answer changes, you are told. ## What you get What you buy is how many separate pages we watch. A site hosted somewhere else counts as one page from the same allowance. - **Three plan sizes** — Starter watches 50 pages, Growth 250 and Pro 1,000, each checked every week. The weekly check of the whole site that every Footprint-Free plan includes carries on alongside. - **Named page targets** — Watch specific pages — the ones that earn — rather than only the site as a whole. Packs of 250 extra pages add to any plan. - **A dated history** — Every check is stored, so you can see exactly when a page left and when it came back, and line that up against what you changed. - **It says what it saw** — A check that could not reach an answer says so rather than reporting a reassuring result. A blank is not the same as a pass. - **Works with the rest of your SEO data** — Indexing sits beside ranking and authority on the same screen, because a ranking drop and a de-index look identical from a traffic graph. - **Any site you have added** — Hosted with us or not — this is a question about Google, not about your server. A whole site hosted elsewhere uses one page of your allowance. ## How it works 1. **Pick what to watch** — The site as a whole is watched already. Add the individual pages that matter — a product page, a landing page, a piece of content you paid for. 2. **We check every week** — Each page is checked once a week and the result recorded, whatever it is. Checks pause automatically if your account is not in good standing and resume on their own when it is. 3. **You hear when it changes** — A change of state is what you are told about. A page that has been indexed for a year does not need a weekly email saying so. ## Why it is worth the money The cost of not knowing is asymmetric. Knowing a week late that your best page is out of the index is not a small inconvenience — it is a week of the traffic that page was earning, and the time it then takes to get re-crawled on top of that. We can price this the way we do because the checks are batched rather than made one at a time. Your plan sets how many pages we watch, and packs of 250 raise it whenever you need more. ## Frequently asked questions **Is weekly checking enough?** For most pages, yes: a de-index is something you want to know about within days, not the month later a traffic report would tell you. Weekly across hundreds of pages is what makes watching every page that earns affordable. **What counts as a page?** One URL. The weekly check of your hosted site as a whole is included with your plan and does not use a page. A whole site hosted elsewhere uses one page of your allowance. **Do the packs stack?** Yes. Buy the 250-page pack twice and you have 500 extra pages on top of your plan. **Will you tell me why a page dropped out?** We tell you that it did, and when. Why is a judgement about your content and Google's guidelines — the technical audit add-on is the one that goes looking for causes. **Do I have to host with you to buy this?** No. Index monitoring works on any domain, wherever it is hosted. You need a Zinn Digital® account, which is free to create, and you add the domain you want watched. **Can I cancel whenever I want?** Yes. It is billed monthly, or yearly at a saving, with no minimum term, and cancelling stops the next charge. The history we have already collected for you stays readable for as long as your account is open. **What happens if my account is suspended or unpaid?** Checks stop while the account is not in good standing, and start again by themselves once it is — you do not have to ask. Everything already collected stays visible in the meantime, with its real age shown, so you are never looking at stale data that is pretending to be current. --- # Find out what people actually search for before you write it URL: https://zinndigital.com/add-ons/keyword-research Search volumes, related phrases and how hard each one is to win — for any market and any language — so the next page you write has a reason to exist beyond a hunch. ## What it is Most content is written first and justified afterwards. Keyword research reverses that: before you commission a page, you find out how many people are looking for it every month, what they type instead, and how entrenched the sites already answering it are. It is the cheapest part of a content budget and the part most often skipped, because it usually means yet another subscription. Here it is an add-on on the account that already hosts the site the content is going on. ## What you get Real search data, not a plugin's guess from your own analytics. - **Monthly search volume** — How many people search a phrase, by market, so you can size an opportunity before you pay somebody to write for it. - **Related phrases** — The searches around the one you typed — usually where the winnable traffic is, because the obvious phrase is the contested one. - **Difficulty** — How hard a phrase is to rank for given who already ranks, so you can tell an achievable target from a vanity one. - **Any language, any country** — The same research in the fifty-eight languages the rest of the platform speaks, which matters if you sell in more than one. - **On demand and on a schedule** — Run research whenever you want, and get a refresh of your saved phrases weekly so you can see seasonality. - **Straight into rank tracking** — A phrase you decide to go after can be added to rank tracking without retyping it anywhere. ## How it works 1. **Start from a phrase or a domain** — Type a seed phrase, or point it at a site and ask what that site is found for. 2. **Read the numbers** — Volume, related phrases and difficulty come back together, in your chosen market. 3. **Send the winners to rank tracking** — Phrases you commit to go straight into daily tracking, so you can tell later whether the content worked. ## Why it is not metered per search Research you are frightened to run is research you do not do. Charging per query makes people ration the cheapest and most useful step in the whole process, so we do not: it is a flat monthly price and you run what you need. We can do that because the underlying data is bought in bulk rather than per question. Where a genuinely expensive operation exists — very large on-demand jobs — it draws on the credit meter your account already has, so there is never a surprise on the invoice. ## Frequently asked questions **Where does the data come from?** A commercial search-data provider, the same source behind our rank tracking and audit products, rather than an estimate derived from your own traffic. **Can I research in languages other than English?** Yes, and this is worth saying plainly: volumes and difficulty are available for every market the platform sells into. **Is there a limit on how many searches I can run?** There is no per-search charge. Very large on-demand jobs draw on your account's credit meter, which you can see and top up. **Do I have to host with you to buy this?** No. Keyword research works on any domain, wherever it is hosted. You need a Zinn Digital® account, which is free to create, and you add the domain you want watched. **Can I cancel whenever I want?** Yes. It is billed monthly with no minimum term, and cancelling stops the next charge. The history we have already collected for you stays readable for as long as your account is open. **What happens if my account is suspended or unpaid?** Checks stop while the account is not in good standing, and start again by themselves once it is — you do not have to ask. Everything already collected stays visible in the meantime, with its real age shown, so you are never looking at stale data that is pretending to be current. --- # LiteSpeed Enterprise, installed and licensed by us URL: https://zinndigital.com/add-ons/litespeed The commercial web server our own hosting is built on, put on a machine you run — ordered, licensed, installed, kept up to date and handed back when you are done. Buy it from LiteSpeed and you get a serial in an email. Buy it from us and you get a server that is already serving. ## What it is LiteSpeed Web Server is the commercial web server we run our own hosting on. It serves the same sites Apache would, on less hardware, and it brings LSCache — the full-page cache that makes WordPress and WooCommerce feel instant rather than merely acceptable. Zinn Digital® is an official LiteSpeed Partner, so we can supply it for a machine of your own and manage it the way we manage our own fleet. What you buy here is that management with the licence inside it: we order the licence, bind it to your server, install the web server, prove it is actually running, keep the licence current every month, and give it back if you stop. ## What we do, and when Everything below happens without you doing any of it. - **We buy the licence** — Ordered against your server's address, so it is locked to your machine from the moment it exists. No serial to copy, no form to fill in. - **We install the web server** — Onto the machine as it stands. We check first that there is room, that the operating system is one we stand behind, and that nothing else is already serving on it — and we stop rather than break what is there. - **We prove it is running** — Not that a file appeared: that the server is up, licensed and answering. An unlicensed LiteSpeed does not serve at all, so this is the step that matters. - **We keep it current** — The licence renews with your account, on your normal invoice. Nothing to diarise and nothing that quietly expires. - **We hand it back** — Cancel, or tear the machine down, and the licence is released to LiteSpeed rather than left billing. That is our job, not yours. - **One place to ask** — It is our service, so if it misbehaves you talk to us — not to a vendor you have no relationship with. ## How it works 1. **Pick the server** — Any Zinn® cloud server or VPS you run. You do not need to rebuild it — this installs onto a machine that is already up. 2. **We check it will work** — Operating system, memory, disk, and whether anything is already serving on ports 80 and 443. If it will not work we say so, in words, and charge nothing. 3. **We order, install and license it** — The licence is bought bound to your machine, LiteSpeed is installed, the serial applied and the server started. 4. **It serves** — Your sites are answered by LiteSpeed Enterprise from that point, and you can see it on the server's page in your dashboard. ## Why buy it managed A licence on its own is the easy part. The work is everything around it: binding it to the right address, installing a web server without taking the machine down, noticing when a renewal fails, and remembering to hand it back when the server goes away. Every one of those costs money quietly when nobody does it. We already do all of it, every day, on our own fleet. Buying it here is buying that same routine pointed at your machine — which is also why we are able to offer it at all: our agreement with LiteSpeed is to bundle their software with our own service, not to resell serials. ## Frequently asked questions **What am I actually buying?** LiteSpeed Web Server Enterprise on a machine you run, with us doing everything around it: ordering the licence, binding it to your server, installing the web server, keeping the licence current, and releasing it if you stop. It is a managed service with the licence inside it, not a licence on its own. **Why not buy the licence from LiteSpeed myself?** You can, and for some people that is the right answer. The difference is what arrives: from LiteSpeed you get a serial and an installation to do; from us you get a server that is already serving, and one place to ask when it is not. **Does it work on a server I already have?** Yes, if it is one we can reach — a Zinn® cloud server or VPS you run with us. We install it onto the machine as it is; you do not have to rebuild it. If the box is somewhere we have no access to, talk to us: we can still supply and manage the licence, a person just does the handover instead of a script. **I already have a control panel on that server.** Then we will refuse rather than break it. A panel brings its own web server and owns ports 80 and 443, so putting LiteSpeed underneath it would stop your sites being served. We check before anything is installed, and nothing is charged if we stop. **Do I need this if I already host with Zinn Digital®?** No. Every site on our own fleet already runs on licensed LiteSpeed Enterprise with LSCache — it is included and there is nothing to buy. This is for a machine of your own. **Which edition, and what does it include?** There is a ladder, and the price list above is it. Web Host Essential — unlimited domains, one worker process, with LSCache — is the one most single servers want. The smaller tiers cap the number of domains; the larger ones add worker processes for a busy machine, and the ADC tiers are load balancers rather than web servers. If you outgrow a tier we move you up it rather than selling you a second licence: two licences on one box is money for nothing. **Can I cancel?** Yes, monthly, with no minimum term. Cancelling stops the next charge and we hand the licence back to LiteSpeed for you; you do not have to remember to. **What happens if my account is suspended or unpaid?** We stop spending on it while the account is not in good standing, and pick it up again on their own once it is — you do not have to ask. --- # See where you appear on Google Maps URL: https://zinndigital.com/add-ons/local-rankings Choose your business, the towns you serve and the searches your customers make, and we show where you sit on Google Maps, whether you make the local 3-pack, and where your website ranks — with who is above you and how it moves over time. ## What it is When someone nearby searches for what you do, Google answers in three places: the map, the three businesses it picks out above the ordinary results, and the ordinary results themselves. Where you appear depends on where the searcher is — the same search from the next town can put you in a different place. Local rankings searches your keywords from each town you choose, as a customer there would, and records all three: your place on Google Maps, whether you are in the local 3-pack, and where your website ranks. ## What you get Built around the one business that matters — yours — in the towns you actually serve. - **Your place on Google Maps** — Found by Google's own id for your business, so a branch of the same chain or a similarly named rival is never mistaken for you. - **The local 3-pack** — Whether you are one of the three businesses shown above the ordinary results, and in which place. - **Your website's position** — Where your site ranks in the ordinary results of the same search, from the same town. - **Who is above you** — The businesses ahead of you on the map for that search, in order — the ones to beat. - **The trend** — Every check adds a point, so you can see each keyword in each town moving up or down over time. - **Your schedule** — Check each keyword every month, week or day, up to what your plan includes. If a schedule would need more checks than your plan has, we say so — with the numbers — before anything is saved. ## How it works 1. **Find your business** — Add your website, then search the map from one of your towns and pick your business from the list. 2. **Choose towns and keywords** — Pick the towns you serve from Google's own list of places, and add the searches your customers make. 3. **Watch where you appear** — Read your map, pack and website positions for every keyword in every town, and who is above you. ## Frequently asked questions **What counts as one check?** One keyword searched from one town. Each check reads the map and the ordinary results together, so you get all three positions for it. Finding your business on the map the first time also uses one check. **How far down do you look?** On Google Maps we read the first hundred places. For your website we read deep enough to find it — up to the first hundred results — and we never say you are not there until we have looked the whole way. **Why mobile?** Most local searches happen on a phone, so each town is searched as a mobile user by default. **Can I check now instead of waiting?** Yes. Check now searches every keyword that has not been checked in the last hour, straight away, using your month's checks. There is no extra charge. **Does my website have to be hosted with you?** No. Any business with a place on Google Maps can be followed, wherever its website lives. --- # We move your site here and you watch it happen URL: https://zinndigital.com/add-ons/managed-migration Give us access to your current host and we do the whole move — files, database, mail, DNS — test it before anything switches, and put it live when you say so. Free, for every site, with no limit. ## What it is Migration is the step where most people give up on changing host. It is not technically hard, but it is fiddly, it touches DNS and email, and the failure mode is your site being down or your mail disappearing while you work out what went wrong. So we do it. You give us access to the current host, we bring everything across, we stand it up here where you can test it on a temporary address, and only when you are happy do we move the DNS. If anything is wrong at that point, the old site is still there. ## What is included The whole move, including the parts people forget until they break. - **Files and database** — Everything, at the version it is at now, not a fresh install you then have to reconfigure. - **Email, properly** — Mailboxes, forwarders and the records behind them. This is the part that most often goes wrong on a self-service move. - **DNS, when you say so** — We prepare the records and cut over on your word, not on a schedule that suits us. - **Tested before the switch** — The site runs here on a temporary address first, so you check it yourself while the live site is untouched. - **Certificates and redirects** — HTTPS working on day one, and your existing redirects preserved so search engines and old links keep working. - **A rollback that actually exists** — Until DNS moves, your old site is live and unmodified. There is a real way back, not a promise of one. ## How it works 1. **Give us access** — Whatever your current host provides — control panel, SFTP, or a backup file. We work with what you have. 2. **We build it here and you test it** — The site runs on our infrastructure at a temporary address. You check it properly while your live site carries on. 3. **You say when** — We move DNS at a time you choose, watch it settle, and confirm mail and certificates are working before we call it done. ## What it costs Nothing. Managed migration is free for every site on every plan, and there is no limit on how many sites you ask us to move. Self-service migration is free too, and it is the fastest route — it starts the moment you submit it. Ask us when you would rather hand it over, or when a source cannot be automated. ## Why it is free Changing host should not cost you anything, and the move is where most people give up. So we do not charge for it — not for the first site, and not for the fiftieth. Most moves are fastest done yourself: sign in to your old host from the migration form and the workflow does the rest. When that is not the right fit, a person does it for you, tests it before the switch and is accountable if it goes wrong. ## Frequently asked questions **How long does it take?** The site is promised ready for you to test within 3 days. The switch itself is minutes and happens when you say so, which may be days later. **Will my site be down?** No. The site is built here while the old one stays live, and the DNS switch is designed so visitors reach one or the other, never nothing. **What about my email?** Included. It is the part most self-service migrations break, so it is explicitly part of the job rather than a caveat. **What if my current host will not give me access?** We deal with that regularly. A backup file is usually enough, and where it is not we will tell you what we need in terms you can pass on. **I have fifty sites to move.** Fifty is fine: there is no limit and it is still free. The fastest way to move many sites is self-service from the Migrations page, which runs them side by side — or ask us and we move them for you. --- # Keep a copy of every backup in storage you own URL: https://zinndigital.com/add-ons/offsite-backups We back your sites up already. This sends an encrypted copy of each backup to your own S3-compatible bucket or SFTP server, so you hold one copy that does not depend on us, and you can restore from it in a click. ## What it is Every site we host is backed up to our own storage, off the server it runs on. That protects you from a server failing. It does not give you a copy you control. With this add-on, each backup of the site is also written to storage you own: an Amazon S3, Cloudflare R2, Backblaze B2, Wasabi or any other S3-compatible bucket, or an SFTP server such as a NAS in your office. The copy stays there for as long as you choose, whatever happens to your account with us. ## What you get Built so the copy is useful on the day you need it, not just present. - **Encrypted before it leaves us** — Each archive is encrypted with AES-256 and signed with HMAC-SHA256 before a byte reaches your storage, so your storage provider only ever holds ciphertext. - **Yours to open without us** — The encryption key is in your dashboard. With it, a standard openssl command turns any copy back into the original archive of files and database. - **Tested before it is trusted** — When you add storage we write a test file, read it back and delete it. If your credentials cannot do all three, we say so before anything is saved. - **Restore in a click** — Pick a copy on the site's Backups tab. We check it has not been altered, then put the site back from it. - **Your retention** — Keep copies for 7, 30, 90, 180 or 365 days. Older copies are removed from your storage for you, never one that a newer copy still needs. - **Paused, not lost** — If an invoice goes unpaid we stop sending new copies, and pick up again as soon as it is settled. Copies already in your storage stay there. ## How it works 1. **Add your storage** — An S3-compatible bucket with an access key, or an SFTP server with a password or key. We prove we can write, read and delete there. 2. **Switch it on for a site** — Choose the storage and how long to keep copies. The newest backup is copied straight away. 3. **Every backup follows** — Each new backup reaches your storage within about ten minutes of finishing. ## Frequently asked questions **Which storage can I use?** Any S3-compatible bucket — Amazon S3, Cloudflare R2, Backblaze B2, Wasabi, DigitalOcean Spaces, MinIO and others — or an SFTP server reachable from the internet. **Can my storage provider read my site?** No. The copy is encrypted before it leaves us, and the key is not stored with it. **Can I restore without Zinn Digital®?** Yes. Show the key in your dashboard, take the IV from the .json file beside the archive, and openssl gives you back the original archive. **Does this replace the backups on my plan?** No. Your plan's backups carry on exactly as before. This adds a second copy in a place you control. **What happens if I stop the add-on?** We stop sending new copies. Everything already in your storage stays there and remains yours. --- # See what ties your sites together URL: https://zinndigital.com/add-ons/pbn-footprint-checker Search engines and competitors look for the traces that show a set of sites has one owner. We check every site you host with us — and any you host elsewhere — for the traces anyone can see, score how exposed the set is, and tell you how to fix each link. ## What it is A network of sites is only as private as the details its sites share. Sites set up by one person tend to have things in common by accident, and anything one site shows the world, anyone can compare across all of them. The footprint checker reads what is publicly visible about each of your sites, compares every site with every other one, and reports each thing two or more of them share that could tie them together — how serious it is, which sites it involves and what to change. ## What you get Built to tell you what to change, not to hand you a pile of raw data. - **One score for the set** — A score out of 100 and a grade for the whole group, with the trend from check to check so you can watch a fix land. - **Every link, explained** — Each finding names the sites it involves, says why it matters and exactly what to change — in plain words, in your language. - **The most closely tied pairs** — See which two sites are most strongly linked and why, strongest first, and pick any site to see everything it is tied to. - **Our side kept apart** — Anything that comes from our own platform is listed separately, is ours to fix, and never lowers your score. - **Sites hosted elsewhere too** — Add the sites you host with other providers with a site pack, and they are checked alongside every site you host with us. - **Check now** — Changed something? Start a check whenever you like — twenty a month on the monthly plan, sixty on the weekly one. ## How it works 1. **Turn it on** — Every site you host with us is included from the start. Add a site pack to include sites hosted elsewhere. 2. **Let it check** — Monthly or weekly, automatically — or on demand whenever you change something. 3. **Fix what it finds** — Work down the list, strongest links first, and watch the score rise. ## Frequently asked questions **Do you publish what you check for?** No. The list of what we compare is kept private on purpose, so it cannot be used to work around a check. Your screen shows what we found on your sites and how to fix each one. **Are the sites I host with you included?** Yes — all of them, on every plan. They are always included and never count against a site pack. **What does a site pack add?** Room for sites hosted with other providers: five, ten, twenty-five, fifty or a hundred at a time. Packs stack. **What counts as a check-now run?** A check you start yourself. Automatic checks never count, and a check that could not read any of your sites is not counted either. **Does it change anything on my sites?** No. It reads only what any visitor could read, and never signs in to a site or changes it. --- # More room for one busy site URL: https://zinndigital.com/add-ons/performance-boost Lift a single site one, two or three resource tiers above what its plan gives it. More CPU, more memory and more processes for that site, without moving the whole account to a bigger plan. ## What it is Every site on our hosting runs inside its own resource limits: how much CPU it may use, how much memory, how much disk I/O, and how many processes and PHP requests it may run at once. Your plan decides which tier of limits a site gets. Performance Boost raises those limits for one site. Level 1 lifts it one tier, level 2 two tiers and level 3 three tiers, up to the highest tier we run. The rest of your sites, and your plan, stay as they are. ## What changes for the site The same limits the plan sets, one or more steps higher. - **More CPU** — A higher share of processor time, so heavy pages and busy moments queue less. - **More memory** — A higher memory ceiling for the site, which also raises the ceiling available to PHP. - **More disk I/O** — Higher read and write limits for sites that move a lot of data. - **More processes** — More processes and more PHP requests at the same time, for traffic that arrives together. - **Applied for you** — There is nothing to configure. The new limits are written to the server for that site, and the site is checked against them from then on. - **One site at a time** — Buy it for the site that needs it. You can boost different sites by different amounts. ## Boost every site on your account at once The Account Performance Boost: one level for all your hosting sites, priced per site by what each site runs. Choose level 1, 2 or 3 once and every hosting site on your account gets 1.5x, 2x or 3x its plan's CPU and memory, including sites you add later, up to the most one server gives a site. Static sites are not counted, because they are served straight from disk. It is priced per site each month. A standard site (WordPress, PHP, a PHP application) costs $0.86, $1.72 or $3.43. A heavier site (a WooCommerce store, Node, Python, Ruby or .NET, Nextcloud, a headless CMS, and every site on app, LMS, AI and developer hosting) costs $7.58, $15.15 or $30.29, because it uses more of the server. The monthly minimum is $9.99, $19.99 or $39.99. Footprint-Free (PBN) accounts have their own PBN Performance Boost at $0.10, $0.20 or $0.40 per site. You choose, change or stop either boost from Billing in your dashboard. ## How it works 1. **Choose the site and the level** — Level 1, 2 or 3, from the site's settings in your dashboard. 2. **We raise its limits** — The site's resource tier moves up by that many steps on the server. 3. **It stays in place** — The boost is billed monthly for as long as the site keeps it. ## Frequently asked questions **Does it boost every site on my account?** This one applies to the one site you buy it for. To lift every site on your account at once, choose the Account Performance Boost instead. **What is a resource tier?** A set of limits for one site: CPU, memory, disk I/O, I/O operations, processes and concurrent PHP requests. Your plan sets the tier, and a boost moves the site up from there. **Can I go higher than level 3?** A boost cannot take a site above the highest tier we run. If a site needs more than that, talk to us about the right setup for it. **Is this the same as upgrading my plan?** No. A plan change affects the whole account. A boost changes one site and leaves everything else where it is. **Can I boost every site on my account instead of one?** Yes. The Account Performance Boost gives every hosting site on your account more CPU and memory at once, priced per site with a monthly minimum. Heavier sites such as WooCommerce stores and applications cost more per site. --- # Know what your products cost on somebody else's shelf URL: https://zinndigital.com/add-ons/product-price-tracking Track your products — and your competitors' — on Google Shopping and Amazon every week. Ten products included, packs of 25 and 100 to add more. ## What it is If you sell physical goods, your price is being compared with somebody else's several times a day by people you never see. Google Shopping and Amazon are where most of that comparison happens. This add-on watches both, weekly, for the products you name. You find out when a competitor undercuts you, when a reseller lists your product below your own price, and when you disappear from a shelf you were on last week. ## What you get Two marketplaces, weekly, with the history kept. - **Google Shopping and Amazon** — Both, not one. Watching a single marketplace tells you half of what is happening to your price. - **Ten products included** — The base add-on comes with ten tracked products, so it is useful from the day you buy it rather than after you buy a pack. - **Stackable packs** — Packs of 25 and 100 extra products add to the allowance, so a small shop and a large catalogue both pay for what they watch. - **Competitor listings too** — Track a rival's product, not just your own, and see the gap as a line over time. - **Price history** — Every weekly reading kept, so a promotion's effect is visible rather than remembered. - **Beside the store you host** — If your WooCommerce store is with us, this sits on the same screens as its performance and its uptime. ## How it works 1. **Name the products** — Yours, your competitors', or both. Ten are included and packs add more. 2. **Weekly readings on both shelves** — Each product is looked up on Google Shopping and on Amazon once a week and the listing recorded. 3. **See the gap** — Prices over time, yours against theirs, with the dates a change happened. ## Why weekly, and why both marketplaces Weekly is the cadence at which a price change is a decision rather than a fluctuation. Daily readings on a marketplace where sellers adjust constantly produce a chart nobody can act on. Both marketplaces because a single one is misleading. Plenty of products are competitively priced on one shelf and undercut on the other, and knowing only one of those is worse than knowing neither, because it feels like information. ## Frequently asked questions **Do I need a WooCommerce store with you?** No. This tracks public marketplace listings, so it works whether your shop is hosted here, elsewhere, or nowhere. **Can I track products I do not sell?** Yes. Competitor products are a normal use, and they consume the same allowance as your own. **What counts as one product?** One product, watched on both marketplaces. You are not charged twice for the two shelves. **Will it change my prices for me?** No. It measures and reports; repricing is your decision and your shop's job. **Do I have to host with you to buy this?** No. Product price tracking works on any domain, wherever it is hosted. You need a Zinn Digital® account, which is free to create, and you add the domain you want watched. **Can I cancel whenever I want?** Yes. It is billed monthly with no minimum term, and cancelling stops the next charge. The history we have already collected for you stays readable for as long as your account is open. **What happens if my account is suspended or unpaid?** Checks stop while the account is not in good standing, and start again by themselves once it is — you do not have to ask. Everything already collected stays visible in the meantime, with its real age shown, so you are never looking at stale data that is pretending to be current. --- # Know where you rank, without checking by hand URL: https://zinndigital.com/add-ons/rank-tracking We check your phrases in Google and keep every reading, so you can see whether last month's work moved anything. Starter tracks 50 phrases weekly; Pro and Agency track 200 and 750 phrases every day, and packs of 50 add more when you need them. ## What it is Rank tracking answers one question and answers it repeatedly: for the phrases that matter to your business, where do you actually appear in Google today, and is that better or worse than last week? You give us the phrases; we check them every day and keep every reading. The value is not the number, it is the line. A single position tells you almost nothing — results move for reasons that have nothing to do with you. A month of daily readings tells you whether the change you made in week two did anything, which is the only way to know what is worth doing again. ## What you get Everything is in your dashboard beside the site it belongs to, so ranking is not a separate tool you have to remember to open. - **Daily checks, kept for ever** — Pro and Agency check every phrase once a day, Starter once a week, and every reading is stored. You can look back over any period rather than only at today. - **Three plan sizes** — Starter tracks 50 phrases, Pro 200 and Agency 750. Every plan includes its phrases from the moment you buy it. - **Stackable packs** — Need more? Packs of 50 extra phrases add to your plan's allowance rather than replacing it, and are checked as often as your plan checks. - **Any domain, anywhere** — Track a site you host with us, a client's site on someone else's hosting, or a competitor. It is a search result, not a server reading. - **Position history, not just alerts** — Charts over time per phrase, so you can put a content change or a link campaign beside the line it moved. - **Included in the SEO surfaces you already have** — Ranking sits with indexing, authority and site health on the same screens, rather than in a separate product with a separate login. ## How it works 1. **Add your phrases** — Type the searches you want to be found for, or paste a list. The counter shows where you are against your plan's allowance. 2. **We check them for you** — Starter checks every phrase once a week; Pro and Agency check every day. We read only as deep as your position needs, which is what keeps the cost of this sensible at any number of phrases. 3. **Watch the line, not the number** — Positions land in your dashboard with their history. Movement is what you act on, and movement needs more than one reading. ## Why buy it from your host Most rank trackers are a separate subscription, a separate login and a separate export you then have to line up against what you changed on the site. Ours sits on the same screen as the site itself, beside its indexing state, its authority score and its speed readings, because those are the things that explain a ranking change. It also means one bill. If you already host with us, rank tracking is a line on the invoice you already receive rather than another card on file somewhere else. ## Frequently asked questions **How many phrases can I track?** Starter includes 50, Pro 200 and Agency 750. Packs of 50 add to any of them, and the allowances add up. **Which search engine and which country?** Google, and you choose the location the check is run from, because a phrase ranks differently in different places and a single global number would be misleading. **How often are phrases checked?** Starter checks once a week; Pro and Agency once a day. Phrases that rank deep cost more to read, so if a month's checks on your plan reach their budget, the rest of that month is checked weekly and daily checks start again on the 1st. Your dashboard shows which you are on. **Can I track a competitor's site?** Yes. A rank check is a search result, so any domain can be tracked whether or not you control it. Competitor Intelligence is the add-on built for watching several of them at once. **Do I have to host with you to buy this?** No. Rank tracking works on any domain, wherever it is hosted. You need a Zinn Digital® account, which is free to create, and you add the domain you want watched. **Can I cancel whenever I want?** Yes. It is billed monthly, or yearly at a saving, with no minimum term, and cancelling stops the next charge. The history we have already collected for you stays readable for as long as your account is open. **What happens if my account is suspended or unpaid?** Checks stop while the account is not in good standing, and start again by themselves once it is — you do not have to ask. Everything already collected stays visible in the meantime, with its real age shown, so you are never looking at stale data that is pretending to be current. --- # Find out what the first page of your own name says URL: https://zinndigital.com/add-ons/reputation-monitoring Somebody searches your brand before they buy. We check what comes back every week — including the results that are not yours — and tell you when it changes. ## What it is Almost every purchase now includes somebody typing your name into a search box. What comes back is your real front door — your own site, your listings, your reviews, and anything else that has managed to rank for you. Reputation monitoring watches that page. Every week we run the searches for your brand and record what ranked, so a new result you did not expect — a review site, a complaint thread, a competitor's comparison page — is something you learn about rather than something a customer mentions. ## What you get The page as a searcher sees it, kept week by week. - **The whole first page, recorded** — Not just your position — every result, so you can see who else is occupying your own brand search. - **New results flagged** — Something that was not there last week is the thing worth your attention, and it is what you are told about. - **Lost ground flagged too** — A profile or listing of yours that has slipped off page one is a silent loss, and it is the one people notice last. - **Several brand terms** — Your company, your product names, your founder — whichever searches actually carry your reputation. - **Kept as history** — So you can show what a campaign or a piece of PR actually changed. - **Works for a person too** — The same monitoring applied to a name rather than a company, which is what executives and consultants usually want. ## How it works 1. **Name your brand terms** — The searches that carry your reputation — usually your company name and a handful of product or people names. 2. **We run them weekly** — The full first page is captured and stored for each term. 3. **You hear about changes** — New results and lost positions are what surface. A page that has not moved does not need an email. ## Why it is cheaper than the tools that do only this Standalone reputation tools are priced as a crisis product, because that is when people buy them. We are not in that business: this is search data we already collect for other reasons, applied to your brand terms instead of your commercial ones. That is the pattern across all of these add-ons. The infrastructure exists because we host you; pointing it at another question costs us very little, so it does not have to cost you very much. ## Frequently asked questions **How many brand terms can I watch?** Enough to cover a normal brand — your company, your products, your key people. If you have an unusual number, competitor intelligence adds domain capacity and the two work together. **Will you remove a bad result for me?** No, and be wary of anyone who says they will. What we do is tell you it is there, and how it moves, so you can respond with content and PR that outranks it. **Does this monitor social media?** It monitors search results, which is where a purchase decision usually starts. Social listening is a different product and we do not pretend to do it. **Do I have to host with you to buy this?** No. Reputation monitoring works on any domain, wherever it is hosted. You need a Zinn Digital® account, which is free to create, and you add the domain you want watched. **Can I cancel whenever I want?** Yes. It is billed monthly with no minimum term, and cancelling stops the next charge. The history we have already collected for you stays readable for as long as your account is open. **What happens if my account is suspended or unpaid?** Checks stop while the account is not in good standing, and start again by themselves once it is — you do not have to ask. Everything already collected stays visible in the meantime, with its real age shown, so you are never looking at stale data that is pretending to be current. --- # SEO data for every client site, on one flat bill URL: https://zinndigital.com/add-ons/reseller-seo-data Authority, links and search data across your whole book of client sites for one monthly price up to two hundred sites, then a small amount per site after that. Sell it on at your own rate. ## What it is Agencies get asked for SEO reporting by every client and can rarely justify a per-seat tool licence across a hundred of them. The tools are priced for a brand watching its own site, not for somebody watching two hundred sites they do not own. This is the wholesale version. One flat monthly price covers up to two hundred client sites, and beyond that you add sites individually for a small amount each. The data lands in the same dashboard your clients already log into, under your brand. ## What you get The same readings our direct customers buy, priced for somebody who needs them across a book rather than for one site. - **A flat rate to two hundred sites** — One price, however many of your first two hundred client sites you switch it on for. Beyond that, sites are added individually. - **Weekly readings per site** — Authority, trust and link profile for every site, refreshed weekly and kept as history you can show a client. - **Under your own brand** — It appears in the white-label dashboard your clients use, so the reporting is yours rather than ours. - **Set your own price** — Charge it on as part of a retainer or as a line item at whatever margin you choose. We do not set your resale price. - **No per-client contracts** — Switch a site on when you win the client and off when you lose them. There is no minimum term per site. - **Sits on the hosting you already resell** — Same account, same invoice, same dashboard — not a separate vendor relationship to manage. ## How it works 1. **Switch it on for your account** — One add-on, bought once, that covers your whole book rather than one site. 2. **Choose which client sites** — Turn it on per site. The first two hundred are covered by the flat rate; extra sites are added individually. 3. **Charge it on** — The data appears in your branded dashboard. What you charge for it is entirely yours. ## Why the cadence is weekly, and why that is the right answer Our paid client-site data is deliberately capped at weekly, and it is worth saying why rather than leaving it to look like a limitation. Authority and trust move on the timescale at which links are actually acquired. A daily reading of those numbers is measurement noise, and selling it as insight would be selling a chart that means nothing. Weekly is also what lets the flat price work at this scale. Sub-weekly cadences remain available on a client's own data-provider key, where both the quota and the choice belong to them. ## Frequently asked questions **How many client sites does the flat rate cover?** Two hundred. Beyond that each site is added individually at a small monthly amount, so growing past two hundred is gradual rather than a cliff. **Do my clients see your brand?** No. It renders inside the white-label dashboard, so the reporting carries your brand, your logo and your domain. **Can I charge my clients whatever I like for it?** Yes. We sell it to you wholesale and take no view on your resale price. **Can a client take their data with them if they leave?** The history belongs to the site. If a client moves to their own account, the readings we have taken move with them. **What if I only have twenty client sites?** The flat rate still applies — it is a ceiling, not a commitment. If twenty sites is where you are, you pay the same as somebody with two hundred and grow into it. --- # A person reads your site and writes you a plan URL: https://zinndigital.com/add-ons/seo-audit Not a scan with a score out of a hundred. An engineer goes through your site, finds what is actually holding it back, and writes it up in an order you can work through. ## What it is Automated audits are useful and we sell one. What they cannot do is tell you which of their forty findings actually matters for your business, or notice the thing that is not on any checklist. This is a person. An engineer looks at your site with access to the server it runs on — its real response times, its error log, its cache behaviour, its indexing state — and writes you a document that says what to fix, in what order, and what each one is likely to be worth. ## What you get A written report you can hand to a developer, not a dashboard you have to interpret. - **A prioritised list** — Ordered by what it is likely to be worth, not by what a scanner happened to check first. - **Server-side facts, not guesses** — We host it, so the audit is written against real response times, real cache behaviour and your actual indexing state rather than a synthetic test from outside. - **Technical and content both** — Crawlability, speed, structure and the on-page work — because fixing one and not the other rarely moves anything. - **Written for a developer** — Specific enough to act on. 'Improve page speed' is not a finding; 'this query runs on every request and is not cached' is. - **One-off, no subscription** — Buy it when you need it. There is nothing to cancel afterwards. - **Follow-up work is separate and optional** — If you want us to do the fixing, the speed-up and database services exist. Nobody is upsold inside the report. ## How it works 1. **Buy the audit** — One-off, from your dashboard, against the site you want looked at. The report is promised within 3 days. 2. **We do the work** — An engineer goes through the site and the server behind it. This is human work and takes working days, not minutes. 3. **You get the report** — A written, prioritised document. Ask us anything about it — that conversation is part of what you bought. ## Why this costs more than a scanner subscription Because it is somebody's time. A scan is a machine doing in ten seconds what it does for everybody; this is an engineer spending hours on your site specifically, and writing something a developer can act on without translation. If a generated report is what you want, the whole-site technical audit is the automated product and costs a fraction of this. They answer different questions and we would rather sell you the right one. ## Frequently asked questions **How long does it take?** The report is promised within 3 days, and that promise is attached to the purchase rather than being a target we aim at. You are told the expected date when you buy it. **Do I have to host with you?** It is much better if you do, because the audit uses server-level facts we can only see on our own infrastructure. We will still do it for a site elsewhere, with that limitation stated in the report. **Will you fix what you find?** Not as part of this. The report is the deliverable. If you want the work done, the speed optimisation and database services are separate and you choose whether to buy them. **Is this the same as the automated audit?** No, and they are priced very differently for that reason. The automated one runs every month and checks a fixed list; this is a person forming a judgement about your specific site once. --- # A tuning pass on the site you already have URL: https://zinndigital.com/add-ons/speed-optimization Caching set up properly, images dealt with, render-blocking assets moved, and the queries that actually cost you time found and fixed. One job, with before and after numbers. ## What it is Most slow sites are not slow because of anything exotic. They are slow because caching was never configured for how the site actually behaves, because images are being served at four times the size anybody sees them, and because two or three queries run on every request that did not need to. This is a person going through that list on your site. We measure before, do the work, and measure after on our own testing hardware — so the improvement is a number rather than an impression. ## What we do The changes that reliably matter, done properly rather than switched on and hoped for. - **Caching configured for your site** — Not a default profile. What can be cached, for how long, and what must never be — which is what makes the difference between fast and broken. - **Images dealt with** — Sized, compressed and served in modern formats, which on most sites is the single biggest win available. - **Render-blocking assets** — CSS and JavaScript that stops the page drawing, moved or deferred so the visitor sees something sooner. - **The queries that cost you** — We can see what your site actually runs, so this is the real slow query rather than a generic recommendation. - **Measured on our own lab** — Before and after Core Web Vitals from our own testing hardware, with no third-party quota and no waiting for a slot. - **Nothing rebuilt** — This is tuning what you have. Your theme, your plugins and your content are left as they are. ## How it works 1. **We measure first** — A baseline on our own lab hardware, so there is something honest to compare against afterwards. 2. **We do the work** — Caching, images, assets and queries, in the order that gives you the most for the time — within 2 days. 3. **We measure again** — The same tests, the same hardware, and you get both sets of numbers. ## How this differs from the speed-up service This is a tuning pass: a fixed list of high-value changes applied well, at a one-off price that suits a normal business site. The expert site speed-up is a bigger engagement, priced by site size, for cases where the answer is architectural rather than configurational — a store with thousands of products, a site with a plugin doing something fundamentally expensive. If the tuning pass is not enough we will say so rather than repeating it. ## Frequently asked questions **Will you break my site?** Caching is the part that can, which is why it is configured against how your site actually behaves rather than switched on generically. Changes are made with a restore point available. **How much faster will it be?** We will not put a number on it before we have looked, because the honest answer depends entirely on what is wrong. You get real measurements before and after, which is the only figure worth having. **Do I need this if I already have your caching?** Our caching gets you most of the way on a normal site. This is for when it is not enough — usually images, third-party scripts or the site's own queries, none of which caching can fix. **Is this a subscription?** No. It is one job. AccelerateWP is the ongoing performance capability if that is what you are after. --- # Every page on your site, checked every month URL: https://zinndigital.com/add-ons/technical-audit Broken links, missing titles, duplicate descriptions, pages nothing links to, redirects that chain. The whole site, monthly, with the list of what changed since last time. ## What it is Sites decay. Somebody deletes a page and forgets what linked to it, a plugin update drops the meta description template, a redirect gets chained behind another redirect, and a year later nobody knows why traffic drifted down. The technical audit crawls the entire site every month and lists the problems in the order they matter. Because it runs monthly and keeps history, the most valuable output is not the list — it is the diff. Eleven new broken links this month means somebody did something last month. ## What it checks The technical faults that are invisible from the front of a site and expensive over time. - **Broken links and dead images** — Internal and external, with the page each one is on so it can actually be fixed. - **Missing and duplicate metadata** — Titles and descriptions that are absent, too long, or identical across pages that should compete for different searches. - **Orphan pages** — Pages nothing on your site links to. They are usually accidents and they almost never rank. - **Redirect chains and loops** — A redirect to a redirect costs speed and dilutes what the link was worth. Loops cost the page entirely. - **Duplicate content** — Pages that are substantially the same, which make search engines choose one and ignore the others. - **A month-on-month diff** — What is new since last month, which is the part that tells you somebody changed something. ## How it works 1. **We crawl the whole site** — Every page, once a month, not a sample and not just the pages in your sitemap. 2. **We compare with last month** — The findings are diffed, so new problems stand out from ones you have already decided to live with. 3. **You get the list** — In your dashboard, ordered by impact, with the URL of every affected page. ## Why it is not priced per page Charging per page would mean the biggest sites — the ones with the most to go wrong — pay the most to find out, and would encourage people to audit only part of a site. Half a crawl finds the problems in half a site and tells you nothing about the rest. So it is one price per site at any size. The crawl runs on our own hardware rather than through a metered third-party service, which is what makes that possible. ## Frequently asked questions **Is there a page limit?** No. One price per site whatever its size. **How is this different from the expert audit?** This is a machine checking a fixed list every month. The expert audit is a person forming a judgement about your specific site once. Most sites want this one running continuously and the expert one occasionally. **Will it slow my site down while crawling?** No. The crawl is rate-limited and runs off-peak, and on sites we host it goes through infrastructure that never touches your visitor traffic. **Does it fix anything?** No. It finds and reports. Fixing is your developer's job, or ours if you buy one of the expert services. **Do I have to host with you to buy this?** No. The technical audit works on any domain, wherever it is hosted. You need a Zinn Digital® account, which is free to create, and you add the domain you want watched. **Can I cancel whenever I want?** Yes. It is billed monthly with no minimum term, and cancelling stops the next charge. The history we have already collected for you stays readable for as long as your account is open. **What happens if my account is suspended or unpaid?** Checks stop while the account is not in good standing, and start again by themselves once it is — you do not have to ask. Everything already collected stays visible in the meantime, with its real age shown, so you are never looking at stale data that is pretending to be current. --- # Get paid for sending people somewhere genuinely good URL: https://zinndigital.com/affiliates The Zinn Digital® affiliate programme is built into the platform, not bolted on with a plugin. Your links are tracked server-side, commissions are rules rather than a single flat rate, and earnings settle through the same payments and wallet engine that runs the rest of the business — with a dashboard showing clicks, signups, conversions and payout history end to end. Availability: the programme is open. Apply from your dashboard — we review every application before a link goes live. Earnings clear a 30-day holdback, which covers the refund window on the payment they came from, and are then settled to your Zinn® wallet or paid out to you. ## How the programme works Five steps, all handled by the engine. You promote, we track, attribute, calculate and pay. - **Your links and codes** — An affiliate account issues unique referral links and referral codes tied to your organisation. Use the link on a site, a newsletter or a video description; use the code where a link will not fit. Both resolve to the same attribution record. - **Tracking on click** — A referral click sets a first-party cookie and is recorded server-side through the platform's attribution layer. The cookie window is a configurable setting on the programme, so a visitor who leaves and returns later is still credited to you. - **Signup and conversion** — When a referred visitor signs up, the attribution is carried across from the marketing site to the app and stored against their organisation as first-touch and last-touch. Conversion is then reported for the lifetime of that customer, not just the first order. - **Commission calculation** — Commission is applied by rule against the converting order or subscription — percentage or fixed, one-off or recurring, and scoped to the product line or plan that was actually bought. - **Payout** — Earnings accrue to your affiliate balance, then pay out on the programme's schedule via the platform's payment provider and wallet, with a statement covering every line in the period. ## Attribution that survives the real web Most affiliate tracking breaks in exactly the places that matter. Browser-side pixels get blocked, cookies get cleared between the ad click and the purchase, and the customer journey crosses two different domains — the marketing site where they read about the product, and the app where they actually sign up. Programmes that only measure the browser quietly lose conversions, and affiliates carry the loss. Zinn Digital® captures the journey at both ends. UTM parameters, ad click IDs, referrer and landing page are captured on the marketing site into a first-party cookie, then carried across to the dashboard on signup via a shared first-party cookie on the apex domain. Conversion events are fired from the engine itself rather than from the visitor's browser, so an ad blocker or a cleared cookie does not silently erase a referral you earned. Attribution is then stored on the referred organisation as both first-touch and last-touch, which is what makes lifetime and recurring commission possible at all. The record does not expire when the session does. ## Commissions are rules, not one flat rate A single global percentage suits the platform's convenience, not the affiliate's business. Commission structures here are configurable along several dimensions at once. - Percentage or fixed amount — a share of the order value, or a set amount per conversion, whichever fits the offer. - One-off or recurring — earn on the first payment only, or keep earning for as long as the referred subscription keeps renewing. - Per product line and per plan — Footprint-Free Hosting, mainstream WordPress hosting and the rest can each carry their own rate, because they carry different margins. - Tiered by volume — structures can step up as your referred volume grows, so scale is rewarded rather than flat-rated. - Holdback and clawback — commission on a refunded or charged-back order is reversed. Money that did not stay with the business does not stay in your balance either. - All amounts are held in integer minor units with an explicit currency, so multi-currency earnings never drift through rounding. ## Payouts, statements and compliance Getting paid is the part affiliate programmes are usually worst at, so it runs on the platform's real money plumbing rather than a spreadsheet. - **Paid through the payment engine** — Payouts run through the platform's payment provider payout path and wallet balance — the same audited engine that handles customer billing, refunds and marketplace settlements. No parallel, unreconciled ledger. - **Scheduled and on method** — The programme defines a payout schedule and the available payout methods, and your balance settles against it automatically once earnings clear their holdback period. - **Statements you can hand to an accountant** — Every payout comes with a statement itemising the conversions behind it, including reversals, so the number you are paid can always be traced back to the orders that produced it. - **KYC for larger affiliates** — Above a defined earnings threshold, identity verification is required before payout. It is a normal condition of paying real money to real people, and it protects legitimate affiliates from the fraud that gets programmes shut down. ## The affiliate dashboard Everything in one place, in your language and your currency, on the same design system as the rest of the platform. - **Clicks and signups** — See traffic by link and code, and how much of it turns into an account. The gap between the two is the number that tells you which placement is actually working. - **Conversions and earnings** — Track which referred organisations converted, on which plan, and what each one has earned you — including recurring commission still accruing on live subscriptions. - **Payout history** — Every payout, its statement, its status and the lines behind it, retained rather than emailed once and lost. - **Asset library** — The approved creative assets for the programme, alongside the affiliate terms, so you are never guessing what you are allowed to publish. ## What you are actually promoting An affiliate programme is only as good as the product behind it. This is a bespoke hosting platform operated by Zinn Digital®, not a reseller account with a logo on it. - Footprint-Free Hosting with 106 auto-managed footprints, footprint-aware CDN account rotation and static-HTML delivery — running across more than 600,000 PBN sites worldwide. - 42 Footprint-Free tiers, from PBN 5 at $6/mo to PBN 2000 at $2,000/mo, so there is a plan for a first network and a plan for a serious operation. - A hosted MCP server that connects any MCP-capable AI tool directly to a customer's hosting — a genuine differentiator to lead with rather than a feature-list filler. - Free, repo-grade WordPress plugins shipped with every site: Zinn® Cache for LiteSpeed and Redis caching, Zinn® Footprint for fingerprint removal. - A card-free 14-day trial on Footprint-Free Hosting with up to 5 sites, plus a 30-day money-back guarantee and free migrations — so the offer you send people to has almost no friction. - The whole platform sells in 58 languages with region-aware currency, so your audience does not have to be English-speaking for your links to convert. ## Referring as a customer, and fair play There are two routes. One is for publishers and partners; one is for customers who simply like the product. - **Customer-to-customer referral** — Existing customers can refer others and both sides receive credit to their wallet — a give-and-get reward that comes off future invoices rather than arriving as a payout. It runs on the same wallet balance used for top-ups, credits and refunds. - **Affiliate accounts** — For publishers, agencies, SEO operators and anyone driving referral volume at scale, an affiliate account gives you the tracked links, the commission structure, the asset library and the payout path described above. - **Anti-abuse checks** — Self-referral, duplicate identities and fraudulent signups are checked against the platform's fraud rules and payment signals, the same ones that protect the marketplaces. Referrals flagged as self-dealing do not pay. - **Terms you can read** — Programme terms sit on the affiliate account itself, alongside the commission structure that applies to you, so the deal you are working to is always visible rather than buried in an email from signup day. ## Frequently asked questions **What commission rate do you pay?** There is no single global rate — commission is set as a rule and can differ by product line, by plan and by your referred volume, and can be one-off or recurring. Your applicable structure is shown on your affiliate account. If you are driving meaningful volume, talk to us and we will discuss the structure rather than point you at a fixed number. **How long does the referral cookie last?** The cookie window is a configurable programme setting rather than a fixed period baked into the code. What matters more is that a referral is not only a browser cookie: attribution is captured server-side and stored against the referred organisation as first-touch and last-touch, so it is not lost the moment a browser clears its storage. **Do I keep earning if the customer stays for years?** That depends on the commission rule applied to your account. Recurring commission is fully supported — attribution is stored on the organisation for lifetime reporting, which is what makes it possible — so a recurring structure keeps paying for as long as the referred subscription keeps renewing. **What happens if a customer I referred refunds or charges back?** The commission is reversed. Rules carry holdback and clawback, so earnings sit through a holding period before payout and are deducted if the underlying payment is refunded or charged back. This is why payouts run on a schedule rather than instantly on conversion. **Do I have to be a Zinn Digital® customer to be an affiliate?** No. An affiliate account can be attached to a user or an organisation independently of whether you host with us. That said, hosting a site or two yourself makes for far better content — and the card-free 14-day trial on Footprint-Free Hosting costs you nothing to try. **Can I refer people without becoming a formal affiliate?** Yes. Existing customers have the customer-to-customer referral route, where both you and the person you refer receive credit to your wallet, applied against future invoices. It is simpler than an affiliate account and needs no payout setup or identity verification. **How do I get paid, and do I need to verify my identity?** Payouts run through the platform's payment provider and wallet on the programme's schedule, with an itemised statement each period. Identity verification is required above a defined earnings threshold before payout can be released — a standard condition of paying out at scale, and one that protects legitimate affiliates from the fraud that closes programmes down. **What creative assets do I get?** Approved marketing assets live in the asset library on your affiliate dashboard, alongside the programme terms, so you always know what is current and what you are permitted to publish. If you need something specific for a placement, ask us and we will look at producing it. --- # Connect any AI tool to your hosting URL: https://zinndigital.com/ai-mcp Zinn Digital® exposes your hosting as a single MCP server, so your preferred AI agent can manage, build and deploy sites in plain language. Connect Claude Code, Claude Desktop or Cursor once, and every tool we add becomes available to it automatically. ## One connection, every AI tool MCP (the Model Context Protocol) is the open standard for connecting AI agents to real systems. We support the protocol, not each app, so you connect the tool you already use and control hosting conversationally. - **Claude Code** — Build, push and deploy from your terminal-based agent, then let it roll back if a release goes wrong. - **Cursor** — Read logs, purge caches, change DNS and deploy from your editor without leaving your flow. - **Any MCP client** — Any client that supports remote MCP servers with a header connects the same way. ChatGPT is the exception for now: it only signs in with OAuth. - **Claude Desktop** — Diagnose a site, prepare a migration or check billing usage in natural language, from the desktop app — connected through the free Zinnector® CLI. ## Three primitives your agent can use The MCP server is a thin adapter over our engine API, so it reuses the same action catalog, RBAC and audit trail. It exposes three things. - **Tools** — Actions the AI can invoke — the same API endpoints behind the dashboard, with no separate logic to drift out of sync. - **Resources** — Read-only context — your account, each site's summary and its health — so the agent reasons with real data before it acts. - **Prompts** — Reusable workflow templates we publish, such as "diagnose this site" or "prepare a migration", so common jobs are one instruction. ## A tool catalogue for real hosting work Every tool is gated by the connected identity's scopes. A sample of what your agent can do: Because the MCP server rides the same API, everything new we add to the platform becomes available over MCP automatically — you are never waiting on a per-tool integration. - List and create sites, deploy them, and roll back a release - Purge a site's cache and choose which crawlers may index it - Take a backup, and restore a site from one - Sync a site's files with its git repository, in both directions - List your domains and edit their DNS records - Read a site's error and access logs, build logs, metrics and usage - Check index status and SEO metrics - Read plan, usage and invoices, and buy add-ons with confirmation ## Built for AI acting on live infrastructure An agent with access to production needs guardrails that are designed in, not bolted on. Ours are: - **Token, org and RBAC scoped** — Your AI client holds a connection token scoped to your org; every session is bound to your user and permissions, with Postgres row-level security enforced. A connection can never out-scope the person who created it. - **Per-tool, revocable tokens** — Tokens are scoped and revocable per tool, with sandbox and production kept separate, so you grant only what each agent needs. - **Destructive-action confirmation** — Delete, suspend, billing and large-spend actions require explicit confirmation or a human-approval policy before they run. - **Spend caps and full audit log** — Rate limits and spend caps bound AI-triggered paid actions, and every MCP action — identity, tool, arguments, result — is audit-logged. ## Frequently asked questions **Which AI tools can I connect?** Any MCP client that can send a token. The dashboard gives you the exact config for Claude Code, Claude Desktop and Cursor, and any client that supports remote servers with a header connects the same way. ChatGPT is the exception for now: it connects only by OAuth sign-in, so it cannot use a token. **How do I connect a tool?** In your dashboard, choose "Connect AI tool" to create a connection — the server address and a token — then paste the config the dashboard gives you into your agent. Tokens are scoped, per-tool and revocable, with separate sandbox and production access. **Can an AI agent do something destructive by accident?** No. An agent can only do what the connected identity is permitted to do, and destructive actions — delete, suspend, billing or large spend — require explicit confirmation or a human-approval policy. Spend caps and a full audit log bound the rest. **Does the agent see real data before it acts?** Yes. It can read a site's error and access logs, its metrics and usage, and its health and configuration, so it diagnoses with real context before taking any action. **Is there a cost to try it?** You can start on a card-free 14-day trial, and every plan carries a 30-day money-back guarantee, free migrations and no vendor lock-in. --- # The MCP tool catalogue: everything your agent can do URL: https://zinndigital.com/ai-mcp/tools Connect an AI agent to Zinn Digital® and it gets a real hosting toolkit — twelve categories of actions covering sites, code, domains, DNS, SSL, databases, configuration, backups, email, SEO, observability, billing and support. Every tool is the same API endpoint the dashboard calls, gated by the same RBAC, written to the same audit log. Availability, updated 12 September 2026: sites (list, create, deploy, roll back), two-way sync with a git repository, site error and access logs and build logs, domains, DNS, email, cache, crawler policy, PHP version, WordPress core and plugins, backups, SEO and index status, metrics and usage, billing documents, the knowledge base and tickets, and reseller operations (your client services, holds, price list and client wallets) are LIVE over MCP today, together with Resources and Prompts. Still in active development and not yet reachable over MCP: domain registration and SSL issue/renew, guarded database queries, raw wp-cli and direct file editing, and — on the reseller surface — adjusting a client wallet, connecting a payment gateway, issuing a client sign-in link and publishing a dunning run. Each needs a priced, irreversible or credential-bearing action handled properly before an agent is given it. Everything else described here is live today. ## One catalogue, not a plugin surface The MCP server is a thin protocol adapter over the engine API. It does not reimplement anything — it exposes the action catalogue that already powers the dashboard, the CLI and our own AI assistant. Three consequences follow, and they are the whole design. - **No second implementation to drift** — An MCP tool is an API endpoint. There is no parallel logic path that can fall behind the product, and no behaviour an agent can reach that the dashboard cannot. - **New capability arrives automatically** — The server is kept in sync with the API from the same OpenAPI and action-catalogue source. Everything we add to the platform becomes available over MCP without a per-tool integration on your side. - **Versioned, with capability discovery** — The server is versioned and publishes capability discovery with a deprecation policy, so an agent can ask what it is allowed to do rather than guess and fail. - **The same identity, the same audit trail** — Sessions are bound to org, user and scopes, with Postgres row-level security enforced underneath. An agent is not a special class of caller — it is your account, acting through a protocol. ## The twelve categories This is the catalogue as specified. Every tool in it is gated by the connected identity's scopes — an agent can only reach what that identity may already do. - **Sites** — List sites, read one in detail, and create a site from a blueprint. Deploy it, follow the deploy, and roll back to an earlier release. - **Code and files** — Sync a site's files with its connected git repository in both directions — commit what changed on the site, or deploy what was pushed — and settle a held sync by choosing which side wins. This is the path that makes "the agent builds, pushes, and the platform deploys" a single conversation. Raw wp-cli and direct file editing are not exposed to an agent yet. - **Domains, DNS and SSL** — List your domains, check whether a domain is indexed, and create, update and delete its DNS records. Registering a domain and issuing certificates are not exposed to an agent yet. - **Database** — A site's backups include its database, and the agent can list them, take one and restore one. Direct database access — guarded queries and optimisation — is deliberately not exposed to an agent yet: there is no database tool on the server, and we would rather say so here than have you discover it from your agent. - **Configuration** — Read and change a site's PHP version, and see and update WordPress core and its plugins. "Move this site to PHP 8.4 and update its plugins" is one instruction. - **Backups** — List, create and restore backups. An agent about to attempt something risky can take its own restore point first, then roll back to it if the change misbehaves. - **Email** — Create and manage mailboxes and forwarders, provisioned through our mail driver — so the contact addresses on a site are handled in the same flow as the site itself. - **SEO** — Index status, rank data and audits, drawn from our SEO data layer. The agent can check whether a change actually landed in the index rather than assuming it did. - **Observability** — A site's error and access logs, its build logs, metrics and usage. This is what turns "the site feels slow" into a diagnosis, because the agent reads the real signals before it proposes a fix. - **Billing and commerce** — Read plan, usage and invoices; buy add-ons and Extras as guarded actions. Anything that spends money requires confirmation — see the guardrails below. - **Support** — Create and list tickets and search the knowledge base, with a published triage prompt that walks the agent through checking a site before a ticket is ever opened. - **Reseller operations** — If you resell our hosting, your own client estate is on the same surface: see every service you have provisioned, place and release a non-payment hold, read your price list with your wholesale cost beside it, and reconcile the client wallet balances you hold. Your clients' sites, driven from your agent — not ours. ## Resources and Prompts: context before action Tools are only one of the three MCP primitives. The other two are what stop an agent acting blind, and they matter as much as the catalogue itself. The practical effect is that a good agent session looks like an engineer's: read the logs, read the config, check the metrics, form a hypothesis, then act on one thing and re-check. The catalogue makes that possible in a single connection. - **Resources — read-only context** — Your account, each site's summary and its health. The agent fetches real state with no side effects, so it diagnoses from evidence rather than from your description of the symptom. - **Prompts — published workflows** — Reusable templates we publish for the jobs people repeat: "diagnose this site", "prepare a migration". A common piece of work becomes one instruction instead of a remembered sequence of steps. - **Triage that ties the two together** — Our published triage prompt — the site's status, its traffic and error rate, the last deploy, its WordPress state and a knowledge-base search — is available to your agent through the same surface, so it runs the checks before it opens a ticket. ## Guardrails, because this is live infrastructure An agent with production access needs limits that are structural rather than advisory. Ours sit in the engine, underneath the protocol — an agent cannot negotiate its way past them. - **Scopes and RBAC** — The agent inherits the connected identity's permissions exactly. If your role cannot deploy, neither can your agent. Role permissions are enforced at the API, not filtered in the client. - **Per-tool, revocable tokens** — Tokens are scoped and revocable per tool, with sandbox and test tokens kept separate from production. You grant one agent what it needs and revoke it without disturbing the others. - **Destructive-action confirmation** — Delete, suspend, billing and large-spend actions require explicit confirmation or a human-approval policy before they execute. The agent proposes; a human — or a policy you set — decides. - **Rate limits, spend caps and idempotency** — Rate limits and per-customer spend caps bound AI-triggered paid actions, and operations are idempotent on retry, so an agent that repeats a request after a timeout does not repeat the effect. - **Full audit log** — Every MCP action is recorded with identity, tool, arguments and result. You can reconstruct exactly what the agent did, in what order, and on whose authority. ## Your models, your keys The catalogue is model-agnostic. MCP is the connector; which model drives it is your decision, and so is who pays for the tokens. - Bring your own keys — your Anthropic, Google, OpenAI or image-generation credentials live in our Vault credential store, and you pay your own AI costs directly to the provider. - The model registry is data, not code. Providers, models and capabilities are an admin-editable, auto-synced list, so a new model becomes selectable without waiting for us to ship a release. - All inference and embedding calls ride the AI gateway, which handles caching, provider fallbacks, rate limits and cost analytics on the way through. - The same foundation drives AI automations — scheduled recipes such as auto-blog, image generation, alt-text and SEO rewrites — with optional human approval before anything publishes. - Nothing here is exclusive to our own assistant. The in-dashboard AI, the web code editor, the CLI and your external agent all ride the identical API and action catalogue. ## Built to be driven hard An agent catalogue is only useful if it responds at conversational speed while other people are hammering it. The MCP server is engineered for that from the start. The server is stateless and horizontally scaled behind a load balancer, autoscaling on load, so many customers driving agents simultaneously does not create a serial bottleneck. Actions stream and are never parked behind a job queue — MCP is an interactive path, not a background one, and there are no artificial response caps. Async I/O and connection pooling run throughout, and the AI gateway load-balances across provider keys with backoff and failover when a provider throttles. Long-running platform work still runs as durable, retryable workflows underneath, but your agent is never left waiting on a queue to hear back. The deploy path is first-class rather than an afterthought: connect a GitHub or GitLab repository, push, deploy and roll back, all drivable by the agent on top of the same CD pipeline the dashboard uses. Two-way sync between the site and its repository works the same way. ## Frequently asked questions **What can an agent actually do — is this a read-only integration?** It is a full action catalogue, not a viewer. Twelve categories are exposed: sites, code and files, domains/DNS/SSL, database, configuration, backups, email, SEO, observability, billing and commerce, support, and reseller operations. That includes creating sites, deploying and rolling back, syncing a site with its repository in both directions, reading logs, editing DNS, restoring backups, buying upgrades with confirmation and opening tickets — all subject to the connected identity's permissions. **Can an AI agent do something destructive by accident?** The design is layered to make that hard rather than to promise it is impossible. An agent can only invoke what the connected identity is permitted to do; delete, suspend, billing and large-spend actions require explicit confirmation or a human-approval policy; rate limits and spend caps bound paid actions; retries are idempotent; and every action is audit-logged with identity, tool, arguments and result. We would still recommend a scoped, sandbox token while you learn how an agent behaves on your estate. **Do I need a separate integration for each AI tool?** No. We implement the protocol rather than individual apps, so any MCP-capable client connects to the same server. The dashboard gives you the exact configuration for Claude Code, Claude Desktop and Cursor, and clients that adopt MCP later work without changes on our side. ChatGPT is the exception for now: it connects only by OAuth sign-in, so it cannot use a token. **How do tokens and permissions work?** Your AI client connects with a scoped connection token you mint in the dashboard, and the server publishes OAuth 2.1 protected-resource discovery (RFC 9728) pointing at our Keycloak identity provider. Every session is bound to org, user and scopes, with Postgres row-level security enforced at the database. Tokens are scoped, per-tool and revocable, and sandbox or test tokens are kept separate from production. A headless API-key option exists for automation that has no interactive user; API keys are issued per organisation with their own scopes. **Which model does it use, and who pays for it?** Whichever you choose. You bring your own Anthropic, Google or OpenAI keys, stored in our Vault credential store, and you pay your AI provider directly. The model registry is admin-editable and auto-synced data rather than a hardcoded list, so new models become selectable as they appear. **Does the agent see real data before it acts?** Yes. It can read a site's error and access logs, its build logs, metrics, usage, health and configuration with no side effects, and our published triage prompt walks it through checking a site — status, traffic and errors, the last deploy, WordPress state and the knowledge base — before it proposes a change or opens a ticket. **Can I try it without paying?** You can start on a card-free 14-day trial of Footprint-Free Hosting, which covers up to five sites and needs no payment details. Paid plans carry a 30-day no-quibble money-back guarantee and free migrations of existing PBN sites. --- # Hosting you can drive from code URL: https://zinndigital.com/developers Zinn Digital® is an API-first platform. The same engine API that powers our dashboard is the one you get — versioned, spec-first and 100% documented at build time, with generated SDKs, a CLI, a Terraform provider, signed webhooks and an MCP server on top of it. Whatever you use to work — a terminal, a pipeline, a state file or an AI agent — the platform answers to it. ## One API. Every surface rides it. Most hosts bolt an API onto a control panel after the fact, and it shows — half the panel's features never make it out. We built the other way round. The dashboard, the admin console, the CLI, the Terraform provider, the MCP server and your own integrations all consume the same engine API. If you can do it in the panel, you can do it in code. - **Spec-first, not documented later** — The OpenAPI spec is the source of truth, and no endpoint ships unless it is in the spec. That single rule is what makes the public API fully documented at build time rather than eventually — there is no undocumented corner, because an undocumented endpoint cannot exist. - **Generated, never hand-maintained** — Interactive reference docs, the four client SDKs, much of the CLI and the Terraform provider scaffolding are all generated from that one spec. One source, many artefacts, always in sync — you never chase a doc that drifted away from the implementation. - **Versioned with a deprecation policy** — Endpoints live under /v1 with a published deprecation policy and a changelog. You get told before something changes, in writing, rather than discovering it from a failing build. - **Contract-tested in CI** — Implementation-versus-spec contract tests and OpenAPI linting run on every change. Drift between the code and the contract fails the build — so the spec you generate your client from is the spec the server actually honours. ## Auth, scoping and the things that bite at scale Two ways in, one uniform principal behind them. Whichever you use, the same permission checks and the same database-level isolation apply. - **API keys, per organisation** — Keys look like zdk___. Only a SHA-256 hash of the secret is stored — we cannot show you a key again after issue, and neither can anyone who reaches our database. Keys carry scopes, can be revoked, and are issued per organisation rather than per person. - **Live and test modes, kept apart** — Sandbox keys are separate from production keys and run against sandbox mode: no real billing, no real provisioning. Your integration tests can hammer the API without spending money or building servers. - **OIDC for humans** — User sessions authenticate with Keycloak-issued JWTs, verified against the realm public key, and resolve to the same Principal object an API key does. Endpoints gate on granular permission keys such as sites.create or apikeys.manage, checked per organisation — a permission in one org grants no access in a separate, unrelated org, though it applies to the orgs nested beneath it. - **Row-level security underneath** — Every tenant request runs in a transaction with the Postgres org scope set from the principal, so isolation is enforced by the database, not by an ORM filter someone might forget. The queryset filter is still there as defence in depth. ## Built for machines, not just for demos An API is easy to make look good in a README and hard to make behave under real traffic. These are the parts we sweated, because they are the parts that break integrations at three in the morning. One detail worth calling out, because it shapes how bulk work behaves: a 409 on duplicate domain answers "is this hostname hosted here?" for any tenant, which is an enumeration oracle and a real deanonymisation risk against Footprint-Free. Throttling site creation would have been the lazy fix and would have broken the bulk-provisioning product outright. Instead only rejected duplicate-domain attempts are budgeted, per principal. Successful creates are never charged against it — so you can provision in bulk all day, and probing dies almost immediately. - A consistent error envelope on every failure: a code, a human message, optional field-level details and a request_id you can quote to support. Validation errors return 422 with the offending fields named. - Idempotency keys on POST, with the replay record written on commit rather than inline — so a retry can never replay a cached 201 that names a row which never committed. A failed request releases its in-flight lock immediately, so a 422 does not lock out your corrected retry. - Cursor pagination as keyset over UUIDv7 — stable under concurrent writes, with no page-drift when rows are inserted mid-scan. - RateLimit-Remaining on responses, so a generated client can back off intelligently instead of guessing. - Out-of-scope resources return 404 rather than 403 — a 403 would confirm the resource exists. Filtering by an organisation outside your scope returns an empty page for the same reason. - Site creation is registration, not provisioning: POST /v1/sites returns 201 with status pending and never blocks on the build. The event is written to the transactional outbox in the same transaction as the row, so a site exists if and only if its provisioning is guaranteed to be requested. ## SDKs, a CLI and a Terraform provider Three consumers of the same spec, for three different ways of working. - **Client SDKs** — Generated for TypeScript, Python, PHP and Go, tracking the spec so a new endpoint arrives in your language without waiting on a hand-written wrapper. - **Zinnector®, the CLI** — Scaffold a WordPress site, run it locally with nothing installed but Node, and deploy it. Zinnector® pre-flights your project against the slot you are about to deploy to — PHP version, disk, file count — and warns before you push rather than after. It also signs in, lists sites, deploys, manages domains and DNS, reads mail services, takes backups, runs allow-listed WP-CLI, tails logs and fires bulk operations. Free, MIT-licensed, and built on this same public API. - **The Terraform provider** — Manage sites, domains, DNS records, mailboxes and plans as infrastructure as code. terraform apply provisions hosting, and your environments become reproducible and reviewable instead of a sequence of clicks nobody wrote down. - **Interactive reference** — Generated docs you can read and call from the browser, describing exactly the endpoints the server implements — because both come from the same spec. ## Webhooks that survive your endpoint being down Behind the platform is a durable event spine: every state change writes an event to a transactional outbox in Postgres, atomically with the database change, and a relay publishes it to NATS JetStream. Events are typed and versioned — site.deployed, order.paid, invoice.overdue, backup.completed, abuse.flagged, trial.ending and the rest. - **Subscribe to what you care about** — Register an endpoint as a WebhookSubscription and choose the event types it receives. One stream feeds notifications, analytics, automations and your integration alike — you are consuming the same events we do. - **Signed with HMAC** — Every delivery is HMAC-signed so you can verify it came from us before you act on it. - **Retried with backoff, and logged** — Failed deliveries retry with backoff and each attempt is recorded as a WebhookDelivery. You can inspect and replay deliveries from the dashboard rather than emailing support asking what we sent. - **At-least-once, so dedupe on the id** — The pipeline is deliberately at-least-once rather than pretending to be exactly-once. A relay that dies mid-publish has its claim lease expire and its events republished. Dedupe on the envelope id and your consumer is correct by construction. ## Getting code onto the site An API is only half a developer story. The other half is shipping. - Connect GitHub, GitLab or Bitbucket over OAuth, with deploy keys held in the credential store — not in a config file. - Push triggers a build-and-deploy pipeline, with branch-to-environment mapping (main to production, staging to staging) and per-stack build steps for composer and npm. - Roll back to a previous release when a deploy goes wrong. - Staging clone and push-to-live, so a change is proven somewhere real before it reaches visitors. - SFTP per site under CageFS isolation, so each tenant sees only their own files, plus a jailed SSH shell on the shared platform. - wp-cli from the panel terminal and over SSH. - VS Code in the browser via code-server — a full editor with git, editing the site's files directly. - Per-site PHP version, editable PHP settings, per-site extensions, environment variables and real cron alongside WP-cron. ## Four ways to work on a site The API is one door. These are the other four, and every one of them is included with the plan rather than sold as a developer tier. - **The web editor** — VS Code in the browser, opened from the site's page in the dashboard, editing that site's real files with git built in and the whole editor inside the same CageFS jail as your SFTP access. It edits the LIVE site — there is no staging copy in between, so 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. - **Zinnector®, the CLI** — Free, MIT-licensed and built on this same public API. Scaffold a WordPress site, run it on your own machine, pre-flight it against the slot you are about to deploy to — PHP version, disk, file count — and deploy. Needs Node 24 or newer. - **The MCP server** — One catalogue of tools, so the AI client you already use can work on your sites through the same API and the same permissions the dashboard uses. The same server your own client connects to is the one wired into the web editor. Read-only until you say otherwise. - **Per-site developer access** — Client work does not need your password. Invite somebody by email address and they get exactly one site: they sign in as themselves, with a viewer, editor or manager role, and every other site answers 404 before any handler runs — a Postgres row-level security policy and a request-level fence, not one check. The account owner grants it and revokes it in one click, effective on their next request. ## And the same API your AI agent can use We expose the platform as a hosted MCP server: a thin protocol adapter over the engine API that reuses the identical action catalogue, RBAC and audit trail. Connect Claude Code, Cursor, ChatGPT, Claude Desktop or any MCP-capable client once, and every capability we add to the API becomes available to it automatically. The agent gets three things: Tools (the same API endpoints, no parallel logic to drift), Resources (read-only site health, config, recent logs, metrics, uptime and KB articles, so it diagnoses with real data before acting) and Prompts (published workflow templates such as "diagnose this site" or "prepare a migration"). Safety is the same story as authentication: OAuth 2.1, tokens bound to your org and RBAC permissions with row-level security enforced, scoped and revocable per tool, sandbox separated from production. Destructive actions — delete, suspend, billing, large spend — require explicit confirmation or a human-approval policy. Rate limits and spend caps bound AI-triggered paid actions, and every MCP call is audit-logged with identity, tool, arguments and result. We support the protocol rather than integrating each app one at a time, which means your choice of AI tooling can change without your hosting integration changing with it. ## Frequently asked questions **Is the public API the same one the dashboard uses?** Yes — it is the same engine API, published and hardened. The dashboard, admin console, CLI, Terraform provider, MCP server and webhooks are all consumers of one surface, which is why the API does not lag behind the panel. **Can I test an integration without spending money or building real servers?** Yes. Sandbox keys are issued separately from production keys and run in test mode: no real billing and no real provisioning. Point your CI at sandbox credentials and exercise the full request and response cycle safely. **How do I stop a retry from creating two of something?** Send an Idempotency-Key on your POST. The replay record is written on commit rather than inline, so a retry can never replay a cached success for a row that did not actually commit, and a request that fails releases its lock immediately so your corrected retry is not held up. Webhook delivery is at-least-once by design — dedupe on the envelope id at your end. **Can I give one API key access to all my client organisations?** Not today. API keys are issued per organisation, so an integration spanning several client orgs holds a key for each. Permissions are also checked per organisation for user principals: holding sites.create in one org grants no access in a separate, unrelated org, though it applies to the orgs nested beneath that one. That is deliberate — it confines a compromised key to its own organisation and the sub-orgs beneath it, not the whole platform. **What does the built-in Developer role actually allow?** The dev role covers organisation read, API key management, viewing and creating sites, restarting them, purging their cache, and viewing and replying to tickets. It deliberately excludes billing control. Note that deploy and push-to-live permissions are not part of it — if a team member needs those, assign a role that carries them rather than assuming Developer is the broadest technical role. **What happens to my webhooks if my endpoint goes down for an hour?** Deliveries retry with backoff and every attempt is recorded as a WebhookDelivery you can inspect. Upstream, events are written to a transactional outbox in the same database transaction as the change itself, so nothing is lost while a consumer is unavailable — a down consumer lags, it never breaks the producer, and you can replay deliveries from the dashboard once you are back. **What does it cost to start building against it?** Start on a card-free 14-day trial of Footprint-Free Hosting — no payment details, up to 5 sites. Paid Footprint-Free tiers begin at $6/mo for PBN 5. Every plan carries a 30-day money-back guarantee, free migrations and no vendor lock-in. --- # Custom web development, whatever the stack URL: https://zinndigital.com/development Over 25 years of full-stack development across PHP, Python, .NET, JavaScript and Node, Tailwind and every modern framework. From complete applications to WordPress plugins and theme customisations, tell us what you need and we will build it. ## What we build A genuine catch-all. If it runs on the web, we have almost certainly built something like it before. - **Full applications** — Complete web apps and back ends, front to database, built to the same standards as our own platform, secure and ready to scale. - **WordPress plugins** — Custom plugins built to WordPress.org directory standards, coding-standards clean, translation-ready and security-reviewed. - **Theme customisations** — Bespoke themes and precise tweaks to existing ones, from layout and design changes to performance work and Core Web Vitals. - **APIs and integrations** — Connect your systems together, wire up third-party services, or expose a clean API of your own that other tools can build on. - **Migrations and rescue** — Move a legacy app to a modern stack, or take over and fix a project someone else left in a difficult state. - **Automation and scripts** — Bulk tooling, data processing, scheduled jobs and one-off scripts that take repetitive work off your hands. ## Every language, every modern stack Deep experience means we pick the right tool for your problem instead of forcing everything through one framework. - PHP, including Laravel and the full WordPress and WooCommerce ecosystem - Python, including Django and modern async back ends - JavaScript and TypeScript, Node, React and the current front-end frameworks - Microsoft .NET for enterprise and Windows-adjacent work - Tailwind and modern CSS, responsive and accessible by default, RTL where you need it - PostgreSQL, MySQL and the databases and queues that sit behind them ## 25 years of full-stack engineering, led by Neil Lock Custom development here is led by founder and CEO Neil Lock, a full-stack developer with around 25 years building enterprise-grade applications across Laravel, Python, Django, WordPress and beyond. That range is the point: the right tool gets chosen for your problem, by someone who has shipped production code in most of them. He is also an SEO scientist and an AI developer — building custom LLMs and n8n and Zapier automations — and the engineer who built the world's first AI-driven footprint-free PBN hosting. When we take on your project, that is the depth behind it, not a junior team learning on your budget. - Around 25 years full-stack — Laravel, Python, Django, .NET, Node and WordPress - SEO scientist, so builds are engineered to rank as well as run - AI developer — custom LLMs, n8n and Zapier automations - Built the world's first AI-driven footprint-free PBN hosting ## Built the way we build our own platform We run a live hosting platform with more than 700,000 sites worldwide, so the same engineering discipline goes into client work: proper testing, security review, clean handovers and no cut corners. You get code you can read, maintain and take anywhere. There is no vendor lock-in. Whatever we build is yours, documented and handed over. And if you host the result with Zinn Digital®, you also get our card-free 14-day trial, 30-day money-back guarantee, free migrations and a 99.99% uptime assurance, so the thing we build for you has somewhere solid to live. ## Every service we offer One team and one free quote, whichever of these you need — and most projects need more than one. - **WordPress development** — Custom builds, WooCommerce, headless WordPress, performance work and rescues, by people who host WordPress at scale. - **Custom plugins and themes** — Bespoke plugins, Gutenberg blocks, child themes and full custom themes, built to WordPress.org directory standards. - **Bug and error fixing** — White screens, fatals, broken checkouts, plugin conflicts and hacked sites — on any site, hosted anywhere. - **Python and application development** — Apps, APIs, automation and AI/LLM integrations in Python, Django and modern async back ends. - **Expert site speed-up** — A tuning pass on the site you already have — Core Web Vitals, queries and caching, measured before and after. - **Malware cleanup and hack repair** — Infection removed, the entry point closed, and the blacklist and reputation work that follows. - **Managed migration** — We move the site here and you watch it happen — or we hand it to whoever is hosting it next. ## Frequently asked questions **What kinds of projects do you take on?** Almost anything web-based, from a full custom application to a single WordPress plugin or a theme tweak. If you are not sure whether it fits, tell us about it and we will let you know honestly. **Which languages and frameworks do you work in?** PHP, Python, .NET, JavaScript and Node, plus Tailwind and every modern front-end and back-end framework. With 25+ years across the field we choose the stack that suits your project rather than the one we happen to like. **Do I own the code you write?** Yes. There is no vendor lock-in. The code is yours, documented and handed over, and you are free to host and maintain it wherever you like. **Can you host what you build for me?** If you want us to. Hosting with Zinn Digital® gets you free migrations, a card-free 14-day trial, a 30-day money-back guarantee and a 99.99% uptime assurance, but it is entirely optional. **How do we get started?** Tell us about your project through the contact form and we will come back with a plan, a rough scope and honest next steps. This service is also available from inside your dashboard. --- # Bug fixing and error fixing — on any site, whoever built it URL: https://zinndigital.com/development/bug-fixing White screens, PHP fatals, 500s, a checkout that silently fails, an update that took the site down, a plugin conflict nobody can find, JavaScript errors, a site that has been hacked. Send us the symptom and we find the cause. WordPress, WooCommerce, Laravel, Django, Node or plain PHP — and you do not have to host with us to get it fixed. ## What we fix If the site is doing something it should not, or has stopped doing something it should, it is on this list. - **White screens and PHP fatal errors** — A blank page, a 500, or an error that only appears for some visitors. We turn the logging on properly, reproduce it, and trace it to the line rather than disabling plugins until it stops. - **Updates that broke the site** — A core, plugin, theme or PHP-version update that took things down. We get you back up first, then make the update land safely rather than telling you never to update again. - **Plugin and theme conflicts** — Two things that each work alone and fight each other. Found by bisecting on a staging copy, not on your live site in front of customers. - **Broken checkouts and payments** — WooCommerce orders that fail silently, payment gateways that time out, emails that never send, tax or shipping that calculates wrongly. The ones that cost money while nothing looks wrong. - **Errors that show up as slowness** — N+1 queries, a cron that runs on every page load, an uncached external call, a table with no index. Often reported as 'the site is slow' and fixed as a bug. - **Hacked, defaced and blacklisted sites** — Malware removed, the way in closed, the backdoors found, and the reputation work done — Search Console, blacklists and the mail reputation that goes with them. - **JavaScript and front-end errors** — A form that will not submit, a script that dies on one browser, layout that breaks on mobile, a console full of errors nobody has read. - **Database and data problems** — Corrupt or bloated tables, a failed migration, duplicate or orphaned rows, an import that went in wrong. Repaired with a copy taken first. - **Email that is not arriving** — Site mail going to spam or vanishing entirely — SPF, DKIM, DMARC, the sending path and the plugin that is quietly swallowing failures. ## How it goes Most jobs follow the same four steps, and you hear from us at each one. 1. **Tell us the symptom** — You do not need a diagnosis — that is our job. What you saw, when it started, and what changed just before is usually enough. 2. **We look before we quote** — We take a read-only look at the site and the logs so the quote is based on the actual cause, not on what the symptom looked like. That look is free. 3. **We fix it on a copy, then on the site** — A backup first, the fix proven on a staging copy where we can, then applied live. On a hacked site we close the way in as well as clearing what it left behind. 4. **You get told what it was** — A short write-up of the cause, the fix, and anything we noticed on the way that is going to bite you next. If it is a hosting problem rather than a code problem, we say so. ## 25 years of full-stack engineering, led by Neil Lock Rescue work here is led by founder and CEO Neil Lock, a full-stack developer with around 25 years of production PHP, Python, .NET and JavaScript behind him. Debugging somebody else's codebase is a different skill from writing your own, and it is one that only comes from having read a great many of them. We also run the platform underneath, with more than 700,000 sites on it, so we see what actually breaks WordPress and WooCommerce at volume — not what a forum thread from 2019 says breaks it. - Around 25 years full-stack — PHP, Laravel, Python, Django, .NET, Node and WordPress - Reads logs, traces and queries — not just the symptom on the screen - Fixes the cause, then tells you what caused it in plain English - Works on sites we do not host, with no obligation to move ## Some problems have a page of their own Where the job is a known shape, there is a dedicated service for it. - **Malware cleanup and hack repair** — Infection removed, the entry point closed, and the blacklist and reputation work that follows. - **Expert site speed-up** — A tuning pass on the site you already have, measured before and after. - **Managed migration** — When the honest answer is that the site needs to be somewhere else. We move it and you watch it happen. ## Every development service we offer One team, one quote, whichever of these you need — and most projects need more than one. - **WordPress development** — Custom builds, WooCommerce, headless WordPress, performance work and rescues, by people who host WordPress at scale. - **Custom plugins and themes** — Bespoke plugins, Gutenberg blocks, child themes and full custom themes, built to WordPress.org directory standards. - **Python and application development** — Apps, APIs, automation and AI/LLM integrations in Python, Django and modern async back ends. - **Custom web development** — Full-stack work across PHP, Laravel, .NET, Node and every modern framework, whatever the stack. - **Expert site speed-up** — A tuning pass on the site you already have — Core Web Vitals, queries and caching, measured before and after. - **Malware cleanup and hack repair** — Infection removed, the entry point closed, and the blacklist and reputation work that follows. - **Managed migration** — We move the site here and you watch it happen — or we hand it to whoever is hosting it next. ## Frequently asked questions **Do I have to host with you?** No. We fix sites wherever they live, and there is no obligation to move afterwards. If the cause turns out to be the hosting rather than the code, we will tell you that plainly — including when the fix is something your current host can do for free. **What access do you need?** Usually an admin login and either SFTP or panel access, plus the error logs. For a hacked site we also want the raw access logs. We ask for the least we can work with, and you can revoke it the moment we are done. **What if you cannot find it?** The free look happens before the quote precisely so that this is our risk rather than yours. If we cannot see a route to a fix we say so at that point, and you have paid nothing. **Is this only WordPress?** No. WordPress and WooCommerce are the bulk of it, but we work across Laravel, Django and modern Python, .NET, Node and plain PHP. If it runs on the web we have very likely debugged something like it before. **My site is down right now.** Say so in the form and we will treat it that way. If you are already a hosting customer, open a ticket from the dashboard instead — that reaches us faster than anything on this page. **Can you stop it happening again?** That is the point of the write-up. Where the answer is a process rather than a patch — staging before updates, backups that are actually tested, monitoring that would have told you first — we say which one, and most of them are included free on our hosting rather than sold to you. --- # Custom WordPress plugins and themes, built to directory standards URL: https://zinndigital.com/development/plugins-themes Bespoke plugins, Gutenberg blocks, child themes and full custom themes — written to the WordPress.org plugin-directory standard, translation-ready from the first line, and handed over documented and yours to keep. You do not have to take our word for the standard: we publish nine of our own plugins for free, and every one of them is built this way. ## What we build Scoped to your project, written to the standard, and handed over clean. - **Bespoke plugins** — A plugin that does the one thing your business needs, built the WordPress way — hooks and filters rather than core edits, an uninstall routine, and settings where an editor expects them. - **Gutenberg blocks and block plugins** — Custom blocks and block patterns so your editors compose pages themselves, with the guardrails that stop a layout being broken by accident. Block bindings, variations and a block.json build. - **Child themes** — The safe way to change a theme you did not write. Template overrides, hooks and styles in a child theme, so the parent can still be updated without losing your work. - **Full custom themes** — A theme designed and built for your brand — classic or block, with a real type scale, real accessibility and Core Web Vitals considered before the first line, not after launch. - **WooCommerce extensions** — Payment and shipping methods, checkout blocks, subscription and product-type logic, and the kind of catalogue work that has to stay fast at volume. - **Integrations and APIs** — A plugin that talks to your CRM, ERP, PIM or a third-party API — with retries, rate limits and a queue, so a slow upstream never becomes a slow checkout. ## Built to the standard we publish to Every Zinn® plugin is built so it could be submitted to the WordPress.org plugin directory and pass: WordPress Coding Standards, a security review, translation-ready code, GPL licensing and no PHP notices. That is a written rule for our own work, enforced by automated checks that read the built zip rather than the source tree — so a plugin cannot ship having quietly lost it. We build your plugin or theme to the same rule. It means the code is readable by any competent WordPress developer, that it will survive a core update, and that you are never locked to us to maintain it. - Output escaped, input sanitised, nonces and capability checks on every action - Database access through $wpdb->prepare, never string-concatenated SQL - Every user-facing string translatable, with a .pot file generated at build - No core edits, no bundled premium libraries, no calling home - Documented handover — what it does, where it hooks in, and how to change it ## Read our code before you commission yours The fastest way to judge a developer is to read what they have shipped. Nine Zinn® plugins are free, GPL and downloadable without an account — and they are the ones our own platform runs on. - **Free Zinn® plugins** — Caching, offload, migration, translation, chat, reseller tooling — nine plugins, free, no account needed. - **WordPress development** — The wider service: builds, WooCommerce, headless, performance work and rescues. - **Bug and error fixing** — Something already built and already broken. Any site, any CMS, whoever wrote it. ## 25 years of full-stack engineering, led by Neil Lock Plugin and theme work here is led by founder and CEO Neil Lock, a full-stack developer with around 25 years building production PHP and WordPress, and the engineer behind the world's first AI-driven footprint-free PBN hosting. You get the person who has shipped this code, not a junior learning on your budget. We are not only a hosting company that also writes plugins. We run a WordPress platform with more than 700,000 sites on it, and the nine plugins we publish for free are the ones that platform runs on. The standard we hold your build to is the standard we hold our own to. - Around 25 years full-stack — PHP, Laravel, Python, Django, .NET, Node and WordPress - Nine Zinn® plugins published free, each one translation-ready in 57 languages - SEO scientist, so a theme is built to rank as well as to render - AI developer — custom LLMs, n8n and Zapier automations ## How a build runs No retainer, no discovery phase you pay for before you know the price. 1. **Tell us what you need** — A paragraph is enough to start. Send the free-quote form what the plugin or theme has to do, what it has to talk to, and when you need it. 2. **We scope it and quote it** — You get a written answer on approach, timeline and a fixed price — not an hourly rate and a shrug. If we think the thing you asked for is the wrong thing to build, we say so before you pay. 3. **We build it in the open** — Work lands in a repository you can see, in reviewable increments, on a staging site you can click. 4. **You get the code** — The repository, the build, the .pot file and the documentation. Host it with us or anywhere else — it is your project either way. ## Every development service we offer One team, one quote, whichever of these you need — and most projects need more than one. - **WordPress development** — Custom builds, WooCommerce, headless WordPress, performance work and rescues, by people who host WordPress at scale. - **Bug and error fixing** — White screens, fatals, broken checkouts, plugin conflicts and hacked sites — on any site, hosted anywhere. - **Python and application development** — Apps, APIs, automation and AI/LLM integrations in Python, Django and modern async back ends. - **Custom web development** — Full-stack work across PHP, Laravel, .NET, Node and every modern framework, whatever the stack. - **Expert site speed-up** — A tuning pass on the site you already have — Core Web Vitals, queries and caching, measured before and after. - **Malware cleanup and hack repair** — Infection removed, the entry point closed, and the blacklist and reputation work that follows. - **Managed migration** — We move the site here and you watch it happen — or we hand it to whoever is hosting it next. ## Frequently asked questions **Can the plugin be published on WordPress.org?** Yes, if that is what you want. We build to the directory's standards as a matter of course, so a submission is a decision rather than a rewrite. We can prepare and make the submission for you, or hand you everything you need to make it yourself. **Who owns the code?** You do. You get the repository and the right to change, extend, re-license or walk away with it. We keep no licence key and build in no phone-home. **Can you take over a plugin or theme somebody else wrote?** Yes, and a lot of our work is exactly that. We read what is there, tell you honestly whether it is worth extending or worth replacing, and then do the one we recommended. **Will it work in other languages?** Every string goes through WordPress's own translation functions and we ship a .pot file with the build, so your translator — or ours — can start immediately. Our own nine plugins each ship with 57 languages, which is the habit rather than an upsell. **Do I have to host with you?** No. Hosting and development are separate decisions. If you do host with us you get free migrations and the same team on both sides of the problem, but nothing we build depends on it. **What does it cost?** Every project is different, so everything here is quoted rather than listed. The quote is free and it is a real number, not a range. --- # Python development URL: https://zinndigital.com/development/python Zinn Digital® builds production Python — web apps, APIs, automation, data pipelines and AI/LLM integrations — drawing on 25+ years of full-stack work and the same engineering that runs 700,000+ sites worldwide in production. ## What we build in Python From a single automation script to a multi-service API, we build Python that ships and stays maintainable. - **Web apps & APIs** — Django and FastAPI services — REST and async endpoints, auth, background jobs, and clean OpenAPI contracts your other systems can build on. - **Automation & scripts** — Repetitive work turned into reliable, scheduled jobs: data syncs, reporting, file processing, and glue between tools that were never meant to talk. - **Scraping & data extraction** — Resilient crawlers and structured extraction that handle pagination, rate limits and change, with the output shaped into data you can actually query. - **Data & AI/LLM integrations** — Pipelines, embeddings and retrieval, plus LLM features behind clean adapters so you are never locked to one model or provider. ## How we work The practices behind our own platform apply to the code we write for you. - Django and FastAPI for the right job — synchronous admin-heavy apps, or async high-throughput services - Typed, tested code with linting and CI gates, so changes ship safely rather than hopefully - Integrations sit behind adapter interfaces — no single vendor SDK wired straight into your business logic - Built to scale horizontally and stay stateless where it can, so growth is a config change, not a rewrite - Clear handover: documented endpoints, runnable locally, and yours to own — no vendor lock-in ## Why Zinn Digital® We are not a generalist agency that also dabbles in Python. We run a live, revenue-generating hosting platform on Python every day, so the code we write for you is informed by what actually holds up under load, over years, at scale. Our founder, Neil Lock, brings around 25 years of full-stack engineering and builds custom LLMs and n8n and Zapier automations, so AI, data and Python work are core competence here rather than a bolt-on. That means practical decisions: async where it earns its keep, caching in the hot paths, idempotent jobs that survive retries, and observability so you can see what your system is doing. The result is software that is fast, debuggable and cheap to change. If your Python work sits alongside a website, we also build WordPress and can host the whole thing — with free migrations, a 30-day money-back guarantee and no lock-in if you ever want to leave. ## 25 years of full-stack engineering, led by Neil Lock Application work here is led by founder and CEO Neil Lock, a full-stack developer with around 25 years building enterprise-grade applications across Laravel, Python, Django, .NET, Node and WordPress. That range is the point: the right tool gets chosen for your problem, by somebody who has shipped production code in most of them. He is also an SEO scientist and an AI developer — custom LLMs, n8n and Zapier automations — and the engineer who built the world's first AI-driven footprint-free PBN hosting, which is this platform's own Python and Django back end. - Around 25 years full-stack — Python, Django, Laravel, .NET, Node and WordPress - AI developer — custom LLMs, n8n and Zapier automations, wired into real systems - SEO scientist, so an application is built to be found as well as to run - Built the world's first AI-driven footprint-free PBN hosting ## Every development service we offer One team, one quote, whichever of these you need — and most projects need more than one. - **WordPress development** — Custom builds, WooCommerce, headless WordPress, performance work and rescues, by people who host WordPress at scale. - **Custom plugins and themes** — Bespoke plugins, Gutenberg blocks, child themes and full custom themes, built to WordPress.org directory standards. - **Bug and error fixing** — White screens, fatals, broken checkouts, plugin conflicts and hacked sites — on any site, hosted anywhere. - **Custom web development** — Full-stack work across PHP, Laravel, .NET, Node and every modern framework, whatever the stack. - **Expert site speed-up** — A tuning pass on the site you already have — Core Web Vitals, queries and caching, measured before and after. - **Malware cleanup and hack repair** — Infection removed, the entry point closed, and the blacklist and reputation work that follows. - **Managed migration** — We move the site here and you watch it happen — or we hand it to whoever is hosting it next. ## Frequently asked questions **Do you use Django or FastAPI?** Both — we pick per project. Django suits admin-heavy apps and fast CRUD with a mature ecosystem; FastAPI suits async, high-throughput APIs and typed request/response models. If you already run one, we work with your stack. **Can you build web scrapers and data extraction pipelines?** Yes. We build resilient scrapers that handle pagination, rate limits and site changes, and turn the results into structured, queryable data. We also build the pipelines that clean, store and schedule that data. **Do you integrate AI and LLMs into Python apps?** Yes. We add LLM features — retrieval, embeddings, summarisation, classification — behind adapter interfaces, so you keep the option to switch model or provider later rather than being locked to one. **Will I be locked into your platform or a specific vendor?** No. We build to no-vendor-lock-in principles: external services sit behind swappable adapters, and the code is documented and yours to run anywhere. If you host with us, migrations are free and there is a 30-day money-back guarantee. **Can you host the Python app you build?** Yes. We can run your Python application on our platform with a 99.99% uptime assurance, free migrations and a card-free 14-day trial, or hand it over for you to deploy elsewhere — your choice. --- # WordPress development, built by people who host WordPress at scale URL: https://zinndigital.com/development/wordpress Custom plugins, themes and blocks, WooCommerce, headless builds, performance work, migrations and rescue jobs. We have written and shipped production WordPress for 25+ years, and we run more than 700,000 sites worldwide on our own platform, so we build for how WordPress actually behaves under load, not how a tutorial says it should. ## What we build Scoped to your project, written to WordPress coding standards, and handed over clean, documented and yours to keep. - **Custom plugins** — Bespoke functionality built the WordPress way, to WordPress.org directory standards: secure, i18n-ready, no PHP notices, and maintainable long after handover. - **Themes and Gutenberg blocks** — Custom themes and block editor experiences, including bespoke Gutenberg blocks and block patterns your editors can actually use without breaking layouts. - **WooCommerce** — Custom checkout flows, payment and shipping integrations, subscriptions and product logic, tuned to stay fast as your catalogue and order volume grow. - **Headless WordPress** — WordPress as an editing backend behind a modern front end, so your team keeps the CMS they know while the site renders fast and server-side. - **Performance and speed** — Core Web Vitals work, query and asset optimisation, and caching done properly. We remove the N+1 queries and blocking calls that slow real sites down. - **Migrations, rescue and fixes** — Moving off a host or platform, cleaning up an inherited codebase, or fixing a site that is broken, hacked or unmaintained. We stabilise first, then improve. ## Why teams bring WordPress work to us Most WordPress problems are not really WordPress problems. They are the result of plugins that fight each other, code that was never written for scale, and hosting that hides the symptoms instead of fixing the cause. Because we build and host at the same time, we see the whole picture and fix the root. Our founder, Neil Lock, has shipped production WordPress for around 25 years — plugins, themes, WooCommerce and rescues — so that judgement comes from experience, not guesswork. We write plugins and themes to the same standards we would submit to the WordPress.org directory: security-reviewed, translation-ready, and free of PHP notices. Everything is documented and handed over so you are never locked to us to make the next change. And when the build is done, it does not have to move. You can host it on our platform with free migrations, a 99.99% uptime assurance and no vendor lock-in, or take the code anywhere you like. The decision stays yours. ## How to start Two ways in, whichever suits where you are. - Tell us about your project from this page and we will scope it, give you a straight answer on approach and timeline, and tell you honestly if it is not something we should build. - Already a customer? Request development work in-app straight from your dashboard, and it lands with the same team that runs your hosting. - Prefer to build and host in one place? We can deliver the work and run it on managed WordPress, WooCommerce, multisite or footprint-free hosting. - No lock-in, ever. You keep the code, the content and the right to move whenever you want. ## 25 years of full-stack engineering, led by Neil Lock WordPress work here is led by founder and CEO Neil Lock, a full-stack developer with around 25 years of production PHP and WordPress behind him, and the engineer who built the world's first AI-driven footprint-free PBN hosting. When we take on your project, that is the depth behind it, not a junior learning on your budget. He is also an SEO scientist and an AI developer, building custom LLMs and n8n and Zapier automations — which is why a build here is engineered to rank and to be automated, not just to render. - Around 25 years full-stack — PHP, Laravel, Python, Django, .NET, Node and WordPress - Nine Zinn® WordPress plugins published free, each translation-ready in 57 languages - SEO scientist, so builds are engineered to rank as well as run - Built the world's first AI-driven footprint-free PBN hosting ## Every development service we offer One team, one quote, whichever of these you need — and most projects need more than one. - **Custom plugins and themes** — Bespoke plugins, Gutenberg blocks, child themes and full custom themes, built to WordPress.org directory standards. - **Bug and error fixing** — White screens, fatals, broken checkouts, plugin conflicts and hacked sites — on any site, hosted anywhere. - **Python and application development** — Apps, APIs, automation and AI/LLM integrations in Python, Django and modern async back ends. - **Custom web development** — Full-stack work across PHP, Laravel, .NET, Node and every modern framework, whatever the stack. - **Expert site speed-up** — A tuning pass on the site you already have — Core Web Vitals, queries and caching, measured before and after. - **Malware cleanup and hack repair** — Infection removed, the entry point closed, and the blacklist and reputation work that follows. - **Managed migration** — We move the site here and you watch it happen — or we hand it to whoever is hosting it next. ## Frequently asked questions **Do you work on existing sites, or only new builds?** Both. A large part of what we do is rescue and improvement work: cleaning up inherited code, fixing broken or hacked sites, and taking over WordPress projects that were left unmaintained. We stabilise the site first, then improve it. **Are your plugins and themes built to a proper standard?** Yes. We build to WordPress.org plugin-directory standards, which means WordPress Coding Standards, a security review, translation-ready code and no PHP notices. Everything is documented and handed over so any competent WordPress developer can maintain it. **Can you build headless WordPress?** Yes. We use WordPress as an editing backend behind a modern server-rendered front end, so your editors keep the CMS they know while visitors get a fast, SEO-friendly site. **Can you host what you build?** You can, but you are never required to. If you host with us you get free migrations, a 99.99% uptime assurance and no vendor lock-in. If you prefer to host elsewhere, you take the code and go. It is your project either way. **How do I get a quote?** Tell us about your project and we will scope it and give you a clear answer on approach, timeline and cost. Existing customers can also request development work directly from the dashboard. --- # Domains, DNS and transfers — under your control, not ours URL: https://zinndigital.com/domains Register a new domain, transfer one in, or connect one you already own elsewhere. Every domain comes with free mailboxes on it, WHOIS privacy, registrar lock, DNSSEC and a full DNS editor — and your EPP authorisation code is always one click away, because a domain you paid for is a domain you can leave with. ## Five ways to get a domain onto the platform Domains are a first-class product line here, not an afterthought bolted onto a hosting plan. Whichever route you take, the domain lands in the same place and behaves the same way afterwards. - **Register a new domain** — Search, add to the cart and check out. The domain is registered through a durable workflow that reconciles with the registrar before it acts, so a retry never double-registers and never double-charges you. - **Transfer a domain in** — Enter the domain and its EPP authorisation code. We pre-flight the transfer first — 60-day lock, registrar lock state, whether the TLD is supported — and tell you exactly what's blocking it before you pay. Bulk transfers accept a whole list of domain and auth-code pairs in one go. - **Connect a domain you already own** — No purchase, no transfer. Prove control with a DNS TXT record, by delegating nameservers to us, or with an HTTP file, and we import your resolvable records and point the domain at your site. Registration stays exactly where it is. - **Buy a domain with your hosting** — One cart, one payment, two jobs. The domain is registered and the site is provisioned onto it automatically — the provisioning workflow waits for the registration to land, then wires DNS, SSL and CDN to the new domain. - **Buy a domain and nothing else** — You do not need a hosting plan to hold a domain here. A domain-only account is fully valid, fully renewable and gets its own dashboard, with hosting available later whenever you want it — the existing domain simply connects to the new site. ## Every domain you register or transfer in comes with mailboxes Email is not something we sell you on top of a domain. Register a domain with us, or transfer one in, and that domain arrives with ten mailboxes of ten gigabytes each, at no extra cost and on no particular plan. A domain-only account gets them exactly as a hosting customer does — there is no hosting subscription to add first. They are yours to run. Create a mailbox the moment the domain is live, rename it, change its password, set a forwarder or an alias, put an autoresponder on it while you are away, adjust its quota, or delete it — all from your dashboard, without raising a ticket and without waiting for us. - Ten mailboxes on every domain, ten gigabytes each — included with registration and with transfer-in alike. - No hosting plan required. A domain on its own is enough. - Create, rename, re-password and delete mailboxes yourself, whenever you want. - Forwarders, aliases, autoresponders and per-mailbox quotas, all self-service. - Open webmail in a browser, or connect any mail client over IMAP and SMTP. ## Search built for people who buy domains in bulk Domain buying is search-heavy, so the search path is engineered like a hot path rather than a form submission. - Bulk mode takes a whole list at once and fans the lookups out concurrently — never one at a time, never truncated at an arbitrary row count. - Availability checks run on the request path, cached briefly and rate-limited. They are never put behind a job queue, so results appear as they resolve rather than after a spinner. - Suggestions come back alongside the exact match, so a taken name immediately offers alternatives instead of a dead end. - Premium domains are priced live by the registry at the moment you search, not read from a stale cache, and the price is bound to your cart for a short window. - Availability is re-verified server-side at checkout. If a domain was taken in the meantime you get alternatives and no charge — the check that matters happens before your money moves, not after. - Prices shown in the browser are display-only. Every line is re-priced server-side from the live catalogue at checkout, so what you see and what you are billed cannot drift apart. ## One DNS editor, wherever you open it The same DNS editor is mounted in the domain screen and in each site's DNS tab. There is one place records live and one behaviour to learn. - **Full record coverage** — A, AAAA, CNAME, MX, TXT, SRV, CAA and NS records, with type-aware validation that catches a malformed record before it reaches the zone rather than after propagation. - **Bulk paste and import** — Paste a zone or import records wholesale when you are moving in, and reset to Zinn® defaults in one action when you want a clean slate. - **Nameservers your way** — Use our branded nameservers, ns1 and ns2 at zinndigital.com, or point the domain at nameservers of your own. Footprint-Free domains are distributed across footprint-aware nameserver pools instead of sharing one obvious set. - **DNSSEC** — DS records are handed to the registrar through the same interface as everything else, so signing a zone is a toggle rather than a support ticket. - **Registrar and DNS stay decoupled** — Holding a domain with us does not force its DNS to live with us, and hosting DNS with us does not require us to hold the registration. The two are separate seams by design. ## Control that stays yours Registrar lock is on by default, so nobody initiates a transfer of your domain without you unlocking it first. WHOIS privacy is offered wherever the registry supports it and defaults to on at checkout, keeping your registrant details out of public WHOIS. Both are toggles you own, not tickets you raise. Your EPP authorisation code is always retrievable. Requesting it unlocks the domain and reveals the code, and the request is recorded in the audit log as the privileged action it is. There is no retention flow, no confirmation maze and no fee-shaped obstacle between you and the code — if you want to move a domain to another registrar, the platform helps you do it. Registrant, admin, tech and billing contacts are held as proper ICANN contact profiles you can edit, with a clear warning before any registrant change that would trigger a 60-day transfer lock. Authorisation codes are never stored as ordinary database columns — they live in Vault and are read only by the workflow that needs them. ## Renewals, expiry and the windows that actually matter Expiry is where domains are quietly lost. Every window is read from the per-TLD catalogue rather than hardcoded, because .com and .co.uk do not behave the same way. - **Auto-renew, per domain** — Toggle auto-renew individually or in bulk across your portfolio. The renewal sweep runs daily against the authoritative expiry date, so a repeated run on an already-extended domain does nothing rather than renewing it twice. - **Advance warning, in your language** — Expiry notices go out ahead of the date and are localised into all 58 languages alongside every other notification — never English-only, never a single last-minute email. - **Grace period** — Past expiry a domain enters the registry's auto-renew grace window, where it is still recoverable at the normal renewal price. The dashboard shows exactly which window a domain is in rather than a vague warning colour. - **Redemption and restore** — After grace comes redemption, where recovery requires a paid restore through the registry. It is a separate, separately priced operation, shown as such — no surprise line item. - **Nothing is silently dropped** — Every state change — expiring, renewed, restored, deleted, transferred out — emits a durable event, so notifications, billing and the dashboard all see the same truth at the same time. ## Priced per operation, captured at purchase Domain pricing is genuinely four different prices, and pretending otherwise is how customers get caught out at renewal. - Registration, renewal, transfer and restore are priced as separate operations against each TLD. A cheap first year does not imply a cheap second one, and we show both. - Every price is stored as integer minor units with an ISO currency code — money is never held as a floating-point number anywhere in the platform. - The price you pay is captured onto the order at the moment of purchase. Later movements in registry cost, our margin or exchange rates never change what you were billed. - Promotional discounts on a first term apply to the registration line only. Renewals always re-price against the real renewal rate — there is no teaser price that quietly becomes permanent and no teaser price that quietly disappears. - Transfers add a year to the domain where the registry grants one. Where a registry does not, we do not claim it does. - Resellers get their own margin overlay on top of platform pricing, composed cleanly through the tenancy tree rather than maintained as a second price list. ## A registrar-agnostic engine underneath No registrar's SDK appears anywhere in our business logic. Every registrar sits behind an adapter interface and is selected by capability rather than by name, which means the platform can add a registrar, swap one out, or route a TLD to a different one without touching the checkout, the DNS editor or your saved settings. If you already have a registrar account of your own, its credentials resolve from Vault per organisation and the domain is registered under your account instead of ours. Registration, transfer, renewal and restore all run as durable Temporal workflows rather than long web requests. Each step is an idempotent activity carrying an idempotency key, and failures compensate backwards — a registration that fails after the nameservers were set undoes the nameservers rather than leaving a half-built domain behind. Payment is captured on the order before fulfilment starts, so a failure at the registrar is a clean refund rather than an argument. Mixed baskets fail independently. If you buy hosting and a domain together and the domain registration is rejected — snatched in the race, registry rejection, registrar outage — the hosting line still completes and the domain line is refunded to your wallet on its own. One failed line never holds the rest of your order hostage. Everything on this page is API-first. Domain search, registration, transfers, DNS records and nameservers are all published endpoints in our OpenAPI specification, which means they are equally available from the dashboard, the generated SDKs, the CLI and our MCP server — so an AI tool can manage your DNS with exactly the permissions you granted it. ## Frequently asked questions **Can I move a domain away from Zinn Digital® later?** Yes, and the platform actively helps you. Requesting transfer-out unlocks the domain and reveals your EPP authorisation code from the Security panel, we approve the gaining registrar's request, and the domain leaves. The code is always retrievable — there is no retention gauntlet and no dark pattern between you and your own domain. **Do I need a hosting plan to buy a domain?** No. A domain-only account is a first-class customer here, with its own dashboard, its own renewals and no hosting subscription attached. If you add hosting later, the domain you already own simply connects to the new site — you never re-purchase it. **Do I have to pay extra for email on a domain I register with you?** No. Ten 10 GB mailboxes are included on every domain registered with us or transferred in, whatever hosting plan you are on — including no hosting plan at all. You can create, rename and delete them yourself from your dashboard, and open webmail from the same screen. **What happens if a domain gets registered by someone else while it's in my cart?** Availability is re-verified server-side at checkout before any charge is attempted. If the domain has gone, the checkout stops with alternatives rather than proceeding, and no money moves. That check is deliberately placed before payment rather than after it. **Can I keep my domain where it is and still host with you?** Yes — that is the connect route. You prove control with a TXT record, a nameserver delegation or an HTTP file, we import your resolvable records, and your site works exactly as it would on a domain we hold. Registration stays with your current registrar and we never touch it. You can transfer it in later if you decide to consolidate. **Is WHOIS privacy included?** WHOIS privacy is offered wherever the registry supports it and is switched on by default at checkout. Some registries do not offer a privacy service at all, and where that is the case we say so on the TLD rather than selling you something the registry does not provide. **What happens if I miss a renewal?** The domain moves into the registry's auto-renew grace window, where it is still recoverable at the normal renewal price. After that it enters redemption, where recovery requires a paid restore through the registry at a higher, separately quoted fee, and finally pending-delete before it returns to the registry. Every window length comes from that specific TLD's own policy, and the dashboard tells you which window a domain is in — with advance notices sent in your language before any of it starts. **Why is the renewal price different from the registration price?** Because they are genuinely different prices at the registry level, and first-year registrations are often discounted where renewals are not. We show the renewal rate next to the first-term price rather than burying it, and a first-term promotion never carries over to renewal in either direction. **Can I manage DNS through an API or an AI tool?** Yes. DNS records, nameservers, availability search, registrations and transfers are all published endpoints in our OpenAPI specification, from which the SDKs and CLI are generated. The same surface is exposed through our MCP server, so an MCP-capable AI tool can work on your domains inside the permissions and audit logging you configure. --- # Send your campaigns from the platform that already hosts you URL: https://zinndigital.com/email-campaigns Write it, schedule it, and send it through your own provider — with consent checked against every recipient before a single message goes out, and every skip counted so you can see why. ## What it is Most hosts leave email marketing to somebody else, so you end up with a separate product, a separate bill and a separate list that never quite matches your customers. We built it into the platform instead. You compose the campaign, choose who it goes to, and schedule it. It sends through your own provider account — you connect it once and the key is stored in our secret vault — so you keep your sending reputation and your own per-message rate, and we do not add a margin to something you are already paying for. ## What you get The parts of campaign sending that are genuinely hard, done properly. - **Consent checked before the send** — Every recipient is audited against unsubscribe state, marketing consent, channel preference and account standing before a message goes. Where consent cannot be established, we do not send. - **Every skip counted** — Unsubscribed, no marketing consent, channel muted, no destination, not in good standing — each one is a number on the campaign, so a small send is something you can explain rather than something you worry about. - **Marketing and service notices kept apart** — A service notice about your invoice is not a marketing email and must not be governed by unsubscribe rules. The two are separate kinds throughout, enforced rather than labelled. - **Saved templates** — Name, subject, body and channels saved and reused, and archived when you stop using them. - **Schedule, pause, cancel mid-flight** — A campaign is a durable workflow, not a queued job. You can pause a send that is running, and cancel one, and it stops. - **Delivery and open tracking** — Delivered, opened and failed are recorded per recipient from your provider's own webhooks. ## How it works 1. **Connect your sending account** — Your provider, your API key. It is stored in our secret vault, not in a database column, and you set your sending domain and reply-to. 2. **Write it, or start from a template** — Subject and body, with the message kind set — news and offers, or a service notice. The kind decides which consent rules apply. 3. **Schedule it and watch it go** — Send now or later. While it runs you can pause or cancel, and you see delivered, opened, failed and every category of skip as it happens. ## What it costs Nothing extra. There is no add-on to buy, no per-message charge from us and no contact-count tier — it is part of the platform, on every plan. You pay your own email provider for what you send, at whatever rate you have with them. We think that is the honest arrangement: we did not build the sending infrastructure, so we should not be charging you a margin on it. ## What it does not do yet We would rather tell you than have you find out. There is no segment builder — you send to your contacts, and choosing an arbitrary slice of them with rules is not something the product does today. And there is no click tracking: delivery, opens and failures are recorded, clicks are not. If either of those is central to how you work, a dedicated email marketing platform is the right tool and we will not pretend otherwise. What this is very good at is sending a well-governed campaign to the people who have agreed to hear from you, without a second subscription. ## Frequently asked questions **Is there an extra charge?** No. It is included on every plan. You pay your own email provider for the messages themselves. **Whose sending reputation is used?** Yours. It sends through your provider account and your sending domain, so deliverability is yours to build and yours to keep. **Can I build a segment?** Not yet. You send to your contacts. The plumbing for segments exists in the engine and the builder does not, and we would rather say so than imply it. **Do you track clicks?** No. Delivery, opens and failures are tracked; clicks on individual links inside a campaign are not counted. **What happens to somebody who unsubscribed?** They are skipped, and the skip is counted on the campaign so you can see it happened. Consent is checked at send time against the recipient, not at list-build time — so somebody who unsubscribed after you scheduled the campaign is still excluded. **Can I send service notices this way?** Yes, and they are a distinct kind rather than a marketing email with a different subject. Unsubscribe rules do not suppress a genuine service notice, which is what keeps invoice and outage mail reaching people. --- # The jobs you'd rather not do, bought in two clicks URL: https://zinndigital.com/extras Extras are first-party services we provide — database maintenance, speed optimisation, malware cleanup, audits and support, plus managed migration, which is free. Some run themselves the moment you buy them. The rest land in a real queue with a named department behind them. Either way you get them where you already manage your sites, in your own currency. ## Services we provide, not a marketplace Extras are the services Zinn Digital® performs for you. They are not third-party listings and they are not recurring plan add-ons that quietly change your entitlements — they are discrete pieces of work with a price, a scope and an outcome. You buy one, we do it, you get told when it's done. Some are one-off: clean up a hacked site, run a performance audit, move a site across by hand. Others are recurring: managed updates, priority support, ongoing maintenance. The catalogue carries both, and each entry is priced accordingly. This matters because the alternative is a support ticket that turns into a quote that turns into an invoice three days later. Extras collapse that into a purchase. The work is defined before you pay for it. ## What's in the catalogue The services below are the first-party extras the platform offers. Availability varies by product line, and each is priced individually in your currency. - **Database maintenance & optimisation** — Clean, optimise and repair tables on a database that has bloated over time — orphaned post meta, expired transients, overgrown revision tables, fragmented indexes. Runs as an automated job against your site. - **Site speed optimisation** — Caching configuration, image optimisation and tuning applied to a specific site. Where the platform can apply it automatically it does; where a site needs judgement, an engineer applies it. - **Malware cleanup & hack repair** — Remediation for a site that has been compromised. Malware scanning, the proactive WAF and per-site isolation are included on every plan — cleanup and repair of an infected site is the service you buy on top. - **Managed migration** — Free, for any site: a staff-run move for unusual stacks, awkward source hosts, or when you simply want somebody else to own the cutover. - **SEO & performance audit** — A reviewed assessment of a site's technical health and performance, delivered as a report you can act on rather than a dashboard reading you have to interpret. - **SSL setup** — Hands-on certificate work for the cases automatic provisioning doesn't cover — custom certificates, unusual chains, or specific edge requirements. - **Managed updates** — Ongoing core, plugin and theme updating handled for you, so a site that has to stay current doesn't depend on somebody remembering. - **Priority & emergency support** — Escalated routing for customers who need their tickets to land at the front of the queue, and emergency cover for when something is on fire outside your normal rhythm. ## Two ways an extra gets done Every extra in the catalogue is classified by fulfilment type, and that classification decides what happens the moment you pay. - **Automated — instant, zero-touch** — Purchase triggers a Temporal workflow or an AI action directly. Database maintenance runs the optimisation job; speed optimisation applies caching and image optimisation. Durable, retryable and idempotent, like every other long-running operation on the platform — nothing is left half-applied if a step fails. - **Staff-fulfilled — a real queue, a real owner** — Purchase creates a task in the admin queue, routed to the department that owns that kind of work — Support, Engineering/Ops, Onboarding, Abuse & Trust-and-Safety, and so on. The task carries status, its own SLA target from the catalogue, and pushes updates back to you as it moves. - **The same lifecycle either way** — Charge, fulfil, notify, mark complete. Every step emits an event, so the work is auditable end to end, and refunds and disputes are handled through the same billing brain as everything else you buy from us. ## Paid for the way everything else is Extras run on the same billing engine as your hosting plan. Prices are held per currency and rendered as stored values, not converted per request — so what you see is what you're charged, and it doesn't drift between the page and the checkout. Money is handled in integer minor units against an ISO currency throughout, because a rounding error on a customer's invoice is not a rounding error. Payment comes from your card or your wallet balance. Credits from a downgrade, a refund or a proration sit in the wallet and can be spent on an extra directly — you don't need to move money back out to buy a service from us. Purchases are org-scoped like every other record on the platform, and privileged actions are audit-logged with actor, action and target. If somebody on your team buys a service, the trail shows who, what and when. ## Offered at the moment you actually need it Extras live in a dedicated section of the dashboard you can browse at any time. But the useful ones tend to find you first, because the platform already knows the state of your sites. - A bloated database gets offered database maintenance — the signal comes from monitoring, not from you noticing. - A site failing Core Web Vitals gets offered speed optimisation, tied to the measurement that flagged it. - A site flagged by malware scanning gets offered cleanup, at the point the flag is raised rather than after the damage spreads. - A new signup with sites elsewhere gets offered managed migration during onboarding, when moving them is still a decision rather than a chore. - The AI assistant can suggest the right extra in context and initiate the purchase for you — the same assistant that already acts on your sites through the platform's tooling. - Nothing is bought without you agreeing to it. A contextual offer is an offer. ## What you already have, so you don't buy it twice We would rather tell you an extra is unnecessary than sell you one. These are included, on plans that carry them, at no additional cost. - Malware scanning and the proactive WAF are included for everyone — they protect the fleet, so they are never optional. - Per-site isolation at the kernel and filesystem layers is included, containing a compromise inside the affected site's own cage rather than letting it spread. - Self-service migrations are free and automated, and managed migration — a person doing it for you — is free too. Neither is a toll on the normal path. - Daily backups with one-click restore, free SSL and the caching stack ship with the hosting itself. - Every extra is data in an admin-managed catalogue — title, description, pricing, product-line eligibility, fulfilment type, SLA and prerequisites — so services are added and adjusted as rows, not releases, and translated into all 58 languages like the rest of the platform. ## Frequently asked questions **Do I need to buy an extra to keep my site secure?** No — baseline protection is included on every plan and is not something we hold back: malware scanning, the proactive WAF, and per-site isolation at the kernel and filesystem layers. What you buy as an extra is remediation — cleaning up and repairing a site that has already been compromised. Isolation is designed to contain a breach to the site it happens on, which is a very different promise from claiming a breach can't happen. **What does an extra cost?** Prices are set per extra in the catalogue rather than fixed platform-wide, because a database optimisation and a malware cleanup are not the same piece of work. Each carries its own one-off or recurring price, held per currency and shown to you in yours. You see the price before you buy, in the Extras section of the dashboard. Migrations — self-service or done by our team — are free. **How quickly is a staff-fulfilled extra completed?** Each extra carries its own SLA target, set on its entry in the catalogue, and the task created by your purchase is tracked against it with status updates pushed back to you. Because the target is per service rather than universal, the applicable one is stated on the extra itself — a malware cleanup and an SEO audit do not share a clock. **Are migrations free?** Free, both of them, with no limit on how many sites. Self-service is the main and fastest route: a workflow handles the transfer, search-replace, verification and DNS cutover, with rollback if something goes wrong. Managed migration is the same move done by our engineers — ask for it when a source is awkward or you would simply rather hand it over, and it costs nothing either. **Can I use wallet credit to pay for an extra?** Yes. Extras are charged through the same billing engine as your subscription, and your wallet balance — top-ups, refunds, prorated credits from a downgrade — can be spent on them directly. Refunds and disputes on an extra go through the same process as any other purchase. **What happens if an automated extra fails part-way through?** Automated extras run as Temporal workflows, which are durable, retryable and idempotent by design. A failed step retries rather than leaving the job half-applied, and the outcome is recorded as an event either way — so a failure is visible and refundable, not silent. **Are extras available on every product line?** Product-line eligibility is a field on each extra in the catalogue, so the services offered to a Footprint-Free network and to a managed WordPress site are not necessarily identical. The Extras section of your dashboard shows what applies to your account rather than a generic list. --- # Everything the platform can do URL: https://zinndigital.com/features AI-native control, enterprise speed, and the tools that get sites in, kept safe and ranking — built in, not bolted on. ## Explore the platform - **Connect any AI tool** — Run your hosting from Claude, Cursor or ChatGPT via our MCP server. - **Enterprise caching** — LiteSpeed + LSCache and per-site Redis — most visits never touch PHP. - **Free plugins** — Repo-grade cache and footprint plugins on every site, auto-updated. - **Footprint remover** — CDN rotation and automatic WordPress-fingerprint stripping. - **Wayback restore** — Rebuild aged domains straight from archive.org history. - **Security & isolation** — CloudLinux isolation, Imunify360 malware protection, layered DDoS. - **Free migrations** — Self-service, automated, verified — free for every site, with no limit. - **Backups & DR** — Immutable, offsite, isolated, tested restores. - **WordPress without wp-admin** — Manage WordPress from your dashboard — plugins, themes, users, updates and integrity checks — without logging into wp-admin. ## DNS, domains and provider control Manage your own DNS, providers and domains — from one dashboard and the MCP, product-line-aware and IP-protected. - **Self-service DNS & cache** — Manage your own records in bulk and purge caches — with origin records locked, and hidden on the PBN line. - **CDN & DNS providers** — Cloudflare, BunnyCDN, CDN77 and more — chosen per site, apex and www on every one, bring your own too. - **Bring your own accounts** — Connect your own CDN, DNS, Cloudflare or GitHub account — validated on entry, stored in Vault, usable across both lines. - **Change a site's domain** — Rename or re-point a site as one operation — Site, WordPress URLs, DNS, CDN, certificate and origin all cascade. - **SEO-crawler blocking** — Block Ahrefs, Majestic and Semrush per site while search engines keep full access — on by default for PBN. - **Business email** — Google Workspace, Microsoft 365 or our own mail, with one-click DNS presets and device autoconfig. ## Why any of this is on the hosting bill Most of what is on this page is sold separately somewhere else. Caching is a plugin you buy. Backups are a subscription. Malware scanning is a service. Staging is a tier. Migrations are a fee. Updates are a care plan. Add them up and the hosting is the cheapest line on the invoice and the least of what you are paying for. We think that is a packaging decision rather than a cost. The platform hosting a site is already closest to all of it — it knows when core shipped, it holds the backups, it runs the scanner, it is the first to know the site is not answering. Charging separately for the platform to use what it already has is a pricing strategy, not an engineering constraint. So the features below are not a tier list. They are what the platform does, and the plan you choose decides how many sites and how much disk you get — not which of these you are allowed to have. ## The four things a site actually needs Everything on this page is one of these four. If you are trying to work out whether a feature matters to you, work out which of the four it is for first. - **Be fast** — LiteSpeed Enterprise with LSCache, per-site Redis, a CDN on every plan, and function-level PHP profiling for the day it is slow anyway. - **Stay up** — Per-site isolation, layered DDoS protection, malware scanning, daily off-site backups you can restore yourself, and a published uptime SLA with credits. - **Be changed safely** — Staging where the plan offers it, a browser IDE on our own fleet, Git deploys, and an AI Update Guard that tells you what a plugin update is likely to break before you press the button. - **Be found** — Automatic Google indexing checks, rank and backlink tracking, AI visibility monitoring, and a footprint remover for portfolios that must not look related. ## Frequently asked questions **Is any of this an upgrade or an add-on?** The features on this page come with hosting. What is sold separately is either a PERSON's time (an SEO audit, a hack repair) or something that costs us money per unit (monitoring an address we do not host, SEO data from a third party, AI generation). Migrations are the exception we make on purpose: an engineer moving a site by hand is free. **Does everything work on every plan?** Nearly. Staging and the browser IDE depend on where the site is placed — the IDE is a feature of our own fleet, so a plan on the shared range does not have one. Each plan page says which, and the WP Care page compares the maintenance list line by line. **Can I use my own accounts instead of yours?** Yes — bring your own Cloudflare, your own registrar, your own DNS. Nothing here requires you to hand us the keys to something you already own, and every external dependency sits behind an interface with more than one implementation, so we can swap a supplier without you noticing. **Is the platform really available in my language?** The whole of it: the dashboard, the emails, the knowledge base, this website and its URLs, in 58 languages. Not a translated marketing page in front of an English product. **Can an AI tool do all of this?** Connect Claude, Cursor or ChatGPT to our MCP server and it can read your estate and run the things that have been switched on for you. Read access is the default; a tool that changes something has to be enabled for your account first. --- # AccelerateWP — server-side caching on every plan, managed at the hosting layer URL: https://zinndigital.com/features/accelerate-wp Every WordPress site gets a full-page cache and a per-site Redis object cache, included with the hosting and running on the server rather than in a plugin you have to configure. Both are switches on the site's Performance tab, and the same tab measures what they change: Core Web Vitals from real visitors, request timings taken on the server, and code-level profiling that names the plugin or query spending the time. ## Two layers included, and they are separate switches These come with the hosting. They are not a tier and turning the paid upgrade off never removes them — which matters, because a downgrade that quietly took your caching away would be taking something you never bought and never stopped paying for. - **Full-page cache (LiteSpeed LSCache)** — Rendered pages are served straight from the cache, skipping PHP entirely for visitors who are not logged in. For a content or brochure site this is the single biggest win available, and it is the difference between a server that shrugs at a traffic spike and one that falls over. - **Object cache (Redis, per site)** — A persistent object cache stops WordPress rebuilding the same database query on every request, so pages assemble faster under load and the database stays cool. Per site, not shared — your cache is not somebody else's eviction. - **Safe exclusions out of the box** — Carts, checkouts, account pages and anything served to a logged-in visitor are excluded by default, for WordPress and WooCommerce alike. A cache that serves one customer another customer's basket is not a performance feature. - **Purge that happens by itself** — Publish a post and it clears that post and the listings it appears on; a comment clears its parent; a theme switch clears everything. - Both layers come with the hosting, on every product line — they are not a tier and are not sold separately. - They are separate switches: a site that has to leave the page cache off still keeps its object cache. - Carts, checkouts, account pages and anything served to a logged-in visitor are excluded by default. - Publishing clears exactly the pages a change affects, and leaves the rest of the cache warm. - There is no plugin licence to buy and no configuration file to edit by hand. ## The weight a cache cannot take off a page Images are usually the heaviest part of a page, and a cache serves a heavy image just as fast as it served it before — it does not make it any lighter. The same is true of a stylesheet that blocks the first paint or a script that runs before anything appears. That is work on the site itself, and it is what the expert speed-up does: an engineer compresses and converts the images, defers what should not block, and on the heaviest sites works out the styling the top of each template needs. - Image compression, modern WebP and AVIF formats and correct dimensions - Minification and deferral of render-blocking assets - Per-template critical CSS on the heaviest tier - Done by an engineer against your site, not switched on ## What the included caching does, and what it cannot Caching makes a page cheaper to serve. It does not make a heavy image lighter or a blocking script stop blocking — that is work on the site itself, and it is what the expert speed-up is for. | | Included caching | Expert speed-up | | --- | --- | --- | | Full-page cache (LiteSpeed LSCache) | Yes | Configured for how the site is built | | Per-site Redis object cache | Yes | Configured and tuned | | Image compression and modern formats | No | Yes | | Render-blocking CSS and scripts | No | Deferred; critical CSS on the heaviest tier | | A CDN in front of the site | From the CDN tab | From the CDN tab | | How it is charged | With the hosting | One-off, by how complex the site is | | Who does the work | You switch it on | Our engineers | | How you get it | The Performance tab | Bought as an add-on | The expert speed-up is priced by how complex the site is, because complexity drives the hours — see the speed-up page for what each tier covers. ## From included to measured, in four steps 1. **Open the Performance tab** — Every site has one. It shows the caching that is already on, what real visitors are experiencing, and where your site's time is going. 2. **Check the caching is on** — The page cache and the object cache are included and listed there. Each is its own switch, so a site that has to leave one off keeps the other. 3. **Measure before you change anything** — Read the Core Web Vitals card and the server-side timings first, so you have something to compare against rather than an impression. 4. **Get the rest looked at, if you need to** — If the numbers still disappoint, the bottleneck is usually not the cache — it is images, a plugin or a query. The expert speed-up is our developers finding and fixing exactly that. ## Three measurements, and only one of them tells you what to fix Core Web Vitals come from what real visitors actually experienced, checked automatically for your homepage and on demand for any other page. Server-side timings are real requests your site served, timed on the server before anything reached a browser — so a slow page is separated from a slow network. Code-level profiling is the one that changes what you do next: every request is profiled on the server, and the history says which pages are slowest, which plugin or query is eating the time, and whether it is getting worse. A score out of a hundred tells you there is a problem; this tells you whose it is. - Core Web Vitals from real visitors, homepage checked automatically - Real requests timed on the server, not a synthetic run - Code-level profiling that names the plugin or query - History over 24 hours, 7 days and 30 days ## Three ways to make a site faster, and they are not alternatives The difference between them is who does the work. Picking the wrong one is easy and expensive, so here is the honest map. - **The caching is already on** — The page cache and the object cache come with your plan and are switched from the Performance tab. Right for most content and brochure sites, and it costs you nothing. - **We set it up properly, once** — A one-off service where we configure the caching against your actual site — the exclusions it needs and the rules it wants — and hand it back working. - **We do the development work** — Our developers work on what is actually slow: a query with no index, a plugin doing something expensive on every page load, a theme rendering the whole catalogue. Priced by how complex the site is. - **The server underneath** — The page cache is LiteSpeed's, and LiteSpeed Enterprise is what our fleet runs. If you host elsewhere and want the same engine, we manage that too. ## Frequently asked questions **What is AccelerateWP?** A server-side caching layer for WordPress, managed at the hosting level rather than by a plugin you install and tune. It is a full-page cache and a per-site object cache, both included with your plan and both switched from the site's Performance tab. There is no licence to buy separately and no configuration file to edit. **What exactly is included at no extra cost?** Two caching layers, and they are separate switches rather than one setting. The page cache serves rendered pages straight from LiteSpeed's LSCache, skipping PHP entirely for visitors who are not logged in — the single biggest win for a content or brochure site. The object cache is a per-site Redis instance that stops WordPress rebuilding the same database query on every request. Both are on every plan, and turning the paid tier off never takes them away. **Do I need to install a plugin or buy a licence?** No. The caching and the optimisations run on the server, underneath WordPress. We do ship the Zinn® Cache plugin as part of a site's deployment, but it is a cache controller rather than a cache engine — it exists so that publishing a post clears exactly the pages that post appears on, and tells our edge to do the same, instead of you clearing caches by hand. **Will it work with my theme and plugins?** The optimisations run at the server and cache layer and ship with safe defaults, including exclusions for the WordPress and WooCommerce paths that must never be cached — carts, checkouts, account pages and anything served to a logged-in user. If something does need excluding, the cache controller lets you exclude it rather than turning the whole layer off. **How do I know it made a difference?** The same tab measures it three ways. Core Web Vitals come from what real visitors experienced. Server-side timings are real requests your site served, timed on the server before anything reached a browser. And code-level profiling names the plugin, query or piece of code that spent the time — which is the only one of the three that tells you what to actually change. **How is this different from the Speed-Up service?** By who does the work. The caching on this page is already on, and you switch it yourself. The setup service is us configuring it properly for your particular site, once. The expert speed-up is our developers working on your site's actual problems — images, a slow query, a heavy plugin, a theme doing something expensive on every page load. They are not versions of one product; one of them may be exactly what you need and the others useless. **Which product lines can use it?** Every WordPress site we host carries both caching layers — they come with the hosting, not with a tier. What varies is the machine underneath: the caching runs where we control the server, so a site on a vendor-managed package gets what that vendor's platform provides instead. **Does it only help WordPress?** The object cache is built for WordPress and that is where it does the most. The full-page cache is not WordPress-specific — a PHP application or a static site on our fleet is served by the same LiteSpeed page cache, and a static site is fast for reasons that make most of this moot. **Is there a premium AccelerateWP tier?** Not at the moment. The caching on this page is what every WordPress site we host runs, and it is included. If your pages are still slow once it is on, the cause is usually images, a plugin or a query rather than the cache — which is work the expert speed-up does, by hand, against your particular site. **Is there a free trial?** There is nothing to trial: the caching is included with the hosting and is on from the first deploy. The hosting itself comes with a card-free 14-day trial. **Does AccelerateWP include a CDN?** No, and deliberately. AccelerateWP ships an integrated CDN and we never switch it on, because every Zinn® site is already fronted by an edge we choose — a second CDN in front of it would mean two caches in series, and a purge on one would leave the other serving a stale page. Your CDN comes from the site's CDN tab. **Can I switch the caching on for some sites and not others?** Yes. Both layers are switches on each site's own Performance tab, and they are independent of each other — a site that has to leave the page cache off still keeps its object cache. --- # An AI assistant that does the work, not just describes it URL: https://zinndigital.com/features/ai-assistant The Zinn Digital® assistant has function-calling access to the same action catalogue that powers the dashboard, so it can reset SSL, add disk, purge cache or open a ticket on your behalf — always within your own permissions. It is grounded in your knowledge base and your resolved tickets, and it speaks every one of our 58 languages. Availability: per-site error tracking and per-site resource statistics are in active development and not yet available. Everything else described here is live today. ## Chat is the interface. The action catalogue is the point. Most hosting "AI" is a search box with a friendlier tone. Ours is wired into the platform API through function calling, so a request becomes an executed action with a confirmed result. The assistant sits on top of the same action catalogue the dashboard, the public API, the CLI and our MCP server all use. There is no separate AI code path to drift out of sync: when we ship a new capability to the platform, the assistant can use it, gated by exactly the same permission checks as a human clicking the button. Ask it to reset a certificate, add disk to a site, purge the CDN, open a support ticket or walk you through a screen with a guided tour, and it carries the request out and reports back — rather than telling you where the setting lives. - **Function calling over the real API** — Every action the assistant can take is a real endpoint on the engine, invoked with your identity. No shadow implementation, no scripted shortcuts, no capability that exists only for the chatbot. - **Bounded by your permissions** — Access resolves through the same role and permission catalogue as the rest of the platform — owner, billing, dev and read-only customer roles, mapped to granular module.action keys. The assistant can never exceed what your membership allows. - **Tenant-scoped by construction** — Every read and write is scoped to your organisation and enforced by Postgres row-level security, the same isolation the API itself runs under. There is no cross-tenant query path for the assistant to take. - **Audited like any privileged action** — Actions taken through the assistant are audit-logged with actor, action and target, so there is a record of what was done, by whom, and on whose behalf. ## Grounded in your knowledge base and your own resolved tickets An assistant that hallucinates hosting advice is worse than no assistant. Ours answers from a retrieval layer built on real, tenant-scoped content. We run a core RAG layer on Postgres with pgvector, holding embedded knowledge-base articles and resolved support tickets under row-level security. It uses multilingual embeddings, so a question asked in Arabic retrieves an answer written in English without an intermediate translation step degrading the match. Every ticket that reaches resolution is embedded back into that index. The assistant improves through retrieval rather than fine-tuning — the knowledge grows continuously, stays scoped to the right tenant, and remains transactionally consistent with the knowledge base it came from. - Semantic knowledge-base search inside the dashboard, not keyword matching. - Ticket auto-suggest and auto-answer, drawing on how comparable issues were actually resolved. - The same grounding behind the assistant, so its answers cite platform documentation rather than general internet lore. - Public help-centre and marketing search runs on a separate, non-tenant edge index, so nothing customer-specific is ever served publicly. ## Triage that runs before a ticket exists When you start to get help, the assistant does not open a blank form. It runs a live diagnostic on the affected site first, in your language. It pulls from our observability signals and runs live checks in the same pass: uptime, HTTP and PHP errors, SSL and DNS state, resource limits and LVE faults, malware flags from the scanner, plugin and theme conflicts, database health and cache state. Within a few seconds it has a picture of the site that a human agent would otherwise spend the first reply gathering. From there it takes one of three routes — fix it, teach you to fix it, or hand it to a human who already knows everything it found. - **Diagnose** — A structured check across uptime, errors, SSL/DNS, resource limits, malware flags, plugin and theme conflicts, database health and cache — combining stored observability data with live probes against the site. - **Auto-fix what is safe** — Where the fix is safe, reversible and inside your entitlement, it applies it through the action catalogue — then re-checks the site and confirms whether the symptom has actually gone. - **Guide what it cannot fix** — For anything outside its guardrails it gives step-by-step instructions grounded in the knowledge base, written for your situation rather than a generic article. - **Escalate with full context** — If a human is still needed, the ticket opens pre-filled with the diagnostics, what was attempted and the outcome — so the agent starts where the assistant stopped, not from scratch. ## What it can put right on its own The auto-fix set is deliberately conservative: reversible operations, inside your existing entitlement, always followed by a re-check. Anything beyond that set — destructive operations, spend, or changes with blast radius — needs your explicit confirmation or falls to a human. That boundary is the reason the assistant is safe to give real access to. - Clear a stale cache and purge the CDN when content is serving out of date. - Restart PHP workers on a site that has stopped responding. - Renew or repair an SSL certificate that has failed to issue or has drifted out of date. - Raise memory within the limits your plan already entitles you to — not a silent upgrade. - Repair database tables after an unclean shutdown or a corrupt index. - Disable a plugin that is throwing a fatal error and taking the site down with it. - Re-run the original check afterwards and tell you plainly whether the issue is resolved or still open. ## Every step in your language The assistant, the diagnostics it reports and the ticket it escalates all run in the customer's language. This is not an English product with a translation bolted on the front. Support runs a translate-both-ways flow: you write in any of our 58 languages, we store your original and machine-translate it to English for the agent, then translate the reply back into your language on send. The assistant works the same way, and because the retrieval index uses multilingual embeddings, the knowledge behind it is available in every language too. Translation sits behind a swappable provider adapter, so no single vendor owns a part of the platform your support experience depends on. ## The same assistant, wherever you work One action catalogue, several front doors. What the assistant can do in the dashboard, your own tools can do too. Every model call — assistant, triage, translation, automations — routes through our AI gateway, which applies prompt and result caching by default and gives us provider fallbacks and rate limiting. Model identifiers are configuration data in a registry, never hardcoded, so we move to a better model without a platform release. - **In the dashboard** — Present throughout the customer dashboard alongside notices and guided tours, so help arrives on the screen where the problem is. - **Through your own AI tool** — Our MCP server exposes the same catalogue to any MCP-capable agent — Claude Code, Cursor, ChatGPT, Claude Desktop — with OAuth 2.1, org and RBAC-scoped, per-tool revocable tokens. - **AI Pack automations** — Recipes that act directly on your sites — auto-blog, image generation, alt text, SEO rewrites, translation — run as durable scheduled workflows using your own provider keys, with per-customer spend caps, optional human approval before publish and action logging. - **On our side of the desk** — Support agents run their own AI agent over a broader catalogue, bounded by their staff RBAC and audit-logged, with sensitive actions requiring confirmation. Your escalated ticket lands with context on both sides. ## Frequently asked questions **Can the assistant break something on my site?** Its auto-fix set is restricted to safe, reversible operations inside your existing entitlement — cache clears, PHP worker restarts, SSL repair, memory within plan limits, table repair, disabling a fatally-erroring plugin — and every fix is followed by a re-check. Anything destructive, anything that costs money and anything outside those guardrails requires your explicit confirmation or goes to a human. That narrows the blast radius substantially, but no automated remediation is risk-free, which is why every action is audit-logged and daily backups sit underneath it. **Can it see or touch another customer's data?** Every query the assistant makes runs under the same Postgres row-level security as the rest of the platform, scoped to your organisation, and the retrieval index it reads from is tenant-scoped in the same way. There is no cross-tenant query path in the platform for it to use, and the public marketing and help-centre search runs on a separate, non-tenant index. **What can it do if I am on a limited role?** Exactly what your role permits, and nothing more. Permissions resolve through the platform's granular module.action catalogue against your membership — so a read-only or billing role's assistant can read and advise where those roles can, but cannot invoke actions those roles are not granted. **How does it know anything about my specific setup?** Two ways. It reads live platform state and observability signals for the site in question — uptime, errors, SSL and DNS, resource limits, malware flags, database and cache health. And it retrieves from an index of knowledge-base articles plus your organisation's own resolved tickets, embedded multilingually and scoped by row-level security. **What happens if it cannot fix the problem?** It gives you step-by-step guidance grounded in the knowledge base, and if a human is still needed it opens a ticket pre-filled with the diagnostics it ran, the fixes it attempted and the results. Support then works in your language: your message is stored in the original and translated to English for the agent, and the reply is translated back on send. **Does it work in my language?** Yes — all 58 languages we support, throughout. The diagnostic run, the explanations, the guided steps and the ticket thread all operate in the customer's language, and the retrieval layer uses multilingual embeddings so the underlying knowledge is reachable regardless of the language the question is asked in. **Can I use my own AI tool instead?** Yes. The assistant is one interface onto the action catalogue; our MCP server is another. Connect Claude Code, Cursor, ChatGPT, Claude Desktop or any MCP-capable client with OAuth 2.1 and org-scoped, per-tool revocable tokens, and drive the same capabilities from wherever you already work. **What does the AI Pack cost to run?** AI Pack automations use your own provider keys, held in our credential store, so you pay your model provider directly for what your recipes consume. Per-customer spend caps, rate limits, action logging and optional human approval before publish bound that usage. Plan inclusions are listed on the pricing page. --- # AI that writes, illustrates and publishes to your sites URL: https://zinndigital.com/features/ai-content Because Zinn Digital® hosts the site, AI acts on it directly. Build a recipe — a trigger and a set of steps — and it runs on a schedule as a durable workflow: write the post, generate the image, publish through the site's WordPress API, update the record, notify you. Bring your own model keys, set a spend cap, and decide whether anything goes live without your approval. ## The difference between drafting and publishing Most AI writing tools hand you text and stop at the clipboard. Ours doesn't stop there, because the site is already on our infrastructure — the same engine that provisions it, caches it and backs it up also runs the automation that fills it. An AI Pack recipe reaches all the way through: it drafts the copy, generates the imagery, pushes the post through the site's WordPress API, writes the result back to your records and sends you a notification. There is no export step, no plugin to authorise, no separate integration to keep alive between your writing tool and your host. That end-to-end reach is what turns AI from an assistant you supervise into a schedule that runs. You define what should be published, how often and against what guardrails — and then it happens, whether or not you are at your desk. ## A recipe is a trigger and a set of steps Recipes are yours to compose. Each one pairs a trigger with an ordered chain of actions, and each run executes as a Temporal workflow — durable, retryable and idempotent, so a failed step resumes rather than duplicating work or leaving a half-published post behind. The example we ship as the canonical pattern is deliberately mundane and deliberately complete: every N days, write a post about X, generate an image, publish it via the site's WordPress API, update the record, notify the owner. Everything else in the library is a variation on that shape. - Trigger on a schedule — every N days, weekly, monthly — so a site keeps publishing without anyone remembering to. - Chain steps in the order you want: write about a topic, generate an accompanying image, publish, update the database, notify. - Runs are logged action by action, so you can see exactly what the AI did on which site and when. - Long-running work never blocks a page or a dashboard — automations execute as background workflows, not in a request. - Because runs are idempotent, a retry after a transient provider error resumes the recipe instead of publishing the same post twice. ## A prebuilt library to start from You do not have to compose a recipe from nothing. Five recipe types ship ready to run — point one at a site, set the cadence, adjust the prompt and guardrails, and it is live. - **Auto-blog** — Keep a site publishing on a fixed cadence. Give it a topic, a schedule and a tone, and it writes and posts through the site's WordPress API without a manual step in the middle. - **Image generation** — Produce featured images and in-post artwork with your own image-model key, generated as part of the same run that writes the post rather than sourced separately afterwards. - **Alt text** — Generate descriptive alt text for images across a site — the accessibility and on-page detail that gets skipped at volume, handled automatically. - **SEO rewrite** — Rewrite existing pages and posts against SEO intent rather than starting from scratch, so pages that already have history get improved instead of replaced. - **Translation** — Translate published content into the locales you serve, wired into the platform's translation lifecycle so a source change marks the translations stale and re-translates them. ## Your keys, your models, your bill The AI Pack runs on bring-your-own keys. You hold the relationship with the model provider and you pay your own inference cost — we run the automation, not a marked-up resale of someone else's tokens. - **BYO provider keys** — Add your Anthropic, Google, OpenAI or image-model keys to the credential store, held in Vault. They are never written into code, config files or logs, and they stay yours. - **A model registry, not a hardcoded list** — Providers, models and their capabilities live in an admin-editable, auto-synced registry. Model IDs are data — when a provider ships a new model you can select it, rather than waiting on us to redeploy. - **Everything through the AI gateway** — All model and embedding calls ride the AI gateway, which gives cost and token analytics, rate limiting and provider fallbacks — so a single provider having a bad day doesn't stop your schedule. - **Caching applied by default** — The gateway caches automatically: stable prompt prefixes aren't re-billed on every call, and deterministic outputs like translations and embeddings are cached by content hash so unchanged content is never re-processed. ## Guardrails, because it publishes on its own Automation that can spend money and put content live in public needs limits designed in from the start. Four of them apply to every recipe. - **Per-customer spend caps** — Set a ceiling on what your automations may spend against your provider keys. Caps bound the whole AI Pack, not one recipe at a time. - **Optional human approval before publish** — Turn on approval and a recipe drafts everything, then waits. Nothing reaches the live site until you have read it and said yes. Leave it off and the schedule runs unattended — the choice is per recipe. - **Action logging** — Every action an automation takes is logged, so you can reconstruct what was written, generated or published on any site, and when. - **Rate limits** — Requests are rate-limited at the gateway, which keeps a runaway loop or an over-eager schedule from burning through your provider quota. ## Written once, published in every language you serve Content created or edited on the platform is translatable across all 58 supported languages, and translation is wired into the content lifecycle rather than treated as a manual afterthought. - Create or edit a piece of content and the platform marks each locale for translation automatically — you don't queue anything by hand. - Change the source and its translations are marked stale, then re-translated, so localised copy doesn't quietly drift out of date behind the English. - Translations are cached by content hash, so unchanged text is never paid for twice. - The same lifecycle covers the surfaces that usually get forgotten — metadata, structured data text, alt text and translated URL slugs on public pages, not just body copy. - Translation status is visible per locale, so you can see what's current, what's stale and what's still pending. ## Grounded in the SEO data we already hold on your sites The AI Content Assistant sits alongside the rest of the SEO toolkit, so what it writes is informed by what we already measure about the site it's writing for. Every plan includes free SEO Basics on each site — indexed status, Trust Flow and homepage Core Web Vitals. Add the paid SEO tools and you get rank tracking, backlink monitoring, competitor intel and a monthly site health audit, with the AI Content Assistant listed among those add-ons at $19–39/mo. The underlying data comes from an established commercial index behind a swappable adapter interface, so no single vendor holds your SEO stack hostage. Because the content assistant and the SEO data live in the same dashboard as the hosting controls, a rewrite recipe can be pointed at the pages the audit actually flagged, rather than at a list you exported from somewhere else and pasted in. Plans and add-ons are priced from the catalog and shown in your own currency at checkout, so the figure you see is the figure you pay. ## One foundation, whichever way you want to drive it AI automations are one surface onto the platform's action catalog. The same catalog is what the in-dashboard AI assistant calls, and what any MCP-capable agent reaches over our MCP server. - Run scheduled recipes from the dashboard when you want content produced on autopilot. - Ask the in-dashboard assistant to do something one-off, using your own model key through the AI Pack. - Connect Claude Code, Cursor, ChatGPT or Claude Desktop over MCP and drive the same actions conversationally from your own tools. - Every route is bounded by the permissions of the identity behind it, and every privileged action is audit-logged. - Build once, expose many ways — a capability we add to the platform becomes available across all three surfaces, with no per-tool integration treadmill. ## Frequently asked questions **Whose AI account does this run on, and who pays for the tokens?** Yours, and you do. The AI Pack is bring-your-own-keys: you add your Anthropic, Google, OpenAI or image-model credentials to the Vault-backed credential store and pay your own inference cost directly to the provider. We run the automation, the scheduling and the publishing. Gateway caching is applied by default — stable prompt prefixes aren't re-billed each call and deterministic outputs like translations are cached by content hash — which is there specifically to keep that bill down. **Will it publish to my live site without me seeing the content first?** Only if you configure it that way. Human approval before publish is an option on every recipe: switch it on and the automation drafts the post and the imagery, then holds until you approve. Switch it off and the schedule runs unattended, which is the point for high-volume networks. Either way, every action the automation takes is logged, so you can review exactly what was published and when. **Can a runaway recipe empty my API credit?** There are three limits working against that, though no automation should be left entirely unwatched. Per-customer spend caps bound what your automations may spend against your keys; rate limits at the gateway stop a loop from firing requests at full speed; and gateway cost and token analytics show you what is actually being consumed, per call. Set a cap that matches your appetite and check the analytics after the first few runs of any new recipe. **Which models can I use, and what happens when a new one launches?** Providers, models and their capabilities live in an admin-editable, auto-synced model registry — model IDs are data, never hardcoded into the product. That means new models can be selected as they become available rather than waiting for a platform release. Calls route through the AI gateway, which also provides provider fallbacks if your primary model is unavailable. **How does a recipe actually reach my WordPress site?** Through the site's WordPress API, because the site is on our infrastructure. A run drafts the content, generates the image, publishes the post via that API, updates the record and notifies you. Each run executes as a Temporal workflow, so it is durable and idempotent — a step that fails on a transient provider error resumes rather than republishing the same post. **Can it write in languages other than English?** Yes. Translation is one of the prebuilt recipe types, and the wider platform translates content into all 58 supported languages as part of the content lifecycle — including metadata, structured-data text, alt text and translated URL slugs on public pages. Edit the source and its translations are marked stale and re-translated, so localised versions don't drift behind the original. **What does the AI Content Assistant cost, and can I try the platform first?** It is listed among the paid SEO add-ons at $19–39/mo, priced from the catalog and shown in your own currency. You can start on the card-free 14-day Footprint-Free trial — no payment details to begin, up to five sites — and every paid plan is backed by a 30-day money-back guarantee, free migrations and no vendor lock-in. --- # Every other host updates your plugins and hopes. We check first. URL: https://zinndigital.com/features/ai-update-guard "Automatic plugin updates" means we will break your site on a schedule and you will find out from a visitor. AI Update Guard checks every plugin and theme you have against the PHP and WordPress versions your site actually runs, grades each one, and offers only the ones that pass. Every 7 days on a subscription, or a single check before you press update. ## The verdict is arithmetic. The AI only explains it. This matters more than it sounds. A language model is never the thing that decides whether we touch your site — three version comparisons are. For every plugin and theme you have installed, we read what its author published: the minimum PHP it needs, the minimum WordPress it needs, and the highest WordPress version they have actually tested it against. Then we compare those three numbers to what your site is really running. That comparison is ordinary arithmetic, it is the same every time, and you can check our working — every reason we give names the two versions it compared. The AI writes the explanation afterwards. If it were unavailable you would still get every verdict, because the verdicts were never its to make. We think that is the right way round for anything that decides whether to change a live website. - **Safe** — The component's published requirements are satisfied by your PHP and WordPress versions, and its author has tested it at or above your version. - **Caution** — It will probably run, but its author has not tested it this high. You are told exactly which two versions disagree. - **Unknown** — We cannot check it — it is not in the public directory, so there is no published compatibility data. It is never quietly graded safe. ## It checks everything installed, not just what has an update waiting The interesting failure is not usually the update you are about to apply. It is the plugin that has been sitting there since your last WordPress upgrade. WordPress's own "updates available" list comes from a cache that can be hours stale, and can be switched off entirely. More importantly, "is your current version safe on your current WordPress" is the same question one step earlier — and it is the one that actually catches things. On a real site we checked, every plugin reported no update waiting, and the directory said one of them had only ever been tested up to WordPress 6.9.7 while the site was running 7.0.4. A tool that looked only at pending updates would have reported "nothing to check". - Every installed plugin and theme, whether or not an update is waiting. - Checked against your site's real PHP version, read from the server. - Checked against your real WordPress version, including what the author tested. - A verdict per component, each naming the two versions it compared. - Anything we cannot check is reported as unknown, with the reason. - The ones that pass are offered for you to apply with a single click. ## How often it runs, and what that costs On a subscription it runs automatically every 7 days, and you can run a check yourself any time in between at no extra cost — which is the one you will use most, right before you press update. A single check can also be bought on its own. - On a subscription — an automatic check every 7 days, plus unlimited checks you run yourself. - One check, on demand, no subscription. Buy it the moment before you update something you are nervous about. - The subscription is exactly 10% below the price of a single check. - It runs more often than AI Webmaster because a compatibility check is a comparison, not a model call — so it costs us far less to run. - Available on every hosting line, including Footprint-Free. ## Against the alternatives What actually happens to a WordPress site when an update lands. | | AI Update Guard | Automatic updates | Checking by hand | | --- | --- | --- | --- | | Checks PHP compatibility first | Yes | No | If you remember | | Checks tested-up-to version | Yes | No | If you remember | | Checks components with no update waiting | Yes | No | Rarely | | Refuses an update that would break | Yes | No | Only if you spot it | | Tells you why, with the versions | Yes | No | You worked it out | | Installs without asking | Never | Always | No | | Time per site per check | None | None | 20–40 minutes | | Cost | On a subscription | Free, until it isn't | Your hourly rate | ## What it does not do The honest limits, because a verdict you cannot check is just a confident tone. - We grade against the compatibility information the author publishes. We do not install the update on a copy of your site and test it — no hosting package on our estate currently permits a staging clone, and we would rather say so than imply a rehearsal that did not happen. - It never installs anything by itself. You approve every update, every time. - A plugin that is not in the public WordPress directory cannot be checked — including our own. Those come back as unknown, never as safe. - A passing verdict means the published requirements line up. It is not a guarantee that a specific plugin has no bug in a specific version. ## What a real check looks like A genuine pre-flight check on one of our own sites, run on 2026-08-19, quoted in full. Every reason names the two versions it compared — you can check our working. - WordPress 7.0.4 on PHP 8.3 — 8 components checked. - [CAUTION] plugin classic-widgets 0.3 — the author has only tested classic-widgets up to WordPress 6.9.7; this site runs 7.0.4. - [UNKNOWN] plugin zinn-cache 1.0.0 — zinn-cache is not in the public WordPress directory, so there is no published compatibility information for us to check it against. (That is our own plugin, and it is still reported as unknown rather than assumed safe.) - [SAFE] plugin litespeed-cache 7.9 — declares WordPress 6.0 and PHP 7.4 as its minimum and is tested to WordPress 7.0.4; this site runs 7.0.4 on PHP 8.3. - [SAFE] theme twentytwentyfive 1.5 — declares WordPress 6.7 and PHP 7.2 as its minimum; this site runs 7.0.4 on PHP 8.3. The third line is our own caching plugin, and it is graded UNKNOWN rather than safe, because it is not in the public directory and there is no published compatibility data for it. An unknown graded as safe is the failure this product exists to prevent, and we do not make an exception for ourselves. ## Frequently asked questions **How often does it run?** On a subscription, automatically every 7 days — and you can run a check yourself any time in between, included. If you buy a single check, it runs once, when you buy it. Most people buy the single check the first time because they are about to update something and want to know. **Does it install the updates for me?** Only if you ask it to, one at a time. Components that pass are offered as a one-click action in your dashboard. Nothing is ever applied automatically, and nothing that failed the check is offered at all. **What happens to a plugin you cannot check?** It is reported as unknown, with the reason — usually that it is not in the public WordPress directory, so there is no published compatibility data. It is never graded safe. Grading an unknown as safe is the exact failure this product exists to prevent. **Do you test the update on a staging copy first?** No, and we would rather be plain about it than let you assume otherwise. We grade against published compatibility requirements rather than rehearsing the update on a copy of your site. Staging clones are available on many of our plans — check yours — and you are welcome to test an update on one; the Update Guard simply does not drive them, and if that changes we will say so. **Is this not what automatic updates already do?** Automatic updates apply the update and find out afterwards. This checks first and refuses the ones that would not work. They are opposite products that sound similar. **Which hosting plans can buy it?** All of them, including Footprint-Free. It is priced per site. **Can I cancel?** Yes, whenever you like, from the same screen you bought it on. --- # Find out whether ChatGPT recommends you — or your competitor URL: https://zinndigital.com/features/ai-visibility Every week we put the questions your customers ask to ChatGPT, Claude, Gemini and Perplexity, and tell you three things: whether they name you, who they name instead, and what is missing from your site that stops them quoting you at all. One price for your whole account — every site you host with us, not one. ## The half you cannot see: what the engines say about you Four answer engines, asked the same questions in the same week, so the answers are comparable rather than anecdotal. - ChatGPT, Claude, Gemini and Perplexity — all four, every run. - Whether you are named at all when someone asks for a business like yours. - Which competitors are named instead of you, and how often each one comes up. - Whether Google's AI Overview cites you. - Every answer kept, so you are reading a trend across weeks rather than one reply on one day. ## The half you can fix: whether they are able to quote you An answer engine can only recommend a site it can read. These are the checks we run on yours — the same eighteen, every time, reported in plain language. - Your robots.txt is readable, and the answer-engine crawlers are allowed in. - Where you stand on AI training crawlers — stated, so it is your decision rather than an accident. - You publish an llms.txt and an llms-full.txt. - You publish a sitemap. - Your pages can be read without JavaScript — several of these crawlers do not run it. - You publish structured data, your business is described in it, and none of it is malformed. - Your profiles are linked back to your site, so the engines know the two are the same entity. - You publish questions and answers in a form they can lift. - Your pages use clear headings and structure, describe themselves, and name their canonical address. - Your site declares its other languages. ## How often it runs, and what that costs One monthly price, billed to your account rather than to each site. Every domain you watch is audited automatically once a week, and you can run one yourself whenever you want. - One price for your whole account, however many sites you host with us. - Every watched domain audited automatically once a week. - Change the rhythm on any domain to weekly, fortnightly or monthly — or pause it — without affecting the others. - Run an audit on demand at any time; on-demand runs draw on your AI credit balance. - One competitor domain included. Add five or twenty-five with a stackable pack — see the price panel on this page. - Your own domains are never counted against the competitor allowance. - Cancel whenever you like — your history and your watch list both stay. - Available on every hosting line we sell, including Footprint-Free. ## Against doing it yourself The same question, asked by hand, on one brand, once a week. | | AI Visibility Monitoring | Asking the chatbots yourself | A rank tracker | | --- | --- | --- | --- | | Four answer engines asked the same week | Included | One at a time, by hand | Not what it measures | | Who is named instead of you | Included | You read and tally it yourself | Ranks pages, not answers | | Whether an AI crawler can read your site | 18 checks | Not something you can eyeball | Not covered | | Google AI Overview citation | Included | Search and squint | Not covered | | History you can compare week to week | Kept for you | Screenshots in a folder | Included | | Runs whether or not you remember | Every week | Only when you think of it | Scheduled | | Priced per account, not per site | Included | — | Usually per domain | ## What it does not do The honest edges of the product, so you are not disappointed by something we never claimed. - It does not change your site. It reads and reports — nothing else. If you want the findings acted on, that is the AI Webmaster's job. - It cannot make an engine recommend you, and neither can anyone else. It tells you whether they do and removes the technical reasons they cannot. - It is not rank tracking. Positions in Google search results are a different product; this one is about being named in an answer. - It does not audit domains you have not asked it to watch. - Answers from these models vary between runs. We handle that by asking repeatedly and keeping the history, not by pretending a single answer is a fact. ## Frequently asked questions **How often does it run?** Every week, automatically, for every domain you are watching. You can change the rhythm on any one of them to weekly, fortnightly or monthly, or pause it — and you can trigger a run yourself at any time in between. **What exactly do you ask them?** The questions your customers ask — the kind that begin “what's the best…” or “who should I use for…” in your category and your market. We put them to ChatGPT, Claude, Gemini and Perplexity, record whether you are named, and record who is named instead of you. **Is it priced per site?** No. It is one monthly price for your whole account, however many sites you host with us — the current figure is in the price panel on this page. Your own domains never count against the competitor allowance either. **What is the competitor allowance?** One external domain — a competitor or a prospect — is included, so you can run the comparison that makes the product worth having. Packs add five more domains or twenty-five, and they stack — both are priced in the panel on this page. If you ever drop below what you are using, nothing is deleted: we simply stop auditing the ones past your allowance, oldest first, and pick them straight back up when there is room. **The answers change every time I ask. Does that make this useless?** It is exactly why the product exists. These models are not deterministic, so one person asking once tells you very little. We ask on a schedule and keep every answer, so what you read is the trend across weeks rather than a single roll of the dice. **Can you make ChatGPT recommend me?** No, and nobody who says they can is telling you the truth. What we can do is tell you whether it does today, show you who it names instead, and remove every technical reason it cannot quote you — which is the half that is actually in your control. **Does it change anything on my site?** Never. This product only reads and reports. If you want the findings acted on, the AI Webmaster proposes the fixes and you approve them with one click. --- # An AI webmaster that reads your server, not your website URL: https://zinndigital.com/features/ai-webmaster Every 30 days our AI reviews your site against facts only the company hosting it can see — how much of your plan you are actually using, what your last malware scan found, and whether your most recent backup could genuinely be restored — writes you a report in plain language, and offers the fixes it found for you to approve with one click. Subscribe for a review every thirty days, or buy a single one whenever you want it. ## A general AI tool guesses from the outside. This one reads the server. Anything can fetch your homepage and tell you to compress your images. The difference here is access: we run the machine your site is on, so the review starts from measurements no external tool can obtain. Most "AI website audit" tools are a page fetch and a checklist. They can see what a visitor sees, which means they can tell you about your title tags and your image sizes and very little else. They cannot tell you whether your last backup would actually restore, because that lives on a server they have no account on. We are that server. The review is assembled from the same site-health snapshot our own support team reads when you open a ticket, so it starts from your real numbers rather than from what can be inferred through the front door. - **Resource use** — Disk, database size and account limits, so you find out you are near a ceiling before something starts failing rather than afterwards. - **Security state** — When the malware scanner last ran, what it found, and whether anything is quarantined or the account is suspended. - **Backups you can actually restore** — When the last backup completed, how large it is, and whether it is restorable — a backup nobody has verified is a hope, not a backup. - **It says when it does not know** — Where a measurement is not available for your site, the report says so in as many words. It never fills a gap with a reassuring sentence — a review that says "all clear" about something nobody measured is worse than no review at all. - **Fixes, not homework** — Up to five specific actions, each prepared and waiting for your approval. The AI proposes; you decide; every decision is audit-logged. ## How often it runs, and what that costs On a subscription it runs automatically every 30 days, and you can trigger an extra review yourself any time in between at no extra cost. Prefer not to subscribe? A single review can be bought on its own. - On a subscription — an automatic review every 30 days, plus unlimited reviews you run yourself. - One review, run on demand, no subscription. - The subscription is exactly 10% below the price of a single review, so it is cheaper from the very first month. - Cancel whenever you like. We keep your report history either way. - Available on every hosting line we sell, including Footprint-Free. ## Against doing it yourself The same review, done by hand, on one site, once a month. | | AI Webmaster | Doing it by hand | A generic AI audit tool | | --- | --- | --- | --- | | Backup verified restorable | Included | Manual restore test | Cannot see it | | Malware scan state | Included | Log in and check | Cannot see it | | Resource-limit warning | Included | Log in and check | Cannot see it | | Written in plain language | Included | You write it | Usually | | One-click fixes | Included | You do the work | No | | Time per site per month | None | 45–90 minutes | A few minutes | | Cost | One monthly price | Your hourly rate | $0–$50/mo | ## What it does not do A product that lets you assume the bigger thing has been sold on a promise it does not keep. So, plainly: - It changes nothing on its own. Every fix it finds waits for you to approve it. - It reports what the malware scanner found — it does not clean an infected site. That is our Malware Cleanup service, done by people. - It only reports what we can measure. Where a signal is missing it says so rather than guessing — a review that says "no errors" about a site nobody measured is worse than no review. - It is not a penetration test, a speed audit or an SEO audit. Those are separate products and we will tell you if one of them is what you need. - It does not yet report your traffic or your server error rate. Those measurements are in active development and not yet available; when they land, this review will include them at no extra cost. ## What a real report looks like This is a genuine review of one of our own sites, run on 2026-08-24, quoted in full rather than rewritten — including the part where it says it could not measure something. - Backups: Healthy. The latest scheduled backup completed on 2026-08-24 at 02:01 UTC (about 58 seconds), status “stored”, and is restorable at ~35.4 MB. - Security: Clean. The last scan on 2026-08-23 at 14:25 UTC found 0 live detections, and the site is not suspended for malware. The Imunify Security plugin was activated on 2026-08-16. - Resources: Very light usage — only 173 MB of disk used, 0 FTP users. - Errors: Not measured — we don’t have error-rate data available for this site, so I can’t tell you whether requests are failing or not. I won’t guess. - Overall: Backups and security look solid, and resource usage is minimal. I don’t see any plugin or theme update waiting, any DNS or crawler policy issue, or any cache anomaly that would justify a fix from our toolkit right now — so I’m not recommending action just to look busy. Read the fourth line. Traffic and server error reporting are in active development and not yet available, and the report says so in as many words instead of filling the gap with a reassuring sentence. A review that says “all clear” about something nobody measured is worse than no review, so ours does not. ## Frequently asked questions **How often does it run?** On a subscription, automatically every 30 days — and you can run an extra review yourself at any point in between, included in the price. If you buy a single review instead, it runs once, when you buy it. **What exactly is in the report?** Disk and database use against your plan limits, the state of your last malware scan including anything quarantined, and your last backup — when it completed, how large it is, and whether it is restorable. Then a plain-language summary of what those numbers mean, and up to five specific fixes you can approve. Traffic and server error reporting are in active development and not yet available; the report says so rather than leaving you to assume. **Can it change my site without asking?** No. It can only propose. Every fix appears in your dashboard with what it would do and why, and nothing happens until you approve it. Every approval is recorded in your activity log, and the reversible ones can be put back with one click. **What if my site has no data yet?** It refuses and you are not charged. A brand-new site with nothing measured yet would produce a report saying everything is fine, which is a comforting lie rather than a review — so we would rather refund it than sell it. **Is this the same as your AI assistant?** No. The assistant answers questions and carries out requests when you ask. AI Webmaster runs on a schedule without being asked and produces a written review. Most customers who use one end up using both. **Which hosting plans can buy it?** All of them, including Footprint-Free. It is priced per site, so you choose which sites are worth reviewing rather than paying across an estate. **Can I cancel?** Yes, whenever you like, from the same screen you bought it on. Your existing reports stay in your account. --- # Backups built to survive the worst day URL: https://zinndigital.com/features/backups Every site you host with Zinn Digital® gets a recovery path: sites on our own fleet get immutable, offsite backups isolated from the running fleet, with regularly tested restores; sites on our resold platform keep that platform's own point-in-time restore points. When something goes wrong — a bad plugin update, a compromise, a mistaken deletion — you roll back in one click, not in a support queue. ## A backup is only as good as its restore Most hosts back up and hope. We test restores, because a backup you have never restored is a guess, not a guarantee. Every site is captured to offsite object storage, and recovery is exercised so that when you need it, it just works. Backups are immutable and isolated from the running fleet — once written they cannot be altered or deleted by a compromised site, which is exactly what ransomware tries to do. If an attacker encrypts your live files, your clean history sits somewhere they can never reach. ## What you get on every site - **Immutable & isolated** — Once a backup is written it cannot be modified or deleted, and it lives apart from your live environment — so a breach on the site cannot reach your recovery history. - **Offsite object storage** — Snapshots ship to Cloudflare R2, stored well away from the worker that runs your site. - **Tested restores** — Restores are exercised regularly, not assumed. Recovery is a routine we practise, so a real recovery is a known quantity, not a first attempt under pressure. - **One-click restore** — Roll a site back to any retained point from the dashboard — files and database together — without raising a ticket or waiting on an engineer. - **30-day retention** — A rolling 30-day window of recovery points, so you can go back past a problem that took days to surface, not just the last overnight snapshot. - **Ransomware-resilient by design** — Immutability plus that isolation means an encryption attack on your live files leaves a clean, untouched copy to restore from. ## Disaster recovery, not just backups - Per-site scope: every site is backed up independently, so restoring one never disturbs its neighbours. - Evidence preserved: if a site is quarantined after a malware or phishing finding, its state is preserved before any cleanup, so nothing is lost to remediation. - Separate control-plane DR: the platform that runs your account is recovered independently of your site data — no single failure takes out both. - Migration safety: bring sites in with free, hands-on migrations, and every deploy and database migration is gated behind a backup and safety checks before it touches production. - No vendor lock-in: your data and your backups are yours — export and leave whenever you choose. ## Frequently asked questions **How often are my sites backed up?** Every site is backed up on a regular schedule to offsite object storage, with a rolling 30-day retention window so you can recover from problems that took time to surface. **What does isolated actually mean here?** Your backups are stored apart from your live environment and are immutable once written. A compromised or ransomware-hit site cannot reach, alter or delete its own backup history — so there is always a clean copy to restore from. **How long does a restore take, and do I need support?** You restore yourself, in one click from the dashboard — files and database together. There is no ticket to raise and no waiting on an engineer for a routine recovery. **Do you actually test that restores work?** Yes. Restores are exercised regularly rather than assumed. A backup that has never been restored is a guess, so we treat tested recovery as the point of backing up at all. **What happens to backups if a site is suspended or terminated?** Suspended sites keep their backups. Terminated sites are deleted only after a grace period, with backup retention respected throughout, so an accidental or disputed closure is recoverable. --- # Connect your own CDN, DNS, Cloudflare and GitHub accounts URL: https://zinndigital.com/features/byo-accounts Already pay for a CDN, DNS provider, Cloudflare or GitHub account? Connect it and we drive it for your sites. Enter the key, we show the privileges required and validate them on entry, then store the credential in Vault. The account joins the pool and is usable across both product lines — under the same origin-record protection as our own accounts, controlled from the dashboard and the MCP. ## Enter a key, we do the rest safely Connecting an account should be quick and safe at the same time. The flow is the same for every provider. - **See the privileges first** — Before you paste anything, we show exactly which permissions the credential needs — least privilege, nothing more — so you grant a scoped key rather than a master one. - **Validated on entry** — The moment you enter a key we call the provider's API to confirm it is live and correctly scoped, and show a green or red check. An invalid or over-scoped key is refused, not quietly stored. - **Straight into Vault** — A validated credential is written to Vault through the same connection seam every account uses. It is never committed to code, printed to a log, or left in an environment file. - **Added to the pool** — The account becomes available for your deploys across both product lines, and can be revoked by you at the provider and removed on our side whenever you like. ## Even a CDN we don't operate You are not limited to the providers we run. There are two tiers, so the long tail is covered without a driver per vendor. - Full integration for popular providers: we drive your account through a provider driver bound to your credentials, so purge, SSL and zone management all work from our dashboard and MCP. - The tier-1 set is Cloudflare, BunnyCDN, CDN77, KeyCDN, Fastly, Gcore, Amazon CloudFront and Akamai. Two of those — Cloudflare and BunnyCDN — are also providers we run accounts on ourselves, so you can use ours instead if you would rather not run your own. - Passthrough for anything else: we delegate DNS to the CNAME or edge you provide, so any CDN works immediately, even one we have never integrated. - The passthrough trade-off is that you manage purge and SSL in your own CDN panel — we handle the DNS delegation, you handle the edge. - Every brought account flows through the same credential-to-Vault seam and the same product-line and IP-protection policy as our own. ## Frequently asked questions **Which accounts can I connect?** The external accounts that power your sites: CDN providers, DNS providers, your Cloudflare account and your GitHub account. Connect one you already pay for and we drive it for your sites, alongside — or instead of — our own accounts. **What happens when I enter a key?** We show you the privileges the credential needs, validate it against the provider's API on entry — confirming it is live and correctly scoped, with a green or red check — and only then store it in Vault. We never save an unvalidated or over-scoped key, and the credential never touches code, a log or an environment file. **Can a connected account be used on both product lines?** Yes. A brought account joins the pool and is usable across the Footprint-Free and Mainstream lines under the same product-line and IP-protection policy as our own accounts — including the rule that origin records can never be changed. **Can I connect a CDN you don't operate?** Yes, two ways. For popular providers we drive your account through a provider driver bound to your credentials, so purge, SSL and zone management work from our dashboard and MCP — Cloudflare, BunnyCDN, CDN77, KeyCDN, Fastly, Gcore, Amazon CloudFront and Akamai. For anything else, passthrough points your domain at the edge you give us, so any CDN works immediately even if we have never integrated it — we just cannot purge or manage its certificate from our side. **Can I revoke access later?** Yes. You stay in control of the account and can revoke our access from the provider at any time, and remove the stored connection on our side. Every action taken through a connected account is audit-logged. --- # Multi-layer caching that keeps sites fast at scale URL: https://zinndigital.com/features/caching Most visits to a Zinn Digital® site never touch PHP or MySQL. A LiteSpeed full-page cache, a per-site Redis object cache and the CDN edge work together, coordinated by smart auto-purge, so pages stay fast and origins stay quiet — across 700,000+ hosted sites worldwide. ## Three cache layers, one coordinated system Speed comes from serving the right thing from the fastest place. We stack three caches so a request is answered as early as possible — at the edge, at the web server, or from memory — and never has to rebuild a page it already built. - **LSCache full-page cache** — On LiteSpeed hosts, cacheable front-end responses are stamped with LiteSpeed cache-control and tag headers, so the web server serves complete pages without invoking PHP or querying MySQL. That is the biggest single win for time-to-first-byte on WordPress. - **Per-site Redis object cache** — A one-click toggle installs a self-contained Redis object-cache drop-in, offloading repeated database reads. If Redis is ever unreachable the drop-in falls back to a per-request in-memory cache, so the site keeps working. - **CDN and edge** — Static assets are served from the CDN close to visitors, and the CDN cache can be purged from the site's CDN tab whenever you need it. ## Smart auto-purge keeps content fresh A cache is only useful if it clears the right pages at the right moment. Ours watches for real changes and purges surgically using LiteSpeed cache tags — not a blunt flush-everything on every edit. - When a post or page is saved, trashed or deleted, only the affected pages and the listings they appear on are purged. - Comments, edited taxonomy terms, theme switches, plugin activation and core/plugin/theme updates all trigger targeted purges. - The page cache is purged at the web server, and the CDN cache from the site's CDN tab. - A REST purge endpoint lets the panel clear everything, specific URLs, or specific tags — authenticated by an admin session or an HMAC-SHA256 signature. ## Safe by default — dynamic pages are never cached Aggressive caching is only safe when the things that must stay live never get cached. Zinn® Cache ships with sensible WordPress and WooCommerce / Easy Digital Downloads defaults: cart, checkout, my-account, REST and AJAX, preview and search are excluded, and any logged-in or session-cookie request is served fresh. That means a shopper never sees someone else's cart and a logged-in editor never sees a stale draft. You can add extra path, query-key and cookie-prefix rules per site when a plugin needs them, without touching the safe defaults. Caching is a per-blueprint capability, so static, PHP and Node sites each get the caching that suits them, and the plugin degrades gracefully wherever a full-page cache layer is absent. ## Frequently asked questions **Do I have to configure any of this?** No. The Zinn® Cache plugin ships in the deploy footprint and the full-page cache, object cache, auto-purge and safe exclusions are wired up on Zinn-hosted sites automatically. You can fine-tune everything under Settings → Zinn® Cache, or from the dashboard, if you want to. **Will caching break my WooCommerce store?** No. Cart, checkout, my-account, and any logged-in or session-cookie request are never cached by default, so dynamic and per-customer pages always stay live. The full-page cache only serves pages that are the same for every visitor. **What happens if Redis is unavailable?** The object cache is optional and fails safe. If the phpredis extension is missing the toggle is disabled with a notice; if Redis becomes unreachable at runtime, the drop-in serves from a per-request in-memory cache so the site never breaks. **Does this require LiteSpeed?** Full-page caching uses a LiteSpeed web server, or the third-party LiteSpeed Cache plugin if it is already active. On other servers no cache headers are emitted, but the object cache and exclusions still work. **How do the CDN and server caches stay in sync?** At the web server, automatically. When content changes, targeted tag-based purges clear only the affected pages from the server's page cache. The CDN cache is cleared from the site's CDN tab. --- # A free global CDN tier, included with your hosting — not sold back to you URL: https://zinndigital.com/features/cdn Serving from an edge close to your visitors costs nothing extra on most of our hosting plans: the free CDN tier is part of what the plan includes, and you switch it on per site from that site's CDN tab. On the whole Footprint-Free (PBN) line there is nothing to switch — the CDN is native, always on, and spread across a five-network pool so no two of your domains share a fingerprint. Where a plan does not include the free tier you can add the Premium CDN for that site, connect a CDN account you already pay for, or point the domain at an edge you run yourself. ## Five ways a site can be served, and you pick per site These are the exact choices on a site's CDN tab. Nothing here is a package you buy once for the whole account — a flagship site can sit on a paid network while everything else stays on the free tier, and you can change your mind without rebuilding anything. - **Off** — Your site is served from its origin only. This is where a new site starts on every line except Footprint-Free, so nothing changes at your edge until you ask for it — and it is always available, because a customer must be able to undo. - **Free** — A global edge cache at no extra cost, on the plans that include it. Static assets and cacheable pages are served from the node nearest your visitor instead of from your server. One click, no per-gigabyte charge, no account to open. - **Premium** — A paid monthly tier per site, for the sites where delivery is the product: more cache capacity and higher limits. Above it, a metered tier on Amazon CloudFront charges per gigabyte against prepaid credit, for people who want that particular network. - **Your own account** — Connect an account you already pay for and we drive it — build the zone, point the domain, purge it, set TLS and report its state beside every other site. Your provider bills you; we charge nothing for the edge. - **Point at your own edge** — You run the CDN yourself and we only point your domain at the hostname you give us. We hold no credential, so purging and certificates stay in your panel — which is exactly the trade, and it means a network we have never integrated still works. ## The tier ladder, per product line The Footprint-Free line and everything else buy a CDN for opposite reasons — one is buying a hidden, rotating edge, the other is buying speed — so the same network is included on one and an upgrade on the other. Here is what each line actually gets. | | Footprint-Free (PBN) Hosting | Every other hosting line | | --- | --- | --- | | CDN on a brand-new site | Always on | Off until you switch it on | | Free tier at no extra cost | Included — the CDN is the product | Included where the plan carries it | | Who picks the tier | We do — it is footprint machinery | You do, per site | | Who picks the network | Yes | Yes | | Which of our accounts it lands on | Never disclosed, by design | Named on the tab | | Monthly traffic plans | No | 500 GB · 900 GB · 1.7 TB · 2.9 TB | | Metered per-gigabyte network | Yes | Yes | | Bring your own CDN account | Yes | Yes | | Point at an edge you run yourself | Yes | Yes | | Origin IP hidden behind the edge | Always, and enforced | While the CDN is on | Read off the running platform on 12 September 2026. Whether a given plan carries the free tier is an entitlement on that plan, so your plan's own page is the authority for your plan — and the site's CDN tab is the authority for a site you already have. ## A pool, not an account — which is the whole point The Footprint-Free line does not put every site behind one CDN account. Sites are spread across a pool, so the network as a whole has no single shared edge fingerprint and no two of your domains can be tied to each other through the edge they happen to share. You still choose the network. What stays hidden is which of our accounts inside it your site landed on — and that is the one fact the line exists to keep, which is why origin records there can never be changed to expose the server behind them. - Spread across a five-network pool, rebalanced at every deploy - The network is your choice; the account is never disclosed - Origin IPs stay behind the edge, enforced rather than configured - Your own accounts widen the pool further ## What you actually control, from the site's CDN tab A CDN you cannot configure is a black box you have to ring somebody about. Every one of these is a control on the site's own tab, and every one of them has a page explaining how it works. - **Cache levels and cache rules** — Cache static files only, ignore query strings, or cache each query string separately, with per-path cache rules where your network supports them — the tab says so plainly when it does not. Changes take effect worldwide immediately. - **Firewall and DDoS protection at the edge** — Attack traffic is absorbed at the edge instead of on your server, and the settings are yours per site rather than a ticket: how traffic to your origin is encrypted, whether an archived copy is served if your server goes down, a cache bypass for the hours you are editing, and firewall rules where your network supports them. - **CDN and DNS account pools** — Multi-account pools, ours and yours. Balance is recomputed from live account state at every deploy — counting deleted sites — so distribution stays even and never clusters. - **Bring your own accounts** — Connect the CDN, DNS, registrar and cloud accounts you already pay for. Each token is checked against the provider's own API before it is stored, and it is stored in Vault — never in a file, a log or a command line. - **Every network and DNS provider we drive** — The full list, with what each one costs you and which DNS providers it pairs with — so you can check the combination you want is one we can actually provision before you commit to it. - **DNS that moves with the edge** — Records, apex handling and the certificate are re-pointed as part of the same change, in order, with the old zone removed only once the new one is live. - **One address, not two** — Pick whether visitors are served on the apex or on www; the other permanently redirects to it, so search engines index one address instead of splitting authority between two. - **Isolation behind the edge** — The edge hides the origin; per-site isolation means that even if somebody found it, one site's compromise is not another site's problem. The two are different guarantees and you get both. ## Move a site's edge without holding your breath Moving between our network, one of your own connected accounts and an edge you run yourself is one card and one button. We build the new zone first, point the domain at it, and remove the old one only once the change is live — nothing is torn down on the strength of a request having been accepted. It works in every direction, as often as you like. A site that outgrows the free tier moves up; a site whose traffic went quiet moves back; a site whose owner signed their own contract with a network moves onto it. - New zone built and live before the old one is removed - Our network, your account, or your own edge — any direction - The certificate and DNS move as part of the same change ## Switch it on in four steps On the Footprint-Free line you can skip to step four — the CDN is already on. 1. **Open the site's CDN tab** — Every site in your dashboard has one. It shows the tier it is on now, the networks available to it, and what each of them costs. 2. **Pick a tier and a network** — Free, a paid tier, an account of your own, or your own edge. A CDN and DNS pairing we cannot provision is refused when you make it, with a message naming which of the two to change — never a site that provisions and then never resolves. 3. **We build the zone and point the domain** — The zone, the DNS records and the certificate are set up in order, and the old edge is removed only once the new one is serving. 4. **Tune the cache and forget about it** — Set the cache level, add page and firewall rules if you need them, and let WordPress purge itself on every content change. ## What a gigabyte costs depends on where it lands A traffic plan's allowance is denominated in base-region-equivalent gigabytes, and the weighting is on the site's CDN tab beside the plans — so you can see what your own audience costs rather than finding out on a bill. It is the same weighting we are charged. - **Europe and North America** — One gigabyte of your allowance per gigabyte served. This is the base region everything else is measured against. - **Asia and Oceania** — Three gigabytes of your allowance per gigabyte served. - **South America** — Four and a half gigabytes of your allowance per gigabyte served. - **Middle East and Africa** — Six gigabytes of your allowance per gigabyte served. ## Frequently asked questions **Is the CDN really free?** The free tier costs nothing extra — there is no per-gigabyte charge and no separate account to open. It is an entitlement your plan either includes or does not, so your plan's own page is the answer for your plan: most of our hosting plans carry it, and a few do not. On the whole Footprint-Free (PBN) line the question does not arise, because the CDN is native to the product and always on. Where a plan does not include the free tier you can still add the Premium CDN for that site, connect a CDN account you already pay for, or point the domain at an edge you run yourself. **What do the paid tiers add?** More cache capacity, and a choice of network. The Premium tier is a monthly per-site add-on; above it sits a metered tier served from Amazon CloudFront and charged per gigabyte against prepaid credit, which people buy for the distinct network rather than for raw speed. Alongside those are four monthly traffic plans with a fixed included allowance — 500 GB, 900 GB, 1.7 TB and 2.9 TB. You pick per site, from that site's CDN tab, and the current price of each is shown there. **Can I bring my own CDN account?** Yes. Connect a Cloudflare, Bunny CDN, CDN77, KeyCDN, Fastly, Gcore, Amazon CloudFront or Akamai account under Connections and we drive it for you — the token is validated against the provider's own API before it is stored, and it is kept in Vault, and the account then appears as a destination any of your sites can be moved onto. For any other CDN, passthrough points your domain at the edge hostname you give us, so a network we have never integrated still works. **How is the CDN different on Footprint-Free hosting?** The tier is ours to set and the account is never disclosed — that is the product, not a limitation. Sites are spread across a pool of accounts so no two of your domains can be tied to each other through the edge they share, and origin IPs stay behind it. What you do choose is the network itself: picking the CDN for a site is yours on every line, Footprint-Free included. What you cannot see is which of our accounts inside that network the site landed on, because that is the fact the whole line exists to hide. **Do I have to manage cache purging myself?** No. Purge is a button on the site's CDN tab for every tier and every account we drive. On WordPress, the Zinn® Cache plugin also purges the server's page cache by itself whenever content changes — a post edit clears that post and the listings it appears on, a comment clears its parent, a theme switch or a site-wide option clears everything. Under passthrough we hold no credential, so purging and certificates stay in your own provider's panel. **Does a new site get the CDN automatically?** On the Footprint-Free line, yes — the CDN is part of provisioning and the site arrives behind it. On every other line a new site starts with the CDN off and nothing at your edge changes until you choose a tier. That is deliberate: turning a CDN on in front of a site somebody is mid-migration with is not a favour, and a cache you did not ask for is the hardest kind to debug. **Why does traffic from some regions count more?** Because it costs more to serve. A traffic plan's allowance is denominated in base-region-equivalent gigabytes: a gigabyte served in Europe or North America spends one, Asia and Oceania spend three, South America four and a half, and the Middle East and Africa six. The weighting is shown on the site's CDN tab beside the plans, so you can see what your own audience actually costs rather than discovering it on a bill. **What happens when I move a site to a different edge?** We build the new zone first, point your domain at it, and only remove the old one once the change is live. Nothing is torn down on the strength of a request having been accepted. You can move between our network, one of your own connected accounts and an edge you run yourself, in any direction, from the same card. **What can I actually change at the edge?** Cache level — cache static files only, ignore query strings, or cache each query string separately. Page rules and firewall rules. Which address visitors are served on, apex or www, with the other permanently redirecting to it so search engines index one address instead of splitting between two. Always-use-HTTPS, and the certificate that covers both names. Plus a purge button, live edge traffic, and a spend budget for the metered tier. **Do I have to move my DNS to use the CDN?** Not necessarily. Some networks answer DNS and serve the CDN from the same zone, so one account can do both and we will offer that when it applies. Others need a DNS provider alongside them. A pairing we cannot provision is refused at the moment you choose it, with a message naming which of the two to change — we would rather say no than hand you a site that never resolves. You can also leave DNS exactly where it is and point a single record at the edge. **If I bring my own account, what do you charge?** Nothing extra for the CDN itself — it is your account and your provider bills you directly. We hold the credential, build and manage the zone, purge it, set TLS and report its state alongside every other site you run with us. The difference between that and passthrough is whether we hold a credential at all: under passthrough we only point DNS, so we cannot purge your cache or manage your certificate. **Does the CDN hide my origin server?** Yes, while it is on: visitors resolve the edge, not the machine. On the Footprint-Free line that is enforced rather than incidental — origin records can never be changed to expose the server, because a single leaked origin IP would tie every site behind it together. --- # CDN account pool URL: https://zinndigital.com/features/cdn-pool Pool your own Cloudflare and CDN accounts alongside ours, choose which account each site deploys to, let footprint-aware balancing spread sites evenly, and purge cache across every account from one control. ## One pool, your accounts and ours Add your own Cloudflare or CDN accounts, use the accounts we provide, or mix both. Every account sits in one pool you control, with keys held in Vault and never exposed. - **Bring your own accounts** — Connect your existing Cloudflare and CDN accounts. Credentials are stored in Vault, so keys stay secret and never appear in code or logs. - **Use our accounts too** — Draw on the accounts Zinn Digital® provides alongside yours. There is no lock-in either way, so you can lean on ours, yours, or both. - **Per-site account selection** — Choose exactly which account each site deploys to. Every CDN account tracks its live site count, so you always see where sites sit. - **Eight providers, one driver** — The CDN driver speaks to eight providers behind a single interface, handling cache purge, HTTPS, certificates and DNS record sync uniformly. ## Footprint-aware balancing For Footprint-Free hosting, spreading sites thin across many accounts is the moat. The pool does the maths for you. With many accounts in the pool, balancing rotates and spreads a user's sites across them to minimise footprint, so no single account carries a tell-tale cluster of related sites. Balance is recomputed from live account state at deploy time, and deleted sites are counted, so the spread stays even rather than drifting as sites come and go. For mainstream hosting the same pool serves whichever CDN tier you switch on for a site, or your own account, with no rotation needed. ## Global cross-account cache purge - Purge cache across every account in the pool from a single control in the panel, no account-by-account clicking. - The same purge control coordinates with the server-side cache layer, so CDN and origin caches clear together. - Purge hooks fire back to the panel on content change, keeping cached pages fresh as sites are edited. - Free migrations bring existing sites and their accounts into the pool without downtime. ## Why a pool rather than one account A CDN account is a fingerprint. Put a hundred sites behind one account and you have told anyone who looks that those hundred sites are run by one person — the nameservers match, the certificate issuance matches, the response headers match, and none of that is visible to you until somebody else notices it. Pooling is the answer, and it only works if the pool is big enough and varied enough. That is why your own accounts are welcome in it and why there is no charge for bringing them: a pool made only of our accounts is a smaller, more uniform pool, which is worse for you and worse for everybody else in it. The balancing is not a setting you tune. The platform places each site to spread the signals that actually correlate — account, nameserver pair, certificate authority and issuance timing — and rotates when a pattern starts to form. ## Bring your own accounts, keep your own keys Your Cloudflare account stays yours. You add it, we place sites in it, and you can take it back at any time — the sites move rather than break, because the platform holds the zone configuration and can rebuild it anywhere. That is the same principle as everything else here: no external dependency we cannot swap, and none you cannot take with you. - Your accounts and ours, balanced as one pool - No charge for bringing your own - Take an account back and the sites move, not break ## Frequently asked questions **Can I use my own Cloudflare accounts?** Yes. Connect any number of your own Cloudflare or CDN accounts, use the accounts we provide, or run both together in one pool. Credentials are held in Vault and never exposed in code or logs. **How does footprint-aware balancing work?** With several accounts in the pool, sites are rotated and spread across them to minimise footprint. The balance is recomputed from live account state at deploy time, counting deleted sites, so the spread stays even instead of drifting over time. **Can I choose which account a specific site uses?** Yes. Per-site account selection lets you pick exactly which account each site deploys to, and every account shows its live site count so you can see the distribution at a glance. **How does cache purging work across many accounts?** A single control in the panel purges cache across every account in the pool at once. It coordinates with the server-side cache layer as well, so CDN and origin caches clear together rather than separately. **Is there any vendor lock-in?** No. The pool works with your accounts and ours behind a swappable driver covering eight providers, and free migrations move sites in. You can leave with your own accounts intact whenever you choose. --- # Rename or re-point a domain — everything cascades URL: https://zinndigital.com/features/change-domain Changing a live site's domain is a first-class operation, not a support ticket. Rename or re-point and the change cascades everywhere it needs to: the Site record, a WordPress site-URL search-and-replace, DNS, the CDN zone, a re-issued certificate and the origin mapping — orchestrated in order, from the dashboard and the MCP, with a clear nameserver-repoint warning on Cloudflare. ## One change, every reference updated A domain name is threaded through a dozen places. Miss one and the site breaks or leaks the old name. So we treat the rename as a single cascading operation and update all of them. - **The Site record** — The canonical domain on the Site is updated first, so the platform and every tool that reads it — dashboard, API, MCP — agree on the new name from the moment the change begins. - **WordPress site-URL search-replace** — For WordPress sites we run a database-wide search-and-replace of the old URL for the new, across posts, options and serialized settings, so internal links, images and canonicals follow the domain instead of pointing back at the old one. - **DNS and CDN** — DNS records are repointed and the CDN zone is moved or updated for the new name, so traffic and caching follow the domain rather than being left behind on the old zone. - **Certificate and origin** — A TLS certificate is re-issued for the new domain and the origin mapping is updated, so the site is served securely on its new name end to end. ## The Cloudflare nameserver warning One case deserves a plain warning rather than a silent surprise. When a site is on Cloudflare, the CDN and the DNS are the same thing — the orange cloud is the zone — so a new domain usually has to have its nameservers repointed to Cloudflare before the zone can be authoritative for it. We flag that during the change so the nameserver repoint is an expected, understood step, and we configure the Cloudflare zone for you once the nameservers are in place. On every other CDN, DNS is a free choice from the provider pool, so a domain change does not force a nameserver move — the warning is Cloudflare-specific, and we only raise it when it applies. ## Frequently asked questions **What actually changes when I rename a domain?** Everything that references the old name. We update the Site record, run a WordPress site-URL search-and-replace so links and stored URLs inside the database follow, repoint DNS, move or update the CDN zone, re-issue the TLS certificate for the new name, and update the origin mapping. It is one first-class operation, not a checklist you run by hand. **Will my internal links and images break?** No. For WordPress sites the site-URL search-and-replace rewrites the stored URLs across the database — posts, options, serialized settings — so internal links, image sources and canonical URLs point at the new domain instead of leaving a trail of the old one. **Is there any downtime?** The change is orchestrated so the pieces move in the right order — DNS, CDN, certificate and origin — to keep the switch clean. DNS and certificate propagation are inherent to any domain change; we sequence around them rather than leaving you to time it. **What's the warning about Cloudflare?** If the site is on Cloudflare, the new domain generally needs its nameservers repointed to Cloudflare for the zone to be authoritative — the orange cloud is the zone. We flag that clearly during the change so a nameserver repoint is an expected step, not a surprise, and we configure the zone for you once it is in place. **Can I do this by API or MCP?** Yes. Changing a domain is a platform action available on the dashboard, the API and the MCP, so you can rename or re-point a site — or a batch of them — from your AI tool, with the whole cascade handled for you. --- # Block the backlink crawlers — never the search engines URL: https://zinndigital.com/features/crawler-blocking A first-class, per-site Footprint-Free control: block the SEO and backlink crawlers — Ahrefs, Majestic, Semrush, Moz, Screaming Frog and the rest — while the search engines keep full access. On by default for the PBN line, enforced at the server by User-Agent, driven from the dashboard and the MCP. It is the footprint game: hide the link from competitors' tools, stay indexable in the SERPs. ## The footprint game, in one control The value of a private network is the link nobody else can see. The moment a competitor's backlink tool can crawl your PBN site and follow its outbound link to your money site, the network is exposed — and the advantage is gone. So the job is precise: shut out the backlink-analysis crawlers that build those link graphs — Ahrefs, Majestic, Semrush, Moz, Screaming Frog, BLEXBot and their kin — while leaving the search engines completely untouched, because a site that Google cannot crawl cannot rank. Block the spies, keep the indexers. This is a per-site toggle on the Footprint-Free line, on by default. Tick or untick each crawler, or a whole group, save, and the engine writes or removes the rules for you. ## Enforced at the server, not just requested robots.txt is advisory, and the aggressive crawlers ignore it — Majestic has been observed doing exactly that. So the real block lives at the server, with robots.txt as a courtesy layer on top. - **User-Agent deny at the server** — The enforcement is a .htaccess, LiteSpeed or nginx User-Agent deny, written by the hosting worker and the Zinn® plugin from your saved toggles. This is the rule that actually stops a crawler, because it does not depend on the crawler's goodwill. - **robots.txt for the compliant ones** — We also write a robots.txt Disallow for the crawlers that respect it — belt and braces, so the well-behaved tools are turned away politely and the misbehaving ones are turned away firmly. - **IP and ASN deny for the worst** — Some crawlers hide behind fake user-agents. For the worst offenders we can add known-IP or ASN denies, so a crawler pretending to be a browser still does not get in. - **Search engines always allowed** — Googlebot, Bingbot and the other indexers are never on the block list. Blocking is aimed exclusively at the backlink tools, so indexation and rankings are untouched. ## You keep your Trust Flow A common worry is that blocking Majestic will make a domain's Trust Flow disappear. It will not. Trust Flow and Citation Flow are computed from a domain's inbound backlink graph — the links pointing to it, which Majestic finds by crawling other sites — not by crawling the domain itself. Blocking MajesticBot on your PBN site stops Majestic from seeing that site's outbound links, which is precisely the footprint you want hidden. It does not remove the domain's Trust Flow or Citation Flow from Majestic's API, so our own SEO-data checks keep reading those metrics normally. The same holds for Ahrefs DR and Moz DA — all inbound-link measures. ## Frequently asked questions **Which crawlers get blocked?** The SEO and backlink crawlers — Ahrefs, Majestic, Semrush, Moz, Screaming Frog, BLEXBot and the like. The search engines are never touched: Googlebot, Bingbot and the other indexers keep full access, because staying indexable is the entire point. You can tick and untick each crawler, or a group, and save. **Will this hurt my rankings?** No. Only the backlink-analysis crawlers are blocked; the search engines that rank you are left completely alone. The site stays indexable and rankable — you are hiding your link graph from competitors' tools, not from Google. **How is the block actually enforced?** At the server, by User-Agent — a .htaccess, LiteSpeed or nginx deny — because robots.txt is only advisory and the aggressive crawlers are known to ignore it. We write a robots.txt Disallow for the compliant ones as well, and can add known-IP or ASN denies for the worst offenders that crawl under fake user-agents. The engine writes and removes the rules automatically from your saved toggles. **If I block Majestic, do I lose my Trust Flow?** No. Trust Flow and Citation Flow are computed from a domain's inbound backlink graph — links to it, found by Majestic crawling other sites — not by crawling the domain itself. Blocking MajesticBot on the site stops Majestic seeing its outbound links, which is the footprint you want hidden, but leaves the domain's metrics in Majestic's API intact. The same logic applies to Ahrefs DR and Moz DA. **Is this on by default?** On the Footprint-Free line, yes — crawler blocking is on by default, because hiding the PBN-to-money-site link is the core of the footprint game. You keep full control to adjust which crawlers are blocked per site. --- # Database maintenance that runs itself, the moment it's needed URL: https://zinndigital.com/features/database-maintenance Every WordPress database grows heavier with age. Zinn Digital® treats that as an engineering problem, not a support ticket: clean, optimise and repair run as an automated workflow you buy in one click — and the platform offers it to you at the moment it sees a database bloating. Availability: per-site database throttling is in active development and not yet available. Everything else described here is live today. ## Why databases quietly become the bottleneck A WordPress site's files stay roughly the size you built them. Its database does not. Tables accumulate, indexes drift out of shape, storage engines leave space allocated that nothing is using any more, and occasionally a table ends up in a state that needs repairing rather than tuning. None of this announces itself. The site simply gets slower, queries take longer, and the first anyone notices is a page that used to feel instant and now doesn't. On a single site that is an annoyance. Across a portfolio or a network of hundreds of sites it is a compounding tax — every one of them a little heavier than it needs to be, every one of them asking more of the database server than it should. Zinn Digital® handles this the same way we handle the rest of the platform: as an automated, repeatable operation. Database maintenance is a first-party service you buy from the dashboard, and buying it runs the optimisation job immediately. There is no queue to join and no engineer to wait for. ## What a maintenance run does Cleaning, optimising, repairing and reporting on the site's MariaDB database, run as one job. - **Clean** — Clear out what the database is carrying but no longer needs, so the working set shrinks back towards the data your site actually serves. - **Optimise** — Reclaim allocated-but-unused table space and put indexes and statistics back into the shape the query planner expects, so reads stop doing more work than they need to. - **Repair** — Detect and repair tables that have ended up in a bad state — the failure mode that turns a slow site into a broken one if it is left alone. - **Report back** — The purchase charges through billing or your wallet, fulfils, notifies you and marks itself complete. If something goes wrong, refunds and disputes run through the same billing path as everything else you buy from us. ## Automated fulfilment, not a support queue First-party services on this platform come in two shapes. Some are staff-fulfilled: buying them creates a task in our admin queue, routed to the right department, tracked and updated. Database maintenance is not one of those. It is automated — the purchase triggers a Temporal workflow that runs the optimisation job directly against your site. Instant, zero-touch. That matters more than it sounds. Temporal workflows are durable, retryable and idempotent by design, which is the standard every long-running operation on this platform is held to. If a step fails partway, the workflow retries from where it was rather than half-finishing and leaving your database in an ambiguous state. If a retry re-runs an operation that already succeeded, that is safe by construction. It also means the service does not degrade under load. Ten customers buying database maintenance at once do not queue behind each other waiting for the same engineer — they are ten workflow executions, and the platform is built to scale them horizontally. - Purchase triggers the job immediately — charge, fulfil, notify, complete. - Runs as a durable Temporal workflow: retryable and idempotent, not a fire-and-forget script. - Every run is visible in workflow history, so there is a record of what ran and when. - Refunds and disputes handled through the same billing path as plans and add-ons. ## Offered at the right moment, not buried in a menu The platform already watches your sites. It uses what it sees to offer the right service at the right time. There is a dedicated Extras section in the dashboard where you can browse and buy first-party services whenever you like. But the more useful path is the one that finds you: contextual upsells. Database maintenance is surfaced against a bloated database, speed optimisation against a slow site failing Core Web Vitals, malware cleanup against a flagged site, migration at signup. Those prompts are driven by real observability signals — the same per-site metrics and resource telemetry the platform collects to operate the fleet, not a generic monthly nag. And the AI assistant can both suggest the service and initiate it for you, so the gap between noticing a problem and fixing it is a conversation rather than a project. ## The database tools you already have Maintenance is the automated layer on top. Underneath, every site ships with full database control. - **MariaDB per site** — Each site gets its own database, with support for multiple databases and multiple database users where a project needs them. - **phpMyAdmin and Adminer, embedded** — Both are built into the dashboard and single-sign-on'd — no separate credentials to manage, no separate login to protect. - **Remote access toggle** — Turn external database access on when a tool or a developer needs it, and off again when they don't. Closed by default is the sane state. - **Per-site Redis object cache** — Offload repeated reads to Redis so the database is answering fewer queries in the first place. Prevention alongside cure. ## MySQL Governor: your queries, your problem — and only yours The other half of database performance on shared infrastructure is the part you don't control: what everyone else's sites are doing to the same server. Our worker fleet runs MariaDB with CloudLinux MySQL Governor, which throttles database usage per site. One site running heavy queries is constrained inside its own limits rather than slowing the server for its neighbours. That sits alongside the rest of the isolation stack — LVE caps on CPU, RAM, IO, IOPS and processes, and CageFS giving each tenant an isolated filesystem view. The design intent throughout is the same: a problem on one site stays on that site. So when your database is slow, the answer is something you can actually act on. It is your database, and database maintenance is the button that fixes it. ## Drive it from your AI tool Database operations are part of the MCP tool catalogue, so any MCP-capable agent can run them on your behalf. Our hosted MCP server exposes the platform to Claude Code, Cursor, ChatGPT, Claude Desktop and any other MCP-capable agent — one connection rather than a separate integration per tool. The database tools in that catalogue include guarded query, optimise, and backup and restore. Buying Extras is exposed too, behind an explicit confirmation step. Everything the agent can do is bounded by the identity it connected as. Tokens are issued through OAuth 2.1, scoped to your organisation and your RBAC permissions, per-tool and revocable. Destructive actions require explicit confirmation, spend caps apply to AI-triggered paid actions, and every MCP action is written to the audit log with identity, tool, arguments and result. In practice: your agent notices the database is heavy, asks whether it should run maintenance, you confirm, and the workflow runs. The AI is a driver, not an unsupervised operator. ## Bought like a plan, priced like a service First-party services are data on this platform, not hardcoded features. - Our staff add, edit, price and enable services in the admin console the same way plans are managed — no code change to launch or adjust one. - Prices are set per currency, as one-off or recurring, so you buy in the currency you already pay in. - Services carry product-line eligibility, so what is offered matches what you actually run. - Charging goes through billing or your wallet balance, alongside your subscription — one account, one set of invoices. - Purchases are ordinary commerce: notified on completion, refundable, disputable. ## Frequently asked questions **How do I know my database needs maintenance?** In most cases you won't have to work it out yourself. The platform monitors per-site resource usage and surfaces database maintenance as a contextual offer when it sees a database bloating, and the AI assistant can flag it and initiate the job for you. You can also browse and buy it any time from the Extras section of the dashboard, and inspect the database yourself through the embedded phpMyAdmin or Adminer. **Is my data at risk during a maintenance run?** We minimise the risk rather than pretend it away. The job runs as a Temporal workflow — durable, retryable and idempotent — so a failed step retries rather than leaving work half-applied, and a repeated operation is safe by design. Every run is recorded in workflow history. On Footprint-Free plans, daily backups are retained for 30 days with one-click restore, so there is always a recent restore point to fall back on if you want one. Take a backup before any significant database change is good practice regardless of who is running it. **Does this replace the database tools in my panel?** It complements them. Every site keeps its own MariaDB database with embedded, single-sign-on'd phpMyAdmin and Adminer, support for multiple databases and users, and a remote access toggle. Database maintenance is the automated version of the routine work — clean, optimise, repair — for when you would rather buy the outcome than run it by hand. **How is this different from an ordinary support ticket?** Services on this platform are fulfilled one of two ways. Staff-fulfilled services create a task in our admin queue, routed to the right department with status tracking and customer updates. Database maintenance is automated: buying it triggers the workflow directly, with no human step in between. That is the whole point of building it as a workflow rather than a process. **Can my AI agent run this for me?** Yes. Database optimise, guarded query, and backup and restore are all in the MCP tool catalogue, and buying Extras is exposed with a confirmation step. Your agent connects over OAuth 2.1 with a token scoped to your organisation and your RBAC permissions — per-tool, revocable, spend-capped on paid actions, and every call audit-logged. It can only do what you could do. **Which plans include it?** Database maintenance is a purchasable first-party service rather than a plan inclusion — you buy it when you need it, at the price shown in your currency in the dashboard, charged to your billing account or wallet. Eligibility is set per product line, so what appears in your Extras section reflects the product line you are on. Everything you need to try the platform is in the card-free 14-day trial: no payment details, up to five sites on Footprint-Free Hosting. **Will one site's heavy database use slow down my others?** The fleet runs MariaDB with CloudLinux MySQL Governor, which throttles database usage per site specifically so one site's heavy queries cannot slow the server for the rest. That sits alongside LVE resource caps and CageFS filesystem isolation. The design goal throughout is containment — problems stay in the cage they started in. --- # Layered DDoS defence, so one attack is one site's problem URL: https://zinndigital.com/features/ddos-protection Floods are absorbed at the edge, network-layer attacks are filtered upstream, and whatever reaches the server is contained inside the target site's own kernel-level cage. Several layers, each doing a different job, so an attack aimed at one site does not become an outage for the ones beside it. This is the defence model we built for a platform hosting 700,000+ sites worldwide, and the baseline runs on every plan. Availability: per-site database throttling is in active development and not yet available. Everything else described here is live today. ## Layered by design, because one is never enough A volumetric flood, an L7 application flood and a slow connection-exhaustion attack are three different problems. We handle each of them where it is cheapest and fastest to handle — upstream of the fleet, at the edge, and inside the cage. - **Network layer (L3/4)** — Provider-level DDoS protection filters network-layer floods upstream of our worker fleet, before that traffic ever consumes a port, a NIC or a CPU cycle on the machine your site runs on. For advanced and enterprise risk profiles, Cloudflare Magic Transit and Spectrum extend the same filtering to non-HTTP traffic. - **Application layer (L7) at the edge** — A managed edge network sits in front of every site. It absorbs volumetric HTTP floods, runs an L7 WAF, applies per-site rate limiting, and uses bot management and managed challenges to separate real visitors from automated traffic — all before a request reaches origin. - **Server layer** — LiteSpeed Enterprise applies connection and request throttling with per-IP connection limits, Imunify360 runs a network firewall with brute-force protection and IP reputation filtering, and CloudLinux LVE entry-process caps bound how many concurrent requests a single site can ever hold open. - **Per-site containment** — LVE caps CPU, RAM, IO, IOPS, processes and entry-processes for every site individually. A flood that gets through the upper layers is throttled inside the target site's own cage, so the pressure it creates stays with that site rather than spreading across the server. ## Containment is the point Most hosting outages during an attack are not caused by the attack reaching its target. They are caused by the target's resource consumption starving everything else on the box. That is the failure mode this architecture is designed to remove. - Every site runs inside its own CloudLinux LVE resource cage — the attacked site is throttled at its own ceiling, and neighbouring sites keep the resources their own limits guarantee them. - CageFS gives each tenant an isolated filesystem view, so an attack that escalates into an intrusion attempt is contained rather than shared across tenants. - CloudLinux MySQL Governor throttles database usage per site, so an application-layer flood that hammers uncached queries cannot drag the database down for everyone else on the server. - Per-site LiteSpeed LSAPI workers are bounded by that site's LVE limits, so a flood cannot spawn unbounded PHP processes. - Per-IP connection limits and LiteSpeed connection throttling absorb slow-connection and connection-exhaustion attacks at the web server, not at the application. ## Cache is the shock absorber most hosts forget The cheapest request to survive is the one that never touches PHP or MySQL. Our two-layer cache means a large share of an application-layer flood is answered by static bytes rather than by your origin doing work. - LSCache, the LiteSpeed Enterprise full-page cache, serves cached pages without invoking PHP or the database — so repeated requests for the same URL cost a fraction of what they would on a stock stack. - A per-site Redis object cache offloads database reads for the pages that genuinely must be dynamic. - Cloudflare edge caching answers requests in the visitor's region, so flood traffic is dispersed across the edge network instead of converging on one origin. - Cart, checkout, my-account, nonce and session pages are excluded from cache by default, so hardening under load never breaks a transaction. - Purge is coordinated across both layers from one control, so raising cache coverage during an incident does not leave you with stale pages afterwards. ## Signal to action, automatically Mitigation is not a support ticket. Signals feed a policy engine that maps each one to an enforcement action, a customer notification and — where possible — an automatic remediation, with every transition logged. - **Dynamic tightening** — When a DDoS signal fires, the policy engine applies Cloudflare mitigation and per-site rate limiting, and can dynamically tighten that site's LVE limits. When the signal clears, the limits relax again. Graduated, reversible, and logged at every step. - **Throttled, not switched off** — If an attack is threatening the origin, the site moves to a 'throttled' state — tighter LVE limits and rate limiting, with the site still up and serving. Throttled recovers automatically once the pressure clears; it is not a suspension. - **Native LVE auto-throttle** — Below the policy engine, LVE throttles CPU, IO and process usage per site natively and automatically. It is the always-on first line, running whether or not anything has classified the traffic as an attack yet. - **Full audit trail** — Every enforcement transition records its reason, whether it was automatic or staff-initiated, and the evidence behind it. You are notified of what changed and how to resolve it, and every action is appealable. ## What is included, and what you buy when risk goes up Baseline protection is not optional, because an attacked or compromised site threatens its neighbours, our server reputation and our IP ranges. Heavier protection exists for sites whose risk profile calls for it. - Included on every plan: LVE and CageFS isolation, LiteSpeed connection and request throttling, a network firewall with brute-force protection and IP reputation filtering, the proactive WAF, and malware scanning. - Available as add-ons: advanced bot management, higher DDoS protection tiers, enhanced WAF rules, priority scanning and dedicated firewall rules. - Also upsold when you need it: one-click malware cleanup and remediation, for the case where an attack was the cover for a compromise rather than the goal. - Advanced network-layer mitigation via Cloudflare Magic Transit or Spectrum is available for enterprise and high-risk workloads. ## Attacks that are really something else A traffic spike is often a symptom. The same signal pipeline that handles floods also catches the compromises that produce them, so an incident gets classified correctly rather than just absorbed. - Every site we host is scanned for malware every day, and the proactive WAF blocks known exploit techniques before a patch exists for the underlying vulnerability — the route by which a site becomes someone else's attack tool. - Outbound mail is rate-limited per site and watched for volume spikes, bounce rates, blocklist hits and complaint signals, so a compromised site sending spam is caught in minutes rather than after a blocklisting. - Suspected malware and phishing are cross-checked against Google Safe Browsing, PhishTank and SURBL/APWG, and correlated with scan results before an enforcement decision is taken. - Resource abuse and crypto-miners surface as LVE CPU and IO faults logged per site, which auto-throttle the offender. - Every signal lands in one Abuse Desk in the admin console — aggregated, deduplicated and prioritised — rather than in four disconnected tools. ## Frequently asked questions **If another site on my server is attacked, what happens to mine?** The design goal is containment. Every site runs inside its own CloudLinux LVE cage with capped CPU, RAM, IO, IOPS, processes and entry-processes, its own CageFS filesystem view, and per-site database throttling via MySQL Governor. An attacked site is throttled at its own ceiling rather than consuming the whole machine, and LiteSpeed per-IP connection limits bound how much of the web server it can hold. Containment is engineered at the kernel, not configured per customer. **Is DDoS protection included, or an add-on?** The baseline is included on every plan: LVE and CageFS isolation, LiteSpeed connection and request throttling, a network firewall, the proactive WAF and malware scanning, with Cloudflare edge absorption and provider-level network filtering in front of the fleet. We include it because we cannot leave the protection of our own fleet optional. Advanced bot management, higher DDoS tiers, enhanced WAF rules and dedicated firewall rules are add-ons for sites that need them. **Will you take my site offline if it gets attacked?** Being a DDoS target maps to Cloudflare mitigation plus per-site rate limiting, and — only if the attack is threatening the origin — the 'throttled' state: tighter LVE limits with the site still up and serving. Throttled recovers automatically once the pressure clears. Suspension is reserved for non-payment or confirmed abuse, and even then the site serves a branded, reason-specific holding page rather than a broken one. **Does an application-layer flood still hit my database?** Not for anything served from cache. LSCache answers cached page requests without invoking PHP or MySQL, and a per-site Redis object cache offloads reads for genuinely dynamic pages. What remains is bounded by your site's LVE process and entry-process caps and by MySQL Governor's per-site database throttling, so database pressure from one site cannot spill onto the server. Cart, checkout, my-account and session pages stay uncached by default so hardening never breaks a transaction. **Can you protect traffic that is not HTTP?** Yes, at the network layer. Provider-level DDoS protection filters L3/4 floods upstream of our fleet regardless of protocol, and for advanced or enterprise requirements Cloudflare Magic Transit and Spectrum extend edge-grade mitigation to non-HTTP traffic. **How do I know an attack happened and what you did about it?** Every enforcement transition is logged with its reason, whether it was automatic or staff-initiated, and the evidence behind it. You are notified of what changed and what resolves it, every action is appealable, and privileged actions are audit-logged for your own compliance trail. Signals are aggregated in a single Abuse Desk rather than scattered across tools. **Can I try this before paying?** Yes. Footprint-Free Hosting starts with a card-free 14-day trial covering up to 5 sites — no payment details, no commitment. Plans are backed by a 30-day no-quibble money-back guarantee, free migrations and no vendor lock-in. --- # Give people exactly the access they need — and nothing else URL: https://zinndigital.com/features/delegated-access Bring in a developer, hand billing to your accountant, give a client a read-only window onto their own sites, or let our support team look at a problem. Every grant is a role with defined permissions, scoped to an organisation, enforced in the database, and written to an append-only audit log. ## Access is a membership, not a shared password Sharing one login is how account access goes wrong. On Zinn Digital® every person has their own identity, and access is a membership — a user, an organisation, and a role — that you can grant, change or revoke on its own. - **Your own identity, always** — Each collaborator signs in as themselves through Keycloak, our identity layer. Nobody types your password, nobody shares a browser session, and removing someone is one action rather than a password rotation and a scramble to work out who else knew it. - **Organisations form a tree** — Accounts are hierarchical — a reseller organisation holds client organisations, and client organisations hold sites. A membership applies to an organisation and everything beneath it, so you can hand an agency client control of their own organisation without ever exposing your other clients. - **Isolation enforced in the database** — Tenant separation is not a filter in application code that a bug could skip. Postgres Row-Level Security scopes every query to the caller's organisation subtree, so a request outside your scope has nothing to return. - **Absence is invisible** — Ask for an organisation or a site outside your scope and the API answers with a plain not-found rather than a permission error. A permission error would confirm the record exists; not-found tells an outsider nothing at all. ## Four customer roles, thirty-five permissions Permissions are granular keys — module plus action, like sites.restart or billing.refund — and roles bundle them. Four roles cover the shapes real teams need, and each one is data we seed, not logic buried in code. - **Owner** — Full control: create child organisations, invite and remove members, change roles, manage API keys, create, restart, purge, suspend and delete sites, run billing and invoices, raise tickets and read the audit log. The role you keep for yourself. - **Billing Manager** — Sees the organisation, its members and the plan catalogue, and manages invoices, payment methods and charges. No access to create, change or delete a single site — exactly the shape an external bookkeeper should have. - **Developer** — Views and creates sites, restarts services, purges cache, manages API keys and works tickets. Deliberately excluded: billing, invoices, payment methods, member management, site suspension and site deletion. A contractor can build without being able to bill you or destroy anything. - **Read-only** — Sees the organisation, its members, its sites, its billing, the plan catalogue, tickets, translation status and the audit log — and can change none of it. The right grant for a client who wants visibility, an auditor, or a stakeholder who only needs to look. ## Sign-in your team cannot quietly weaken Delegating access is only safe if the accounts you delegate to are hard to take over. Authentication runs through Keycloak for every person on the account, on every surface. - Passkeys and WebAuthn for phishing-resistant sign-in, plus TOTP two-factor authentication enforced for everyone by policy — not an optional setting a team member can skip. - Magic-link email sign-in as the default, with email and password as a fallback, and social sign-in through Google, Microsoft, GitHub and others. - SAML single sign-on for enterprise and agency customers, so joiners and leavers are handled by your identity provider rather than by hand. - One session across the customer dashboard, the public site and knowledge base, and support tickets — sign in once, and revoke once. - Session policies, step-up authentication on sensitive actions, and optional per-organisation IP allowlists for accounts that want access pinned to known networks. - Every signup email is validated before an account exists, so undeliverable, disposable and role addresses are caught at the door rather than becoming an orphaned member later. ## When our team needs access, it is scoped and it is logged Support work sometimes means looking inside your account. That access is governed by the same permission model as everything else — staff simply sit in a staff organisation, organised into departments with narrow grants. - **Departments, not blanket admin** — Staff are grouped into Support, Billing and Finance, Abuse and Trust-and-Safety, Sales, Onboarding, Engineering and Ops, Marketing, and Management. Each role grants specific modules and actions, so an agent sees the part of the admin console their job requires and not the rest. - **A support agent's real ceiling** — The Support Agent role grants exactly this: view customers, view and reply to tickets, view sites, restart a site and purge its cache. It carries no billing configuration, no refunds, no plan editing and no fleet management. The remediation an agent can perform is bounded by the role, not by good intentions. - **Signing in as a customer is tightly held** — The customer.impersonate permission is not part of the Manager role — it is held by Super Admin only. When a session is running on your behalf, the dashboard carries a persistent impersonation banner so it is never ambiguous who is acting. - **Everything privileged is written down** — Every privileged and administrative action appends to an append-only audit log recording the actor, the action, the target, supporting metadata, the IP address and the timestamp — time-partitioned in production. Owners and read-only members can read their organisation's log themselves. - **Approval gates on destructive work** — Sensitive and destructive staff actions can require step-up authentication or two-person approval before they run, and new departments and roles are configuration rather than a code change. ## Machines get delegated access too Scripts, CI pipelines, the CLI, the Terraform provider and AI agents all authenticate through the same permission model as people — no shared human credentials, no long-lived secrets pasted into a build. - **API keys are per-organisation and scoped** — Keys belong to an organisation and carry granular scopes tied to the same RBAC permissions — read-only, billing, provisioning. Grant a pipeline the narrow scope it needs rather than a member's whole account. - **Sandbox keys are separate from production** — Test-mode and live-mode keys are distinct, so an integration under development cannot reach into production data by accident or by a copied environment variable. - **Only the hash is stored** — We store a SHA-256 hash of the secret and a lookup prefix — never the raw key. You see a key once at creation. Each key tracks when it was last used and can be revoked on its own without disturbing anything else. - **AI tools connect under your permissions** — Our MCP server lets any MCP-capable agent manage your hosting in natural language, authenticated with OAuth 2.1 and scoped to your organisation and RBAC role, with per-tool revocable tokens, confirmation on destructive actions, spend caps and full audit logging. ## Access to the sites themselves Account access and server access are different problems. Site-level credentials are managed in the dashboard, issued least-privilege, and jailed so that one collaborator's shell is one site's shell. - SSH with a jailed shell, plus SFTP and FTP — CageFS isolation means each tenant sees only their own files. - wp-cli from the panel terminal and over SSH, for the operations developers actually want to script. - A full VS Code editor in the browser via code-server, with git, editing the site's files directly in the dashboard. - Embedded phpMyAdmin and Adminer for databases, and an embedded file manager, both single-sign-on'd from the dashboard rather than gated behind a second set of credentials. - Access keys and credentials are created, listed, rotated and revoked in the dashboard, issued least-privilege, and their use is audit-logged. - Staging with clone and push-to-live keeps risky work off production, so a new collaborator's first change never lands straight on a live site. ## How to structure access for the way you actually work A solo operator keeps a single organisation and one owner membership, and adds a Developer role when a contractor comes in for a project. When the project ends, the membership is removed and their sign-in stops working immediately — there is no shared credential left behind to rotate. An agency uses the organisation tree. Each client gets its own child organisation, holding that client's sites, and the client's own people get memberships there — read-only for a stakeholder who wants visibility, owner for a client who wants to self-serve. Your staff hold memberships higher up the tree and see the portfolio; a client sees only their own branch, and Row-Level Security is what makes that true rather than a promise. A reseller works the same way, one level further up: a reseller organisation holds client organisations, each with its own members, billing view and sites. The same primitive powers sub-accounts, agency teams and reseller hierarchies — there is no separate, weaker mechanism for any of them. Everything is available on the card-free 14-day trial. Sign up without payment details, invite a colleague, watch what each role can and cannot reach, and read your own audit log back. ## Frequently asked questions **Can I give someone access to just one site?** Today a membership grants its role across an organisation and everything beneath it in the tree, so the way to separate site sets is to separate organisations — put those sites in their own child organisation and grant the membership there. It is a clean model for agencies and resellers, where each client already wants their own boundary. Per-membership resource scoping, pinning a single membership to named sites within one organisation, is a planned refinement rather than something available now. **Can a developer I invite delete a site or push to live?** The Developer role does not carry site deletion or site suspension — those keys belong to the Owner role. It grants viewing and creating sites, restarting services, purging cache, managing API keys and working tickets. Deployment and push-to-live permissions are not part of the Developer grant either, so promotion to production stays with the account owner. Pair that with staging so build work happens off the live site in the first place. **What can Zinn Digital® staff see in my account?** It depends entirely on the staff role, and each role is a narrow set of permission keys. A Support Agent, for example, can view your account and sites, view and reply to your tickets, restart a site and purge its cache — and cannot touch billing configuration, refunds, plans or the fleet. Signing in as a customer is a separate permission held only by Super Admin, and when it happens the dashboard shows a persistent impersonation banner. Every privileged action is recorded in the audit log with the actor, action, target, IP and timestamp, and you can read your organisation's log yourself. **How do I revoke access quickly if someone leaves?** Remove the membership and their access to that organisation ends — they still have their own identity, but no role and therefore no permissions in your account. API keys are revoked individually, so a pipeline key can be cut without disturbing anything else. If you use SAML single sign-on, deprovisioning in your identity provider handles sign-in centrally. Site-level credentials such as SSH keys are revoked in the dashboard, and the removal itself is audit-logged. **Do team members share my API keys?** No — but it is worth being precise about why. API keys belong to the organisation, not to an individual member, and they carry their own granular scopes tied to the same permission catalogue. So rather than handing a person a key, you create a key for the job it does with the narrowest scope that job needs, and revoke that key when the job ends. Only a hash of the secret is ever stored, and each key records when it was last used so unused keys are easy to find and retire. **Can I connect an AI agent without giving it the keys to everything?** Yes. Our MCP server authenticates agents with OAuth 2.1 and scopes them to your organisation and your RBAC role, with per-tool revocable tokens, so you grant a specific capability rather than blanket access. Destructive actions require confirmation, spend caps apply, and every action lands in the same audit log as human activity. **What stops one tenant from reaching another tenant's data?** Postgres Row-Level Security scopes queries to the caller's organisation subtree in the database itself, with the application-level filter as defence in depth rather than the only line. Requests for records outside scope return not-found rather than a permission error, so nothing is revealed about what exists. On the server side, per-site isolation through CageFS keeps each tenant's shell and files to their own site. **Can I try this before paying?** Yes. The 14-day trial is card-free — no payment details, no commitment — and covers Footprint-Free Hosting with up to five sites. It is enough to invite a colleague, assign a role, and confirm the boundaries behave the way you need before you commit. --- # Manage your own DNS and purge caches — safely URL: https://zinndigital.com/features/dns-management View, add, edit and delete your own DNS records in bulk, and purge caches on demand, from one panel and the MCP. The records that keep your sites online — the IP and origin A-records — stay locked, and on the Footprint-Free line they are hidden entirely, so you get full control without a footprint leak or a self-inflicted outage. ## Your records, in your hands Everything you would expect from a DNS panel, exposed the same way to a person and to an AI agent. - **View and edit records** — See your zone and add, edit or delete records — TXT for verification, CNAME for services, MX for mail and more — with changes applied through the same DNS driver that runs the platform. - **Bulk operations** — Apply a record set across many domains at once instead of clicking through one zone at a time — a verification TXT across a network, an MX preset across a portfolio. - **Cache purge, coordinated** — Purge the CDN cache from the site's CDN tab. On WordPress, Zinn® Cache also clears exactly the pages a change affects from the server's page cache. - **Same on dashboard and MCP** — Every operation is available to your AI tool through the MCP as well as the dashboard, so bulk and automated DNS work is first-class, not a manual chore. ## IP-protected by design Self-service DNS is only safe if the dangerous records are out of reach. Ours are — and the rule lives in the engine, so it cannot be worked around. - You may never change the IP or origin A-records that point a site at our hosting — the single fastest way to take a site offline. - On the Footprint-Free line those hosting records are not shown at all, so the link between a PBN site and its origin is never exposed in the panel. - On the other lines the records are visible for transparency but locked against editing. - The guardrail is engine-side policy, not an interface check, so the dashboard, the API and the MCP all enforce it identically — an agent cannot bypass it. - Every change is tenant-scoped and audit-logged, with the identity that made it recorded. ## Frequently asked questions **Which records can I manage myself?** The records that are safely yours to change: TXT, CNAME, MX and the rest, added, edited, deleted and managed in bulk. The one thing you cannot touch is the IP or origin A-record that points a site at our hosting — that stays locked so a bad edit can never take a site offline. On the Footprint-Free line those hosting records are not even shown. **Why can't I edit the origin A-record?** Because it is the record most likely to break a site and, on a PBN, most likely to leak a footprint. The guardrail is enforced in the engine, not the interface, so it holds identically on the dashboard, the API and the MCP — an AI agent acting for you cannot change it either. You get full control of everything else. **What is different on the PBN line?** On the Footprint-Free line the IP and origin records are hidden entirely — you manage your TXT, CNAME and MX records, and the hosting records simply are not part of the surface. On the other lines those records are visible but locked. Either way the origin cannot be changed. **Can I purge the cache myself?** Yes. Clear everything, specific URLs or specific cache tags whenever you need to, from the dashboard or the MCP. Purges are coordinated across the server cache, the CDN and the edge so every layer clears the same pages at once. **Can my AI assistant manage DNS and purge caches?** Yes. Record CRUD, bulk edits and cache purges are exposed on the MCP as well as the dashboard, under the same engine-side policy — so an agent can apply a record set across a hundred domains or purge a batch of zones, and still never change an origin record. --- # Free email on every domain you register or transfer to us URL: https://zinndigital.com/features/email Every domain you host gets real mailboxes, forwarders and autoresponders — free 10GB boxes on every Footprint-Free plan — managed from the same panel as the site, the same API as everything else, and the same AI tool you already use. No separate mail provider to buy, wire up or remember the password for. When we host a domain's DNS, a new mailbox comes with its MX, SPF, DKIM and DMARC records written for you and checked at the domain's own nameservers before it is marked ready — nothing to paste. Availability: Google Workspace and Microsoft 365 seat resale, bulk mail-DNS presets, mail provisioned with the site, mailbox import during migration and the Terraform provider are in active development and not yet available. Everything else described here is live today. ## Mail that belongs to the domain, not to a third party A site without an address on its own domain looks like what it is: unfinished. Contact pages that point at a free webmail account, forms that send from somewhere unrelated, privacy notices with no reachable inbox — every one of them is a small tell, and every one of them is avoidable. Zinn Digital® gives every domain you host real mail: named mailboxes, forwarders that route to wherever you actually read, and autoresponders for the addresses nobody watches. It is provisioned alongside the site, not bolted on afterwards, and it is managed from the same dashboard as your files, DNS, SSL, backups and logs. On Footprint-Free plans it is free — 10GB boxes for every domain, included in the plan rather than metered as an add-on. That matters most when you run a network: a hundred domains needing a working contact address would otherwise mean a hundred separate mailbox bills, and none here. ## What you can do with mail The full mailbox lifecycle is exposed as first-class platform actions — the same set whether you drive them from the dashboard, the public API or an AI agent. - **Create and manage mailboxes** — Add a mailbox on any domain you host, set its name and quota, update it later, list what exists and delete what is finished. Standard create, update, list and delete — no ticket, no provisioning wait. - **Forwarders** — Point info@, hello@ or abuse@ at an inbox you actually check. Useful when you want a professional address on every domain without a hundred inboxes to monitor. - **Autoresponders** — Set an automatic reply on any address — holiday cover, an acknowledgement for enquiries, or a polite redirect for an address you no longer staff. - **Webmail, one click away** — Open webmail from the dashboard in one click, with the mailbox already filled in and the page in your language. Sign in with the mailbox's own password, from any browser on any device. - **Quotas per mailbox** — Every mailbox is created with an explicit quota, so a single runaway inbox never becomes everyone else's problem. - **DNS in the same place** — Mail records live in the same DNS surface as the rest of the zone — Let's Encrypt SSL, records and mailboxes managed together instead of across three control panels. ## Free on every Footprint-Free plan Email is part of the Footprint-Free package, not an upsell attached to it. The plan grants it; the platform enforces the grant. - Free 10GB email boxes for every domain, on every Footprint-Free tier — from the 5-site plan at $6/month to the 2,000-site plan. - Included in the entitlement your plan carries, so email capacity is enforced by the platform rather than trusted to a support note. - One address per domain or many — give each site the contact address its niche and content actually call for. - Provisioned with the site, so a domain is live, secured and reachable in the same deploy. - Mailboxes come with you when you migrate in: our free migrations import existing accounts alongside sites and plans. - Managed under the same tenant isolation and audit logging as every other privileged action on your account. ## Sending mail from your sites Receiving mail is the easy half. Getting a WordPress contact form, a WooCommerce order confirmation or a password reset to actually land in an inbox is the part that quietly breaks. Mail from every mailbox we provide leaves through our own mail relay, which we run ourselves — never straight from a shared web server. Every sending address has matching reverse DNS, every connection that supports it is encrypted, and delivery uses only the addresses our own records vouch for. You never paste a DNS record. As soon as a domain has mail with us, we write its MX, SPF, DKIM, DMARC, TLS-reporting and autodiscover records ourselves, and our mail servers sign every message with keys that rotate on their own. If one of those records is later changed or deleted, we spot it at your domain's own nameservers and put it back. The only time you see a record is when your DNS is hosted somewhere we cannot write to — then the mail screen shows exactly what to add. Sending is rate-limited per mailbox and per domain. That is deliberate: a stolen password or a compromised WordPress install trying to blast spam is the most common way a host's addresses get blocklisted, and a per-mailbox ceiling contains the damage to the account that caused it — while an ordinary inbox or a busy shop never comes near it. ## Reputation protection, in detail Mail reputation is shared infrastructure. We treat spam-sending sites as an operational emergency, with a graduated, audited response rather than a blunt switch. - **Per-mailbox sending limits** — Every mailbox and every domain has a ceiling on how much it can send through our relay, and delivery to each receiving provider is paced rather than burst. A stolen password hits the ceiling long before it hits a blocklist, which buys time to fix the cause instead of appealing to a reputation service. - **Mail-log monitoring** — We watch outbound volume spikes, bounce rates, RBL and spam-trap hits and feedback-loop complaints — the signals that show a problem while it is still small. - **Correlated with malware scanning** — A spam signal plus an Imunify360 malware finding is high-confidence evidence of the same compromise, which lets us act on the cause rather than the symptom. - **Graduated enforcement** — Outbound spam is throttled first, then the site moves to restricted — outbound mail off, site still visible — and only escalates to suspended if the sending continues. Every step is audit-logged. - **Isolation by design** — Per-site CageFS isolation and LVE limits are built to contain a compromise to the cage it happens in, so one hacked site is not an open door to the mail of every other site on the server. - **An abuse desk that answers** — Inbound abuse and DMCA reports land in a real intake queue, aggregated and prioritised — so a complaint about your network gets reviewed by a person, not auto-actioned by a script. ## Managed by API, Terraform and AI Mailboxes are platform objects like sites and DNS records. Anything you can do in the dashboard, you can do in code — or ask an agent to do for you. - Public API: mailbox create, update, list and delete are part of the documented API, generated from the same OpenAPI spec as everything else — so the SDKs and CLI have them the day the endpoint ships. - Terraform: manage sites, domains, DNS, mailboxes and plans as infrastructure-as-code, and apply the same mail layout across a hundred domains from one configuration. - MCP: connect Claude, Cursor, ChatGPT or any MCP-capable agent to your hosting and ask it to add a forwarder or provision a mailbox in plain language. - Scoped and safe: agent access uses OAuth 2.1 tokens bound to your organisation and RBAC permissions, tokens are per-tool and revocable, and destructive actions require explicit confirmation. - Fully audited: every mailbox action — panel, API or agent — is recorded with the identity that performed it. ## No lock-in, by architecture Customer mailboxes sit behind a MailDriver adapter, a defined interface with the mailbox, forwarder, autoresponder and webmail operations declared on it. Today that interface is implemented on our own mail servers, which we run ourselves, with SPF, DKIM and DMARC published for every domain you add mail to. That is a deliberate engineering choice, and the abstraction is the point. When customer mail moved onto our own servers, mailboxes, their folders and their messages were copied across and counted folder by folder — the interface stayed the same, so nothing about how you manage mail had to change. The same seam means adding capacity region by region, or bringing in a specialist operator for a particular workload, is a business decision rather than a re-architecture. The same principle runs through the platform: payments, DNS, registrars, CDN and mail all sit behind swappable adapters. You are never holding a configuration that only one supplier can honour. ## Choose your mail provider — or resell one Not everyone wants the same mailbox. Pick the provider that fits, and we wire the DNS and provisioning for you — our own mail, or a seat on a name your team already knows. - **Google Workspace** — Resell Google Workspace seats through the catalogue and provision them for your customers, or connect an existing Workspace in one click — we write the DNS and leave the mailboxes with Google. - **Microsoft 365** — Resell Microsoft 365 seats or connect an existing tenant, with the DNS preset applied for you so mail flows without a manual record-by-record setup. - **Our own mail, included** — Prefer to keep it in-house? Our own mailboxes are free on every Footprint-Free plan and managed in the same panel — no third-party account to buy or wire up. ## One-click DNS presets and device autoconfig The part that usually goes wrong — the records and the phone setup — is the part we automate. Pick a provider and the whole record set is written for you; hand a mailbox to a device in one tap. - Pick Google Workspace, Microsoft 365 or our own mail and we write the whole record set — MX, SPF, DKIM, DMARC and autodiscover, plus TLS reporting on our own mail — onto your DNS for you. Nobody hands you a list of records to paste, and on our own mail the records are checked and repaired automatically after that. - Connect an existing Workspace or Microsoft 365 in one click, or provision a new account, without editing records by hand. - Mailbox device autoconfig: every mailbox has a Set up on a device panel carrying its own server names, ports, encryption and username, with a copy button on each — plus an Apple profile that fills them in for an iPhone, iPad or Mac. Outlook and Thunderbird configure themselves from the address alone. - The presets run on the same DNS driver as the rest of your zone, under the same origin-record protection — mail records are written, hosting records stay locked. - Apply a preset across many domains at once, from the dashboard or the MCP, so a whole network gets working mail in one bulk action. ## Frequently asked questions **How much email do I get, and what does it cost?** Every Footprint-Free plan includes free 10GB email boxes for each domain you host — it is part of the plan entitlement, not a paid add-on. There is no separate mail bill and no per-mailbox charge on those plans. Mailbox provision on other product lines depends on the plan you choose, so check the plan detail at the point of purchase. **Can I keep using Google Workspace or another mail provider instead?** Yes. You manage your own DNS records in the panel, MX included, so you can point mail at any provider you prefer while your sites, SSL and backups stay with us. The included mailboxes are there if you want them, not a condition of hosting. **What happens if one of my sites starts sending spam?** Almost always the cause is a compromised WordPress install. Outbound sending is throttled first; if it continues the site moves to restricted, which turns outbound mail off while leaving the site visible; and it escalates to suspended only if sending persists. You are alerted at each step, the malware scan runs in parallel to find the root cause, and every action is logged. Restricted status lifts on remediation. **Does someone else's compromised site put my mail at risk?** The platform is built to contain that rather than hope it never happens. Every site runs in its own CageFS cage with LVE resource limits, outbound sending is capped per site, and mail-log signals are correlated with malware scanning so a compromise is caught while it is small. Containment is the design goal — no host can promise a shared platform is risk-free, so we build to limit the blast radius and act fast. **Do you run your own mail servers?** Yes. Customer mail runs on our own mail servers, delivered through our MailDriver adapter — a defined interface rather than a dependency on any one operator. Because mail sits behind that interface, adding capacity or changing how it is run is an operations decision rather than a rebuild, and it changes nothing about how you manage mailboxes. **Will my transactional site email actually get delivered?** Mail from the mailboxes we provide leaves through our own relay, never directly from a shared web server, and we write its SPF, DKIM, DMARC and TLS-reporting records for you — then keep checking them and put back anything that goes missing. We cannot control a recipient's own filtering, so what we guarantee is the part that is ours: correct records, signed mail and paced, encrypted delivery. **Can my AI assistant manage mailboxes for me?** Yes. Our MCP server exposes email actions — mailboxes and forwarders — to any MCP-capable agent, including Claude, Cursor and ChatGPT. The agent is bound to your organisation with OAuth 2.1 and can only do what your RBAC permissions allow, destructive actions require explicit confirmation, and every call is written to the audit log. **Do mailboxes transfer when I migrate to Zinn Digital®?** Yes. Migrations are free and hands-on, and existing mailboxes are imported alongside your sites, plans and billing history rather than being left for you to rebuild by hand. --- # Footprint remover URL: https://zinndigital.com/features/footprint-remover Footprints are what get a network found. Zinn Digital® removes them at two layers — the infrastructure your sites sit on, and the WordPress fingerprint each site broadcasts — so your properties present as unrelated, generic sites rather than an obvious cluster. ## Two layers, one clean surface A footprint is more than an IP address. Zinn® removes the signals at both the network layer and inside each WordPress install, because either one on its own leaves a trail. - **CDN account pools** — Deploy across a pool of our Cloudflare and CDN accounts, plus your own bring-your-own accounts, so your sites never share one giveaway account or nameserver set. - **Footprint-aware rotation** — Sites are spread and rotated across accounts, recomputed from live account state at deploy time so the balance stays even instead of drifting into a detectable pattern. - **Static-HTML option** — Rebuild a site as locked-down static HTML with no CMS to fingerprint at all — the smallest possible surface, ideal for aged domains and money pages. - **Locked-down config** — The hosting footprint hardens server configuration and headers so the platform itself does not leave a common, cross-site signature. ## The Zinn® Footprint plugin Shipped inside the Footprint-Free deploy footprint and built to WordPress.org plugin standards, the Zinn® Footprint plugin strips the tell-tale signals that reveal a site is WordPress — and which version. Each measure is an independent toggle under Settings → Zinn® Footprint, so you can switch any of them off if a theme or plugin depends on it. - Removes the generator meta tag from the page head and feeds - Strips the WordPress version from asset URLs — only when the ?ver value equals the core version, so your own cache-busting versions are preserved - Removes discovery links — RSD, Windows Live Writer manifest, shortlink, and REST and oEmbed discovery links - Disables XML-RPC, a common fingerprint and attack surface - Disables pingbacks, including the X-Pingback header - Genericises login errors so they no longer confirm a valid username or password - Removes the X-Powered-By header where PHP allows ## Restore aged domains from the Wayback Machine Aged domains are only useful if you can put the original content back. The Wayback restore tool wraps the Internet Archive's CDX index in a durable workflow: enter a domain, list its snapshots, then pick the date you want — and it never defaults to the last capture, which on an expired domain is usually a parking page rather than the site you bought it for. From there it downloads the pages and assets, strips the archive.org toolbar and injected code, and rewrites internal links and asset paths so nothing points back at the archive. The result is rebuilt either as static HTML or as a working WordPress site, with archived pages converted to posts and pages. Restored properties drop straight into the same footprint-aware hosting and fingerprint removal as everything else — the primary use is Footprint-Free and PBN work, though the same tool recovers a mainstream site when no backup exists. ## Frequently asked questions **What is a footprint, and why does it matter?** A footprint is any shared signal that links your sites together — the same hosting account, nameservers, IP ranges, WordPress version strings, or discovery links. Enough shared signals make a network easy to identify. Zinn® removes them at both the infrastructure and per-site level. **Does the Zinn® Footprint plugin hide that a site is WordPress entirely?** It removes the common application-level fingerprints — the version, generator tag, discovery links, XML-RPC and more. Full obfuscation also depends on server configuration and theme markup, which the Zinn® hosting footprint handles separately. For the smallest surface of all, deploy as static HTML with no CMS to detect. **Will removing these signals break my site?** No — the defaults are safe for typical sites. If a specific integration relies on XML-RPC or on discovery links, each measure is an independent toggle you can turn off individually under Settings → Zinn® Footprint. **Can I use my own Cloudflare and CDN accounts?** Yes. You can use our account pools, bring your own accounts, or mix both. Footprint-aware balancing spreads and rotates your sites across whatever accounts are available, and there is no vendor lock-in. **Can I restore an aged domain from the Wayback Machine?** Yes. Pick a domain and choose any date the archive holds, and the tool downloads the archived content, strips archive.org code, rewrites links, and rebuilds it as static HTML or WordPress — ready to host behind the same footprint removal. --- # Every site in its own cage, so one bad neighbour stays one bad neighbour URL: https://zinndigital.com/features/isolation Isolation is the difference between an incident and an outage. Every site we host runs inside a kernel-level CloudLinux LVE cage with its own CPU, RAM, IO and process ceilings, its own CageFS filesystem view, its own PHP version and its own database throttle. A site that is attacked, compromised or simply running a punishing query is contained where it sits — and the isolation baseline is included on every plan, not sold back to you as an upgrade. Availability: per-site database throttling and per-site resource statistics are in active development and not yet available. Everything else described here is live today. ## Isolation at the kernel, not in a config file The worker fleet runs CloudLinux OS, which pushes multi-tenancy down into the kernel. Each site gets a Lightweight Virtual Environment — an LVE — that is a hard boundary rather than a polite convention. Nothing a site does inside its cage can be spent out of someone else's budget. - **Hard per-site resource ceilings** — LVE caps CPU, RAM, IO, IOPS, processes and entry-processes for every site independently. When a site exceeds its ceiling it is throttled inside its own cage — the fault is logged against that site, and the sites either side of it carry on unaffected. - **Runaway processes are contained, not chased** — A plugin stuck in a loop, a badly written cron job or a crawler hammering an endpoint hits the site's own process and entry-process limits first. One site cannot simply consume the machine. - **Attack traffic is bounded per site** — Because entry-processes are capped per cage, a flood aimed at one site cannot open unlimited work on the host. LiteSpeed connection and request throttling and the Imunify360 network firewall sit in front of that, so the attack stays the target's problem. - **Resource faults become signals, not surprises** — Every LVE fault is recorded per site and flows into the platform's policy engine, which can tighten or relax limits automatically. You see why a site was throttled, and when — graduated, reversible and logged. ## A filesystem view of your own Resource isolation stops a site being loud. Filesystem isolation stops it being nosy. CageFS gives every tenant a private, restricted view of the machine. Under CageFS, a tenant sees its own files and a minimal, sanitised set of system binaries — and cannot see other tenants, other tenants' sites, or sensitive system files. The usual shared-hosting failure mode, where one compromised account becomes a reading position over every other account on the box, is closed off at the kernel. This matters most on the day something goes wrong. If a site is compromised — through a stale plugin, a stolen credential, a vulnerable theme — CageFS is what keeps the blast radius to that single cage. Our security specification is deliberate about the wording: CageFS contains breaches. Containment is the honest claim, and it is the one that decides whether an incident is a one-site clean-up or a fleet-wide one. Backups reinforce the same boundary. Per-site backups are immutable, offsite and isolated from the running fleet, with tested restores, so even a worst-case compromise on one site has a clean, independent recovery path that does not depend on the state of the machine it was running on. ## The database is isolated too — this is where hosting usually gets loud Web-tier isolation is only half the story. On a WordPress fleet, the thing that most often makes a server feel slow is one site's queries, not one site's traffic. That is handled explicitly. - **MySQL Governor** — CloudLinux MySQL Governor throttles database usage per site, so one site's heavy queries cannot slow the server for everyone else. It is the anti-slowdown control, and it runs whether or not the noisy site ever notices it is being restrained. - **MariaDB for WordPress workloads** — The fleet runs MariaDB (or Percona), chosen for WordPress workloads rather than inherited by default, with Governor sitting on top of it as the per-tenant fairness layer. - **Redis object cache in front** — A per-site Redis object cache absorbs repeated reads before they reach the database, which lowers the pressure Governor has to arbitrate in the first place. Caching and isolation work as one system. - **Per-site PHP, hardened** — CloudLinux alt-PHP gives each site its own PHP version selector, its own extensions (imagick, gd, redis and the rest) and its own hardened settings — with LSAPI workers bounded by that site's LVE limits, so PHP concurrency is part of the cage rather than an escape from it. ## Failure is graduated, reversible and explained Isolation decides how far a problem spreads. Enforcement decides what happens next. We replaced the blunt on/off suspend with a state machine, driven by durable workflows and enforced on the worker through LiteSpeed, LVE and Imunify. - Throttled — tighter LVE limits and rate limiting, with the site still up and serving. Typically a resource-abuse or soft signal, and it recovers automatically once the cause clears. - Restricted — outbound mail, cron or POST requests are disabled while the site stays visible. Used for a suspected compromise or spam-sending, and it recovers automatically on remediation. - Suspended — the site goes offline behind a branded, reason-specific holding page (billing, maintenance or abuse) rather than a broken one. It reverses on payment, on fix, or on appeal. - Quarantined — offline, files locked, no execution, isolated for forensics. Reserved for confirmed malware or phishing, and it reverses only after cleanup and review; there is no automatic release on a re-scan. - Every transition is audit-logged with its reason, actor and evidence, notified to you with instructions on how to resolve it, and appealable. Enforcement timing is configurable per product line, so billing, abuse and legal each escalate on their own clock. ## The same isolation across both product lines — and a heavier tier when you need it Isolation is not a plan feature that appears three tiers up. It is a property of the substrate, so it is identical whether you are running one WooCommerce store or two thousand network sites. - **Footprint-Free Hosting** — Bulk and PBN networks run on the same LVE and CageFS substrate, alongside footprint-aware CDN account rotation and static-HTML delivery. Isolation is what makes density safe: sites share a fleet without sharing fate. - **Zinn® Managed WordPress** — Managed WordPress, WooCommerce, PHP, static and Node sites get the same cages plus full self-service — your own PHP version and extensions, Redis object cache, staging and push-to-live. - **Container-per-site as a premium variant** — For workloads that need a stronger boundary than the density-optimised default, full container-per-site isolation is offered as a provisioning-driver variant: same engine, same control plane, different placement, at higher overhead. - **Included, not upsold** — LVE and CageFS isolation, the proactive WAF and malware scanning are included for every customer, because an infected or runaway site threatens its neighbours and our IP reputation. One-click malware cleanup and advanced protection tiers are the paid add-ons — the baseline is not. ## Why isolation is never optional here The commercial temptation in hosting is to sell safety in tiers: put the cheap customers on a shared box with soft limits, and charge the ones who care for a boundary. We do not, because the customer who did not pay for isolation is precisely the one whose compromised site becomes everybody else's incident. We host more than 700,000 sites worldwide, on a fleet where density is the whole economic proposition. That only works if the isolation underneath it is unconditional. Kernel-level cages, a private filesystem view, per-site database throttling and per-site PHP are the price of running at that scale without shared fate — so they are on for everyone, on every plan, from the first site you deploy. The result is a platform that behaves predictably under other people's bad days. Behind it sits a 99.99% uptime assurance, per-site immutable offsite backups with tested restores, and a full audit trail of every enforcement action taken on your sites. ## Frequently asked questions **Can another customer's site slow mine down?** Isolation is designed specifically to stop that. LVE caps CPU, RAM, IO, IOPS and processes per site, MySQL Governor throttles database usage per site, and LSAPI workers are bounded by the site's own cage — so a neighbour's traffic spike or heavy query load is throttled against their ceiling, not yours. Every fault is logged per site, and the policy engine can tighten a noisy site's limits automatically. **If a site on the same server is hacked, is mine at risk?** The honest answer is containment rather than a guarantee. CageFS gives each tenant an isolated filesystem view — a compromised tenant cannot see other tenants, their sites, or sensitive system files — and a confirmed malware or phishing case moves that site to quarantined: offline, files locked, no execution, isolated for forensics. That is what limits the blast radius. Alongside it we run malware scanning and a proactive WAF on every site, plus per-site immutable offsite backups with tested restores, so recovery never depends on the state of the machine involved. **Is isolation included, or does it cost extra?** It is included on every plan. LVE and CageFS isolation, the proactive WAF and malware scanning are baseline for every customer, because an infected or runaway site threatens its neighbours and our IP reputation — we cannot sensibly leave it optional. What is sold as an add-on is one-click malware cleanup and remediation, and advanced protection tiers such as enhanced WAF rules, priority scanning, bot management and higher DDoS tiers. **What happens to my site if it exceeds its resource limits?** It is throttled inside its own cage rather than switched off. Throttled means tighter LVE limits and rate limiting with the site still up and serving, and it recovers automatically once the cause clears. You are notified with the reason, the transition is logged with its evidence, and it is appealable. If the load is genuine growth rather than a fault, the answer is a larger plan, not a permanent throttle. **Does a suspended site just go blank?** No — a suspended site serves a branded, reason-specific holding page (billing, maintenance or abuse) so it reads as intentional rather than broken. Suspension reverses on payment, on fix, or on appeal. Quarantine is stricter and works differently: it reverses only after cleanup and review, never automatically. **Can I choose my own PHP version and extensions?** On Zinn® Managed WordPress, yes — CloudLinux alt-PHP gives each site its own PHP version selector, its own extensions such as imagick, gd and redis, and its own hardened settings, all bounded by that site's LVE limits. Footprint-Free Hosting deliberately runs a more standardised, locked-down per-site configuration, because configuration variety is itself a footprint. **Is there a stronger isolation option than the shared-kernel model?** Yes. CloudLinux LVE and CageFS is the density-optimised default across both product lines. For workloads that need a harder boundary, full container-per-site isolation is offered as a provisioning-driver variant — the same engine and control plane with different placement, trading overhead for stronger separation. **Can I try it before committing?** Yes. Footprint-Free Hosting starts with a card-free 14-day trial covering up to five sites — no payment details, no commitment. Deploy a few sites, push some load through them, and see how the cages behave before you decide. --- # Malware scanning on every site we host URL: https://zinndigital.com/features/malware-scanning Every site we host is protected by a commercial security stack: malware scanning, a proactive WAF that blocks exploits before a patch exists, a network firewall, brute-force protection and IP reputation filtering. Scanning, the WAF and kernel-level isolation are included on every plan — because an infected site is a threat to its neighbours, not just to its owner. When something does get through, one-click cleanup and staff-run hack repair are there to buy. Availability: per-site database throttling and per-site resource statistics are in active development and not yet available. Everything else described here is live today. ## What runs on every site, from the first deploy Every site we host is scanned for malware every day, and anything found is removed automatically — included on every plan, with nothing to configure. On our own fleet we go further: Imunify360 watches files as they are uploaded and removes known malware on sight, so a compromised upload is usually gone before anyone visits the page. Sites on our resold range are scanned daily by the platform they run on. Either way, what was found and what we did about it is waiting in your dashboard, and you can start a fresh scan yourself at any time. - **Malware scanning** — Files are scanned continuously rather than on a nightly cron, so a compromise is flagged when it lands instead of hours later. Scanning is included on every plan, on every product line. - **Proactive WAF** — The proactive firewall blocks known exploit techniques before a patch for the underlying vulnerability is even available — the gap that catches out sites running an unpatched plugin or theme. - **Network firewall and brute-force protection** — A network-level firewall, brute-force protection on login endpoints and IP reputation filtering sit in front of the site, cutting off the credential-stuffing and probing traffic that so often precedes a WordPress compromise. - **One-click cleanup** — When an infection is confirmed, remediation is a single action rather than a manual file-by-file hunt. Cleanup is sold as an add-on — per incident or as a subscription — while the scanning that finds the infection is always included. ## Detection is layered, because malware rarely announces itself A scanner on its own misses the compromises that only show up in behaviour. We correlate several independent signals so a hacked site is caught by whichever one fires first. - Malware and phishing kits are caught by the malware scan, then cross-checked against Google Safe Browsing, PhishTank and SURBL/APWG blocklists. - Outbound mail is watched for the signature of a compromised site: volume spikes, high bounce rates, RBL and spam-trap hits, and feedback-loop complaints, with per-site outbound rate limits enforced. - A spam signal plus a malware signal together is treated as high-confidence compromise — which is how a hacked site gets actioned in minutes rather than after a blocklisting. - Crypto-miners and other resource abuse surface through CloudLinux LVE, which logs CPU and IO faults per site and throttles automatically. - Every signal — scan hits, mail anomalies, LVE faults, inbound abuse reports to our abuse mailbox — lands in one Abuse Desk, aggregated, deduplicated and prioritised. ## Containment first, so an infection stays one site's problem Detection matters less than what happens in the minutes after. Each site sits inside its own kernel-level cage, so a compromise is boxed in while it is dealt with. - **CageFS filesystem isolation** — Each tenant gets an isolated filesystem view and cannot see other tenants, other sites, or sensitive system files. CloudLinux describes this as containing breaches — the blast radius of a compromise is held inside the cage rather than spreading across the server. - **LVE resource caps** — CPU, RAM, IO, IOPS, processes and entry-processes are capped per site. A miner, a mail flood or an attacked site is throttled inside its own cage instead of starving its neighbours. - **Evidence preserved before cleanup** — Quarantine locks files and stops execution while preserving the site as it was found, so forensics and any later dispute have something real to work from. - **Immutable backups as the fallback** — Per-site backups are immutable, offsite and isolated from the running fleet, with restores that are tested rather than assumed. Footprint-Free plans hold daily backups for 30 days with one-click restore. ## What happens when a site is flagged Enforcement is graduated, reversible and reason-tracked — a documented state machine, not a blunt on/off switch. Every transition is logged with its reason and evidence, notified to you with how to resolve it, and appealable. - **Malware detected → restricted** — The site stays visible but is degraded — outbound mail off, cron off, POST blocked — and cleanup is offered. Restricted status lifts automatically once the site is remediated. - **Severe or unresolved → quarantined** — The site goes offline with files locked and no execution, isolated for forensics. Quarantine is reversed after cleanup and review — there is no automatic release on the next scan. - **Phishing confirmed → quarantined immediately** — Confirmed phishing carries legal risk for everyone on the platform, so it skips the graduated path and is quarantined straight away. - **Outbound spam → throttle, then restrict** — Outbound mail is throttled first, then disabled under restricted status, and only escalates to suspension if the sending continues. A suspended site serves a branded, reason-specific holding page rather than a broken one. ## Included, upsold, and repaired We draw the line where the fleet's safety draws it. Anything that protects your neighbours is included; anything that is work done on your site specifically is priced. - Included on every plan: malware scanning, the proactive WAF, and LVE plus CageFS isolation. - Sold as add-ons: one-click malware cleanup and remediation, per incident or as a subscription. - Also sold as add-ons: advanced protection tiers — enhanced WAF rules, priority scanning, bot management and DDoS tiers, and dedicated firewall rules. - Hack repair is a first-party Extra, bought from the dashboard alongside DB maintenance and speed optimisation. Extras are staff-fulfilled or automated; either way you are charged, the work is fulfilled, and you are notified when it is complete. - Cleanup is offered contextually — on a site the platform has already flagged — so you are not hunting for the right service while a site is compromised. ## Built for networks, not just single sites Most of our customers do not run one site. Scanning and enforcement are designed for operators managing hundreds of them. Because scanning runs on every worker rather than inside each site, adding sites does not add scanners to configure or licences to buy. A network of five sites and a network of two thousand get the same the same malware scanning, the same proactive WAF and the same isolation model. Enforcement policies are configurable per product line and per trigger, because a billing issue, an abuse signal and a legal takedown do not deserve the same escalation timing. Whichever path a site takes, the transition is logged, the reason is stated, and you are told how to resolve it. Footprint-Free plans carry free SSL, 4 GB of disk and 100 GB of bandwidth per site with more available at any time, daily backups held for 30 days, free migrations and a 30-day no-quibble money-back guarantee — the security baseline is part of that, not a line item on top of it. ## Frequently asked questions **Is malware scanning included, or do I pay extra for it?** Malware scanning is included on every plan, along with the proactive WAF and LVE/CageFS isolation. We include them because an infected site threatens its neighbours, the server's reputation and our IP ranges — so protection cannot be optional. What is priced separately is the remediation: one-click malware cleanup, per incident or as a subscription, plus advanced tiers such as enhanced WAF rules, priority scanning, bot management and dedicated firewall rules. **If a site on the same server is hacked, is mine safe?** It is contained rather than shared. Each site runs in its own CloudLinux LVE resource cage and its own CageFS filesystem view, so a compromised tenant cannot see your files, your database credentials or sensitive system files, and cannot drain the resources your site needs. Confirmed malware or phishing is taken offline and isolated for forensics on top of that. No host can promise a hosting neighbour will never matter at all, but the isolation model is specifically designed so a breach stops at the cage wall. **What happens the moment my site is flagged as infected?** The default policy moves the site to restricted: it stays visible, but outbound mail, cron and POST requests are turned off so the compromise cannot do further harm, and cleanup is offered. You are notified with the reason and the evidence, and the state lifts once the site is remediated. Severe or unresolved cases escalate to quarantine — offline, files locked, no execution — which is reversed after cleanup and review rather than automatically on a re-scan. **Can you clean an already-hacked site for me?** Yes. One-click malware cleanup handles remediation directly, and staff-run hack repair is available as a first-party Extra bought from the dashboard, routed to the right department with status updates as it progresses. If a clean restore is the better route, per-site backups are immutable, offsite and isolated from the running fleet, with tested restores — Footprint-Free plans keep daily backups for 30 days with one-click restore. **Will scanning slow my site down?** Scanning runs at the host level rather than inside your PHP requests, and per-site resource limits are enforced by LVE with database load throttled by MySQL Governor, so security work is not competing with your visitors for the site's own allocation. We do not publish benchmark figures for the scanner's overhead, so we will not claim a number we cannot show you. **What is a proactive WAF, and how is it different from a normal firewall?** A signature-based firewall reacts to attacks it has already seen. Imunify360's proactive WAF blocks known exploit techniques before a patch exists for the underlying vulnerability, which is what protects a site running a plugin with an unfixed flaw. It sits alongside the network firewall, brute-force protection and IP reputation filtering, all included on every plan. --- # Free automated migrations URL: https://zinndigital.com/features/migrations Bring your sites to Zinn Digital® without the manual grind. A self-service migration workflow pulls your files, database and email, rebuilds the site on our platform, rewrites URLs, verifies the result, and cuts over DNS when you are ready. Migrations are free with no limit on how many sites — and if you would rather we did it, our team moves them for you, free too. ## Connect your source, any way you have access Point the migration at wherever your site lives today. Every source below is self-service, free and unlimited — and if none of them suits you, our team will do it for you, free. - **cPanel, Plesk or DirectAdmin** — Sign in with the control-panel login your host gave you. We copy files, databases and email straight from the account and install nothing on your old server. - **FTP or FTPS** — For hosts that give you FTP and nothing else. We copy the files and tell you up front what an FTP login cannot reach, such as databases or mailboxes. - **An archive of the site** — Paste a link to a cPanel or Duplicator backup, or any zip or tar.gz of the site with its database dump, and we import it. - **SSH or SFTP** — Give SSH access and we pull files and — where the server allows it — databases over the connection for a clean, complete copy. - **The Zinn® Migrate plugin** — For hosts that only give you a WordPress login: install our free plugin on the old site, build the package, and paste the link it gives you. - **Not sure? Ask the assistant** — Type your old host's address and our free migration assistant works out what it runs, which ways in are open, and fills the form in for you. - **Or ask us to do it — free** — From the site's Restore & import tab, ask for a managed migration. An engineer moves it by hand, starts within 72 hours, and it costs nothing — however many sites. ## What the migration does, step by step Every migration runs as a durable Temporal workflow, so it retries around transient failures and reports progress as it goes rather than dying halfway through a big transfer. - Pulls your files and database from the source you connected - Provisions the target site from a blueprint on our platform - Runs an automatic search-replace to rewrite old URLs to the new ones - Fixes configuration so the site is wired up correctly on arrival - Verifies the result with HTTP checks and file checksums before you commit - Cuts over DNS to go live, then confirms the switch - Rolls back cleanly if anything looks wrong — you stay in control the whole way ## Run it yourself, watch it happen The whole process is self-service from your dashboard. Start a migration, follow the live progress as each stage completes, and cut over on your own schedule — there is no ticket queue and no waiting on a support engineer to do it for you. Resellers and agencies run the same workflow across many sites; our own staff use exactly the same pipeline internally, so nothing about it is second-class. Because the workflow verifies before it cuts over and can roll back at any point, moving a site carries far less risk than a manual migration. And with no vendor lock-in on the platform, choosing us is never a one-way door — the same freedom to move applies on the way in and the way out. ## The four things people are actually worried about None of these is unreasonable. Everybody who has moved a site once has been bitten by at least one of them, so here is what we do about each. - **“It will go down while it moves.”** — It will not, because nothing points at us until you say so. The copy runs while your current host keeps serving every visitor; you look at the site running here, and only then change a nameserver. - **“Something will be missing and I will not notice.”** — That is why the migration is verified rather than declared finished: the result is compared against the source, and a difference is reported to you rather than left for a customer to find. - **“It is free until it turns out to be complicated.”** — Free means free: every site, every plan, no limit, including the awkward ones. When the automation cannot reach a site, an engineer moves it by hand — and that is free too. You never pay for a migration. - **“I will have to redo my email.”** — Only if you want to. Moving a website and moving its mail are separate decisions and we do not force them together — plenty of customers move the site and leave mail exactly where it is. ## Ask before you move anything Tell us what you are on now and what is on it. Ask Zinn® answers from our knowledge base and today's price list; a person answers anything it cannot. - **Ask Zinn®** — Answers from the knowledge base and today's prices - **Email** — office@zinndigital.com - **Managed migration** — An engineer does it for you, free ## Frequently asked questions **Are migrations really free?** Yes — every site, on every plan, with no limit on how many. Self-service migration is free and it is the fastest route. If you would rather we did it, ask from the site's Restore & import tab and an engineer moves it for you, also free. **Which sources can I migrate from?** Every common one, all self-service: your control panel login (cPanel or WHM, Plesk, DirectAdmin), FTP or FTPS, SSH or SFTP, or an archive of the site — a cPanel or Duplicator backup, any zip or tar.gz with its database dump, or the package our own Zinn® Migrate plugin builds on hosts that only give you a WordPress login. Not sure what your host runs? The free migration assistant checks the address and fills the form in. And if you would rather not do it yourself, our team will, free. **Will my site go down during the move?** No. The workflow rebuilds and verifies your site on our platform first, and only cuts over DNS once you are ready. The live site keeps serving until the switch. **What if something goes wrong mid-migration?** The migration runs as a durable workflow with progress and rollback surfaced in your dashboard. If a verification check fails or something looks off, you can roll back cleanly rather than being left with a half-moved site. **Do I have to do the migration myself?** No, but it is the fastest way: you run it end to end from the dashboard whenever it suits you, with the same workflow our own staff use. If you would rather not, ask us from the site's Restore & import tab and an engineer does it for you — free, started within 72 hours. --- # Your CDN and DNS, chosen per site URL: https://zinndigital.com/features/providers CDN and DNS are a per-site choice, selected at deploy and controllable from the dashboard and the MCP. The Footprint-Free line rotates across a pool for footprint diversity; the Mainstream line picks per site. Every provider supports both the apex and www — you pick the canonical, the other redirects — and you can always bring your own account. ## CDN providers The content-delivery networks the platform drives, plus anything you bring. On the Footprint-Free line these rotate across a pool; on the Mainstream line you select per site. - **Cloudflare** — Ours or yours. The multi-account footprint pool behind the Footprint-Free line, and a first-class Mainstream CDN — full SSL enforced, never flexible. - **BunnyCDN** — Ours or yours. A cheap, fast footprint-pool provider with no apex or www limitations. - **CDN77** — Bring your own. A capable edge; the apex-and-www rule is handled for you. We do not run CDN77 accounts ourselves, so this one is yours to hold. - **KeyCDN** — Bring your own. Connect your KeyCDN account and we drive it — zones, aliases, HTTPS and purge — with apex and www handled our end. - **Fastly** — Bring your own. A more advanced edge with instant purge; connect your Fastly account and we drive the service, its domain and its TLS. - **Gcore** — Bring your own. A fast global edge; connect your Gcore account and we drive its CDN resources and purge. - **Amazon CloudFront** — Bring your own. The commonest account customers already have. Note CloudFront needs your own certificate in the us-east-1 region before it will serve your domain — we tell you if it is missing. - **Akamai** — Bring your own. You keep your property configuration in Akamai; we detect the hostname, show which edge it maps to, and purge it from here. - **Bring your own CDN** — Connect an account you already run — full integration for popular providers, or DNS-delegation passthrough for anything else. ## DNS providers The nameserver providers in the pool. Diversity here is a footprint feature in its own right, so the set favours cheap, anycast providers you can spread a network across. - **Cloudflare** — Live. Free at any scale with strong anycast. On Cloudflare CDN, DNS is always Cloudflare — the zone and the CDN are one. - **Zinn® nameservers (ours)** — Live. Zinn-branded nameservers for the Mainstream line. A branded nameserver is itself a footprint, so it is not used on the PBN line. - **ClouDNS** — Live. Cheap, anycast and predictably priced — good pool diversity. - **Azure DNS** — Live. Full apex and arbitrary-subdomain support; the old www-only behaviour was a footprint flag, not a provider limit. - **Bunny DNS** — Live. Cheap anycast that pairs with the BunnyCDN account, for near-zero-cost nameserver diversity. - **deSEC** — Live. Free, non-profit anycast with DNSSEC and an API — near-zero-cost diversity for the pool. Bring your own DNS is supported too. - **Hetzner DNS** — Live. Free DNS hosting with a straightforward API from an established European host — more anycast diversity at no per-zone cost. - **Amazon Route 53** — Bring your own. The DNS most AWS customers already run; connect the account and we drive the zone and its records from here. - **DigitalOcean DNS** — Bring your own. Free DNS on an account many teams already have; connect it and we drive the zone and its records from here. ## The rules that make any combination work A few locked rules keep provider choice flexible without ever producing a broken or duplicate-content setup. - Every CDN and DNS provider supports both the apex (non-www) and www — you choose the canonical at deploy and the other 301-redirects to it. - On Cloudflare CDN, DNS is always Cloudflare; on every other CDN you pick the DNS provider freely from the pool. - On the Footprint-Free line the platform rotates providers across a pool for footprint diversity; on the Mainstream line you choose per site. - CDN and DNS are a deploy-time, per-site choice on the dashboard and the MCP, so bulk and AI-driven selection is first-class. - You can bring your own CDN or DNS account and use it alongside ours, across both product lines. ## Frequently asked questions **Which CDN providers can I use?** You can bring your own account on Cloudflare, BunnyCDN, CDN77, KeyCDN, Fastly, Gcore, Amazon CloudFront or Akamai, and we drive it for you. On the accounts we run ourselves — Cloudflare and BunnyCDN — the Footprint-Free line rotates across a pool for footprint diversity, and on the Mainstream line you pick the provider per site. **Which DNS providers can I use?** Cloudflare, ClouDNS, Azure DNS, Bunny DNS, deSEC and Hetzner DNS are all live, plus bring-your-own on Amazon Route 53 and DigitalOcean DNS. Our own branded nameservers, ns1 and ns2 at zinndigital.com, answer on global anycast and are a Mainstream-line option — a branded nameserver is itself a footprint, so it is not used on the PBN line. **Does every provider support a bare domain, not just www?** Yes. Every CDN and DNS combination supports both the apex (example.com) and www.example.com. You choose the canonical at deploy and the other 301-redirects to it, so there is no duplicate-content split and no www-only limitation. **Can I mix any CDN with any DNS?** Almost. On every CDN except Cloudflare you pick the DNS provider freely from the pool. The one fixed rule is Cloudflare: on Cloudflare CDN, DNS is always Cloudflare, because the zone and the CDN are the same thing there. **Why so many DNS providers?** For the Footprint-Free line, nameserver diversity matters as much as cost — every site sharing one nameserver set is a footprint. Running a spread of cheap, anycast providers gives that diversity without a per-zone bill, which is why the pool favours flat and free-priced providers. --- # Security that contains problems before they spread URL: https://zinndigital.com/features/security Every site we host runs inside its own kernel-level cage, watched by a proactive firewall and malware scanning. One compromised or attacked site cannot see its neighbours, drain the server, or drag anyone else down. This is the stack we built to host 700,000+ sites worldwide, and the baseline is included on every plan. Availability: per-site database throttling is in active development and not yet available. Everything else described here is live today. ## Isolation at the kernel, not just the config file CloudLinux LVE and CageFS give each site its own resource cage and its own filesystem view. A runaway process, a traffic spike or a breach is contained inside that cage instead of spilling onto the server. - **Per-site resource caps (LVE)** — Lightweight Virtual Environments cap CPU, RAM, IO, IOPS, processes and entry-processes per site. A site under attack or running away is throttled inside its own cage, so one bad neighbour cannot take down the server. - **Filesystem isolation (CageFS)** — Each tenant gets an isolated filesystem view and cannot see other tenants, other sites, or sensitive system files. A breach on one site is contained, not shared. - **Per-site database throttling (MySQL Governor)** — CloudLinux MySQL Governor throttles per-site database usage, so one site's heavy queries cannot slow the server for everyone else. Redis object cache offloads read pressure on top. - **Hardened per-site PHP** — CloudLinux alt-PHP gives each site its own version selector, its own extensions and hardened settings, with LSAPI workers bounded by the site's LVE limits. ## Malware and exploit defence, always watching Imunify360 runs on every worker as a single integrated layer: it looks for compromise, blocks exploits before they land, and can clean an infection in one click. - Malware scanning on every site, included on every plan — because an infected site threatens its neighbours, the server's reputation and our IP ranges. - A proactive WAF that blocks known exploits before a patch is even available, plus a network firewall, brute-force protection and IP reputation filtering. - One-click malware cleanup and remediation when something does get through — available per incident or as a subscription. - Suspected compromises are cross-checked against Google Safe Browsing, PhishTank and SURBL/APWG blocklists, and correlated with mail-log anomalies to catch spam-sending sites early. ## Layered DDoS defence, so one attack is not everyone's outage Volumetric floods are absorbed at the edge, network-level attacks are filtered upstream, and the server layer contains whatever reaches it. An attack aimed at one site stays that site's problem. - **Edge (L7)** — Cloudflare absorbs volumetric floods with an L7 WAF, per-site rate limiting, bot management and managed challenges before traffic ever reaches origin. - **Network (L3/4)** — Provider-level DDoS protection filters network-layer floods upstream of the fleet, with advanced enterprise mitigation available for high-risk sites. - **Server** — LiteSpeed connection and request throttling, Imunify360's network firewall, per-IP connection limits and LVE entry-process caps keep a flood against one site contained to that site's cage. ## Baseline included, advanced protection when you need it The essentials protect the whole fleet, so they are never optional. Heavier protection is there to buy when a site's risk profile calls for it. - Included for everyone: LVE and CageFS isolation, the proactive WAF, and malware scanning. - Upsold as add-ons: one-click malware cleanup and remediation, enhanced WAF rules, priority scanning, bot management and higher DDoS tiers, and dedicated firewall rules. - Enforcement is graduated and reversible: instead of a blunt on/off suspend, sites move through throttled, restricted and suspended states, each logged with a reason, notified to you, appealable, and auto-recovering once the cause clears. - Suspended sites show a branded, reason-specific holding page rather than a broken one, and every privileged action is audit-logged for your compliance trail. - Per-site backups are immutable, offsite and isolated from the running fleet, with tested restores — so even a worst-case compromise is recoverable. - Encryption in transit is included too: a free TLS certificate is issued for your domains and renewed automatically before it expires, and one switch forces every visitor onto HTTPS. ## Frequently asked questions **Is security included, or is it an expensive add-on?** The baseline is included on every plan: LVE and CageFS kernel-level isolation, the proactive WAF, and malware scanning. We include these because an infected or abusive site threatens its neighbours and our IP reputation, so we cannot leave protection optional. One-click cleanup, enhanced WAF rules, priority scanning and higher DDoS tiers are available as add-ons when a site needs them. **If one site on the server is attacked or hacked, does it affect mine?** No. Every site runs inside its own CloudLinux LVE resource cage and CageFS filesystem view. A runaway, attacked or compromised site is throttled and contained inside its own cage — it cannot see your files, drain shared resources, or take the server down. MySQL Governor applies the same per-site limits to database load. **What happens if my site does get infected with malware?** Every site we host is scanned for malware every day, and anything we find is flagged straight away. You can trigger a one-click cleanup to remediate it, and severe or unresolved cases are quarantined offline with files locked so the infection cannot spread while evidence is preserved. Because backups are immutable, offsite and isolated from the running fleet, a clean restore is always available as a fallback. **How do you handle DDoS attacks?** Defence is layered. Cloudflare absorbs volumetric and L7 floods at the edge with per-site rate limiting and bot management; provider-level protection filters network-layer attacks upstream; and at the server, LiteSpeed throttling, the Imunify360 firewall and LVE entry-process caps keep a flood against one site contained to that site. Advanced bot management and DDoS tiers are available for higher-risk sites. **What is the proactive WAF and how is it different from a normal firewall?** Imunify360's proactive WAF blocks known exploit techniques before a patch exists for the underlying vulnerability, rather than only reacting to signatures after the fact. It sits alongside a network firewall, brute-force protection and IP reputation filtering, all included on every plan. **Do I get an SSL certificate, and does it renew itself?** Yes. A free TLS certificate is issued for your site's domains and renewed automatically before it expires, so there is nothing to remember and nothing to install. One switch on the site's SSL tab forces every visitor onto HTTPS. If you would rather use a certificate you bought elsewhere you can install it yourself, and when you need higher assurance we sell wildcard, multi-domain and extended-validation certificates alongside the free one. --- # Every tool your site needs, in the browser URL: https://zinndigital.com/features/site-tools VS Code in the browser on every site we host on our own fleet, a jailed SSH shell on the shared platform, wp-cli, phpMyAdmin, a file manager, per-site cron and environment variables, and full control of PHP — all in the dashboard, all scoped to your site alone. This is a developer's control surface, not a settings page. Availability: per-site database throttling is in active development and not yet available. Everything else described here is live today. ## A real workspace, not a hosting panel Most hosting control panels stop where the work starts. You can toggle a setting or two, then you are expected to open an FTP client, find a database tool, SSH in from somewhere else and stitch the job together yourself. Zinn Digital® puts the whole toolchain inside the site itself: open a site in the dashboard and the editor, terminal, database, files, cron, environment and logs are already there, already authenticated, already pointed at the right site. Every one of those tools runs inside the site's own cage. CloudLinux CageFS gives each tenant an isolated filesystem view, so a shell, an editor or a file manager can only ever see that tenant's files — not other sites, not other customers, not sensitive system paths. The convenience of a shared panel with the separation of a private box. ## Edit, run and ship from the browser The editing surface is a full IDE, not a textarea with syntax colouring. - **VS Code in the browser (code-server)** — The real editor, running against your site's files: multi-file search and git built in. Open a site, make the change, commit it — no local checkout and nothing to install. - **wp-cli in the panel terminal** — wp-cli is available in the panel terminal and over SSH. Search-replace a domain, activate a plugin, flush rewrites, export a database, run a cron event on demand — the standard WordPress toolkit, in the same window as your code. - **AI assistance, alongside the editor** — The dashboard AI assistant runs on your own model keys, reading and editing files and running wp-cli for you. Bring your own model; the platform provides the hands. It is a separate surface in the dashboard — assistance inside the editor itself is in active development and not yet available. - **Jailed SSH, SFTP and FTP** — Prefer your own tools? Connect over SSH or SFTP and get the same jailed view of the same files. On plans that include SSH you get a real shell inside the same CageFS jail: you add your public key in the dashboard, and you log in as the site's own account. Footprint-Free plans get SFTP rather than a shell. Access keys and credentials are managed in the dashboard on a least-privilege basis, and privileged actions are audit-logged. ## PHP and runtime, under your control Per-site runtime configuration — not a server-wide setting you have to raise a ticket to change. - **Per-site PHP version** — Choose the PHP version for each site independently using CloudLinux alt-PHP. Run a legacy plugin on an older branch while the site next door runs current — no shared runtime, no compromise version for the whole account. - **Editable PHP settings** — memory_limit, max_execution_time, upload and post size and the rest are yours to set within your entitlement, so an import script or a large media upload does not need a support conversation. - **Extensions on demand** — Enable or disable PHP extensions per site — imagick and gd, redis and memcached, bcmath, intl, soap and more — so a site carries exactly the extensions it needs and nothing it does not. - **Dedicated PHP workers** — Each site gets its own LiteSpeed LSAPI workers, with the count configurable within your tier and bounded by the site's LVE entry-process limit. Concurrency is yours; a neighbour's traffic spike is not your queue. - **Per-site object cache** — Redis or Memcached object caching per site, with the WordPress object-cache drop-in wired in — dynamic pages stay fast under load instead of hammering the database. - **Cron and environment variables** — Manage WP-cron and real system cron per site, and set environment variables for the site's runtime — API keys, feature switches and stage flags — without editing wp-config by hand. ## Databases and files, first-class Direct access to the two things developers actually need to reach. - **phpMyAdmin and Adminer, embedded** — Both database tools are built into the dashboard and single-sign-on'd — click through from the site and you are already authenticated against the right database. No separate credentials to store or share. - **MariaDB, multiple databases and users** — Each site runs on MariaDB with as many databases and users as the project needs, plus a remote-access toggle when you want to connect an external client or reporting tool. - **MySQL Governor keeping the peace** — Per-site database usage is throttled by CloudLinux MySQL Governor, so one site's heavy queries cannot slow the server for everyone else — including yours. - **File manager in the panel** — A full file manager (FileGator), embedded and SSO'd, for uploads, permissions, archives and quick edits when opening the IDE is more ceremony than the job deserves. - **Access, error and PHP logs** — Read the site's access, error and PHP logs from the dashboard while you work — the fastest route from 'it broke' to the line that broke it. ## WordPress-aware, end to end The tools know they are managing WordPress, so the common jobs are one action rather than ten. - One-click login to WP admin — no password juggling between sites, and no shared admin credentials floating around a team. - Install, activate, update and remove plugins and themes from the panel or over wp-cli, whichever suits the task. - Clone to staging, work safely, then push to live when it's right. - Take a static-HTML snapshot of a site when you want it served with no PHP, no database and nothing to exploit. - Rebuild a site from its Wayback Machine history when no backup exists — pick any archived date, get a working site out. - Roll a plugin out in bulk across a whole set of sites — our staff tooling can push plugins to every site, a single server's sites or a single customer's sites. - Find every outbound link your sites carry, and change an anchor or a destination across hundreds of posts in one job — with a preview of what it would touch before it writes, and a one-click undo that restores exactly what it replaced. ## Team access, scoped and logged Access to these tools follows your organisation's roles. Customer memberships carry an owner, billing, dev or read-only role, and permissions resolve from those roles — the dev role is a working developer's role, and deploying or pushing to live is deliberately not part of it. Staff access is equally bounded by its own department roles and permissions. Programmatic access uses per-organisation API keys and OAuth clients with granular scopes — read-only, billing or provisioning — so an automation gets exactly the reach it needs. Every privileged action is audit-logged with actor, action and target, which means the answer to 'who changed the PHP version on Tuesday' is a lookup rather than an argument. If you would rather drive all of this from an AI tool, the same capability is exposed through our hosted MCP server — run wp-cli, clone to staging, purge cache or restore a snapshot from Claude, Cursor or any MCP-capable agent, under the same role scoping and audit trail. ## What's available on which product line Mainstream hosting is full self-service: the complete tool set, exposed and editable within your plan's entitlements. Footprint-Free hosting is deliberately more standardised and locked down, because a network's whole value depends on its sites presenting a uniform, unremarkable surface — configuration freedom is a footprint of its own. Entitlements do the rest of the gating. PHP workers, disk and extensions scale with your tier, so the shape of the tooling is the same on every plan while the headroom grows with it. If you are unsure which line fits, start on the card-free 14-day trial and look at the panel yourself before deciding. ## Frequently asked questions **Is the Web IDE really VS Code?** Yes — it is code-server, VS Code running in the browser against your site's files. Available on every site we host on our own fleet; a site you have chosen to deploy elsewhere is edited where it is hosted. You get multi-file search and git, and it edits the LIVE site: a file you save is on the public internet the moment it is written, though a static file may keep serving from the CDN cache for up to four hours. AI assistance inside the editor is in active development and not yet available. **Do I get SSH access, and how isolated is it?** On the shared platform you get a jailed shell over SSH, plus SFTP and FTP, with keys and credentials managed in the dashboard on a least-privilege basis. Sites on our own fleet get SFTP rather than a shell — the account is created with `/sbin/nologin`. The jail is CloudLinux CageFS: each tenant gets an isolated filesystem view and cannot see other tenants, other sites or sensitive system files, which contains a breach rather than letting it spread. No isolation model makes compromise impossible, so malware scanning, the proactive WAF and audit logging run alongside it. **Can I change the PHP version and extensions myself?** Yes. PHP version is selected per site via CloudLinux alt-PHP, settings such as memory_limit, max_execution_time and upload size are editable within your entitlement, and extensions like imagick, gd, redis, memcached, bcmath, intl and soap are toggled per site. Your PHP worker count is configurable within your tier, bounded by the site's LVE entry-process limit. **How do I get to the database?** phpMyAdmin and Adminer are embedded in the dashboard and single-sign-on'd, so you click through from the site and you are already connected. Each site runs MariaDB and can have multiple databases and users, with a remote-access toggle for external clients. MySQL Governor throttles per-site database usage so heavy queries on one site cannot slow the server. **Can I run cron jobs and set environment variables?** Yes. Per-site cron management covers both WP-cron and real system cron, and environment variables are set per site for the site's runtime — so scheduled tasks and configuration live with the site rather than buried in a file you have to remember to migrate. **Are all these tools available on Footprint-Free plans?** Mainstream hosting is full self-service with the complete tool set. Footprint-Free is intentionally more standardised and locked down, because per-site configuration variation is itself a footprint. Entitlements gate the rest — workers, disk and extensions — so what you can adjust scales with your tier. **Who on my team can use these tools?** Access follows organisation roles: owner, billing, dev and read-only for customers, with permissions resolved from those roles. The dev role does not include deploying or pushing to live. Programmatic access uses per-organisation API keys and OAuth clients with granular scopes, and every privileged action is audit-logged with actor, action and target. --- # Deploy from the repository you already use — nine places to put it URL: https://zinndigital.com/features/source-control Connect the GitHub or GitLab account you work in and deploy straight from a branch: to Cloudflare Pages, GitHub Pages, GitLab Pages, Netlify, Vercel, Render, Azure Static Web Apps or AWS Amplify — or onto our own managed hosting, where the repository and the site's files stay in sync in both directions. Every connection shows the privileges it needs, is checked against the provider's API before it is stored, and lives in Vault. You can sign in with GitHub or GitLab too. ## Connect once, and see what you are agreeing to A connection is a credential you are handing someone else. Ours says what it needs before you make it, proves it works before it stores it, and can be taken back from either end. - **The privileges, stated up front** — Before you create a token we tell you what it has to be able to do and why. No blanket scope because it was easier to ask for, and no discovering after the fact that we wanted more than the job needed. - **Checked against the provider, not accepted on trust** — We call the provider's own API with your token before storing it. A wrong, expired or wrongly-scoped token is refused at the form rather than accepted, shown as healthy, and failing at the first real deploy. - **Stored in Vault, and nowhere else** — Not in our code, not in an environment file, not in a log and not on a command line. Resolved at the moment it is used, by the workload that uses it. - **More than one account, picked per site** — Connect a personal account and an organisation's, or two organisations'. Each site chooses which one it deploys from, so a client's repository and your own never share a credential. ## Nine places a repository can land Eight managed edge hosts and our own fleet. The destination is a property of the site, not of the connection, so the same repository can publish one branch to a Pages host and another site can run on our hardware. - **Cloudflare Pages** — Unlimited bandwidth, commercial use permitted, and apex domains handled on the same provider that usually holds your DNS zone. It is the first destination we reach for, for those reasons. - **GitHub Pages** — Publish straight from the repository the code already lives in. Flagged on the Footprint-Free line, because the shared github.io infrastructure is itself a footprint. - **GitLab Pages, Netlify, Vercel and the rest** — GitLab Pages, Netlify, Vercel, Render, Azure Static Web Apps and AWS Amplify are all destinations you can point a site at, with the same connection and the same deploy history. - **Our own managed hosting** — A full application rather than a built bundle — WordPress, PHP, Node. This is the destination that gets two-way sync, so the files on the box and the branch stay in step. - **Sites on somebody else's edge** — A site published to a host we do not own still spends an allowance and still appears in your dashboard with its deploys, its uptime and its SEO data beside everything else you run. - **Or edit it here** — The in-browser editor works on the same files two-way sync pushes back, so a quick fix from the dashboard becomes a commit on your branch instead of a change nobody can find later. ## Your repository and your live site, in step Switch it on and the site's own files are committed back to your branch, while commits on that branch come back down to the site. It works on every site we host, on every line — the only requirement is that the machine underneath can run Git against its files, which is asked of the server rather than assumed from the plan. You choose which directory syncs, because a WordPress customer wants their theme tracked and not forty thousand core files. And it is off until you turn it on: enabling a sync is a decision about somebody else's repository, and a migration must never take it for you. - Edits on our hardware become commits on your branch - Commits on your branch come back to the site - Sync one directory — a theme, a plugin — not the whole document root - Off by default, including on every site that already exists ## Publish a directory, or let your own CI build it Two modes, and the difference is where the build runs. Both end at the same place: a ref we fetch and publish, with the commit recorded against the deploy. - Publish mode takes your branch as it is and publishes the directory you name — blank means the repository root. - CI mode runs your build command in your provider's own pipeline and commits the output to a separate publish branch, which we fetch like any other ref. - The branch a deploy publishes from is always named explicitly, never “the default branch” — a default can change under you, and a history that cannot say which branch it published is not a history. - Auto-deploy is on by default and can be turned off without removing the webhook, so you can watch deliveries arrive before you let them act. - Every deploy records its commit, its outcome and its time, and runs in the background — the page updates as the build completes. - Disconnecting removes exactly the webhook we created, by its id, and nothing else on your repository. ## From repository to live site 1. **Connect the account** — GitHub or GitLab, under Connections. The privileges are listed before you make the token and it is checked against the provider before it is stored. 2. **Point a site at a repository** — Owner, repository, branch, and whether we publish a directory or fetch what your CI built. We register the push webhook as part of it. 3. **Push, or press the button** — A push to the nominated branch starts a deploy, or you can deploy on demand from the site's Deploy tab. Builds run in the background. 4. **Watch it, and sync back if you want to** — The deploy history shows what was published and when. Turn on two-way sync and the edits you make here come back as commits on your branch. ## “Connected but never delivered” is a state we will actually tell you about A repository connection that looks healthy and receives nothing is the classic silent failure — a token with the wrong scope, a delivery blocked at the provider, a hook somebody removed by hand. It is invisible on every other screen, so the repository card carries it directly: when the provider last delivered to us, and what it said. Deliveries are signature-checked before we act on them, with each provider's own scheme rather than one we assumed applied to all of them. A delivery that does not verify is refused and recorded, not quietly ignored. - Last delivery time and message, on the card - Never delivered is stated, not left blank - Signature verified per provider before anything runs - The hook we created is removed by id when you disconnect ## Sign in with GitHub or GitLab — or Google, or Microsoft Alongside an email address and a password, you can sign in to your Zinn Digital® account with GitHub, GitLab, Google or Microsoft. The identity layer runs the handshake; we never see your provider password, and linking a social account to an existing Zinn® account still has to be confirmed by email. Signing in with GitHub and connecting GitHub for deploys are separate decisions and separate credentials. Doing one does not do the other, and removing one does not remove the other. - GitHub, GitLab, Google and Microsoft sign-in - Passkeys and two-factor on the same account - Sign-in and deploy credentials stay separate ## Frequently asked questions **Which source-control providers can I connect?** GitHub and GitLab. Connect the account you already work in and we can deploy from its repositories, register a push webhook on them, and — if you want it — sync your site's files back the other way. Both go through the same connected-account seam, so everything below is true of either. **Can I sign in with GitHub or GitLab?** Yes, and with Google or Microsoft. Alongside an email address and a password you can sign in to your Zinn Digital® account with any of the four. The identity layer handles the handshake and we never see your provider password. Signing in with GitHub is a separate thing from connecting GitHub for deploys — you can do either, both, or neither. **Where can I deploy a repository?** To Cloudflare Pages, GitHub Pages, GitLab Pages, Netlify, Vercel, Render, Azure Static Web Apps or AWS Amplify for a static or built site — or onto our own managed hosting, where the repository and the site's files stay in sync in both directions. You pick the destination for the site; the repository connection is the same either way. **Can you build my site, or does it have to be pre-built?** Either. In publish mode we take the branch as it is and publish the directory you name. In CI mode your provider's own pipeline runs your build command and commits the output to a separate publish branch, which we then fetch like any other ref. The second keeps your build in your own CI, where your secrets and your caching already are. **Does a push deploy automatically?** By default, yes — we register a webhook on the repository and a push to the branch you nominated starts a deploy. You can turn that off and keep the webhook, which is more useful than it sounds: the delivery is still recorded, so you can watch your pushes arriving before you let us act on them. **What is two-way sync?** Edits made on our hardware become commits on your branch, and commits on your branch come back to the site. It is off until you switch it on, because turning it on is a decision about somebody else's repository and we will not take that for you. You choose which directory syncs — usually a theme or a plugin, not forty thousand WordPress core files. **What happens if both sides changed?** Nothing is overwritten and nothing is pushed. The sync stops, tells you the branch moved past the commit we based on, and asks which side you want — keep the repository, or keep the site. A site that has never synced and points at a branch that already has commits is its own state too, and it asks rather than guessing which one is the truth. **How is my access token protected?** We show you the privileges the connection needs before you create it, check the token against the provider's own API on entry — so a token that is invalid or wrongly scoped is never stored at all — and only then write it to Vault. It never touches our code, a log, an environment file or a command line. Revoke it at the provider or remove the connection here, whenever you like. **How do I tell whether you are actually receiving my pushes?** The repository card shows when the provider last delivered to us and what it said. Never delivered is the single most useful diagnostic on that screen, because “connected but never delivered” is exactly what a mis-scoped token or a blocked delivery looks like — and it is invisible everywhere else. Every delivery is signature-checked before we act on it. **Can I use Pages deployment on the Footprint-Free line?** It is offered and it is flagged. GitHub Pages and GitLab Pages share provider infrastructure and public github.io and gitlab.io hostnames, and that is a footprint — the one thing that line exists to avoid. For a zero-footprint network, deploy onto isolated hosting instead. Everywhere else, Pages is first-class. **Why do I have to choose Vercel explicitly?** Because its free tier is licensed for non-commercial use only. We infer a destination from the accounts you have connected where that is safe, and Vercel is deliberately excluded from that inference — connecting an account must never quietly place a commercial site somewhere its licence does not permit. Choose it and it works exactly like the others. **Can I see what was deployed and when?** Yes. Every deploy records the commit it published, when it ran and how it finished, and the site's Deploy tab shows the history with the live URL beside it. Deploys run in the background, so the page updates as the build completes rather than making you sit on a spinner. --- # Staging, push-to-live and git deploys URL: https://zinndigital.com/features/staging Spin up a staging copy in one click, test your changes safely, then push to live when you are ready. Connect a git provider and every push builds and deploys itself. When something goes wrong, roll back to the previous release in seconds. ## Test on staging, ship with confidence Every site gets a full staging environment, not a guess. Clone production, work on the copy, then merge your changes back when they are proven. - **One-click staging** — Create a staging copy of your live site with its files and database intact, on the same stack and blueprint as production, so what you test is what you ship. - **Push-to-live** — When your changes are ready, push staging to production in one action. No manual file copying, no fragile database exports. - **Rollback to previous release** — Every deploy is a versioned release. If a change misbehaves, roll straight back to the last known-good release without a restore ticket. - **Same workflow, every stack** — Managed WordPress, WooCommerce, PHP, static HTML or Node — staging and push-to-live work the same way across your sites. ## Git-based continuous deployment Connect a git provider once and your repository becomes the source of truth. Push code and the platform builds and deploys it for you. Connect GitHub, GitLab or Bitbucket via OAuth and your deploy keys are stored in the encrypted credential store, never in plain config. A webhook fires on every push, which triggers a durable build-and-deploy pipeline that runs the build steps for your stack — Composer, npm and the rest — before releasing to the site. Map branches to environments the way your team already works: main to production, staging to staging, or whatever convention you prefer. Merge to a branch and the matching environment updates on its own, so promoting a change is just a git push. - Connect GitHub, GitLab or Bitbucket over OAuth, with deploy keys kept in the credential store - Webhook on push kicks off a durable build-and-deploy pipeline - Per-stack build steps run automatically (Composer, npm and more) - Branch-to-environment mapping — for example main to production, staging to staging - Roll back to any previous release when you need to - Deploys run as durable, retryable workflows, so a hiccup mid-build never leaves a half-deployed site ## Built for the way you build Continuous deployment should not mean surrendering control. You decide which branch maps to which environment, when a change is promoted, and when to fall back. The pipeline handles the mechanical work — pulling code, running builds, releasing atomically — so a deploy is boring, repeatable and reversible. If you use our AI Pack, the assistant can code changes and push them to your sites through the same pipeline, so an AI-authored change goes through exactly the same build, deploy and rollback path as anything you write by hand. ## Frequently asked questions **How does one-click staging work?** Staging creates a full copy of your live site — files and database — on the same stack and blueprint as production. You test your changes on the copy, then use push-to-live to promote them to production in one action. **Which git providers can I connect?** GitHub, GitLab and Bitbucket. You connect over OAuth and your deploy keys are stored in the encrypted credential store, never in plain config files. **What happens when I push code?** A webhook fires on push and starts a durable build-and-deploy pipeline. It runs the build steps for your stack — Composer, npm and the like — and releases the result to the environment mapped to that branch. **Can I map different branches to different environments?** Yes. Branch-to-environment mapping lets you point, for example, main at production and staging at staging. Merge to a branch and the matching environment deploys automatically. **What if a deploy breaks the site?** Every deploy is a versioned release, so you can roll back to the previous release without a restore ticket. Because deploys run as durable, retryable workflows, a failure mid-build never leaves the site half-deployed. --- # Subdomains that behave like real sites URL: https://zinndigital.com/features/subdomains Point app, shop, docs or staging anywhere you like and get a genuine, fully isolated site behind it: its own stack, database, cache, backups and resource cage. Full DNS record control, automatic SSL including wildcards, and one-click staging subdomains. Availability: per-site database throttling is in active development and not yet available. Everything else described here is live today. ## A subdomain here is a full site, not a folder On most hosts a subdomain is a directory with a rewrite rule in front of it. Here it is a first-class site record with its own blueprint version, its own placement on the fleet and its own isolation boundary. Whatever you can do to a primary domain, you can do to a subdomain. - **Its own stack and blueprint** — Each subdomain site is built from a versioned blueprint and runs its own stack type and runtime: managed WordPress, WooCommerce, PHP, static HTML or Node. Your docs subdomain can be static HTML while the root runs WordPress, with no compromise between them. - **Its own database and object cache** — A MariaDB database per site, LiteSpeed LSCache full-page caching and a per-site Redis or Memcached object cache. Nothing is shared with the parent site, so a heavy subdomain cannot evict the parent's cache or crowd its queries. - **Its own isolation cage** — CloudLinux LVE caps CPU, RAM, IO, IOPS and entry processes per site, CageFS gives each site its own filesystem view, and MySQL Governor throttles per-site database load. A runaway subdomain is contained inside its own cage. - **Its own backups and restore path** — Daily backups held for 30 days with one-click restore, per site. You can roll a subdomain back to yesterday without touching the parent site or any of its siblings. ## DNS records you actually control Subdomains are a DNS problem before they are a hosting problem, so the DNS layer is exposed properly rather than hidden behind a form with two fields. Every registrable domain you host gets a DNS zone managed through our DNS driver seam. You get record CRUD across the record types you would expect, so adding app, shop, docs, mail or a wildcard host is a record edit, not a support ticket. Zone state is reconciled idempotently against the provider, which means a half-applied change or a retried edit converges on the state you asked for rather than leaving your zone in an ambiguous middle. Registrar and DNS are deliberately decoupled: you can register a domain with us and keep DNS elsewhere, or keep the domain at your existing registrar and simply point a subdomain at us. We verify nameserver delegation and activation before we call a domain live, so you find out that a record is wrong from the platform rather than from a customer. - Full record management per zone, including wildcard hosts - Idempotent zone reconciliation, so a retried or partial change converges instead of drifting - Premium anycast DNS included on every plan, across a pool of independent providers - Nameserver and activation checks before a domain is treated as live - Bring a domain you already own: verify ownership, point DNS, keep your registrar - No lock-in on the way out, including auth-code retrieval and registrar unlock for transfers ## Certificates, delivery and speed on every host A subdomain that is slow or shows a certificate warning is worse than no subdomain at all, so the delivery path is the same one the primary domain gets. - **Free SSL, including wildcards** — Let's Encrypt certificates are issued and renewed automatically. Use a wildcard certificate to cover every subdomain at once, per-host certificates where you want them separated, or upload your own custom certificate. - **LiteSpeed and HTTP/3** — Every site is served by LiteSpeed with HTTP/3 enabled, so a subdomain gets the same connection-level performance as the root domain rather than a second-class vhost. - **Full-page and object caching** — LSCache full-page caching plus a per-site Redis object cache, with coordinated purge from the dashboard or from inside WordPress. Purging the parent does not blow away your subdomain's cache. - **CDN account of your choosing** — Deploy through our CDN and Cloudflare account pool or connect your own accounts and choose which account a given site deploys to. Delivery is a decision you make, not one we make for you. ## Staging subdomains and push-to-live The most common reason to want a subdomain is to have somewhere safe to break things. That path is built in and ungated on Mainstream plans. Clone to staging creates an isolated copy of a live site on a staging subdomain, with its files and database intact, on the same stack and blueprint version as production. You work on the copy with the full toolset: jailed SSH and SFTP, wp-cli, the browser-based VS Code editor, phpMyAdmin or Adminer, per-site cron and environment variables. When the change is proven, push to live performs a database-aware sync back to production. You choose files, database or both, and the search-replace is handled for you so the URLs in your content follow the site rather than pointing back at the staging host. Because provisioning, cloning and deployment all run as durable Temporal workflows with per-step retries and compensation, a failure part-way through unwinds the partial work rather than leaving you with a half-cloned site. - One-click clone to an isolated staging subdomain, files and database included - Same stack and blueprint version as production, so what you test is what you ship - Database-aware push-to-live with search-replace, files or database or both - Durable, retryable workflows with compensation, so a mid-clone failure does not strand a site - Full developer access on the staging copy: SSH, SFTP, wp-cli, web IDE, database tools ## When a subdomain is the wrong tool We would rather tell you this up front than sell you something that undermines what you are trying to do. Subdomains are the right answer for structuring one brand: an app, a shop, a docs site, a customer portal, a per-client staging environment. They are the wrong answer for a private blog network. Every subdomain shares a single registrable domain, so anyone who resolves one of them knows exactly who owns the rest. Under a wildcard certificate they also share a certificate, and certificate issuance is published to public Certificate Transparency logs, so hosts under a shared domain are enumerable by anyone who cares to look. That is a property of the public web PKI and DNS, not of our platform, and no hosting configuration changes it. So subdomains sit in our Mainstream and Agency lines, not the Footprint-Free one. If your requirement is that sites must not be linkable to one another, you need separate registrable domains on the footprint-free product line, where the CDN and DNS account pools, footprint management and static-HTML delivery exist precisely to break that pattern. Both live on the same engine and the same dashboard, so choosing correctly costs you nothing in convenience. ## Subdomains across a portfolio Agencies and resellers use subdomains at volume: a staging host per client, a preview host per project, a portal per account. The platform is built for that shape of work. - **Hierarchical tenancy** — Organisations nest as a tree, reseller to client to sites, and every record is scoped and enforced at the database with row-level security. A client's subdomains belong to that client's organisation, not to a shared bucket you have to police by convention. - **Bulk operations** — Deploy, update and manage many sites in one action instead of repeating yourself once per site. - **API, CLI and MCP access** — Everything in the dashboard is in the public API, generated from the OpenAPI specification. Drive subdomain creation from an org-scoped API key, the CLI, Terraform, or an AI tool over our MCP server. - **Audit-logged administration** — Privileged and administrative actions are audit-logged, and role-based access control governs who on your team can do what. You can see who created, changed or removed a host. ## Frequently asked questions **Does a subdomain count against my plan's site allowance?** Yes. Because each subdomain runs as a full, separately isolated site with its own stack, database, cache and backups, it occupies a site slot on your plan in the same way a primary domain does. Plans are sold by the number of sites they cover, so adding a subdomain site is the same accounting as adding any other site. **Can each subdomain run a different stack from the main site?** Yes, and they are genuinely independent. Each subdomain is its own site record with its own blueprint, so the stacks do not have to match: WordPress on the main domain, WooCommerce on shop, a Node.js app on app and a static site on docs is an ordinary setup here rather than a special case. They can sit on different machines, run different runtimes and different PHP or Node versions, and be deployed, staged, backed up and rolled back on their own schedules. Nothing about one constrains another beyond sharing a domain name. **Do subdomains get their own SSL certificate?** They are covered automatically either way. You can issue a wildcard certificate that covers every host under the domain at once, or issue per-host certificates where you want them kept separate. Let's Encrypt certificates are free, issued and renewed automatically, and you can upload a custom certificate instead if you have one. **Can I use subdomains to build a PBN?** We would advise against it, and we will not sell it that way. Every subdomain shares one registrable domain, and under a wildcard certificate a shared certificate whose issuance appears in public Certificate Transparency logs, so the hosts are linkable to one another by anyone who looks. For work where sites must not be connectable, use separate registrable domains on our Footprint-Free line, which is engineered specifically for that with CDN and DNS account pools, managed footprints and static-HTML delivery. **Can one subdomain's problem affect the others?** The platform is built to contain it rather than let it spread. CloudLinux LVE caps each site's CPU, memory and IO inside its own cage, CageFS gives each site an isolated filesystem view so a breach is contained, and MySQL Governor throttles per-site database load so one site's heavy queries do not slow the server. Malware scanning, a proactive web application firewall and per-site immutable backups back that up. Containment is the design goal; no host can promise that a compromise is impossible. **Can I point a subdomain at you while my DNS stays elsewhere?** Yes. Registrar and DNS are deliberately decoupled. You can keep your domain at your current registrar and your zone at your current DNS provider and simply point a subdomain's record at us. We verify the delegation and activation before treating the site as live, so a mistyped record surfaces immediately rather than silently failing. When the parent domain's zone is already hosted here, we write the subdomain's record into it for you instead, so there is nothing for you to add by hand. **How does a staging subdomain differ from an ordinary one?** Only in how it is created. Clone to staging builds an isolated copy of a live site, files and database included, on a staging subdomain running the same stack and blueprint version as production. When you are happy, push-to-live syncs it back with a database-aware search-replace. Everything else, isolation, SSL, caching, backups and developer access, is identical to any other site. **What happens to my subdomains if I leave?** You take them with you. There is no lock-in anywhere in the platform: you can retrieve auth codes, unlock domains and transfer them out, bring your own CDN and DNS accounts, and export your sites. Every external provider we use sits behind a swappable adapter, which is as true for you as it is for us. --- # Know your site is up before anyone tells you URL: https://zinndigital.com/features/uptime-monitoring Zinn Digital® watches the web addresses you give us — uptime, Core Web Vitals and resource usage against your entitlement — and surfaces it per site in the dashboard. Alerts go to email, Telegram, Slack or your own webhook, and our status page lives off-platform so it still answers when we cannot. Uptime and page-speed monitoring is live now: add any web address — three free on every account, and we do not have to host it — and we check it every minute from outside our own network. Availability: per-site error tracking and per-site resource statistics are in active development and not yet available. Everything else described here is live today. ## Four signals per site, in one place Hosting dashboards usually tell you what you are paying for. Ours tells you what your site is doing. Every site you run with us reports the same set of signals, per site, with no agent to install and nothing to wire up. - **Uptime monitoring** — Continuous availability checks per site, surfaced against the site's own history so a blip and a real outage look different. Uptime state is a first-class signal the platform acts on, not a graph nobody reads. - **Core Web Vitals & performance** — Real performance data per site — the metrics Google actually ranks on. Slow pages show up as a measurement you can act on, next to the caching controls that fix them. - **Error tracking** — HTTP and PHP error logs are available per site, so a fatal from a bad plugin update or a broken deploy is something you can go and find rather than guess at. - **Traffic, bandwidth & resource usage** — Bandwidth per site, plus resource usage measured against your plan entitlement — including per-site LVE statistics — so you can see which site is working hardest and whether it is near a ceiling. ## Alerts that reach you where you already work A dashboard you have to remember to open is not monitoring. Every signal feeds the platform's notification layer, and you choose where it lands. - Four channel adapters, live: email, Telegram, Slack and your own webhook endpoint — each behind a swappable adapter, so no single vendor owns your alerting. - Preferences are set per organisation and per user: decide which events go to which channels, so the person on call gets the outage and the finance contact does not. - Webhooks are HMAC-signed, retried with backoff and logged — every delivery is inspectable and replayable from the dashboard, so a receiver that was down does not mean an alert you never saw. - Every signal rides the same durable event bus as the rest of the platform. A consumer that lags never blocks the producer, and no event is silently dropped. - Alerts are localisable like everything else we send — 58 languages, in the language the recipient set. ## A status page that survives the outage A status page hosted on the infrastructure it monitors is useless at exactly the moment you need it. Ours is deliberately somewhere else. Our public status page is self-hosted on separate infrastructure, entirely off-platform — a different box, a different failure domain from the control plane and the fleet it reports on. When something goes wrong with the platform, the status page keeps answering, because nothing it depends on is inside the incident. It is branded, fed by the same monitoring that drives your per-site alerts, and independent by design rather than by accident. The public frontend follows the same principle: the marketing site and help centre are deployed separately from the control-plane cluster, so a platform incident does not take our documentation down with it. This is the same reasoning that runs through the rest of the platform — separate failure domains, no shared fate, nothing that can take out both the thing and the tool you use to diagnose it. ## Monitoring your AI assistant can actually read Signals are worth more when something can act on them. Ours are wired into the assistant and into the MCP server, not locked in a graph. - **Pre-ticket diagnostics** — When you start to raise a ticket, the assistant runs a live diagnostic on the affected site first — uptime, HTTP and PHP errors, SSL and DNS state, resource limits and LVE faults, malware flags, plugin conflicts, database health and cache — before a human is ever involved. - **Safe auto-fixes, then re-check** — Within your permissions and the platform's guardrails it will clear cache, restart PHP workers, repair or renew SSL, repair database tables, disable a fatally-erroring plugin or purge the CDN — then re-check the signal and confirm whether it actually resolved. - **Escalation with the evidence attached** — If a human is still needed, the ticket arrives pre-filled with the diagnostics, what was tried and what happened — so support starts from the facts instead of asking you to describe the symptom. - **Readable over MCP** — Connect any MCP-capable AI tool and it can read site health, recent logs, metrics, uptime and errors as resources — so your own agent can diagnose before it acts, under OAuth 2.1 with org and role-scoped, revocable tokens and a full audit log. ## Core Web Vitals as an SEO signal, not a vanity chart Performance monitoring belongs next to the tools that change performance. On our platform it sits between the caching stack and the SEO layer. - Every plan carries the free SEO Basics tile: is the site indexed, its Trust Flow, and homepage Core Web Vitals — the three numbers that tell you whether a site is working as an SEO asset. - Footprint-Free plans add automatic Google indexing checks with weekly monitoring, so an indexation problem surfaces as an alert rather than as a traffic drop you notice a month later. - When CWV degrades, the fix is one page away: LiteSpeed Enterprise with LSCache full-page caching, per-site Redis object cache and CDN edge delivery, coordinated with smart auto-purge. - Deeper SEO monitoring is available as paid add-ons — rank tracking, backlink monitoring, competitor intel and a monthly SEO health audit — priced separately from your hosting plan. - Hands-on site speed optimisation is available as a purchasable extra when you would rather we did the tuning than you did. ## Built to watch a million sites Behind your dashboard is the same observability stack we run the platform on: Prometheus and Grafana for metrics, OpenTelemetry for distributed tracing across the engine, workflows and drivers, and centralised structured logs that are tenant-tagged with audit data kept separate. Metrics are collected per service, per worker and per tenant, with per-site LVE statistics from the isolation layer. Every workflow run — provisioning, migration, enforcement — is visible end to end, which is why a support answer can be specific instead of a guess. Monitoring at scale is a data-volume problem, so it is engineered as one. High-volume metrics are time-partitioned and rolled up rather than kept per-site per-minute forever, traces are sampled, and per-tenant cardinality controls stop one noisy account degrading everyone else's dashboards. The design target is a million sites, not the number we run today. Alerting is routed through Alertmanager to our on-call rota with SLOs defined and tracked — kept deliberately separate from the customer notifications above, so operational noise never lands in your inbox and your alerts never queue behind ours. ## Frequently asked questions **What exactly do you monitor on my sites?** Per site: uptime, Core Web Vitals and performance, bandwidth, and resource usage measured against your plan entitlement — including per-site LVE statistics from the isolation layer. It is all surfaced in the dashboard per site, with no agent to install. **How do I get told when a site goes down?** Through whichever channels you connect: email, Telegram, Slack or your own webhook endpoint. Notification preferences are set per organisation and per user, so you decide which events reach which channel and which person. Webhook deliveries are HMAC-signed, retried with backoff and logged, so you can inspect or replay any delivery. **Does the status page go down when the platform does?** That is exactly what it is designed to avoid. The status page is self-hosted on separate infrastructure, entirely off-platform, in a different failure domain from the control plane and the fleet it reports on — because a status page running on the infrastructure it monitors is useless during an outage. **What does the 99.99% uptime assurance mean?** It is the uptime target we build and operate to, and it is stated as an assurance on Footprint-Free plans. It is a commitment about how the platform is engineered — isolated per-site compute, horizontally scalable stateless services, separate failure domains — rather than a published measurement of past availability. Our contractual commitment is a separate and narrower thing, and it is published: see the Uptime SLA at /legal/sla, which sets out the level we guarantee and the service credits we pay when we miss it. **Can my own tools or AI agents read the monitoring data?** Yes. Site health, recent logs, metrics, uptime and error data are exposed as resources over our hosted MCP server, so any MCP-capable AI tool — Claude, Cursor, ChatGPT and others — can read them and diagnose before acting. Access is OAuth 2.1, scoped to your organisation and the connecting user's role, revocable per tool, and every action is audit-logged. Customer webhooks cover the same ground for conventional integrations. **Is monitoring extra, or part of hosting?** The observability signals described here are part of the platform and surfaced in your dashboard for the sites you host with us, and the free SEO Basics tile — indexed, Trust Flow, homepage Core Web Vitals — is bundled on every plan. Deeper SEO monitoring such as rank tracking and backlink monitoring is sold as separate paid add-ons, and hands-on speed optimisation is a purchasable extra. **Can I try it before I commit?** Yes. The Footprint-Free trial is 14 days, card-free and covers up to 5 sites — no payment details, no commitment. Deploy a few sites and watch what the dashboard actually reports before you decide. --- # Wayback Machine restore, built into your hosting URL: https://zinndigital.com/features/wayback-restore Point us at a domain, choose the date you want back, and Zinn Digital® rebuilds the archived site as clean static HTML or WordPress. The archive.org toolbar and injected code are stripped, internal links and asset paths are rewritten, and the result deploys straight onto your account. Two jobs, one tool: recover an aged domain for a footprint-free network, or bring back a site that was lost with no backup. ## From archive snapshot to live site A durable workflow handles the whole restore, so a large multi-page crawl never ties up your browser or fails halfway. - **Pick a snapshot** — Enter a domain and we list its archived captures from the Internet Archive's CDX index. Choose the date that best represents the site you want back — every date the archive holds, not just the last one. - **Never the parking page** — The most recent capture of an expired domain is routinely a parking page or a holding screen, so we never quietly pick it for you. Pages and their assets are fetched together, so what comes back renders — images, stylesheets and layout, not a wall of text. Where the archive never captured a page, we tell you how many and suggest a different date rather than quietly counting it as restored. - **Cleaned automatically** — The archive.org toolbar and any injected code are stripped out, and internal links plus asset paths are rewritten to point at your own site rather than the archive. - **Rebuilt your way** — Relaunch as fast static HTML, or convert the archived pages into WordPress posts and pages for a site you can keep editing. What comes back is the pages: the archive holds rendered HTML and its assets, never a database or an admin login, so a shop or a CMS returns as its pages and its basket, login and search do not work. ## Two ways people use it The same restore engine serves both product lines. Aged-domain recovery for footprint-free networks. Bought an expired domain with real history? Rebuild its original archived content as static HTML, then deploy it into a footprint-free network with account-pool rotation and server-side caching. The restore runs on the same provision-and-verify path as a fresh build, so a recovered domain behaves like any other site on your account. Site recovery for mainstream hosting. If a live site went down and no backup existed, the Wayback restore is often the only way back. Choose the last good snapshot, rebuild it as WordPress or static HTML, and you have a working site to edit and grow from again, hosted with staging, backups and monitoring from that point forward. ## Why it lives inside the platform - No separate downloader tool, local scripts or manual link-fixing. The restore is a managed workflow that runs to completion and reports progress. - Restored sites land on the same engine as everything else, so caching, CDN, backups and staging apply immediately. - Static-HTML mode keeps recovered aged domains lightweight and footprint-aware; WordPress mode gives you a fully editable rebuild. - Free migrations, a card-free 14-day trial, 30-day money-back and no vendor lock-in, so trying a restore costs you nothing to start. ## Frequently asked questions **How do I choose which snapshot to restore?** Enter the domain and we query the Internet Archive's CDX index to list its captures. You pick the date that best matches the version of the site you want. We never default to the most recent capture: the last thing the archive saw of an expired domain is usually a parking page, not the site you are buying it for. **Is the archive.org toolbar removed from restored pages?** Yes. The restore strips the archive.org toolbar and any injected code, then rewrites internal links and asset paths so the rebuilt site references your own hosting rather than the archive. **Can I rebuild as WordPress instead of static HTML?** Both are supported. Static HTML is ideal for lightweight, footprint-free aged domains; WordPress converts the archived pages into posts and pages so you can keep editing. You choose per restore. **Can I recover a site that had no backup?** Often, yes. If a site went offline and no backup existed, restoring from the last good Wayback snapshot is usually the only route back. You get a working rebuild to edit and grow from, hosted with backups and staging going forward. **Does a large restore slow anything down?** No. The restore runs as a durable background workflow, so even a deep multi-page crawl completes on its own and reports progress. It never blocks your dashboard or your other sites. --- # Web IDE — VS Code in the browser, on your live site URL: https://zinndigital.com/features/web-ide Open a full VS Code editor straight from the dashboard and work on your site's real files, with git built in and the whole editor inside the same CageFS-isolated jail as your SFTP access — nothing to install locally, and no separate copy to drift out of date. It edits the LIVE site: a file you save is on the public internet the moment it is written, though a static file may keep serving from the CDN cache for up to four hours. ## The editor you already know, pointed at the live filesystem The Web IDE is VS Code running in the browser via code-server, opened from the site you are looking at in the dashboard. It edits that site's actual files — no upload step, no local checkout to keep in sync, and no cut-down web text box pretending to be an editor. - **Full VS Code, not a file editor** — Syntax highlighting, multi-file search, split panes and the keyboard shortcuts you already have muscle memory for, delivered in the browser by code-server. - **The editor you already know** — The file tree, search across the whole site, multi-file editing and the keybindings you already know — the editor you use locally, running against the server instead of your laptop. - **The live files, not a copy** — You are editing the site itself. There is no staging copy in between and nothing to sync afterwards — which is what makes it fast, and what makes it worth reading twice before you save. Static files may keep serving from the CDN cache for up to four hours. - **Git built in** — Stage, commit, branch, diff and push from inside the editor, so work done on the server stays under version control instead of becoming an undocumented hotfix. ## wp-cli where the code is For WordPress work the command line matters as much as the editor. Both are in the same place. wp-cli runs against your site from the panel terminal. Search-replace a database, flush a cache, roll a plugin back, bulk-update, export a table or run a one-off script — without leaving the file you were editing. That closes the usual loop. Read the error in the log, open the file in the editor, change it, run the wp-cli command that proves it, move on. Everything happens against the real site on the real stack, so what you test is what your visitors get. - wp-cli from the panel terminal - One-click WP admin login when the fix belongs in the admin rather than the code - Plugin and theme install, activate, update and remove from the panel - Access, error and PHP logs available alongside the editor - phpMyAdmin and Adminer embedded and SSO'd for direct database work - FileGator file manager embedded and SSO'd for bulk file operations ## Isolated at the kernel, audited at the edge Browser access to a server is only acceptable if the boundary is real. The Web IDE sits inside exactly the same isolation as every other access route. - **CageFS filesystem isolation** — Each tenant gets an isolated filesystem view and cannot see other tenants, other sites or sensitive system files. CageFS is designed to contain breaches, and it is the same jail your SFTP sessions run in. - **LVE resource isolation** — CPU, RAM, IO, IOPS, processes and entry-processes are capped per site, so a heavy build or a runaway script is throttled inside its own cage rather than dragging neighbours down with it. - **Least-privilege credentials** — Access keys and credentials are managed in the dashboard on a least-privilege basis, so you grant the access a job needs and nothing beyond it. - **Audit-logged access** — Access is audit-logged with actor, action and target — the same discipline applied to every privileged action on the platform. ## Shape the runtime, not just the code An editor is only half of a development environment. The other half is the stack underneath it, and that is configurable per site. - Per-site PHP version selector, so a legacy plugin and a modern build can live on the same account - Editable PHP settings — memory_limit, max_execution_time, upload and post size and the rest — within your entitlement - Per-site PHP extensions toggled on or off: imagick, gd, redis, memcached, bcmath, intl, soap and more - Per-site LSAPI PHP workers, bounded by LVE entry-processes and configurable within your tier - Per-site cron management for both WP-cron and real cron, plus per-site environment variables - Redis or Memcached object cache per site, served by LiteSpeed Enterprise with HTTP/3 on - MariaDB per site with multiple databases and users, and a remote access toggle when you need an external client ## From edit to live, safely Editing production directly is sometimes the right call and sometimes a bad idea. The platform supports both paths from the same editor. Clone the site to staging in one click, open the Web IDE against the staging copy, work there, and push to live when the change is proven. Files and database come across together, on the same stack and blueprint as production, so staging is a real rehearsal rather than an approximation. If your work belongs in a repository, use git from inside the editor and let git-based deploys carry the change through the build-and-deploy pipeline. Code authored in the browser then follows the same versioned release and rollback path as code written on your laptop. When a change goes wrong anyway, backups are listed in the panel with one-click restore, and every deploy is a versioned release you can roll back to. The safety net is not a support ticket. ## AI in the editor, and any AI outside it The Web IDE pairs with the in-dashboard AI assistant, and the whole platform is built to be driven by the AI tools you already use. AI assistance is available in the dashboard, running on your own model through the AI Pack — you bring the model, and the assistant reads and edits files, runs wp-cli and pushes changes. There is no lock-in to an embedded model you did not choose. Outside the browser, our MCP server lets any MCP-capable client — Claude Code, Cursor, ChatGPT and others — control your hosting and sites in natural language, scoped by your API permissions. The pattern is deliberate: one API and one action catalog, exposed many ways. Build in our editor, build in yours, or let an agent do it, and the same deploy path serves all three. ## Frequently asked questions **What exactly is the Web IDE?** It is VS Code running in your browser, delivered by code-server and opened from the site's page in the dashboard. You get the full editor, with git, editing that site's real files on the server — the live ones, with no staging copy in between. Nothing is installed locally and there is no separate copy to keep in sync. **Do I still get SFTP?** Yes. The web editor is one way in, alongside SFTP — and, on plans that include SSH, a jailed shell. All of them land in the same CageFS-isolated view of your files, so you can use the editor for one task and your own client for the next. Footprint-Free plans get SFTP rather than a shell. **Can other tenants see my files through it?** Each tenant gets an isolated filesystem view under CageFS and cannot see other tenants, other sites or sensitive system files, and LVE caps CPU, RAM, IO, IOPS and processes per site so one cage cannot exhaust the server. CageFS is designed to contain breaches rather than to make risk zero, which is why baseline malware scanning, the proactive WAF and that isolation are included on every account instead of being sold as an option. **Can I give a developer access to just one of my sites?** Access today is governed by your organisation roles — owner, billing, dev and read-only — and members inherit the permissions of the role they hold in that organisation. Note that the dev role does not carry deploy or push-to-live permission. Optional per-membership resource scoping, such as limiting a member to specific sites, is a planned refinement rather than something available now, and API keys are issued per organisation with granular scopes rather than per individual member. **Is the web editor available on every plan?** It isn't a plan feature, so the answer doesn't depend on which plan you buy — it depends on where the site runs. The editor opens on sites we host on our own fleet, because it runs inside that site's own isolated container on our servers. If you've chosen to deploy a site somewhere else — another hosting platform, Cloudflare Pages, Netlify, GitHub Pages or your own server — you edit that site where it runs. VPS and cloud products don't include it either: there's no managed container for it to open onto. **Does the AI assistance in the editor cost extra?** AI assistance runs on your own model through the AI Pack, so you bring and pay for the model you want rather than being tied to one we picked. It is in the dashboard today; inside the editor it is in active development and not yet available. Separately, our MCP server lets external AI tools such as Claude Code or Cursor drive your hosting directly, scoped by your API permissions. **Should I edit production directly?** You can, and sometimes that is the fastest correct answer. For anything substantial, clone to staging in one click, open the Web IDE against the copy, and push to live once the change is proven. Git-based deploys and versioned releases with rollback are there when the change belongs in a repository, and backups with one-click restore sit behind everything. **How do I try it?** Start a card-free 14-day trial. No payment details are needed; the trial covers Footprint-Free hosting with up to 5 sites, so you can open the editor, work on a real site on the real stack and judge it for yourself. --- # Help, support and answers URL: https://zinndigital.com/help Everything you need to get an answer: a searchable knowledge base, an assistant that answers from it, and people who reply. Start wherever suits you — nothing here is behind a login. ## Pick a route All four work without an account. The first two answer immediately; the last two reach a person. - **Knowledge base** — Guides, how-tos and troubleshooting, in your language. - **Ask Zinn®** — A pre-sales assistant that answers from the knowledge base and today's prices. - **Contact us** — Email, Telegram, or a support ticket from your dashboard. - **Priority support** — Faster response targets when you need them. - **Emergency support** — For a site that is down right now. ## Something is wrong — what to do first In this order. Each step is faster than the one after it, and three of the four take under a minute. 1. **Check whether it is us** — Our status page is on separate infrastructure and reports platform incidents as they happen. If there is an incident open, it is already being worked on and you do not need to report it. 2. **Search the knowledge base** — Most of what breaks on a website breaks the same way for everyone. The knowledge base is written for the platform you are actually on, not for WordPress in general. 3. **Ask Zinn®** — It answers from those same articles and from our live price list, and it says so plainly when it does not know rather than guessing. 4. **Open a ticket** — From your dashboard, so it arrives attached to your account and your sites. A person picks it up — the assistant never closes a ticket for you. ## Things you can fix yourself, right now - **Restore a backup** — Daily off-site backups are restorable from your dashboard without asking anyone. - **Point a domain at us** — A free tool that tells you exactly what to change at any registrar, and whether it has taken effect yet. - **Check what is slow** — Function-level PHP request profiling per site, with Core Web Vitals beside it. - **Move a site in** — Free, automated, verified migrations that run before you change a nameserver. - **Manage WordPress** — Plugins, themes, users and updates from your dashboard, without wp-admin. - **Read the API docs** — Every endpoint, generated from the same specification the platform is built from. ## Ways to reach a person We answer in English and, through the platform's translation layer, in the language you write in. Support is included with hosting and is not metered per incident. - **Email** — office@zinndigital.com - **Telegram** — @zinndigital - **Support tickets** — From your dashboard, attached to your sites - **Status page** — Platform incidents, on separate infrastructure If your site is down right now and you cannot wait, emergency support is a paid, immediate-response service — it exists so that “urgent” means something rather than being what everyone writes in the subject line. ## Frequently asked questions **Do I need an account to get help?** Not to read the knowledge base, use Ask Zinn®, check status or email us. You need one to open a support ticket, because a ticket is attached to your account and your sites — which is what makes it answerable. **Is support included or extra?** Included. Priority support and emergency support are separate paid services with faster response targets; ordinary support is part of hosting and always has been. **What can Ask Zinn® actually do?** It answers questions about the platform and what things cost, from published knowledge-base articles and our live price list. It cannot see your account, your sites or your invoices, and it will tell you when a question is outside what it was given rather than guessing. **Is the knowledge base in my language?** Yes. Articles are published in English and translated into every language the site runs in, and each one tells you which parts you are reading in translation. **Where do I report a security issue?** Email us and say so in the subject. A security report is not a support ticket and we do not want it queued behind one. --- # One platform, every way to host URL: https://zinndigital.com/hosting Footprint-free bulk hosting for SEOs, and fully-managed WordPress for everyone else — 600,000+ PBN sites and 100,000+ money sites on the same engine, tuned for the job. ## Choose your hosting - **Footprint-Free PBN** — 106 footprints auto-managed, CDN rotation, static-HTML and Wayback restore — for 5 to 2,000 sites. - **Multisite without footprints** — Host a portfolio with isolated, no-shared-fingerprint delivery per site. - **WordPress Hosting** — Managed WordPress on LiteSpeed Enterprise + LSCache, staging and free migrations. - **WooCommerce Hosting** — Store-tuned caching that never breaks cart or checkout, with dedicated resources. - **Reseller Hosting** — Resell under your own brand with white-label sub-accounts and client sub-accounts. Three tiers, from 50 to 500 client sites. - **Agency Hosting** — Manage many client sites with team seats, staging and a portfolio dashboard. Three tiers, from 25 to 200 client sites. - **Cloud Hosting** — Dedicated cloud servers you configure — CPU, memory and NVMe storage — fully managed on the same engine, for workloads that have outgrown a shared plan. ## Not sure which one you want? Four questions, in this order. Most people know the answer to the first two already and are really asking the third. 1. **Start with what you are building** — One WordPress site or a shop: managed WordPress or WooCommerce. A portfolio of separate sites that must not look related: Footprint-Free. Client sites you bill for: Agency or Reseller. Something that is not WordPress at all: Web & PHP, an application plan, or a machine of your own. 2. **Then decide how much machine you want** — Shared hosting is the platform deciding for you and is right for most sites. A VPS or a cloud server is you deciding, with root. The rung matters more than the brand on it — a customer who cannot tell why the expensive one costs more buys the cheap one and is disappointed by it. 3. **Check the two numbers that actually bite** — How many sites the plan allows, and how much disk it gives you. Everything else on a hosting comparison is either included everywhere or something you will never reach. Both numbers are on every plan card, from the live price list. 4. **Ask if it is still not obvious** — Ask Zinn® answers from our knowledge base and today's prices, and tells you when it does not know rather than guessing. It costs nothing and it does not need an account. ## Static & app hosting — three backends Static and app sites deploy to whichever backend suits the job, chosen per site at deploy, on both product lines and from the MCP. - **Static & app hosting choices** — Our fleet, Cloudflare Pages or GitHub Pages — one Static product, a per-site backend choice at deploy. - **Cloudflare Pages hosting** — Full edge apps — client JS, Pages Functions and KV/D1/R2 bindings — on our Cloudflare account or your own. - **GitHub Pages hosting** — Connect your GitHub account and we create, deploy and manage Pages sites for you — bulk-capable, footprint caveat stated. ## On every plan, whatever you pay These are not tiers and they are not add-ons. They are what the word hosting means here, and they are why there is no care plan to buy. - **Free SSL** — Issued and renewed by the platform. An expired certificate is the commonest self-inflicted outage there is. - **LiteSpeed Enterprise with LSCache** — The commercial web server, not a community build — so most visits never touch PHP at all. - **Daily off-site backups** — On every plan on our own fleet, restorable by you from the dashboard without opening a ticket. - **Malware scanning** — Every site on our fleet is scanned, and a site we cannot scan reports why rather than quietly reporting nothing. - **Request profiling** — Function-level PHP profiling per site — what you actually need when a page is slow and the plugin list is long. - **Core Web Vitals** — Measured for you on the sites we host, beside bandwidth and resource use against your plan. - **Free migrations** — Automated and verified, run before anything is pointed at us — so you look at your site running here before you change a nameserver. - **The whole platform from your AI tool** — An MCP server, so Claude, Cursor or ChatGPT can run your hosting. Read-only until a write tool is switched on for you. ## Moving in is the part we do for you The reason people stay somewhere they have outgrown is that moving sounds worse than staying. It is not. Migration on to our platform is free on every plan that lists it, automated rather than a checklist you follow, and verified against the source before anything is pointed at us. You look at your site running here first. Only then do you change a nameserver — and if you change your mind before that, nothing has happened to your visitors, because nothing was pointing at us yet. - Free on every plan that lists free migrations - Verified against the source, not assumed - Your old host keeps serving until you say otherwise ## Ask before you buy You should not have to guess whether a plan fits. Ask Zinn® answers from our knowledge base and our live price list — not a sales script — and it says so when it does not know. - **Ask Zinn®** — Answers from the knowledge base and today's prices - **Email** — office@zinndigital.com - **Knowledge base** — Guides for everything on this page No account needed, and nothing you type is stored. ## Frequently asked questions **Which plan do most people start on?** Whichever one matches how many sites they have. The plans are separated by what you are building rather than by which features get switched on, because a feature ladder makes you buy a tier for one line item you need and nine you do not. **Can I move up later?** Yes, and without rebuilding anything. Changing plan changes what your account is allowed to do; it does not move your sites or take them offline. **Do you charge extra for backups, SSL or malware scanning?** No. Those come with hosting on our own fleet — see the WP Care page for the whole list and what the rest of the industry charges for it. **What is Footprint-Free hosting and do I need it?** It is hosting for a portfolio of sites that must not look related to each other — separate IPs, separate CDN accounts, and automatic removal of the fingerprints that give a network away. If you have one website, you do not need it. **Is there a free trial?** You can start without a card. The trial length is set per plan and each plan says which it offers, because a trial on a $2 shared plan and a trial on a dedicated machine are not the same offer. **What happens if my site goes down?** We publish an uptime SLA with service credits — 99.9% of every calendar month, in writing, adjudicated against our own monitoring. We engineer to a 99.99% uptime target; the agreement is what counts if the two ever disagree. --- # Full application hosting on Cloudflare Pages URL: https://zinndigital.com/hosting/cloudflare-pages Ship a static site or a real edge application to Cloudflare Pages, deployed and managed entirely inside Zinn Digital®. Client-side JavaScript, Pages Functions for serverless compute, and bindings for KV, D1, R2, Durable Objects and Queues — on our Cloudflare account or your own, driven from one dashboard and the MCP. ## Not flat HTML — a full application platform Cloudflare Pages runs client-side code and gives you edge compute and storage, so you build the site you actually want rather than a brochure. - **Client-side JS and SPAs** — Any JAMstack or single-page build runs natively on the edge — React, Vue, Svelte, Astro, a static export from your framework of choice. We deploy the build output; the browser gets fast, cached assets close to every visitor. - **Pages Functions (edge compute)** — Serverless functions run on Cloudflare Workers alongside your site: API routes, form handlers, authentication and light server-side rendering, without a separate backend to stand up. - **Storage and data bindings** — Bind Functions to KV for key-value data, D1 for SQL, R2 for object storage, Durable Objects for coordination and Queues for background work — so a Pages app can hold real state, not just serve files. - **Custom domain, configured for you** — Choose a project name and bind your own domain; we write the Pages custom-domain and DNS records automatically, with both apex and www served and the non-canonical one redirected. ## Managed end to end — you never need the Cloudflare console Every step of the lifecycle is a first-class action on both the dashboard and the MCP, so a person or an AI agent can drive it, one site or a hundred. - Deploy from a connected Git repository or by direct upload — the build lands as a Pages project with a live URL. - Preview every deploy on its own URL before you promote it, so a change is reviewable, not a gamble on production. - Roll back to any previous deploy in one action when a release misbehaves. - Read build and function logs, set environment variables and manage bindings without leaving the panel. - Bind and re-point custom domains, and let us handle the DNS and certificate for you. - Do all of it in bulk through the MCP: create and deploy many Pages sites, or apply the same settings across a set, by asking your AI tool. ## One-click Cloudflare product suite Beyond the site itself, the surrounding Cloudflare products activate per site or account — we handle the API wiring, credentials to Vault, routing, dashboard controls and MCP tools, and meter the usage through the catalogue. - **R2 object storage** — Zero-egress buckets per customer or site — ideal for backups and the app line's assets, with no surprise bandwidth bill. - **Stream and Images** — Video hosting with an embeddable player, and image storage with automatic optimisation, resizing and delivery URLs. - **Workers edge compute** — Deploy standalone Workers alongside your Pages app for edge logic that runs close to every visitor. - **Managed Cloudflare upsells** — Activate and configure Pro, Argo Smart Routing, Tiered Cache, Cache Reserve, Load Balancing, WAF, Bot Management, Rate Limiting and Zero Trust on your zone — we set them up; you get the result without the console. ## Frequently asked questions **Is this only for static HTML, or can I run a real app?** A real app. Client-side JavaScript, SPAs and any JAMstack build run natively, and Pages Functions add serverless edge compute for API routes, authentication and light SSR. Functions can bind to KV, D1 SQL, R2 object storage, Durable Objects and Queues, so you can build dynamic applications, not just flat pages. **Do I need my own Cloudflare account?** No, but you can. Deploy on our Cloudflare account with nothing to set up, or connect your own via the bring-your-own-account flow — we show the privileges required, validate the credentials on entry, and store them in Vault. Either way you drive everything from our dashboard and MCP; you never need the Cloudflare console. **Can I use my own domain?** Yes. Pick a project name and bind your own domain, and we configure the Pages custom domain and the DNS records for you automatically — including the apex-and-www rule, so both example.com and www.example.com resolve and the non-canonical one 301-redirects. **How do deploys and rollbacks work?** Deploy from a connected Git repository or by direct upload. Every deploy gets a preview URL, and production is a promotion you can roll back with one action if a release goes wrong — from the dashboard or by asking your AI agent through the MCP. **Is Cloudflare Pages a good fit for the PBN line?** Yes. A static or app site on Cloudflare Pages with a custom domain is a strong footprint-diverse backend, and mixing Pages sites with our-fleet and other backends across a network adds diversity rather than removing it. It is offered on both the Footprint-Free and Mainstream lines. --- # Hosting that behaves like a tool, not a control panel URL: https://zinndigital.com/hosting/developers Deploy from the GitHub or GitLab repository you already work in, branch a staging copy and push it live when it is ready, open real VS Code in the browser on the running site, and drive the whole platform from a REST API, a CLI and an MCP server. Everything the dashboard does, the API does — because the dashboard is built on it. ## The workflow, not a screenshot of one Four things that turn hosting from somewhere you upload files into somewhere you ship from. - **Deploy from your repository** — Connect GitHub or GitLab once. We show exactly which permissions the connection needs before you authorise it, validate the token on entry, and store it in Vault — never in a database column and never in a log. - **Staging with push-to-live** — Branch the whole site — files and database — work on the copy, then promote it. Test the thing you are about to ship on a copy of the thing you are shipping to. - **VS Code in the browser** — Real code-server on the live site's files, with git built in, inside the same CageFS-isolated jail your SFTP session lands in. Nothing to install, nothing to sync. - **Your own tools, still** — SFTP on every site, and a jailed SSH shell with wp-cli on the shared platform. Use the browser editor for one task and your own client for the next — both see the same files. - **Zinnector®, the CLI** — Build WordPress locally with nothing installed but Node — no Docker, no MAMP — then check what you built against the platform it is going to. Free and MIT-licensed. - **An MCP server for your agent** — Twelve categories of real actions — sites, code, domains, DNS, SSL, databases, configuration, backups, email, SEO and observability — so an AI assistant can do the work rather than describe it. ## Every door into the platform The dashboard is one client of the API. These are the others, and they are all public. - **REST API reference** — Every operation, generated from the OpenAPI spec that is the source of truth — so the docs cannot drift from the endpoint. - **The developer platform** — How the API, SDKs, Terraform provider and webhooks fit together, and what to reach for when. - **CLI command reference** — Every Zinnector® command, generated from the tool itself rather than written beside it. - **Zinnector® — the CLI** — Local WordPress on Node alone, and pre-flight checks against the platform you are deploying to. - **Webhooks** — Events pushed to you, signed and retried, so you do not poll us. - **MCP tool catalogue** — What an AI agent connected to your account can actually do, listed action by action. ## The things that only matter once you are working Small print that is not small when it is your Tuesday afternoon. - Per-site PHP version, so one site can move to 8.4 without dragging the others with it - Per-site cron and environment variables in the dashboard, not in a file you have to remember - phpMyAdmin and a file manager for the times a GUI really is quicker - wp-cli in the panel terminal and over SSH on the shared platform - Free migrations, done and verified before anything is switched over - Free SSL issued and renewed for you, on every site - Sites on our own fleet get SFTP rather than an interactive shell — the account is created with /sbin/nologin and SFTP enters the jail through PAM, which is a security decision rather than a missing feature ## From repository to live site The path a change takes, once the connection exists. 1. **Connect the repository** — Authorise GitHub or GitLab once, having seen the exact scopes first. The token is validated on entry and written to Vault. 2. **Branch a staging copy** — Files and database, one click. Your staging copy is the site, not an approximation of it. 3. **Push, and we deploy** — A push to the branch you nominated deploys to that environment. Static sites can go to our fleet, Cloudflare Pages or GitHub Pages, chosen per site. 4. **Promote to live** — When it is right on staging, push it live. Every deploy is a versioned release, so if it is wrong afterwards you roll back to the previous one rather than opening a restore ticket. ## Frequently asked questions **Do I get SSH?** On the shared platform, yes — a jailed shell with wp-cli, with keys managed in the dashboard. On our own fleet, no: those accounts are created with /sbin/nologin and you get SFTP into the same CageFS jail instead, alongside the browser IDE with git built in. We would rather tell you that here than have you find out after you have paid. **Is the public API the same one the dashboard uses?** Yes, and that is the point. It is API-first: no endpoint ships unless it is in the OpenAPI spec, and the SDKs, the CLI and the reference on this site are all generated from that spec. There is no private API with the good endpoints in it. **Which languages and stacks?** WordPress and WooCommerce, plain PHP, Laravel, Node, Python and Django, .NET, static sites and modern app frameworks. Or take an unmanaged machine with root and run whatever you like on it. **What is the MCP server for?** It lets an AI assistant — Claude, or anything else that speaks MCP — take real actions on your account instead of telling you which button to press. What it can do is listed in the tool catalogue, and you decide what it is allowed to touch. **Am I locked in?** No. Every site can be exported, the code is in your repository, and the platform is deliberately built with swappable providers underneath it. If you want to leave, the answer is a migration rather than an argument. **Can you build the thing as well as host it?** Yes — that is a separate service and a separate decision. Development is quoted per project, and hosting it with us is never a condition of it. --- # PBN Hosting, Footprint-Free URL: https://zinndigital.com/hosting/footprint-free Every site on its own CDN and its own nameservers, deployed as WordPress, static HTML, Joomla or a build pushed to Netlify — then run a thousand of them from one screen. Footprint-aware rotation, 106 auto-managed footprints, LiteSpeed Enterprise, daily backups and Wayback restores, on 42 tiers from $6/mo. ## A footprint model, not a hosting account Deindexation almost never comes from one site — it comes from the pattern that links a network together. Every layer here is designed to break that pattern, automatically, at deploy time. - **Footprint-aware CDN rotation** — Spread your sites across multi-Cloudflare and CDN account pools — ours and your own. Balance is recomputed from live account state at every deploy, counting deleted sites, so distribution stays even and never drifts into a detectable cluster. - **106 footprints auto-managed** — The Zinn® Footprint plugin ships in every deploy: it strips the WordPress version and generator tag, removes discovery links, disables XML-RPC and pingbacks, hides login detail and drops X-Powered-By — so sites present a clean, generic surface with nothing tying them to a common origin. - **Static-HTML mode** — Serve any site as pure static HTML — no PHP, no database, no CMS fingerprint and nothing to exploit. The fastest, lowest-footprint way to keep an aged domain live and indexed. - **Wayback Machine restore** — Rebuild an aged domain straight from its archive.org history. Pick any date the archive holds — we never default to the last capture, which on an expired domain is usually a parking page — and we strip the archive toolbar, rewrite links and assets, and rebuild it as static HTML or WordPress. ## No two of your sites have to come from the same place A private network is found by what its sites have in common. Most hosts give you one CDN and one pair of nameservers, so every domain you own answers from the same place and resolves through the same authority — which is one query wide. Here the CDN and the DNS are a per-site choice, made at deploy. Sites are balanced across a pool of accounts — ours and any you connect — and the balance is recomputed from live account state every time, counting sites you have deleted, so the spread never drifts into a cluster. - Eight content-delivery networks and nine DNS providers, every one of them named further down this page - Chosen per site, not per account — and changeable afterwards - Bring your own Cloudflare, Bunny, CloudFront, Route 53 or Azure account into the pool - On this line the origin A-records are hidden entirely, so DNS control cannot leak an origin ## Run a thousand sites the way you would run one The WordPress manager lists every WordPress site you own, on every plan and every platform, with its core version, its waiting plugin and theme updates, its disk use and a one-click way in — and it tells you which sites are healthy, which need attention and which are not answering at all. Group the sites however you actually think about them — by client, by tier, by money site — and a site can be in as many groups as you like. Then point a bulk job at a whole group. - Update WordPress core, plugins and themes across hundreds of sites in one job - Install a plugin or a theme everywhere, or apply a whole blueprint - Search and replace text across the network — a link, a phone number, an old brand - Target every site, one product line, one customer, one group, or a list you paste in - Anything destructive asks first, and every job shows you what it will touch before it runs ## Every link your network points out — and one way to change them all A network is only worth what its outbound links are worth, and on most of them nobody can say where they all are. The Link Tracker builds that answer from the sites themselves: every domain your network links out to, every post each link sits in, and how many times — for one site, or for the whole network at once. So when a money site changes domain, or an anchor has to move, you do not open three hundred WordPress admins. Point one edit at the target, see exactly how many links, posts and sites it would touch before anything is written, and run it. If it was wrong, one click puts back exactly what it replaced. - Every outbound target across the network, with the posts and sites each link appears in - Read it for one site, or for everything you host - Preview first — how many links, posts and sites a bulk edit would change, before it writes - Change an anchor or a destination across hundreds of posts in a single job - Undo restores exactly what the edit replaced, and the undo is itself recorded as an edit - Every edit is kept with who ran it and what it changed, so the network has a history ## An expired domain to an indexed site, in four moves None of this needs a ticket, a migration form or a wait. It is the same four steps whether it is your first site or your thousandth. 1. **Bring the domain** — Buy it here or point one you already own. The built-in checker shows WHOIS, expiry and the domain's own authority score before you commit to it. 2. **Rebuild or start clean** — Restore the domain's old site from the public web archive — any date it holds, not just the last capture — and we strip the archive toolbar, rewrite links and assets and rebuild it as static HTML or WordPress. Or deploy a fresh site from a blueprint. 3. **Pick its edge** — Choose the CDN and the DNS for this site, from our pool or an account of your own. LiteSpeed Enterprise with LSCache, a per-site Redis object cache and the Zinn® cache plugin are already on. 4. **Check it, then point it** — Every site gets a preview address on a hostname of ours that carries nothing about your domain, so you can open the finished site and check it over BEFORE any DNS points at us. When it looks right, move the nameservers. ## Check it before it is live. Move it without losing it. A preview address stands in for the real domain until the real domain points at us — which is the only window in which a preview is worth anything. The hostname is derived from the site's own id and carries no trace of your domain, because a link between a footprint-free site and a name we own is archived by historical-DNS services for ever. And when a site outgrows its name, changing it is one form. We build the new side, flip it, then tear the old side down — a durable job that resumes if anything upstream fails, not a field you edit and hope. You choose whether the old domain keeps serving as an alias, because for a network with backlinks pointed at it, that is not a detail. - The preview address works until your DNS moves — and it is not a second permanent hostname - Nothing in the preview name reveals the domain it stands in for - Change a site's primary domain from the dashboard, with the old name kept as an alias if you want it - SSL is provisioned and renewed on both sides automatically ## Everything a network needs, included One flat plan per tier — no metered surprises, no add-ons that turn footprint control into a paywall. - 4 GB of NVMe disk, 100 GB of bandwidth a month and 100,000 files on every site, on every tier — and you can buy more disk or files for any single site the moment it needs them. - Free SSL on every site, provisioned and renewed automatically across all accounts. - Free 10GB email with each domain, so contact addresses match the sites they belong to. - Majestic metrics surfaced per site, so you can judge domain quality without leaving the panel. - Bulk operations — deploy, manage and purge hundreds of sites at once, in a single action. - Free migrations, no vendor lock-in, and a 30-day money-back guarantee behind everything. - Change tier when it suits you — an upgrade takes effect at once, you pay only the prorated difference, and the period you have already paid for is kept. A smaller tier is offered whenever it still fits what you are using, and says which number is in the way when it does not. ## Fast enough that a crawler comes back Measured, not promised: across 16,038 mobile Lighthouse checks of 39 PBN sites on our fleet in the 30 days to 20 October 2026, the median performance score was 100 out of 100, the median time to first byte was 83 ms and the median largest contentful paint was 1.2 seconds. Every box on our own fleet runs licensed LiteSpeed Enterprise with LSCache — the commercial build, licensed and kept current by us, never the free one — plus a per-site Redis object cache and our own repo-grade cache plugin, installed at deploy. Most visits never reach PHP or MySQL at all. On a static-HTML site nothing reaches them ever: no PHP, no database, no CMS fingerprint and nothing to exploit. - LiteSpeed Enterprise + LSCache on every fleet box, licensed by us - Per-site Redis object cache and the Zinn® cache plugin, pre-installed - Static-HTML mode for the lowest footprint and the fastest first byte - 4 GB disk, 100 GB bandwidth and 100,000 files per site on every one of the 42 tiers — upgradeable per site at any time ## Priced for one site or a thousand Footprint-Free Hosting runs on 42 tiers, from PBN 5 at $6/mo for a starter network to PBN 2000 at $2000/mo for operators running at scale. You size to the network you actually have and move up a tier when it grows — the footprint engineering is identical at every level. This is not a repackaged shared-hosting plan with a marketing label. It is a purpose-built product line on the Zinn Digital® engine, sharing the infrastructure we built to host more than 600,000 PBN sites worldwide, backed by a 99.99% uptime assurance. Start with a card-free 14-day trial. No payment details, no commitment — build a few sites, watch how rotation and the footprint layer behave, and decide from there. Need more headroom for a busy network? The PBN Performance Boost gives every Footprint-Free site on your account 1.5x, 2x or 3x its plan's CPU and memory — including sites you add later — for $0.10, $0.20 or $0.40 per site a month (minimum $9.99, $19.99 or $39.99). It is priced on your total PBN site count, re-priced only when it renews, and you choose, change or stop it from Billing in your dashboard. ## Everything the footprint-free stack includes Each of these is built into every one of the 42 tiers — not an add-on, not a higher plan. Follow any card for how it actually works. - **CDN & DNS account pools** — Multi-account CDN and DNS pools, ours and your own. Balance is recomputed from live account state at every deploy — counting deleted sites — so distribution stays even and never clusters. - **Footprint remover** — Strips the WordPress version and generator tag, removes discovery links, disables XML-RPC and pingbacks, hides login detail and drops X-Powered-By — on every deploy, automatically. - **Wayback Machine restore** — Rebuild an expired domain's original site straight from the Internet Archive and serve it as static HTML — the fastest way to bring an aged domain back online and indexed. - **Per-site isolation** — Every site runs inside its own containment boundary, so a compromised or runaway site cannot reach a neighbour — and no shared-fate incident can take a network down at once. - **Caching & speed** — LiteSpeed Enterprise with LSCache, a per-site Redis object cache and our own repo-grade cache plugin pre-installed. Most visits never reach PHP or MySQL. - **Daily backups & one-click restore** — Every site backed up daily and held for 30 days, restorable in one click. Disaster recovery is part of the plan rather than a paid tier above it. - **Majestic metrics & indexing checks** — Full Majestic SEO metrics for every domain, automatic Google indexing checks with weekly monitoring, and a built-in domain checker with WHOIS and expiry warnings. - **Subdomains** — Run subdomain sites where the strategy calls for them — without the shared fingerprint a conventional multisite install creates. - **Malware scanning** — Continuous scanning across the fleet behind a swappable scanner adapter, so an infected site is found and contained rather than quietly poisoning your network's reputation. - **Free 10 GB mailboxes** — Ten free 10 GB mailboxes on every domain you host, at every tier — with forwarding rules, a catch-all and autoresponders behind them. No per-mailbox pricing, no second provider to keep in sync, and the DNS records and deliverability for every mailbox set up for you automatically. - **Free migrations** — We move your existing PBN over for you, at no charge — including sites currently sitting on a host that has fingerprinted them. - **Free Zinn® plugins** — The Zinn® cache and footprint plugins ship with every deploy, auto-updated and built to WordPress.org directory standards. - **WordPress manager** — Every WordPress site you own — on every plan and every platform — with its core version, its waiting plugin and theme updates, its disk use and a one-click way in. It tells you which are healthy, which need attention and which have stopped answering. - **Site groups** — Organise the network the way you actually think about it — by client, by tier, by money site — and put a site in as many groups as you like. Then filter the list, or point a bulk job at a whole group. - **Bulk actions across the network** — Update core, plugins and themes, install a plugin or a whole blueprint, or search and replace text across hundreds of sites in one job. Target everything, one product line, one client, one group or a list you paste in — and anything destructive asks first. - **A PHP version per site** — Each site picks its own PHP — the current release, or one of the hardened legacy branches — so an aged domain's old theme lands and runs on day one instead of white-screening. Set it per site, change it whenever, and the site next door is unaffected. - **Outbound link tracker & editor** — Every domain your network links out to, with the posts each link sits in — and a bulk editor that shows you what it would touch before it writes, and can put back exactly what it replaced. - **Posting on a schedule** — Plan a run of articles across a window and watch the queue — what is scheduled and when each one lands. Pause it, resume it, cancel what has not started, or move a single article to a different moment. Point it at a list of sites or at a whole group. - **Your own DNS records** — View, add, edit and delete records on any domain you host — A, CNAME, MX, TXT — in bulk, from the panel, the API or the MCP. A verification record or a mail record is something you set, not something you ask us for. - **Export the network** — Download the sites you are looking at as a CSV — the same scope and the same filters that are on screen — so the network can be reconciled against a spreadsheet, a client report or another system without writing an integration first. - **Preview URLs before DNS moves** — Open and finish a site at a temporary address of ours before any DNS points at us. The hostname is derived from the site's own id and carries nothing about your domain, so nothing links the two in historical DNS. - **One-stop domain change** — Outgrown a name? Change a site's primary domain from the dashboard. We build the new side, flip it and tear the old one down as a durable job — and you choose whether the old domain keeps serving as an alias, which for a network with backlinks is not a detail. - **Deploy anywhere from one panel** — WordPress, static HTML, Joomla, PHP applications, WooCommerce, Node.js and headless CMSes on our own fleet — or publish a build straight to Cloudflare Pages, Netlify, GitLab Pages or GitHub Pages, or to a Vercel, Render, Azure or Amplify account of your own. ## The honest comparison We tested every major PBN host and documented what they actually deliver. Here is how footprint-free hosting on Zinn Digital® compares — us first. | | Zinn Digital® | SeekaHost | PBN.Hosting | Easy Blog Networks | LaunchCDN | Bulk Buy Hosting | PBNHosting.io | Priority Prospect | | --- | --- | --- | --- | --- | --- | --- | --- | --- | | Price per site (monthly) | $1.00–$1.20 | $1.60–$1.90/IP | $1.60–$2.90 | €1.49–€3.50 | $1.69–$2.18 | $2.30–$2.76 | $1.00–$1.50 | $2.30–$2.89/IP | | Genuine footprint-free architecture | Yes | No | No | No | No | No | No | No | | No cPanel / DirectAdmin | Yes | Partial support | Yes | Partial support | No | No | No | No | | No single-account Cloudflare footprint | Yes | Yes | Partial support | Yes | Partial support | Yes | Partial support | Yes | | Static HTML + WordPress | Yes | — | Yes | No | Yes | — | Yes | — | | Independent, diversified infrastructure | Yes | Yes | Yes | Yes | Partial support | Yes | Partial support | Yes | | Free migration | Yes | — | Yes | Yes | Yes | Yes | No | — | | All niches accepted | Yes | — | — | — | — | — | — | — | | AI-driven footprint balancing | Yes | No | No | No | No | No | No | No | | Free trial | Yes | Yes | yes (7 days) | yes (7 days) | $10 (30 days) | $10 (30 days) | — | — | | Bulk outbound link editing across the network | Yes | — | Yes | — | — | — | — | — | | Scheduled content posting across the network | Yes | — | — | Yes | — | — | — | — | Every competitor figure above carries the provider’s own page it was read from and the day we read it — click a number to jump to the source. A ✓, • or ✕ is OUR READING of that cited page on that day, not a statement about what the provider does today: prices, plans and features change without notice, so check the source before you rely on a cell. “—” means the provider’s own page did not state it, so we make no claim. Prices are as displayed on each provider’s own storefront in the currency shown; Easy Blog Networks quotes in euros excluding tax, and per-IP providers are shown in their own unit because a per-site figure depends on how many domains you put on an IP. Found something out of date? Tell us and we will correct it. The “Genuine footprint-free architecture” row is our own hands-on test of each provider (Zinn Digital®, 2026-10-14): every one of them left footprints that link a network's sites; its source link is the provider's own PBN hosting page that we tested against. ## Talk to people who actually run PBNs Every plan includes real support from engineers who host private blog networks for a living — not a scripted first line that escalates your ticket into a queue. Ask about footprints, indexing or a migration and you get a straight answer. - **In-dashboard support tickets** — Open a ticket from any site and a real engineer answers — no bot, no call-back window. - **Free SEO & PBN advice** — Ask our SEO team about footprints, link structure, indexing and recovering a de-indexed domain. It is included, not a paid tier. - **Free network migrations** — Moving an existing network in? We do the whole migration for you at no cost, however many sites it is. ## The SEO data this line is bought for A network is only worth what search engines think of it. These read the same data our own reports do, per site, on the invoice you already receive. - **PBN footprint checker** — Checks your whole set of sites for the public traces that tie them to one owner, scores the set and tells you what to fix for each one. Every site hosted here is included, and sites you host elsewhere can be added. - **Daily index monitoring** — Your plan checks weekly. This checks daily and watches the individual pages that earn, so the gap between a page dropping out and you knowing is a day. - **Rank tracking** — Your phrases checked in Google every day with the history kept, so a change is something you can point at rather than something you think you remember. - **Backlink monitoring** — Links appearing and disappearing across the network, with the domain's own authority score tracked beside them. - **The whole add-on catalogue** — Monitoring, SEO data and expert services, bought per site and billed on the invoice you already receive. Migrations are free. ## Frequently asked questions **How does footprint-aware rotation actually work?** You add your own Cloudflare and CDN accounts alongside ours, and each site deploys to a chosen account. When you deploy, the balancer reads live account state — including deleted sites — and spreads your network evenly across the pool, so no single account holds a detectable cluster and the distribution never drifts. **What are the 106 footprints you manage?** They are the signals that link a network's sites, handled with no action from you: the WordPress fingerprints the Zinn® Footprint plugin strips on every deploy (generator and version tags, RSD and discovery links, XML-RPC and pingbacks, login error detail, powered-by headers), the backlink crawlers networks are found with, the CDN account, DNS provider and origin each site is given on its own, and the cross-site signals our footprint checker watches for, such as shared analytics IDs, nameservers and certificates. The plugin has per-measure toggles if a theme needs one left on. **What happens if one of my sites gets DDoSed?** Flood Guard protects that one site on its own. We check every site's traffic every two minutes; a flooded site gets a visitor check at our edge, and Under Attack mode if it is on its own Cloudflare zone. Your other sites never notice. You get an email, and the protection lifts itself once traffic has been normal for a few checks. **What if a CDN suspends one of my sites?** CDN auto-move handles it. We check every CDN zone every ten minutes; when the zone serving a site has been suspended for an hour, we rebuild the site on another CDN from our pool and point the domain at it. Your nameservers do not change and nothing needs a ticket. You get an email once the site answers again. A site on a CDN account of your own is yours to decide: we email you and you choose the new CDN in one click. **Can I restore an aged domain from the Wayback Machine?** Yes. Enter a domain and pick any archived date it holds, and we download its archived pages, strip the archive.org toolbar and injected code, rewrite internal links and asset paths, then rebuild it as static HTML or a full WordPress site. **Is there really no bandwidth or disk limit?** You pick a plan by the size of your network, not by a usage meter — every tier carries the same per-site allowances. Each site gets 4 GB of NVMe disk, 100 GB of bandwidth a month and 100,000 files, and you can add more disk or files to any individual site at any time: it is billed monthly for that site and the new ceiling shows in the site's stats straight away. Free SSL plus 10GB email per domain are included at every level. **How much does it cost and can I try it first?** There are 42 tiers, from PBN 5 at $6/mo to PBN 2000 at $2000/mo. Every plan starts with a card-free 14-day trial and is covered by a 30-day money-back guarantee, with free migrations and no vendor lock-in. **Which CDNs and DNS providers can I actually choose from?** Eight CDNs — Cloudflare, bunny.net, CDN77, KeyCDN, Fastly, Gcore, Amazon CloudFront and Akamai — and nine DNS providers: Cloudflare DNS, Bunny DNS, ClouDNS, deSEC, Hetzner DNS, Gcore DNS, Amazon Route 53, Azure DNS and DigitalOcean DNS. Both are a per-site choice made at deploy, not an account-wide setting, and you can bring your own account for any of them. Our own branded nameservers are deliberately NOT offered on this line: a branded nameserver is itself a footprint, so the Footprint-Free line never puts one in front of your network. **Can I deploy something other than WordPress?** Yes. On our own fleet you can deploy WordPress, static HTML, Joomla, plain PHP applications, WooCommerce, Node.js apps and headless CMSes. You can also publish a build to a third-party edge — Cloudflare Pages, Netlify, GitLab Pages and GitHub Pages from our pool or your account, and Vercel or AWS Amplify on an account of your own. Render and Azure Static Web Apps deploy from your repository. **Can I see a site before I point the domain at you?** Yes. Every site on our fleet gets a preview address on a hostname of ours, and it stands in for your domain until your DNS moves. The name is derived from the site's own id and contains nothing about your domain, because a published link between a footprint-free site and a hostname we own is archived by historical-DNS services permanently. **Can I change a site's domain later without rebuilding it?** Yes, from the dashboard. The engine runs it as a durable job: it builds the new side, flips the site over, then tears the old side down, and it resumes rather than half-finishing if something upstream fails. You decide whether the old domain keeps serving as an alias — leave that off and every backlink pointing at the old name stops working the moment the flip lands. **How do I manage hundreds of sites without opening hundreds of tabs?** The WordPress manager lists every WordPress site you own with its version, updates, space and health. Site groups let you organise them however you like — a site can be in several — and a bulk job can target everything, one product line, one client, one group, or a list you paste in. Core and plugin updates, plugin and theme installs, blueprint application and network-wide search and replace all run that way. **Do you run LiteSpeed, and is it the licensed build?** Yes. Zinn Digital® is an official LiteSpeed Partner and every box on our own fleet runs licensed LiteSpeed Enterprise with the LSCache plugin — the commercial build, not the free one — alongside a per-site Redis object cache and our own cache plugin. The whole Footprint-Free line deploys to that fleet. **What happens to my sites if I stop paying?** They are suspended, not deleted, and nothing that costs money runs against a suspended account — index checks, SEO refreshes and scans all skip it. Your data, your backups and your schedule stay as they were, and the moment the account is back in good standing everything resumes on its normal rotation without you asking. **Can I choose the PHP version for each site?** Yes, per site and whenever you like — the current release or one of the hardened legacy branches. That matters on a PBN more than on a normal host: an aged domain often arrives with a theme or a plugin that was last touched years ago, and it has to run on day one. The legacy branches are security-patched builds rather than abandoned ones, and the version a new site starts on is always a current, supported release — you opt into an older one deliberately, per site. **Can I change a link across the whole network at once?** Yes. The Link Tracker reads every site you host and lists every domain your network links out to, with the posts each link sits in. Point an edit at one of those targets and it tells you how many links, posts and sites it would change before it writes anything. Run it, and if it was wrong, one click restores exactly what it replaced — the undo is recorded as an edit of its own, so the history stays honest. **Can articles be posted on a schedule rather than all at once?** Yes. Plan a run of articles across a window and you get a queue you can read: what is scheduled, and when each one lands. Pause it, resume it, cancel what has not started yet, or move a single article to a different moment. A run targets a list of sites or a whole site group, and the group is resolved when the run starts rather than when you set it up, so sites you add later are included without you editing the schedule. **Can I get my network out of here as a file?** Yes, and without asking us. Every site in the scope you are looking at exports as a CSV, with the same filters that are on screen. The point is that it is yours on demand: no lock-in by inertia, no ticket, and nothing that needs an integration built first. --- # Deploy and manage GitHub Pages, without leaving the panel URL: https://zinndigital.com/hosting/github-pages Connect your GitHub account and let Zinn Digital® create repositories, push builds, enable and deploy GitHub Pages, wire up a custom domain and roll back — all from one dashboard and the MCP, one site or in bulk. Connect the enterprise way with our least-privilege GitHub App, or a validated fine-grained token. ## Connect the enterprise way — least privilege, validated Connecting a source-code account should not mean handing over a powerful long-lived key. We give you two paths and default to the safe one. - **The Zinn® GitHub App (preferred)** — Install our GitHub App on your account and grant it only the repositories you choose. It gets granular permissions — contents, Pages and administration for repo creation — issues short-lived installation tokens rather than a standing secret, and you revoke it in one click whenever you like. - **A fine-grained token (fallback)** — Prefer to use a token? We show you exactly which scopes to grant for the target repositories — least privilege, nothing more — and validate it against the GitHub API on entry, with a green or red check, before it is ever saved. - **Credentials in Vault** — Whichever path you choose, the credential flows through the same connection seam as every other account you bring and is stored in Vault. It is never written to code, a log, or an environment file. - **Revocable and auditable** — You stay in control: revoke access at any time from your side, and every action we take on your account is recorded in the audit log with the identity that performed it. ## What we do for you, managed and automated Once connected, GitHub Pages becomes a first-class deploy backend you drive from our tools — never the GitHub UI. - Create repositories or use an existing one, and push your content or build output for you. - Enable GitHub Pages from a branch-and-directory source or the GitHub Actions build, and deploy. - Roll back to a previous deploy when a release goes wrong. - Bind a custom domain: write the repo CNAME, enforce HTTPS, and configure the apex and www DNS for you. - Back the repository up to R2 object storage on a schedule — a repo backup and DR product. - Run our tooling against the live site: because Pages sites are public static, indexation, SEO-data, backlink and uptime checks all work. - Do it in bulk through the MCP: create and deploy Pages sites across many repositories from your AI tool. ## The footprint caveat, stated plainly We would rather tell you the trade-off than hide it. GitHub Pages has no server-side rules — there is no .htaccess — so the SEO-crawler blocking that hard-denies Ahrefs, Majestic and the rest at the server on our own fleet cannot work there. On GitHub Pages the best available control is robots.txt plus meta tags, which the aggressive backlink crawlers are known to ignore. Every GitHub Pages site also shares GitHub's infrastructure and published IP ranges, which is a shared footprint in itself. For a money site or a mainstream project none of that matters, and GitHub Pages is a genuinely good, free static backend. For the Footprint-Free line it matters, so we handle it honestly: GitHub Pages is offered but flagged footprint-weaker, the PBN default stays on our fleet or Cloudflare Pages, and the interface warns you when you choose GitHub Pages for a footprint-sensitive site. You decide with the facts in front of you. ## Frequently asked questions **How do I connect my GitHub account?** The preferred way is our Zinn® GitHub App, which you install on your account and grant to selected repositories. It uses granular permissions and short-lived installation tokens — there is no long-lived secret to leak — and you can revoke it in one click. If you would rather use a fine-grained personal access token, we tell you exactly which scopes to grant and validate the token the moment you enter it. **What do you validate about my token?** On entry we call the GitHub API to confirm the token is live and carries the required permissions — repository contents, Pages, and administration for repo creation — and show a green or red check before anything is saved. We never store an unvalidated or over-scoped key. Credentials go to Vault through the same connection seam as every other account you bring. **What do you actually do on my account?** We create repositories (or use an existing one), push your content or build output, enable GitHub Pages from a branch and directory or the GitHub Actions build, and can roll back. For a custom domain we write the repo CNAME, enforce HTTPS, and configure the DNS for you. We can also back the repository up to R2 object storage on a schedule. **Can I use my own domain on a Pages site?** Yes. We write the repository CNAME file, turn on Enforce HTTPS, and configure the DNS — the apex A-records to GitHub's Pages addresses and the www CNAME — following the same apex-and-www rule as every other backend. **Is GitHub Pages safe to use on my PBN?** Use it with your eyes open. GitHub Pages has no server-side rules, so the SEO-crawler blocking can only fall back to robots.txt and meta tags there — it cannot hard-block Ahrefs or Majestic the way our own fleet can — and every Pages site shares GitHub's infrastructure and IP ranges, which is a shared footprint. So on the Footprint-Free line we offer GitHub Pages but flag it as footprint-weaker, keep the PBN default on our fleet or Cloudflare, and warn you when you pick it for a footprint-sensitive site. On the Mainstream line it is a first-class, free static option. --- # Host your whole portfolio, with no shared fingerprint URL: https://zinndigital.com/hosting/multisite 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. ## Portfolio hosting that doesn't act like one server 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. ## Isolation and delivery, built in Every site is separated at the layers that matter, then served over its own path. - **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. - **Isolated filesystem (CageFS)** — Each site gets its own filesystem view. It cannot see other sites, other tenants, or sensitive system files — breaches are contained, not spread. - **Per-site CDN accounts** — 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. - **Clean IP space** — No bad-neighbourhood IPs. Sites are balanced across accounts and separated at the edge, so one compromised site's reputation problem stays its own. ## Why no shared fingerprint matters Separation isn't cosmetic — it protects every site's availability, security and reputation. - One site under load or attack is throttled in its own LVE cage, so the rest of the portfolio stays fast. - Per-site CDN account selection means sites don't all resolve back to the same edge configuration. - MySQL Governor throttles per-site database usage, so one site's heavy queries can't slow the server for the others. - Malware scanning and a proactive WAF are included on every site — a compromise is caught before it can blocklist your IPs. - Immutable, offsite backups per site mean any one site can be restored without touching the others. ## Built for bulk Portfolio and agency work is repetitive by nature — so the platform is designed to do it once, across many. - **Bulk operations** — Deploy, update and manage many sites at once, in a single action instead of one site at a time. - **Server-side caching everywhere** — LSCache full-page cache and per-site Redis object cache keep every site fast, with coordinated purge from the panel or from inside WordPress. - **Free migrations** — Bring your existing portfolio across at no cost. We move the sites; you keep working. - **No vendor lock-in** — Bring your own CDN and DNS accounts, keep ownership of your infrastructure, and leave whenever you like — nothing here is a trap. ## Many sites, no shared fingerprint What makes running dozens or hundreds of sites here different from a conventional multisite install. - **Per-site isolation** — Each site gets its own containment boundary rather than a shared install — one compromise cannot become all of them. - **Per-site CDN accounts** — Sites are distributed across multi-account CDN and DNS pools, so a shared edge account is never the thread that ties your portfolio together. - **Subdomains** — Run a large estate on subdomains without collapsing it into one install and one fingerprint. - **Delegated access** — Give a client or a contractor access to exactly the sites they need, with every privileged action audit-logged. - **Daily backups & restore** — Daily backups with 30-day retention across every site, restorable individually in one click. - **Site tools at scale** — Bulk operations, a web IDE and database maintenance across the whole estate rather than one dashboard login at a time. ## Add-ons that suit a network A multisite is many sites behind one install, so the add-ons that pay off are the ones that scale across all of them. - **AI Update Guard** — 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. - **External 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. - **Managed migration** — We take the network off your old host, put it up here, and check it works before anything is pointed at it. - **The whole add-on catalogue** — Monitoring, SEO data and expert services, bought per site and billed on the invoice you already receive. Migrations are free. ## Frequently asked questions **How is this different from WordPress Multisite?** 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. **How many sites can I host?** 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. **Can one site's problem affect the others?** 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. **Do the sites share IPs or a CDN account?** 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. **Can you move my existing sites over?** 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. --- # Three backends for static and app hosting, one deploy choice URL: https://zinndigital.com/hosting/static Static and app sites deploy to whichever backend suits the job — our own fleet, Cloudflare Pages, or GitHub Pages on your connected account. Same Static product, same custom domains, CDN, DNS and certificates; the backend is a per-site choice at deploy, on both the Footprint-Free and Mainstream lines, from the dashboard and the MCP. ## Choose the backend at deploy Static hosting means files and a build served fast with a custom domain, a CDN and a certificate. Where those files live is the choice you make per site. - **Our own servers** — The V1-style static blueprint: your files served from our fleet with our CDN and DNS and a Let's Encrypt certificate, isolated per site. The default footprint-pool path, and the strongest control for footprint-sensitive PBN sites. - **Cloudflare Pages** — Deploy to Cloudflare Pages for edge delivery plus real application power — client-side JS, Pages Functions and bindings for KV, D1, R2, Durable Objects and Queues. On our Cloudflare account or your own. - **GitHub Pages** — Deploy to GitHub Pages on your connected account — a free, first-class static option for mainstream sites. Offered on the PBN line too, but flagged footprint-weaker so you choose with the trade-off in view. ## One product, one control surface Whichever backend you choose, the rest is identical — so the decision is about fit, not about learning three different systems. - Custom domains work the same way on all three, with both apex and www served and the non-canonical one 301-redirected. - The backend is a deploy-time option, chosen per site on the dashboard and exposed on the MCP for bulk and AI-driven deploys. - Certificates, DNS and CDN are handled for you regardless of where the files land. - Mixing backends across a network is a footprint plus for the Footprint-Free line, not a complication. - Move a site between backends with a redeploy — the domain and DNS travel with it, no rebuild. ## Add-ons that suit a static site There is no database and no PHP to tune here, so the add-ons worth buying are the ones about whether the site is up and whether it is found. - **Uptime and Core Web Vitals monitoring** — Checked on a schedule with the history kept, including sites you host somewhere else entirely. - **Daily index monitoring** — Know the day a page falls out of Google rather than the week, watched per page rather than per site. - **External deploy targets** — Publish to a server of your own from the same deploy tooling, per target. - **The whole add-on catalogue** — Monitoring, SEO data and expert services, bought per site and billed on the invoice you already receive. Migrations are free. ## Frequently asked questions **When is static or app hosting the right choice?** When your site is a build rather than a database-backed CMS: a marketing site, docs, a landing page, a JAMstack or single-page app, or a footprint-diverse PBN property. You get speed and a small attack surface, and with Cloudflare Pages or GitHub Pages you can add edge functions and real data where you need them. **Can I change the backend later?** The three backends sit behind one Static product, so the concept — files, a build, a custom domain, our CDN and DNS, a certificate — is the same across them. Moving a site between backends is a redeploy, not a rebuild, and your domain and DNS come with you. **Which backend is best for a PBN?** Our own fleet and Cloudflare Pages are the strong footprint choices, and mixing backends across a network adds diversity. GitHub Pages is offered too, but flagged footprint-weaker because it shares GitHub's infrastructure and cannot hard-block backlink crawlers — so it is not the PBN default. **Do I choose per site or once for the account?** Per site, at deploy — it is a deploy-time option on the dashboard and the MCP. Different sites in the same account can use different backends, which for the Footprint-Free line is a footprint plus. --- # Sell Zinn® hosting from HostBill URL: https://zinndigital.com/integrations/hostbill Our HostBill module provisions, suspends, unsuspends and terminates real hosting accounts from the panel you already run — free, open source, and no licence key. ## What it does HostBill is the other billing platform serious hosting resellers run, and it has its own module format rather than WHMCS's. This is a real HostBill hosting module, not a WHMCS module with a compatibility shim. The point of a provisioning module is that your panel's own buttons start doing real things. An order creates the account and the site; your suspend button suspends it; your terminate button terminates it. Your client never learns our name unless you want them to. ## What is in it Everything a reseller needs to run hosting as their own product. - **Provisioning on order** — A paid order creates your client's organisation and provisions their site, with the plan you mapped it to. - **Suspend, unsuspend, terminate** — Your panel's lifecycle actions drive ours, so a client who does not pay is suspended by the system that noticed rather than by you, later. - **Single sign-on** — Your client presses “Log in to hosting” in your client area and lands in their control panel already signed in. - **Daily usage sync** — Disk and bandwidth refreshed in your panel from ours, so your overage rules work on real numbers. - **Installed by hand, in one folder** — The archive unpacks to includes/modules/Hosting/zinn/ and there is nothing to compile and no dependency to install. - **Open source** — GPL-2.0-or-later, on GitHub, so you can read exactly what it does before you install it and change it if you need to. ## How to get started 1. **Download the module** — From our billing-panel modules page. No account, no sign-up and no licence key — the archive is served with its SHA-256 so you can verify it. 2. **Create an API key** — In your Zinn Digital® dashboard, with the seven permissions the module needs. The download page lists them exactly. 3. **Map your products and sell** — Point each of your panel products at one of our plans and your next order provisions itself. ## What it costs The module is free. There is no licence key, no per-installation fee, no paid tier holding back the features you need, and no account required to download it. What you pay for is the hosting your clients buy, at reseller rates, and you set what you charge them on top. Reseller hosting has the wholesale plans and the margins; the SEO reporting most agencies charge on is a separate add-on priced for a whole book of client sites rather than per seat. ## Why it is free Because we want you selling our hosting, and charging you for the means to do it would be a strange way to ask. There is no licence key, no per-install fee and no paid tier of the module holding back the features you actually need. It is also open source under the same licence the rest of that ecosystem uses, so nothing about your ability to keep running it depends on our goodwill. If we vanished tomorrow you would still have the code. ## Frequently asked questions **Does the module cost anything?** No. It is free to download and free to use, for ever, with no licence key and no per-installation fee. **Do I need an account to download it?** No. The archive is on our public downloads page with its checksum, and the source is on GitHub. You need an account only when you want to provision something. **Where does it install?** It unpacks to includes/modules/Hosting/zinn/. The folder name matters — it is how the panel finds the module's own functions — so use the path exactly as given. **What can my clients buy through it?** Any hosting plan you have mapped to one of your panel products. You set your own prices; we bill you at reseller rates. **Do my clients see your branding?** Only if you want them to. With white-label branding switched on, the control panel they log into carries your brand, your logo and your domain. **Is this a port of the WHMCS one?** It does the same job and it is written for HostBill's own module interface. A shim between the two would break in ways that are hard to debug at exactly the moment a client is trying to buy something. **Does it support HostBill's automation?** Yes — provisioning, suspension, unsuspension and termination are wired to HostBill's own lifecycle, so your existing automation rules drive it. --- # Sell Zinn® hosting from your own PHP application URL: https://zinndigital.com/integrations/php-client Our your own PHP application module provisions, suspends, unsuspends and terminates real hosting accounts from the panel you already run — free, open source, and no licence key. ## What it does Not everybody bills through WHMCS or HostBill. Some resellers have their own system, and some are building one. The single-file PHP client is the same provisioning logic with no panel around it, so you can call it from whatever you have. The point of a provisioning module is that your panel's own buttons start doing real things. An order creates the account and the site; your suspend button suspends it; your terminate button terminates it. Your client never learns our name unless you want them to. ## What is in it Everything a reseller needs to run hosting as their own product. - **Provisioning on order** — A paid order creates your client's organisation and provisions their site, with the plan you mapped it to. - **Suspend, unsuspend, terminate** — Your panel's lifecycle actions drive ours, so a client who does not pay is suspended by the system that noticed rather than by you, later. - **Single sign-on** — Your client presses “Log in to hosting” in your client area and lands in their control panel already signed in. - **Daily usage sync** — Disk and bandwidth refreshed in your panel from ours, so your overage rules work on real numbers. - **Installed by hand, in one folder** — The archive unpacks to anywhere in your own codebase and there is nothing to compile and no dependency to install. - **Open source** — GPL-2.0-or-later, on GitHub, so you can read exactly what it does before you install it and change it if you need to. ## How to get started 1. **Download the module** — From our billing-panel modules page. No account, no sign-up and no licence key — the archive is served with its SHA-256 so you can verify it. 2. **Create an API key** — In your Zinn Digital® dashboard, with the seven permissions the module needs. The download page lists them exactly. 3. **Map your products and sell** — Point each of your panel products at one of our plans and your next order provisions itself. ## What it costs The module is free. There is no licence key, no per-installation fee, no paid tier holding back the features you need, and no account required to download it. What you pay for is the hosting your clients buy, at reseller rates, and you set what you charge them on top. Reseller hosting has the wholesale plans and the margins; the SEO reporting most agencies charge on is a separate add-on priced for a whole book of client sites rather than per seat. ## Why it is free Because we want you selling our hosting, and charging you for the means to do it would be a strange way to ask. There is no licence key, no per-install fee and no paid tier of the module holding back the features you actually need. It is also open source under the same licence the rest of that ecosystem uses, so nothing about your ability to keep running it depends on our goodwill. If we vanished tomorrow you would still have the code. ## Frequently asked questions **Does the module cost anything?** No. It is free to download and free to use, for ever, with no licence key and no per-installation fee. **Do I need an account to download it?** No. The archive is on our public downloads page with its checksum, and the source is on GitHub. You need an account only when you want to provision something. **Where does it install?** It unpacks to anywhere in your own codebase. The folder name matters — it is how the panel finds the module's own functions — so use the path exactly as given. **What can my clients buy through it?** Any hosting plan you have mapped to one of your panel products. You set your own prices; we bill you at reseller rates. **Do my clients see your branding?** Only if you want them to. With white-label branding switched on, the control panel they log into carries your brand, your logo and your domain. **What exactly is this?** One PHP file with no dependencies that wraps our provisioning API — create, suspend, unsuspend, terminate, usage and single sign-on. Drop it in and call it. **Do I have to use PHP?** For this file, yes. Everything it does is available on our public REST API, which has generated SDKs in TypeScript, Python, PHP and Go if you would rather work from those. **Is it supported?** It is open source and we use the same API behind our own panels, so it does not rot quietly. Bugs go to the GitHub repository. --- # Sell Zinn® hosting from WHMCS URL: https://zinndigital.com/integrations/whmcs Our WHMCS module provisions, suspends, unsuspends and terminates real hosting accounts from the panel you already run — free, open source, and no licence key. ## What it does WHMCS is the billing system most hosting resellers already run, and its server modules are how it talks to the infrastructure behind a product. Ours makes Zinn Digital® hosting one of those products. The point of a provisioning module is that your panel's own buttons start doing real things. An order creates the account and the site; your suspend button suspends it; your terminate button terminates it. Your client never learns our name unless you want them to. ## What is in it Everything a reseller needs to run hosting as their own product. - **Provisioning on order** — A paid order creates your client's organisation and provisions their site, with the plan you mapped it to. - **Suspend, unsuspend, terminate** — Your panel's lifecycle actions drive ours, so a client who does not pay is suspended by the system that noticed rather than by you, later. - **Single sign-on** — Your client presses “Log in to hosting” in your client area and lands in their control panel already signed in. - **Daily usage sync** — Disk and bandwidth refreshed in your panel from ours, so your overage rules work on real numbers. - **Installed by hand, in one folder** — The archive unpacks to modules/servers/zinn/ and there is nothing to compile and no dependency to install. - **Open source** — GPL-2.0-or-later, on GitHub, so you can read exactly what it does before you install it and change it if you need to. ## How to get started 1. **Download the module** — From our billing-panel modules page. No account, no sign-up and no licence key — the archive is served with its SHA-256 so you can verify it. 2. **Create an API key** — In your Zinn Digital® dashboard, with the ten permissions the module needs. The download page lists them exactly. 3. **Map your products and sell** — Point each of your panel products at one of our plans and your next order provisions itself. ## See it working in a real WHMCS A short screen recording on a licensed WHMCS with this module, against the live Zinn® platform: connect your account, sell a plan, and the order builds the site. There is no sound. Turn on captions to follow each step in your language. ## What it costs The module is free. There is no licence key, no per-installation fee, no paid tier holding back the features you need, and no account required to download it. What you pay for is the hosting your clients buy, at reseller rates, and you set what you charge them on top. Reseller hosting has the wholesale plans and the margins; the SEO reporting most agencies charge on is a separate add-on priced for a whole book of client sites rather than per seat. ## Why it is free Because we want you selling our hosting, and charging you for the means to do it would be a strange way to ask. There is no licence key, no per-install fee and no paid tier of the module holding back the features you actually need. It is also open source under the same licence the rest of that ecosystem uses, so nothing about your ability to keep running it depends on our goodwill. If we vanished tomorrow you would still have the code. ## Frequently asked questions **Does the module cost anything?** No. It is free to download and free to use, for ever, with no licence key and no per-installation fee. **Do I need an account to download it?** No. The archive is on our public downloads page with its checksum, and the source is on GitHub. You need an account only when you want to provision something. **Where does it install?** It unpacks to modules/servers/zinn/. The folder name matters — it is how the panel finds the module's own functions — so use the path exactly as given. **What can my clients buy through it?** Any hosting plan you have mapped to one of your panel products. You set your own prices; we bill you at reseller rates. **Do my clients see your branding?** Only if you want them to. With white-label branding switched on, the control panel they log into carries your brand, your logo and your domain. **Which WHMCS versions are supported?** The module declares WHMCS module API 1.1 and runs on PHP 8.2 or later, which covers every supported WHMCS release. **Will it survive a WHMCS upgrade?** Yes. It is a standard server module in its own directory and uses no core patches, so a WHMCS upgrade leaves it alone. --- # Buy and sell links, placements, plugins and expertise — with the money held until it is proven URL: https://zinndigital.com/marketplaces Every storefront runs on one marketplace engine. Every order goes into escrow, fulfilment is verified against live data before funds release, and you buy from Zinn Digital® — one invoice, VAT handled, and the money held until you have the work and have accepted it. ## One engine, four storefronts Backlinks, guest posts, WordPress plugins and third-party services all sit on the same marketplace engine — the same escrow ledger, the same payouts, the same reviews and disputes. Learn it once and it behaves identically everywhere. - **Backlinks** — Sellers list domains they can place a link on. The authority figures are ours, not theirs: we read Trust Flow, Citation Flow, referring domains and Topical Trust Flow from the site itself and stamp each one with the date we checked. The domain is masked until you buy, and any material change sends the listing back through review — so the asset you pay to see is the asset that was approved. - **Guest posts** — Publishers list sites that accept placements, with a sample post and their full offer terms — link type, how long the link stays, price and turnaround. The authority figures are measured by us from the site they name, never typed in by the seller, and each one carries the date we last checked it. Buyers order a placement and run it through a tracked editorial workflow. - **WordPress plugins** — Free and paid plugins with categories, screenshots, ratings, changelogs and WordPress/PHP compatibility. Because we host your sites, buying is not a download — it is a one-click install onto any site in your account. - **Services** — Third-party experts offer malware removal, speed optimisation, SEO, development, design and migration work. The same job may also be available first-party as one of our own Extras — you compare and choose. ## Escrow is the default, not an upgrade Every order on every storefront follows one path: cart and checkout, funds into escrow, fulfilment, verification, release. Nothing about that is optional. - Funds are held in an escrow ledger from checkout — the seller can see the order is funded, and you keep the money until the work is proven. - Pay by card, PayPal or crypto through our payment drivers, or from your wallet and credit balance on the platform. - Commission is taken per sale, and seller payouts run on a schedule and method the seller sets, with KYC for larger sellers. - Buyer and seller message each other inside the order, so the brief, the revisions and the delivery all live in one thread. - Disputes follow a structured resolution path with admin arbitration if the two sides cannot agree. - Ratings and reviews are attached to completed orders, and fraud checks look for self-dealing, fake reviews and manipulated metrics. ## Backlinks that verify themselves The trust problem in a link market is that you pay first and find out later. We close that loop with data instead of goodwill. The figures on a listing are the seller's own — authority, referring domains, traffic — and we do not dress them up as our measurement. What we enforce is identity, which is what actually protects your money: the domain is masked until you buy, and any material change to a listing, the domain above all, sends it back through review before it can go live again. Nobody gets a clean site approved and then quietly swaps another one in behind it. Seller ratings are computed from completed orders rather than typed in. You filter by niche, authority, traffic and price, then order — supplying your target URL and anchor. Funds go into escrow. Once the seller places the link, we poll live backlink data for your URL and confirm four things: the link exists, it carries the attribute you paid for, the anchor matches, and it was first seen after your order. Only then does escrow release. No screenshots, no chasing, no taking anyone's word for it. Verification does not stop at release. Backlink history and new-and-lost monitoring keep watching your placement, so a link that disappears inside the guarantee window triggers a clawback and refund rather than a support ticket you have to open yourself. ## Guest posts, with the editorial workflow built in Placements involve content, editors and revisions — so the marketplace models all three, with every step timestamped and tracked. - **Real offer terms up front** — Publishers set price tiers, turnaround, link attributes, number of links allowed, placement rules, word-count range, content ownership, permanence and their sponsored-disclosure policy — plus acceptable niches and prohibited topics. You see the terms before you order, not after. - **Three ways to get the article** — Supply your own article, order content writing, or have the publisher write it. The brief, target URLs and anchors travel with the order. - **A tracked pipeline** — Brief, draft, plagiarism and quality checks, publisher editorial review, limited revisions, publish, proof with live URL and screenshot, link verification, your approval, escrow release. Each step is timestamped and messaged between both parties. - **Bulk and campaign orders** — Order many placements across a filtered set of sites in one go — built for agencies and operators running campaigns rather than one-off buys. - **Vetting before a site goes live** — Publishers pass manual moderation before their site reaches the storefront, and any material change to a listing sends it back through review before it can go live again. - **Still-live monitoring** — Placements are monitored after publication, with a guarantee and clawback if a link is removed inside the window. ## Plugins that install, not download Because we host the sites, the WordPress plugin marketplace skips the part where you download a zip and upload it somewhere. - One-click install, update and remove to any of your hosted sites, driven by the provisioning API rather than an FTP client. - License keys and a built-in update server, so paid plugins auto-update on your hosted sites with entitlement tied to your purchase or subscription. - Every listed plugin is scanned for malware and quality through our SecurityScanner adapter before it is allowed to go live. - Developer accounts with submissions, versioning, changelogs, revenue share and payouts — with KYC where required. - Our own Zinn® Cache and Zinn® Footprint plugins are featured here free, built to WordPress.org directory standards and credited to Neil Lock — CEO, Zinn Digital® Ltd. - Plugin pages are server-rendered and indexable, so developers get organic discovery, not just an in-app catalogue. ## Services, verified on outcome The services marketplace lets third-party providers sell into the platform: malware removal, speed optimisation, SEO, development and design work, migrations and more. Providers publish a profile, service packages, pricing, turnaround and portfolio, and carry ratings and reviews like any other seller. The order flow is the familiar one — brief, escrow, delivery, your approval, release — with disputes and ongoing or retainer arrangements supported. For security work the bar is higher: a malware removal job is verified by a clean re-scan through Imunify before escrow releases, so the outcome is checked by a scanner rather than declared by the provider. This sits alongside our first-party Extras, which we fulfil ourselves. The same job can exist in both places, and you pick on price, turnaround and rating. ## Selling on the platform Sellers, buyers and staff all live inside the same RBAC and tenancy model as the rest of the platform, so a marketplace account is not a separate silo. - **Commission — 15%** — One platform commission on each marketplace sale. It is 15% today and it is the same rate on every storefront — there is no per-storefront tier to work out and no listing fee to pay before you have sold anything. The commission is recorded against the sale as its own figure, so what you earned and what we took are both on the record rather than folded into one net number. - **Listings with a lifecycle** — Listings are typed per marketplace and move through draft, pending review, live, paused and delisted — and they are versioned, so you can see what changed and when. - **Moderation and vetting** — New listings go through a moderation queue with fraud checks before they can be sold, and admin manages taxonomy, commission tiers and featured placements. - **Payouts and earnings** — Sellers see incoming orders, content to review, earnings and payout history in their dashboard, with listing analytics alongside. - **Promoted placement** — Featured and promoted listings are available for sellers who want visibility beyond organic ranking on the storefront. - **Localised for the markets you sell into** — Storefront and listings localise across 58 languages, which matters when guest-post and backlink demand is per-language and per-market. - **Indexable by design** — Category and listing pages are server-rendered with schema markup and built to rank, so your listings are found from search as well as from inside the platform. ## Frequently asked questions **When does the seller actually get paid?** After fulfilment is verified, not at checkout. Funds sit in the escrow ledger from the moment you pay. For backlinks, release is automatic once live backlink data confirms the link exists with the right attribute and anchor and was first seen after your order. For guest posts, release follows the proof, link verification and your approval. For services, it follows delivery and your approval — and for malware removal, a clean re-scan. Commission is taken per sale and the balance goes to the seller on their payout schedule. **What happens if a link I paid for is removed later?** Placements stay monitored after release. Backlink history and new-and-lost monitoring track the link, and a removal inside the guarantee window triggers a clawback and refund automatically rather than requiring you to notice and complain. The exact guarantee period is set per marketplace policy — check the listing terms before ordering, as publishers also state their own permanence terms. **Can sellers fake their metrics to get better placement?** Less easily than on a marketplace that publishes seller numbers as facts — but the protection is not a metric. A seller must pass review before they can list at all, and any material change to a listing sends it back through review before it can go live again. The figures on a listing are the seller's own and we present them as such, rather than implying we measured them. Your money sits in escrow until fulfilment is verified, ratings are computed from completed orders rather than entered, and disputes follow a structured path with admin arbitration. **Do I have to write the guest-post article myself?** No — you choose. You can supply your own article, order content writing, or have the publisher write it. Whichever route you pick, the article goes through plagiarism and quality checks and the publisher's editorial review, with a limited number of revisions defined in the listing terms, before it is published and verified. **How does buying a plugin work if my sites are hosted with you?** You buy it in the storefront and install it with one click onto any of your hosted sites through the provisioning API — no zip file, no upload. Paid plugins carry a license key and update through our update server, so they stay current automatically for as long as your entitlement is active. Everything listed is scanned for malware and quality before it goes live. **Do I need a hosting plan to use the marketplaces?** You need an account, and the fastest way in is the card-free 14-day trial — no payment details required. One-click plugin install naturally applies to sites you host with us; backlinks, guest posts and services are useful whether the target site is here or elsewhere. **Can I sell as well as buy?** Yes. The same account can be both. Sellers list domains, guest-post sites, plugins or services, pass moderation, and get paid out on their chosen schedule and method, with KYC for larger sellers. Buyers and sellers share the same RBAC and tenancy model as the rest of the platform. **What does it cost to sell here?** 15% commission on each sale. There is no listing fee, no monthly fee, and no charge for the escrow that holds the buyer's money until the work is accepted — so on a completed sale you keep 85%. The rate is the same across every storefront, and the commission is recorded against the sale as its own figure rather than quietly netted out of your payout. --- # Free WordPress plugins from Zinn Digital® URL: https://zinndigital.com/plugins Every WordPress site we host ships with Zinn® Cache for server-side full-page and object caching, and Zinn® Footprint for a cleaner, more generic site fingerprint — pre-installed and kept up to date for you, with nothing to configure. We publish four more you can install on any WordPress site, ours or your own: Zinn® Cache Pro for full-page, object, database and CSS/JS optimisation, Zinn® Connector to publish scheduled articles to a site we do not host, and the Zinn® Reseller Toolkit to sell Zinn Digital® hosting from your own site. All of them are built to WordPress.org directory standards, translated into 58 languages, licensed GPL, tested against the current stable WordPress before every release, and free to download at zinndigital.com/wordpress-plugins. ## Two plugins, no admin, no cost We wrote these plugins to run our own hosting fleet — more than 700,000 sites worldwide — so they are built for scale, security and performance, not as add-ons to upsell. They come switched on when your site is provisioned, and the worker agent keeps the files current: on a new release the plugin is redeployed and re-activated for you, so you never click update. Both are repo-grade: they meet the WordPress Coding Standards, pass security review, raise no PHP notices, and degrade gracefully where a capability is absent. Because they are GPL-2.0-or-later there is no lock-in — you keep working plugins whether or not you stay with us. ## Zinn® Cache — server-side caching and smart purge Full-page caching at the web-server layer, an optional Redis object cache, and purges that only clear what actually changed. - **LSCache control** — Stamps X-LiteSpeed-Cache-Control and tag headers so a LiteSpeed server serves whole pages without touching PHP or MySQL. If the third-party LiteSpeed Cache plugin is present, page caching is deferred to it — no conflict. - **Smart tag-based auto-purge** — When a post, comment, term, theme or plugin changes, only the affected pages and their listings are purged via targeted cache tags — not the whole site. - **Redis object cache** — A one-click toggle installs a self-contained object-cache drop-in that offloads repeated database reads. It never overwrites another plugin's drop-in, and falls back to an in-memory cache if Redis is unreachable, so the site keeps working. - **Safe cache exclusions** — Sensible WordPress, WooCommerce and Easy Digital Downloads defaults — cart, checkout, my-account, REST/AJAX, preview, search and any logged-in or session request are never cached. Add your own path, query and cookie rules per site. - **A signed purge endpoint** — A REST endpoint purges everything, specific URLs or specific tags, for a signed-in administrator or for a request signed with the site's own HMAC-SHA256 secret — reading only the signed payload, never query parameters. - **Graceful degradation** — Full-page caching needs a LiteSpeed server; without one the plugin simply emits no cache headers while the object cache and exclusions keep working. Caching is a per-blueprint capability, not an all-or-nothing switch. ## Zinn® Footprint — a smaller WordPress fingerprint Removes the tell-tale signals that reveal a site is running WordPress, and which version. Every measure is an independent toggle, so any can be turned off if a theme or plugin depends on it. - Removes the generator meta tag from the page head and feeds. - Strips the WordPress version from asset URLs — but only when the ?ver value equals the core version, so custom cache-busting versions are preserved. - Removes RSD, Windows Live Writer, shortlink and REST/oEmbed discovery links. - Disables XML-RPC, a common fingerprint and attack surface. - Disables pingbacks, dropping the pingback methods and the X-Pingback header. - Hides login error detail behind a single generic message instead of confirming which of the username or password was wrong. - Removes the X-Powered-By header where PHP allows it. ## How they reach your site and stay current - Deploy-push is the primary path: the worker agent lays the plugin files into each site as part of the deploy footprint and redeploys them on every release — an idempotent overwrite that also keeps the plugin active. - An in-plugin self-hosted updater is the belt-and-braces layer, force-enabling WordPress auto-updates so the admin reflects the right version even if a fleet push lags. - Updates are pulled over HTTPS from our control plane, HMAC-authenticated in both directions, with the package host restricted and a SHA-256 checksum verified before install — a tampered download is refused. - Per-site secrets are injected from Vault at provision time and never committed; every feature is inert without its constants, so the plugins also run standalone. ## Frequently asked questions **Do the plugins cost anything?** No. Zinn® Cache and Zinn® Footprint are free and ship pre-installed on every WordPress site we host. They are licensed GPL-2.0-or-later, so there is nothing to buy and no lock-in. **Does Zinn® Cache require a LiteSpeed server?** Full-page caching does — it uses the LiteSpeed (LSCache) module or the third-party LiteSpeed Cache plugin. On other servers the plugin simply emits no cache headers, while the Redis object cache and the exclusions continue to work. **What happens if Redis is unavailable?** The object cache is optional. If the phpredis extension is missing the toggle is disabled with a notice, and if Redis becomes unreachable at runtime the drop-in serves from a per-request in-memory cache, so the site never breaks. **Will Zinn® Footprint break my site?** The defaults are safe for typical sites, and every measure is an independent toggle. If an integration relies on XML-RPC — the WordPress mobile app or Jetpack, for example — or on discovery links, you can turn that one measure off. **Do I have to manage or update them?** No. The worker agent keeps the files current on every release and the in-plugin updater force-enables auto-updates, so no one ever has to click update. Updates are signed and checksum-verified before they install. --- # Your sites run where you say they run URL: https://zinndigital.com/regions Region is not a support ticket on this platform — it is a property of the site, honoured by the placement engine every time something is deployed. You choose the data centre when you create a site, from the cities its hosting line offers today, and every deploy lands on fleet capacity in that location, with a global edge in front of it. Each hosting page lists those cities, read live. ## Where we run Two things sit behind every location: the worker fleet that runs your sites, and the control plane that manages them. Both are region-aware. Which location you pick is yours to choose; the capacity underneath it is our own arrangement, and we deliberately run across more than one supplier so no single one is ever the platform. - **Chosen per site** — Each hosting line offers its own set of data centres. You pick one when you create a site, and the order form only offers a city where that line has room today. - **Listed live** — The cities on every hosting page and in the order form are read from the placement engine, so a new location appears the day it has capacity, and a full one is not offered. ## How placement actually works Region is enforced in code, at the moment a site is created — not by an operator remembering which box to use. - **Every worker is tagged** — Each host in the fleet registers itself with a region key, a product-line affinity list, a web-server type and a capacity figure, then pulls work. The placement service filters candidates on region first, then product line, then free capacity, and picks the least-loaded eligible host. - **The site inherits and keeps the region** — If you pinned a region, only workers in that region are eligible. If you did not, the site inherits the region of the worker it lands on and that value is stored on the site — so the record of where your data lives is a field you can read, not an assumption. - **Capacity is claimed atomically** — Placement claims capacity with a conditional update that only succeeds while the worker is still active, still accepting deploys and still under capacity. Two deploys racing for the last slot cannot both win, so a region is never quietly oversubscribed. - **No silent fallback to the wrong region** — If nothing eligible in your region has room, the deploy raises a placement error and stops. It does not fall back to another continent to make the request succeed. A visible failure and a capacity addition beats a site that silently moved country. - **Drain instead of disruption** — Every worker carries an accepts-deploys switch. Flipping it to drain stops new sites landing while existing sites keep running untouched, which is how we do maintenance, hardware refreshes and decommissioning inside a region without moving your workloads. ## Residency as a product decision Data residency is one of the few hosting decisions that is genuinely hard to reverse, so the platform treats it as a first-class dimension rather than a deployment detail. The customer's residency choice is an input to placement, the region is recorded against the site, and the fleet is tagged to match. That is what makes a residency answer auditable instead of anecdotal. The tenancy model runs alongside it. Every record in the engine carries an organisation scope with PostgreSQL row-level security enforced at the database, and tenancy is hierarchical — a reseller organisation above client organisations above sites. Region answers where the data sits; row-level security answers who can reach it. Both matter to a compliance reviewer and neither is optional. GDPR data export and erasure are part of the same design rather than a bolt-on process, and privileged and administrative actions are audit-logged. If your buyer's questionnaire asks where the data lives, who can query it and what happens when a subject asks for it back, those are answerable questions here. ## A local origin is only half the speed story Choosing a nearby region helps, but most of the latency your visitors feel is decided before a request ever reaches your origin. - Cloudflare fronts everything — CDN, WAF, DNS and DDoS protection — so cacheable responses are served from the edge close to the visitor rather than from your origin region. - LSCache runs on the worker itself as a server-level full-page cache with ESI and smart auto-purge, which means most WordPress requests never touch PHP or MySQL at all. - A per-site Redis object cache takes the repeat database reads out of the requests that do reach the application. - Purge is coordinated across both layers from one control in the panel, and from inside WordPress via the Zinn® cache plugin, so an edge copy and an origin copy never disagree after you publish. - Footprint-Free customers layer CDN account pools on top: sites spread across our accounts and your own, with balance recomputed from live account state at deploy time. - We publish no latency or throughput benchmarks, and we do not claim a given region will be fastest for your audience. Pick the region your visitors and your compliance position point at, and let the cache layers do the rest. ## Failure domains, backups and honest boundaries Multi-region is worth very little if everything still shares one fate. The architecture separates the pieces that must not fail together. - **Control plane and fleet are separate** — The engine, database, workflow layer and dashboards run on their own Kubernetes control plane, entirely apart from the worker fleet that serves customer sites. A control-plane incident must not take customer sites down, and a fleet incident must not take the platform down. - **The public surfaces are independent too** — The customer dashboard, the admin console and this marketing site are deployed on Cloudflare independently of the control-plane cluster, so a platform incident does not also remove the place you would go to read about it. - **Status lives off-platform** — The status page is deliberately hosted with a different provider in a different region. A status page running on the infrastructure it monitors is useless at precisely the moment you need it. - **Immutable, offsite, isolated backups** — Per-site backups are immutable and offsite, written to object storage, with restores tested rather than assumed. Restores are one-click from the panel alongside the file manager, domains, DNS, SSL and logs. - **What we do not claim** — We do not assert a service-level agreement, a response time or a latency figure on this page — SLA terms are agreed per contract. The 99.99% figure attached to Footprint-Free plans is an uptime assurance, a target we build to, not a measured historical availability record. ## Picking a region In practice the decision comes down to four questions, and most customers answer them in under a minute. - Do you have a contractual or regulatory residency requirement? If yes, that decides it — EU customers with GDPR obligations choose a data centre inside the European Union, and we have a GDPR-native EU route when a contract demands one specifically. - Where is the audience you actually monetise? Choose the data centre closest to it from the cities the order form offers. - Does your buyer's procurement require a certified underlying platform? If a SOC 2 or ISO 27001 attestation on the infrastructure beneath your sites is a hard gate, tell us before you build and we will place on capacity that holds one. - Do you want your portfolio split across failure domains? Placing sites in more than one data centre removes single-location concentration. - Unsure? Start on the card-free trial. Nothing about the panel, the drivers or the feature set changes when you later deploy elsewhere. ## Frequently asked questions **Can I choose which region my sites are deployed to?** Yes. Region is an input to the placement engine, not a request handled out of band. Pin a region and only fleet workers tagged for that region are eligible to receive the site; the chosen region is then stored on the site record so you can always read back where it runs. Leave it unset and the site inherits the region of the worker it lands on. **Which regions do you run in?** It depends on the hosting line, because each line runs on the capacity built for it. The order form and each hosting page list the cities you can choose today, read live from the placement engine, so this answer never goes out of date. For strict EU residency, choose a data centre inside the European Union; where procurement requires a certified underlying platform, we can place on capacity that meets those requirements. The suppliers behind each location are our own commercial arrangement — you choose the location, not the vendor. **Do you hold SOC 2 or ISO 27001?** No — Zinn Digital® holds no compliance certifications of its own today, and we will not imply otherwise. What we can do is place your workload on an underlying platform that holds them, where a buyer's procurement makes a certified platform beneath your sites a hard requirement. Separately, the platform's own controls are real and inspectable: per-site isolation, row-level security on every tenant-scoped table, secrets held in Vault, TLS throughout, and audit logging of privileged actions. **What happens if the region I want has no capacity?** The deploy fails visibly with a placement error rather than silently landing your site somewhere else. That is deliberate: a site that quietly moved jurisdiction is a far worse outcome than a deploy that stopped and told you why. Capacity is added by bringing more hosts online in that region, where they register themselves and immediately start accepting work. **Will my site be slow for visitors far from its data centre?** We do not publish latency benchmarks and will not promise a specific figure. What we can describe is the architecture: Cloudflare fronts every site so cacheable responses are served from an edge location near the visitor, LSCache serves full pages from the worker without touching PHP or the database, and a per-site Redis object cache absorbs repeat queries. For most content sites that combination means the origin region matters far less than the cache configuration. If your audience is concentrated in one continent, place the origin there anyway. **Can I move an existing site to a different region later?** Region is set when a site is placed and stored on the site record, so a change of region is a migration rather than a toggle. Talk to us before you build if you already know a move is coming — it is much cheaper to place correctly the first time than to relocate a live portfolio. **Where are my backups kept?** Per-site backups are immutable, offsite and isolated from the running fleet, written to object storage with restores tested rather than assumed, and restorable in one click from the panel. If your compliance position requires backup storage to sit in a specific jurisdiction, raise it with us directly — that is a contractual detail we agree per customer rather than a blanket claim we make on a web page. **Can I try it without committing to a region?** Yes. The trial is 14 days and card-free. It covers Footprint-Free Hosting with up to five sites, which is enough to see how deploys, placement and the cache layers behave before you decide where your production portfolio should live. --- # Your account, locked down at the identity layer URL: https://zinndigital.com/security/account Server security protects the sites. Account security protects the keys to them. Every Zinn Digital® login runs on one standards-based identity system — passkeys and WebAuthn, TOTP two-factor, magic-link sign-in, SAML SSO for enterprise and agency teams — with granular roles, per-organisation API keys and an append-only audit log behind it. ## One identity, every surface Most hosting accounts are a password in a database, bolted to a control panel. Ours is a dedicated identity system — Keycloak, speaking OIDC and SAML — that sits in front of everything: the customer dashboard, the staff admin console, this public site and knowledge base, and your support tickets. Sign in once and you are signed in across all of them. Because it is built on open standards rather than a proprietary login, the identity layer is swappable in the same way every other component of the platform is. No part of your access model is trapped inside a vendor's product, and none of your team's authentication depends on us keeping one supplier. That is the same no-lock-in principle we apply to CDN accounts, DNS and payment providers. Sign-in is localised, and the handoff from the site to the login screen carries your language with it — so a team spread across countries is not forced through an English-only login. ## Sign in the way that suits your team Four methods, all first-class, all configurable per person. Nobody is forced onto the weakest option because it is the only one on offer. - **Magic-link email (the default)** — Enter your email, click the link, you are in. No password to phish, reuse, or leak in a breach dump. This is the default route for new accounts, and for most people it is the only one they ever need. - **Passkeys / WebAuthn** — Register a passkey — Touch ID, Face ID, Windows Hello, or a hardware key like a YubiKey — and sign in with no password at all. Passkeys are bound to the origin, so a lookalike login page cannot harvest one. The platform accepts ES256 and RS256 authenticators and prefers user verification. - **Social login** — Sign in with Google through a standard identity-provider connection, so an account inherits whatever controls your Google Workspace already enforces. Further providers connect the same way — nothing about it is a bespoke integration. - **Email and password (fallback)** — Kept for the people and scripts that need it, and held to a real policy: minimum twelve characters, never your username or email address, no reuse of your last three, hashed with Argon2. Email addresses are verified before an account becomes usable. ## Two-factor and brute-force defence Second factors are part of the identity system, not an add-on you buy or a plugin you install on your own site. - TOTP two-factor via any standard authenticator app — six digits on a thirty-second period, the same scheme Google Authenticator, 1Password and Authy speak. It can be enforced by policy across an organisation rather than left to each person's good intentions. - Passkeys can replace the password entirely rather than sitting on top of it, which removes the credential a phisher is trying to steal in the first place. - Brute-force protection is on at the realm level: repeated failed attempts trigger an escalating wait, growing to fifteen minutes, so a credential-stuffing run stalls out instead of grinding through a wordlist. Lockouts are temporary by design — an attacker cannot lock a real customer out of their own account permanently. - Signup email addresses are validated at registration through a ZeroBounce-backed adapter: undeliverable and invalid addresses are rejected, and disposable, role and abuse-flagged addresses are flagged. Fake or unreceivable emails do not get an account, which also feeds trial anti-abuse and fraud checks. - Sessions are held on a short leash — access tokens are short-lived, idle sessions expire, and every session has a hard maximum lifetime, so a forgotten browser on a shared machine is not an open door tomorrow. ## SAML SSO for enterprise and agency teams If your organisation already runs an identity provider — Okta, Entra ID, Google Workspace, or anything else that speaks SAML — you connect it and your people sign in to Zinn Digital® with their existing corporate credentials. There is no second password for your team to manage, and no second offboarding checklist to forget. That matters most at agency and reseller scale, where staff turnover is a genuine security event. When someone leaves and you disable them in your directory, you have disabled their route into your hosting too. Access follows employment, centrally, rather than being chased across a dozen SaaS tools. SAML sits alongside everything else rather than replacing it: contractors can still be given a magic-link account inside a scoped role, while permanent staff come in through SSO. One organisation, one permission model, two front doors. ## Roles that grant only what the job needs Access is scoped to the organisation tree — reseller to client to site — and enforced in the database itself through row-level security, not just in the application. Cross-tenant access is not a policy we ask people to respect; it is a query that cannot return rows. Four customer roles cover the realistic split of duties. - **Owner** — Full control of the organisation and its sub-accounts: create child organisations, invite and remove members, assign roles, manage every site, run billing and invoicing, manage API keys, and read the audit log. - **Billing Manager** — Invoices, subscriptions, payment methods and the plan catalogue — and nothing else. Your finance person or accountant can settle an invoice without ever holding the ability to touch, suspend or delete a live site. - **Developer** — Sites and API access without billing control: view and provision sites, restart services, purge caches, manage API keys and work tickets. Deliberately no access to payment methods, invoicing or plan changes. - **Read-only** — View-only across the organisation — sites, billing, plans, tickets, translation status and the audit log. The right role for an auditor, a client who wants visibility, or a new starter in their first week. ## API keys, tokens and AI connections The dashboard is one way in. The API, the CLI, the Terraform provider and the MCP server are others — and they are held to the same access model, because an unscoped key is a bypass of every role you just configured. - **Keys belong to the organisation** — An API key is issued to an organisation, not to an individual person, and carries its own scopes. Treat it as shared credential material: name it for its purpose, give it the narrowest scopes that work, and rotate it when the person who created it moves on. - **Only a hash is ever stored** — The raw key is shown to you once, at creation. What we keep is a SHA-256 hash and a short prefix for lookup. We cannot show you a key again, and a database compromise does not hand an attacker working credentials. - **Scoped, revocable, observable** — Every key carries granular scopes tied to the same permission catalogue the roles use, records when it was last used, and can be revoked outright the moment it looks wrong. Separate sandbox keys exercise the API with no real billing or provisioning behind them. - **AI tools connect under the same rules** — The MCP server lets any MCP-capable agent manage your hosting — and it authenticates through OAuth 2.1, scoped to your organisation and its RBAC permissions, with per-tool revocable tokens, confirmation on destructive actions, spend caps and full audit logging. Connecting an AI assistant does not mean handing it the keys to everything. ## The audit log, and access to it Every privileged action writes an append-only record — who did it, what they did, what they did it to, the supporting evidence, and the source IP address, with a timestamp. It is not a debugging convenience; it is the evidence trail. - Owner and read-only roles can read the audit log directly, so accountability inside your organisation does not require raising a support ticket with us. - Staff access to your account is governed by the same machinery: our people sit in departments with per-module, per-action permissions, so a support agent sees tickets and basic remediation, not your billing configuration or your fleet. - Sensitive and destructive staff actions can require step-up authentication or two-person approval before they execute. - IP allowlisting is available per organisation for teams that want access narrowed to known networks on top of everything else. - The same audit trail, least-privilege model and per-tenant isolation are what feed our SOC 2 and ISO 27001 roadmap — the evidence is being produced from day one, rather than reconstructed later. ## Frequently asked questions **Do I have to use a password at all?** No — and we would rather you did not. Magic-link email sign-in is the default, and you can register a passkey (Touch ID, Face ID, Windows Hello or a hardware key) and sign in with no password ever set. Email and password remains available as a fallback, held to a twelve-character minimum, no reuse of your last three, and Argon2 hashing. **Can I make two-factor authentication mandatory for my team?** TOTP two-factor is built into the identity layer and can be enforced by policy across an organisation rather than left to each member to opt into. Passkeys are the stronger option where your team's devices support them, since they remove the password an attacker would be phishing for. **Someone on my team only handles invoices. Can I stop them touching sites?** Yes. The Billing Manager role grants invoices, subscriptions, payment methods and the plan catalogue, and nothing else — no ability to view, provision, restart, suspend or delete a site. The reverse also holds: the Developer role manages sites and API access with no billing control at all. Roles are assigned per organisation, so a role in one organisation grants no access in a separate, unrelated organisation — though a role in a parent organisation applies to the organisations nested beneath it. **What happens if one of our API keys leaks?** Revoke it from the dashboard and it stops working immediately. The damage window is bounded by what that key could do in the first place, which is why keys carry granular scopes and record a last-used timestamp — narrow scopes and a visible usage trail are what turn a leak into a contained incident rather than a full account compromise. Note that keys are issued to the organisation rather than to an individual, so treat them as shared credentials and rotate them when people move on. Only a hash of the key is stored on our side, so a leak from our database does not produce a working credential. **Can I see who did what in my account?** Yes. Every privileged action is written to an append-only audit log with the actor, the action, the target, supporting evidence, the source IP and a timestamp. Owner and read-only roles can read it directly. Staff actions on your account are logged in the same trail, and sensitive or destructive staff actions can require step-up authentication or two-person approval first. **We already use Okta / Entra ID. Can our team sign in with that?** Yes — SAML SSO is supported for enterprise and agency accounts, so your people authenticate with existing corporate credentials and offboarding in your directory removes their access here too. You can mix approaches: SSO for permanent staff, scoped magic-link accounts for contractors, all inside the same permission model. **I'm moving from your V1 platform. Does my old password come across?** No — passwords are deliberately not migrated. Your account is imported without one, and on first sign-in you either use magic-link or set a fresh password under the current policy. Porting old password hashes would carry old weaknesses into a new system, so we do not. **How do I try this without handing over card details?** The Footprint-Free trial is 14 days, card-free, and covers up to five sites. You get the full identity layer during the trial — passkeys, two-factor, roles, API keys and the audit log are not gated behind a paid plan. --- # SEO tools and rank tracking, built into your hosting URL: https://zinndigital.com/seo-tools Every site you host with Zinn Digital® ships with free SEO Basics — is it indexed, how strong is its Trust Flow, how fast does the homepage load. When you need more, seventeen SEO tools are each sold on their own, and three or more save 20%. ## SEO built in, not bolted on Because we host the site, the SEO data lives where the controls live. There's no separate tool to log into, no export-and-import, no second bill for a rank tracker that doesn't know anything about your server. Your indexing status, Trust Flow and page speed sit next to the buttons that fix them. Checks are event-driven and cache-first: a new or unindexed site is watched closely, a stable one is re-checked on a lighter cadence, and a re-check fires when your sitemap changes or a new URL appears — not on blanket daily sweeps. You get current data without paying for noise. ## SEO Basics — free on every plan Three signals that answer the questions that matter most, included with every site at no extra cost. - **Is it indexed?** — A straight answer on whether Google has your pages, checked continuously and re-checked when your content changes. - **Trust Flow** — A domain strength score for every site, so you can see at a glance which sites are pulling their weight and which need work — the number PBN operators actually manage to. - **Core Web Vitals** — Homepage load and responsiveness measured against Google's thresholds, with our caching layer already tuned to keep them green. The upsell surface for pages that need attention. ## Seventeen SEO tools, each sold on its own Every tool comes in plans that grow with you, billed monthly or yearly, with no minimum term. Buy only the ones you need. - **Rank tracking** — We check your phrases in Google and keep every reading, so you can see whether last month's work moved anything. Starter tracks 50 phrases weekly; Pro and Agency track 200 and 750 phrases every day, and packs of 50 add more when you need them. - **AI visibility** — Every week we put the questions your customers ask to ChatGPT, Claude, Gemini and Perplexity, and tell you three things: whether they name you, who they name instead, and what is missing from your site that stops them quoting you at all. One price for your whole account — every site you host with us, not one. - **Index monitoring** — A page that is not indexed earns nothing, and nothing tells you when one drops out. We check the pages you name every week and tell you when one leaves — 50, 250 or 1,000 pages depending on your plan. - **Site audits** — Broken links, missing titles, duplicate descriptions, pages nothing links to, redirects that chain. The whole site, monthly, with the list of what changed since last time. - **Backlink monitoring** — Links are bought, earned and then quietly removed. We watch your profile every week and tell you what appeared, what vanished and what it was worth. - **Keyword research** — Search volumes, related phrases and how hard each one is to win — for any market and any language — so the next page you write has a reason to exist beyond a hunch. - **Domain overview and competitor tracking** — Track a competitor the way you track yourself: what they rank for, what is being linked to, and what changed this month. Five domains in a pack, stackable to as many as you need. - **Product price tracking** — Track your products — and your competitors' — on Google Shopping and Amazon every week. Ten products included, packs of 25 and 100 to add more. - **Reputation monitoring** — Somebody searches your brand before they buy. We check what comes back every week — including the results that are not yours — and tell you when it changes. - **Brand mentions** — Tell us the phrases that matter — your brand, a product, a person — and we find the news stories, blog posts and shop pages that mention them, show you whether each one reads positive or negative, and tell you when new ones appear. - **Local rankings** — Choose your business, the towns you serve and the searches your customers make, and we show where you sit on Google Maps, whether you make the local 3-pack, and where your website ranks — with who is above you and how it moves over time. - **Client reports** — Put the rankings, AI visibility, Google index status, site health and backlinks you already track for a client into one PDF under your own logo — written in their language, e-mailed weekly, monthly or quarterly, with a link they can open online. - **PBN footprint checker** — Search engines and competitors look for the traces that show a set of sites has one owner. We check every site you host with us — and any you host elsewhere — for the traces anyone can see, score how exposed the set is, and tell you how to fix each link. - **Domain vetting** — One report reads a domain's backlinks, anchor texts, link history, spam signals, search traffic, Google index status and archived past — then tells you whether it looks clean, needs care or is high risk, with every reason shown. - **Domain alerts** — Save a search of our aged-domain list — by rating, trust flow, referring domains, price, extension, language or topic — and we e-mail you once a day when a new domain matches it, or one you were told about gets at least 10% cheaper. - **Agency SEO data** — Authority, links and search data across your whole book of client sites for one monthly price up to two hundred sites, then a small amount per site after that. Sell it on at your own rate. ## Cheaper together Hold three or more different SEO tools and every one of them is 20% cheaper — the ones you already pay for too, from their next renewal. Pay for a tool yearly and it costs ten months instead of twelve. The two savings stack, so three tools paid yearly cost a third less than their monthly list price. Move a tool to a bigger plan and you pay only the difference for the days left in the period you have already paid for; a difference under 1.00 is not charged. The bigger plan works at once and renews on the same day your old one did. A smaller plan is chosen for your renewal and costs nothing now: your current plan keeps working until its renewal date, then the smaller one replaces it. Change your mind before then and it simply renews as it is. ## Ask our site anything - Our own help centre and marketing pages answer natural-language questions directly — ask how rank tracking is priced or what Trust Flow means and get a cited answer, no digging through docs. - Data comes from an established commercial backlink index behind a swappable adapter, so you're never locked to one vendor. - Every SEO surface is localisable across all our supported languages, so multilingual portfolios get the same tooling in every market. ## Frequently asked questions **What do I get for free versus paid?** SEO Basics is included on every plan at no extra cost: indexed-status checks, Trust Flow and homepage Core Web Vitals for each site. Everything deeper — rankings, AI visibility, audits, backlinks, research and the rest — is one of seventeen SEO tools, each sold on its own. **How many keywords can I track?** Rank tracking Starter tracks 50 phrases weekly; Pro and Agency track 200 and 750 phrases every day, and packs of 50 add more on any plan. **Is there a bundle?** The bundle is a saving rather than a product: hold three or more different SEO tools and every one of them is 20% cheaper. Paying yearly saves two months more. **Does this work across a large PBN?** Yes. The tools are built for networks: the PBN footprint checker reads a whole set of sites at once, and checks are cached and event-driven so fresh data does not mean runaway cost. **Can I try it before paying?** Yes. Start on a card-free 14-day trial and you get SEO Basics on every site straight away. Add a tool whenever you are ready; there is no minimum term. --- # SEO tools pricing — every tool on its own, cheaper together URL: https://zinndigital.com/seo-tools/pricing Every SEO tool is sold on its own, in plans that grow with you. Hold three or more and each is 20% cheaper; pay yearly and save two months more. The prices below are read live from our catalogue, in your currency. ## Where the free line sits SEO Basics is free on every plan, on every site, forever. That means indexed-status checks, a Trust Flow score for the domain and homepage Core Web Vitals — the three things you look at first when you want to know whether a site is working. We can give those away because the underlying bulk endpoints take up to 1,000 targets per request, so answering them across a whole fleet stays inexpensive to run. Everything above that line is deep, per-site work: crawling 250 pages for a technical audit, running Lighthouse, pulling a full backlink profile, checking a keyword's position in a specific location every week. That work has a real per-site cost, so it is priced as an add-on rather than smeared across everyone's hosting bill. You pay for depth on the sites that need it, and nothing on the ones that don't. There is no separate SEO subscription, no seat count and no data-export dance. Add-ons attach to the hosting account you already have, appear as lines on the same invoice, and switch on immediately. ## Three tools or more: 20% off every one Hold three or more different SEO tools and every one of them is 20% cheaper — the ones you already pay for too, from their next renewal. Pay for a tool yearly and it costs ten months instead of twelve. The two savings stack, so three tools paid yearly cost a third less than their monthly list price. A tool counts once however many of its packs you hold. The saving is worked out again on the day each renewal bills, so it is never lost while you qualify — and if you drop to two tools, the rest return to their list price from their next renewal. ## Seventeen SEO tools, each sold on its own Every tool comes in plans that grow with you, billed monthly or yearly, with no minimum term. Buy only the ones you need. - **Rank tracking** — We check your phrases in Google and keep every reading, so you can see whether last month's work moved anything. Starter tracks 50 phrases weekly; Pro and Agency track 200 and 750 phrases every day, and packs of 50 add more when you need them. - **AI visibility** — Every week we put the questions your customers ask to ChatGPT, Claude, Gemini and Perplexity, and tell you three things: whether they name you, who they name instead, and what is missing from your site that stops them quoting you at all. One price for your whole account — every site you host with us, not one. - **Index monitoring** — A page that is not indexed earns nothing, and nothing tells you when one drops out. We check the pages you name every week and tell you when one leaves — 50, 250 or 1,000 pages depending on your plan. - **Site audits** — Broken links, missing titles, duplicate descriptions, pages nothing links to, redirects that chain. The whole site, monthly, with the list of what changed since last time. - **Backlink monitoring** — Links are bought, earned and then quietly removed. We watch your profile every week and tell you what appeared, what vanished and what it was worth. - **Keyword research** — Search volumes, related phrases and how hard each one is to win — for any market and any language — so the next page you write has a reason to exist beyond a hunch. - **Domain overview and competitor tracking** — Track a competitor the way you track yourself: what they rank for, what is being linked to, and what changed this month. Five domains in a pack, stackable to as many as you need. - **Product price tracking** — Track your products — and your competitors' — on Google Shopping and Amazon every week. Ten products included, packs of 25 and 100 to add more. - **Reputation monitoring** — Somebody searches your brand before they buy. We check what comes back every week — including the results that are not yours — and tell you when it changes. - **Brand mentions** — Tell us the phrases that matter — your brand, a product, a person — and we find the news stories, blog posts and shop pages that mention them, show you whether each one reads positive or negative, and tell you when new ones appear. - **Local rankings** — Choose your business, the towns you serve and the searches your customers make, and we show where you sit on Google Maps, whether you make the local 3-pack, and where your website ranks — with who is above you and how it moves over time. - **Client reports** — Put the rankings, AI visibility, Google index status, site health and backlinks you already track for a client into one PDF under your own logo — written in their language, e-mailed weekly, monthly or quarterly, with a link they can open online. - **PBN footprint checker** — Search engines and competitors look for the traces that show a set of sites has one owner. We check every site you host with us — and any you host elsewhere — for the traces anyone can see, score how exposed the set is, and tell you how to fix each link. - **Domain vetting** — One report reads a domain's backlinks, anchor texts, link history, spam signals, search traffic, Google index status and archived past — then tells you whether it looks clean, needs care or is high risk, with every reason shown. - **Domain alerts** — Save a search of our aged-domain list — by rating, trust flow, referring domains, price, extension, language or topic — and we e-mail you once a day when a new domain matches it, or one you were told about gets at least 10% cheaper. - **Agency SEO data** — Authority, links and search data across your whole book of client sites for one monthly price up to two hundred sites, then a small amount per site after that. Sell it on at your own rate. ## Answer-engine visibility Rank tracking tells you where you sit in a list of blue links. This tells you whether ChatGPT, Claude, Gemini and Perplexity name you when someone asks them for a business like yours. It is one of the seventeen tools, so it counts toward the 20% saving. - **AI Visibility Monitoring** — Four answer engines asked the questions your customers ask, every week, automatically. You get whether they name you, which competitors they name instead, and eighteen checks on whether your site can be quoted at all. One price for your whole account, however many sites you host with us — and one competitor domain is included so the comparison works from day one. - **Competitor tracking — 5 more domains** — Five more external domains to watch alongside your own. Your own domains are never counted against this allowance. - **Competitor tracking — 25 more domains** — Twenty-five more. The packs stack, so five and twenty-five together give you thirty-one including the one that comes with the product. ## Changing plan, and going over one Move a tool to a bigger plan and you pay only the difference for the days left in the period you have already paid for; a difference under 1.00 is not charged. The bigger plan works at once and renews on the same day your old one did. A smaller plan is chosen for your renewal and costs nothing now: your current plan keeps working until its renewal date, then the smaller one replaces it. Change your mind before then and it simply renews as it is. Nothing is billed for going over a plan. If you track more than it allows — keywords, pages, brands, sites — the extra items are kept and are not checked until you remove some or add a pack. Packs stack on any plan and are billed as their own monthly line. ## The data you're paying for Margins on SEO tooling are only defensible if the data underneath is good and the cost of fetching it is controlled. Both are engineering decisions we've already made. - Backlink and authority data comes from an established commercial index, refreshed continuously. - Majestic runs alongside it specifically for Trust Flow and Citation Flow, because those are the metrics operators ask for by name. You see Trust Flow and Citation Flow together. - Every provider sits behind a swappable adapter interface, so we can add a second source or change one without touching your data or your reports. - Every provider sits behind a swappable adapter interface, so a vendor's pricing change or outage is our problem to solve, not a reason to re-plumb your reporting. - Re-checks are event-driven and cache-first: new and unindexed sites are watched closely, stable ones settle to a lighter cadence, and a re-check fires when your sitemap's lastmod changes or a new URL appears — never a blanket daily sweep. That discipline is why the free tier can stay free. ## Frequently asked questions **Is there an SEO bundle?** Not as a separate product. Every tool is sold on its own, and the bundle is a saving: once you hold three or more different SEO tools, every one of them is 20% cheaper. **How much does paying yearly save?** A yearly plan costs ten months instead of twelve (16.67% off), and it stacks with the three-tool saving. **How do upgrades and downgrades work?** Move a tool to a bigger plan and you pay only the difference for the days left in the period you have already paid for; a difference under 1.00 is not charged. The bigger plan works at once and renews on the same day your old one did. A smaller plan is chosen for your renewal and costs nothing now: your current plan keeps working until its renewal date, then the smaller one replaces it. Change your mind before then and it simply renews as it is. **What happens if I go over my plan?** Nothing is billed for going over a plan. If you track more than it allows — keywords, pages, brands, sites — the extra items are kept and are not checked until you remove some or add a pack. Packs stack on any plan and are billed as their own monthly line. **Do I have to pay to find out whether my sites are indexed?** No. Indexed-status checks, Trust Flow and homepage Core Web Vitals are the free SEO Basics, included on every plan and every site at no extra cost. **Can I pay in my own currency?** Yes. USD is the base price and your region sets the default currency, which you can switch. A plan renews in the currency it was bought in. --- # Give every person on your team exactly the access they need URL: https://zinndigital.com/teams Four customer roles, sub-accounts that mirror how your business is actually structured, per-organisation API keys, single sign-on and an audit log behind every privileged action. The same access model runs across the dashboard, the API, the CLI, Terraform and our MCP server. Availability: the Terraform provider is in active development and not yet available. Everything else described here is live today. ## Four roles, drawn where the work actually divides Access is not a single on/off switch. Every customer organisation ships with four roles, each a fixed bundle of granular module.action permissions — so a finance contact never touches a server and a developer never sees an invoice. - **Owner** — Full control of the organisation and its sub-accounts: create child organisations, invite and remove members, change roles, manage API keys, provision, restart, suspend and delete sites, manage invoices and payment methods, and read the audit log. Two things deliberately sit outside it — closing an organisation and issuing refunds are staff actions, not a customer role. - **Billing Manager** — Everything financial and nothing else: invoices, subscriptions, payment methods and the plan catalogue, plus a view of the organisation and its member list. No site access at all — a finance contact or an external bookkeeper cannot restart, suspend or delete anything. - **Developer** — Work on sites without touching money: view and provision sites, restart services, purge caches, manage API keys, and raise or reply to support tickets. No billing view, no member management, no suspend and no delete — the destructive and commercial actions stay with the owner. - **Read-only** — A complete view with no ability to change anything — members, sites, billing, plans, tickets, translation status and the audit log. The right role for a client stakeholder, an internal auditor or a new starter still finding their feet. ## Sub-accounts that match your real structure Tenancy is a tree, not a flat list. A reseller organisation sits above its client organisations, and sites sit under those. A team member is a membership — one user, one organisation, one role — so the same primitive powers a two-person team, an agency managing a hundred client accounts and a reseller running sub-accounts under its own brand. Roles are granted per organisation, and enforcement is per organisation too. A role in one organisation grants no access in a separate, unrelated organisation — a contractor can be a Developer on one client account and Read-only on a second, from the same login. Access flows down your own hierarchy, though: a role in a parent organisation applies to the organisations nested beneath it, which is how resellers and agencies manage their clients. Isolation is enforced in the database, not just in application code. Postgres row-level security scopes every tenant query to the caller's subtree, and anything outside that subtree returns a not-found rather than a permission error — so the platform never even confirms that another tenant's organisation or site exists. ## The same permissions across every surface Roles are not a dashboard-only convenience. Every way into the platform resolves to the same permission keys, so there is no back door that skips your access rules. - **Dashboard** — Sites, billing, tickets, notices, notifications, API keys and team management in one shell. The interface renders what the signed-in member's role permits, so people are not shown controls they cannot use. - **Public API and CLI** — The published API is the same engine API the dashboard uses. API keys are issued per organisation with granular scopes tied to the RBAC permissions, and separate sandbox and live modes mean you can test integrations without touching real billing or provisioning. - **Terraform provider** — Manage sites, domains, DNS, mailboxes and plans as infrastructure-as-code and run terraform apply to provision hosting — governed by the same scopes as everything else. - **MCP server** — Connect Claude Code, Cursor, ChatGPT, Claude Desktop or any MCP-capable tool. Tokens are scoped to an organisation and its RBAC permissions, revocable per tool, with confirmation on destructive actions, spend caps and a full audit trail. - **Key handling** — Only a hash of each API key is stored — never the raw key. Keys carry a name and a visible prefix so you can tell them apart, record when they were last used, and are revocable individually without disturbing the rest. ## One login, standards-based, across everything Identity runs on Keycloak, so authentication is proper OIDC and SAML rather than a bespoke login form bolted onto a hosting panel. - Magic-link email login by default, with email and password as a fallback for people who prefer it. - Passkeys and WebAuthn for phishing-resistant sign-in, plus TOTP two-factor authentication enforced for everyone by policy. - Social login via Google, Microsoft, GitHub and other identity providers. - SAML single sign-on for enterprise and agency customers, so team access follows your existing directory. - One session across the dashboard, the admin console, the public site and knowledge base, and support tickets — sign in once, not five times. - Every signup email is validated before an account is created, so undeliverable and invalid addresses never make it onto your team. - Because it is standards-based, the identity provider itself is swappable without re-architecting anything around it — the same no-lock-in rule we apply to every other vendor. ## Accountability you can hand to an auditor Every privileged action writes an append-only audit record: who did it, what they did, what they did it to, the supporting evidence and the originating IP address. The log is append-only — events are added, not edited in place — and in production it is time-partitioned so it stays fast as it grows. Reading that log is itself a permission. Owners and read-only members hold it, so the person responsible for the account and the person auditing it can both see the full history without needing elevated rights to do so. Around that sit the controls larger teams ask for: session policies, optional per-organisation IP allowlists, and step-up authentication on sensitive actions so a live session alone is not enough to do something serious. ## How permissions grow with you The permission catalogue is data, not hardcoded logic — which is why it can be extended without re-plumbing the platform. - 35 granular module.action keys today, spanning organisations, members, API keys, sites, billing, plans, fleet, tickets, customers, abuse, campaigns, translations and audit. - The catalogue is seeded idempotently on every deploy, and validation fails loudly if a role ever references a permission that does not exist — a typo cannot silently grant nothing. - New product capabilities add their permission keys to the catalogue before the endpoint ships, so access control is never retro-fitted after a feature is live. - Scoping a single membership down to specific sites or a specific region is a planned refinement, not something you can switch on today. The current pattern is to place those sites in a child organisation and grant the person a role there — which gives you the same separation using the tenancy tree. - API keys are issued at organisation level rather than per person, so treat them as service credentials for integrations and use memberships for human access. ## Frequently asked questions **What can each role actually do?** Owner has full control of the organisation and its sub-accounts, including members, API keys, sites and payment methods. Billing Manager sees invoices, subscriptions, payment methods and plans, with no site access. Developer manages sites and API keys and handles tickets, with no billing or member control. Read-only can view members, sites, billing, plans, tickets and the audit log without changing anything. **Can I give someone access to just one site?** Not as a per-site setting yet — narrowing a single membership to specific sites is a planned refinement. Today you achieve the same separation with the tenancy tree: put those sites in a child organisation and give the person a role there. Because roles are granted per organisation, that access does not carry over to anything else in your account. **Are API keys tied to individual team members?** No — API keys are issued per organisation, with granular scopes tied to the same RBAC permissions, and separate sandbox and live modes. Use them as service credentials for integrations, CI or Terraform, and use memberships for people. Only a hash of each key is stored, each key records when it was last used, and any key can be revoked on its own. **Can a developer push changes to a live site?** The Developer role covers viewing and provisioning sites, restarting services, purging caches, managing API keys and handling tickets. It does not carry publishing rights over a live site, so if you want someone to be able to promote changes, that access needs to sit with an owner. Roles are per organisation, so you can hold a different one on a different account. **Do you support SSO for our company directory?** Yes. Identity runs on Keycloak with OIDC and SAML, so SAML single sign-on is available for enterprise and agency customers alongside magic-link login, email and password, social providers, passkeys and TOTP two-factor authentication, which is enforced by policy. One session covers the dashboard, the public site and knowledge base, and support tickets. **How do I know who changed something?** Every privileged action is written to an append-only audit log recording the actor, the action, the target, supporting evidence and the IP address. Reading it is a permission in its own right, held by both the Owner and Read-only roles, so an account owner and an auditor can review the same history. **Does adding team members change what I pay?** Plans are priced by hosting capacity rather than by people. On the Footprint-Free line, for example, all 42 tiers share exactly the same entitlement set and differ only by the number of sites they allow. Pricing is always rendered from the live catalogue, in your currency, so what you see on the pricing page is what is actually charged. **Can I try this before committing?** Yes. The Footprint-Free trial runs for 14 days, needs no card details and covers up to 5 sites, so you can set up your organisation, invite your team and test the roles against real work before you pay anything. There is a 30-day money-back guarantee behind the paid plans. --- # Why you can trust your sites to Zinn Digital® URL: https://zinndigital.com/trust A registered UK company, an owned fleet, and more than 600,000 PBN sites hosted in-house, worldwide. This page sets out exactly who you are buying from, how your sites are isolated and backed up, what happens when something goes wrong, and how you get your money back if it does. Availability: per-site database throttling, per-site error tracking and per-site uptime monitoring are in active development and not yet available. Everything else described here is live today. ## A real company, with its name on the door Zinn Digital® LTD is registered in the United Kingdom under company number 16385785, at 71-75 Shelton Street, Covent Garden, London WC2H 9JQ. "Zinn Digital®" is a registered trademark (EUIPO no. 018672629). Those details appear in the footer of every page on this site, in our legal terms and in our structured data — because a hosting company that will not say who it is should not be holding your network. We are the operator, not a reseller. The fleet your sites run on is infrastructure we build, tune and own end to end, and it is the same infrastructure that already carries more than 600,000 PBN sites worldwide. There is no white-labelled upstream between you and your servers, and no third-party panel deciding what we are allowed to fix. The company is led by founder and CEO Neil Lock, with 25+ years of full-stack engineering behind the platform. You can reach us by email at office@zinndigital.com, on Telegram at @zinndigital, or through support tickets from inside your dashboard. ## Try it, and get your money back if it is not right Trust is easier to extend when leaving is cheap. Every commercial term here is designed so the risk of trying us sits with us, not you. - **A card-free trial** — The 14-day Footprint-Free trial starts without payment details — no card, no authorisation hold, no silent conversion. It runs up to 5 sites so you can watch rotation and the footprint layer behave on a real network, then you choose whether to continue. - **30-day no-quibble money-back guarantee** — Paid plans carry a 30-day no-quibble money-back guarantee. "No-quibble" means what it says: you do not have to argue a case or pass a technical interrogation to get a refund inside the window. - **Free migrations in** — We move your existing sites in for you, with an automated migration that imports over a connector, FTP, cPanel or Plesk backup, or SSH, rewrites URLs, verifies the result and cuts DNS over — with rollback if the verification does not pass. - **No vendor lock-in, by architecture** — Every external dependency — payments, DNS, registrar, CDN, mail, AI — sits behind a swappable adapter, and nothing about your site is stored in a proprietary format that only our panel can read. Standard WordPress, standard databases, standard backups. ## How your sites are kept apart from everyone else's Shared infrastructure is only dangerous when it is shared badly. Isolation here is enforced by the kernel, not by good manners. - **Per-site resource cages (LVE)** — CloudLinux Lightweight Virtual Environments cap CPU, RAM, IO, IOPS, processes and entry-processes per site. A site that is attacked, or that runs away with a bad plugin, is throttled inside its own cage — so one bad neighbour cannot take the server down with it. - **Filesystem isolation (CageFS)** — Each tenant gets an isolated view of the filesystem and cannot see other tenants, other sites or sensitive system files. If a site is compromised, CageFS contains the breach rather than letting it walk across the machine. - **Database throttling (MySQL Governor)** — Per-site database usage is governed, so one tenant's heavy or badly-indexed queries cannot drag the server's performance down for everybody else on it. - **Layered DDoS absorption** — Volumetric and L7 floods are absorbed at the Cloudflare edge with per-site rate limiting and managed challenges, network-level protection sits underneath, and LiteSpeed connection throttling plus LVE entry-process limits keep a flood against one site contained to that site. ## Security that is included, and security that is extra We are explicit about the line, because "included security" that turns out to be a paywall is where most hosting trust dies. - Included on every plan: malware scanning, across every site we host. - Included on every plan: the proactive WAF, which blocks exploit attempts against vulnerabilities before a patch exists. - Included on every plan: LVE and CageFS isolation, network firewalling, brute-force protection and IP reputation filtering. - Included on every plan: free SSL certificates, provisioned and renewed automatically across every account. - Upsold as an add-on: one-click malware cleanup and remediation — the fixing of an infected site, on a per-incident or subscription basis. - Upsold as an add-on: advanced protection tiers — enhanced WAF rules, priority scanning, bot management and higher DDoS tiers, dedicated firewall rules. - Why the baseline is free: an infected site threatens its neighbours and our IP reputation, so we cannot leave detection optional. Detection protects the fleet; remediation is work we do for you. ## When something goes wrong Backups only count if they survive the incident that made you need them, and enforcement only counts if it is predictable. - **Daily backups, held 30 days** — Every site is backed up daily and retained for 30 days, with one-click restore from the dashboard. You do not file a ticket and wait to get yesterday back. - **Immutable, offsite, isolated** — Per-site backups are written immutably to offsite object storage and isolated from the running fleet, with restores tested rather than assumed. Ransomware that reaches a site does not reach that site's history. - **Graduated enforcement, not a kill switch** — Instead of a single on/off suspension, sites move through reason-tracked states: throttled (tighter limits, site still up), restricted (outbound mail, cron or POSTs disabled, site still visible), suspended (offline behind a branded, reason-specific holding page), and quarantined (offline and locked for forensics). - **Every transition is logged, notified and appealable** — Each change records its reason, its evidence and whether a human or the policy engine made it; you are notified with what to do about it; and you can appeal. A suspension lifts on payment, fix or successful appeal, and a quarantine lifts after cleanup and review. ## Accountability inside the platform Trust is not only about outsiders. It is also about what we can see, what your team can do, and what is recorded. - **Tenant isolation enforced in the database** — Every record carries a tenant scope and PostgreSQL row-level security enforces it, so cross-tenant reads are blocked at the database rather than trusted to application code getting it right every time. - **Strong authentication as standard** — Identity runs on Keycloak: magic-link login by default, passkeys and WebAuthn, TOTP two-factor, social login, and SAML single sign-on for enterprise and agency customers — one login across the dashboard, the knowledge base and tickets. - **Role-based team access** — Memberships map a user to an organisation with a role — owner, billing, dev or read-only — so a billing contact never touches infrastructure and a read-only account cannot change anything. Organisations nest, so a reseller or agency parent scopes cleanly over its clients. - **Audit logging on privileged actions** — Every privileged and administrative action is written to an audit log with actor, action, target, evidence and IP — including anything our own staff do. Sensitive or destructive staff actions can require step-up authentication or two-person approval. - **Secrets never live in code** — Credentials are held in HashiCorp Vault and injected at runtime, never committed to a repository, baked into an image or written to a log line. - **Scoped API access** — API keys are issued per organisation with granular scopes — read-only, billing, provisioning — tied to the same permission catalogue as the dashboard, with sandbox keys kept separate from production. ## Transparency you can check without asking us Our status page runs on separate infrastructure, off-platform and independent of the fleet it monitors — because a status page hosted on the systems it reports on is worthless at precisely the moment you need it. It is fed by the same monitoring that drives our alerting. Inside the dashboard you get per-site uptime monitoring, Core Web Vitals and performance data, bandwidth, and resource usage measured against your entitlement. The numbers we act on are the numbers you can see, and alerts reach you through your chosen notification channels. Our plans carry a 99.99% uptime assurance — that is the availability target the fleet is engineered and monitored against, stated as a commitment rather than as a historical scorecard. Commercially, the same openness applies: prices are shown in your own currency as a stored, stable figure rather than a live exchange-rate guess, the platform speaks 58 languages, and plan inclusions are published rather than buried. ## Frequently asked questions **Who am I actually buying from?** Zinn Digital® LTD, a company registered in the United Kingdom under number 16385785, at 71-75 Shelton Street, Covent Garden, London WC2H 9JQ, led by founder and CEO Neil Lock. "Zinn Digital®" is a registered trademark (EUIPO no. 018672629). We are the operator of the fleet, not a reseller of somebody else's. **Can another site on the same server compromise mine?** Isolation is designed to contain that, not to be hoped for. CageFS gives each tenant an isolated filesystem view so a compromised site cannot see other tenants' files, and LVE caps its CPU, memory, IO and process usage so it cannot starve its neighbours. No host can honestly promise zero risk on shared infrastructure — what we can tell you is that a breach is contained rather than free to spread, that malware scanning and the proactive WAF run on every site, and that your backups are held immutably offsite and away from the running fleet. **Is malware removal included, or do I pay for it?** Detection is included and removal is an add-on. Every plan includes malware scanning, the proactive WAF that blocks exploits before a patch exists, LVE and CageFS isolation, network firewalling and brute-force protection. One-click malware cleanup and remediation is sold separately, per incident or by subscription, as are advanced protection tiers such as enhanced WAF rules, bot management and higher DDoS tiers. **What happens if my site gets suspended?** Enforcement is graduated and reason-tracked rather than a single switch. A site may first be throttled with tighter resource limits while staying online, then restricted with outbound mail, cron or POST requests disabled while still being visible, then suspended and served a branded holding page that states the reason, and in confirmed malware or phishing cases quarantined with files locked for forensics. Every transition is logged with its reason and evidence, you are notified with the steps to resolve it, and you can appeal. A suspension is lifted on payment, fix or a successful appeal; a quarantine is lifted after cleanup and review, not automatically. **How do I get my money back if it does not work out?** Paid plans carry a 30-day no-quibble money-back guarantee, so you can ask inside the window without having to argue a case. Before that, the 14-day Footprint-Free trial starts card-free with up to 5 sites, so most people never need to pay to find out whether the platform suits them. **If I leave, am I stuck?** No part of your site is held in a format only our panel can read — you run standard WordPress or static HTML, on standard databases, with standard backups you can restore from. Architecturally, every external dependency we use sits behind a swappable adapter, which is the same discipline applied to ourselves: we build so that nothing, including us, becomes a component you cannot replace. **Can I see whether the platform is up without contacting support?** Yes. Our status page runs on separate infrastructure off the platform it reports on, fed by the same monitoring that drives our alerting, and your dashboard shows per-site uptime, Core Web Vitals, error tracking and resource usage against your entitlement. Plans carry a 99.99% uptime assurance as the target the fleet is engineered and monitored against. --- # White-label hosting — your brand on our engine URL: https://zinndigital.com/white-label Sell hosting as your own product. Your brand carries across the panel, the emails and the invoices your clients receive; your clients sit in their own isolated tenants underneath you; and you set the prices. Underneath it is the same control plane, driver fleet and infrastructure we built to host 700,000+ sites worldwide. ## White-label is part of the account model, not a skin Most platforms treat white-labelling as a stylesheet bolted onto a customer panel. Here it is a property of the tenant itself: every organisation carries a brand reference alongside its type, its parent organisation and its default currency. The brand travels with the account, so anything rendered for that account — or for any account beneath it — is rendered in your identity rather than ours. That works because the whole product is built on the Zinn® Design System with semantic design tokens rather than hardcoded colours. The same token layer that gives every surface a light and a dark theme is the layer a brand overrides. There is no separate white-label build to fall behind the main product: your clients get the current panel, in your colours, on the day we ship it. And because product line is a first-class dimension on plans, blueprints and sites, white-label works across every line on the engine — footprint-free, mainstream managed WordPress, WooCommerce and multisite — from one account rather than four integrations. ## The tenancy tree does the isolation for you Organisations are hierarchical from row one: your reseller org sits above client orgs, which sit above their sites. That tree is not an org chart — it is the boundary the database enforces. - **A separate tenant per client** — Each client is its own organisation with its own users, sites, billing and data. Postgres row-level security enforces the boundary at the database, not in application code, so tenant isolation does not rely on every query getting it right. - **Sub-accounts and team seats, one primitive** — Access is a membership: a user, an organisation and a role. Client sub-accounts and your own internal team seats use exactly the same mechanism, so there is no second, weaker access model to reason about. - **Four customer roles** — Owner, billing, developer and read-only. Roles resolve to granular module-and-action permissions, so what each person can reach is explicit rather than inherited from whoever invited them. - **Per-site compute isolation** — Sites run isolated from one another, so a compromise on one client's site is contained rather than free to reach a neighbour's. - **Everything privileged is audit-logged** — Actor, action, target, metadata, IP and timestamp on every privileged action, scoped to the organisation it happened in. When a client asks who changed what, there is an answer. - **Scoped API access** — Per-organisation API keys and OAuth clients with granular scopes tied to the same permission catalogue. The public API, CLI, Terraform provider and MCP server all authenticate the same way. ## You set the prices. We bill you, you bill them. Reseller billing is hierarchical in the same shape as the tenancy tree: we invoice you, and you invoice your clients — in your own currency, at your own markup. You set your own plan prices; commissions and margins are tracked for you rather than reconciled by hand in a spreadsheet. Two details matter more than they sound. First, price is captured at purchase: a subscription pins the exact plan version and records the amount and currency the customer actually paid — which may reflect FX, a discount or your markup — so a later catalogue edit or currency movement never rewrites what a live subscriber was sold. Second, on domains the reseller overlay is explicit: cart pricing composes platform sell price, then your markup, then any promotion, and the difference between wholesale cost, sell price and your cut is written to a margin ledger row per order line. Invoicing follows the tree too. You see your invoices from us; your clients see invoices from you. Recurring charges are driven by our engine rather than by a payment gateway's subscription object, which is what keeps hierarchical reseller billing and multi-currency capture possible in the first place — there is no gateway construct that models a reseller. ## Branded on every surface a client actually sees A white-label panel is worth little if the confirmation email arrives from somebody else. The brand carries through the whole customer-facing chain. - The panel — the full self-service surface, in your brand, on the same design system and the same release train as the product we run ourselves. - Transactional email — templates are ours and admin-editable, brand-tokened, and white-label per reseller, so the layout, header and footer follow the brand on the account. - Your own sending domains — white-label product lines and resellers can send from their own verified domains under the same typed sender scheme (system, billing, support, updates), with SPF, DKIM and DMARC on the sending domain. - Marketing and lifecycle campaigns — the built-in campaign system uses the same brand-tokened, auto-translated templates, so a nudge to your client reads as coming from you. - Invoices and receipts — issued in the right direction of the tree, in the right currency, with the right identity on them. - Login — one Keycloak-backed identity across panel, knowledge base and tickets, with magic-link, password, social, passkeys and TOTP, plus SAML SSO for enterprise and agency clients. - Your own nameservers — claim a domain you own and your clients' zones are delegated to ns1 and ns2 under it, served from our own anycast DNS estate. The glue records stay yours to publish at your registrar, and we verify they answer before a single zone moves. ## Localized and multi-currency without a second build Every user-facing string, notification and email is localizable into 58 languages, and content is auto-translated as part of the content lifecycle rather than as a manual afterthought. Right-to-left languages including Arabic are handled properly — the interface uses logical CSS properties throughout, so a mirrored layout is the same layout, not a separate stylesheet that drifts. Pricing is multi-currency on the same terms. USD is the base; other currencies are derived through an FX adapter, charm-rounded and stored, and the panel renders the stored price rather than converting on every request. A subscription locks its currency and price at signup. Money is never a float anywhere in the system: it is integer minor units plus an ISO currency code, end to end. The practical consequence for a white-label partner is that selling into a second country is a pricing decision, not an engineering project. ## The same engine, with nothing you cannot leave with There is no separate reseller stack. White-label runs on the control plane that owns customers, billing, provisioning, tickets and events, and drives the same pluggable drivers for CDN, DNS, registrar, payments, mail and everything else. Whatever ships to the platform ships to your clients. Every external dependency sits behind an adapter interface with more than one implementation, so no payment gateway, registrar, DNS provider or CDN is welded into the business logic. That rule protects us, and by extension it protects the book of recurring revenue you build on top of us: a gateway can be swapped, or a second added per region, without migrating your customers. Migrations onto the platform are free and run as a durable, resumable workflow rather than a manual copy — so moving an existing client base is a scheduled operation, not a weekend. ## Pricing White-label sits on our reseller and agency lines, which are new — tiers are not published yet. If you are already running client sites at scale and want early pricing, [talk to us](/contact) and we will scope it with you, including migrating your existing sites across at no cost. In the meantime you can start free with a card-free 14-day trial on our footprint-free line (up to 5 sites, no card details) and see the panel, tenancy and billing model for yourself. ## Frequently asked questions **What exactly gets white-labelled?** The brand is a property of the organisation, so it carries across the client-facing panel, the transactional email templates, marketing and lifecycle campaigns, and the invoices your clients receive. White-label partners can also send from their own verified domains rather than ours. Because the design system uses semantic tokens rather than hardcoded styling, branded surfaces stay on the same release train as the standard product. Your nameservers can carry the brand too: claim a domain you own and your clients' zones are delegated to ns1 and ns2 under it rather than to ours, served from the same anycast DNS estate, with the glue records published at your own registrar and verified to answer before any zone moves. **How are my clients kept separate from one another?** Each client is a distinct organisation in a hierarchical reseller-to-client-to-site tree, and Postgres row-level security enforces that boundary at the database rather than in application code. On top of that, sites run with per-site compute isolation, so a compromise on one site is contained rather than able to reach a neighbour. **Can I set my own prices and keep the margin?** Yes. Billing is hierarchical: we bill you, you bill your clients, in your own currency and at your own markup. Price is captured at the moment of purchase against a pinned plan version, so later catalogue or FX changes never rewrite what a live subscriber was sold. On domain orders the platform sell price, your markup and any promotion compose in that order, and your cut is recorded on a margin ledger row per order line. **Which product lines can I white-label?** White-label works across every line on the engine — footprint-free hosting, mainstream managed WordPress, WooCommerce and multisite — because product line is a first-class dimension on plans, blueprints and sites rather than two separate applications. **How do team access and sub-accounts differ?** They do not, mechanically. Both are memberships — a user, an organisation and a role — so client sub-accounts and your own internal seats use the same access model. The customer roles are owner, billing, developer and read-only, and each resolves to a granular set of module-and-action permissions. **Will my clients see the platform in their own language and currency?** Yes. The interface, notifications and content are localizable into 58 languages with proper right-to-left support, and pricing is multi-currency: USD is the base, other currencies are derived, charm-rounded and stored, and a subscription locks its currency and price at signup. **Am I locked in if I build my business on this?** Every external service — payments, registrar, DNS, CDN, mail — sits behind an adapter interface with more than one implementation, and recurring billing is driven by our engine rather than by a gateway's own subscription objects. That is what makes a recurring book portable. Migrations onto the platform are free and run as a durable workflow. **What does white-label cost?** Reseller and agency are new product lines and their tiers are not published yet. Contact us for early pricing. You can evaluate the platform now on a card-free 14-day trial on the footprint-free line, which covers up to 5 sites and needs no card details. --- # Eight reasons this platform is built differently URL: https://zinndigital.com/why-zinn Zinn Digital® is an operator-run hosting platform: we own the engine, the plugins and the automation — built by founder Neil Lock, an SEO scientist and 25-year full-stack engineer — which is why the platform can do things a repackaged control panel cannot. Here is every one of them, with the page that proves it. Availability: per-site database throttling is in active development and not yet available. Everything else described here is live today. ## The eight things that make the difference Each one is a real capability with its own page — read the detail rather than taking the summary on trust. - **1 · Connect any AI tool to your hosting** — A hosted MCP server lets any MCP-capable agent — Claude Code, Cursor, ChatGPT, Claude Desktop — manage, build and deploy your hosting in plain language. One connection, the whole tool catalog, scoped to what your account may already do. - **2 · Two-layer caching, one control** — LiteSpeed Enterprise with LSCache full-page caching, plus a per-site Redis object cache, plus CDN at the edge — coordinated, with smart auto-purge so editing a post clears only the pages it affects, across server and CDN in step. - **3 · Free plugins we build and ship** — Zinn® Cache and Zinn® Footprint are written to WordPress.org directory standards, GPL-2.0+, security-reviewed and translation-ready. They ship pre-installed in the deploy footprint, auto-update silently, and cost nothing. - **4 · Footprint control at two layers** — Infrastructure: multi-Cloudflare and CDN account pools with footprint-aware rotation recomputed at deploy time, per-site CDN selection and static-HTML mode. Site: the Footprint plugin strips the WordPress fingerprint automatically. - **5 · Multisite hosting without a shared fingerprint** — The same technology, framed for portfolios and agencies: host dozens or hundreds of sites with isolated delivery, no bad-neighbourhood IPs and full self-service — without any of the network language. - **6 · Wayback Machine restore, built in** — Point us at a domain and pick any date the archive holds, and we rebuild it: archive toolbar and injected code stripped, links and asset paths rewritten, output as static HTML or a full WordPress site. - **7 · SEO tools in the panel** — A free SEO Basics tile on every plan — indexed or not, Trust Flow, Core Web Vitals — and seventeen paid SEO tools adding rank tracking, backlink monitoring, competitor intelligence, site health audits and an AI content assistant. - **8 · Everything else, included rather than upsold** — Kernel-level isolation, malware scanning and a proactive WAF, free automated migrations, immutable offsite backups, staging with push-to-live and git deployment, and a CDN account pool — all part of the platform. ## AI-native, because the platform was designed for agents from the start Most hosting bolts an assistant onto a dashboard. We expose the platform itself over an open protocol, so your AI tool of choice drives it directly. The Model Context Protocol is the open standard for connecting AI agents to systems. Our MCP server is a thin protocol adapter sitting over the same engine API the dashboard uses — the same action catalog, the same permissions, the same audit trail. That means there is no second, weaker set of AI-only logic to get out of step, and no per-tool integration to maintain. We support the protocol; whatever agent you use next works too. The three primitives are all there. Tools are the actions: clone to staging, push to live, purge cache, restore from Wayback, run wp-cli, connect a git repo and deploy or roll back, edit DNS, issue certificates, take backups, read SEO data, check billing. Resources are read-only context — site health, config, recent logs, metrics, KB articles — so the agent diagnoses with real data before it touches anything. Prompts are reusable workflows we publish, such as diagnosing a site or preparing a migration. Safety is the reason it can be allowed near live infrastructure. Authorisation is OAuth 2.1, tokens are scoped to your organisation and your role permissions with row-level security enforced in the database, and every token is per-tool and revocable. Destructive actions require explicit confirmation, spend caps bound anything that costs money, retries are idempotent, and every action is written to the audit log with the identity, the tool, the arguments and the result. - Connect from the dashboard: generate an endpoint, then paste a one-click config snippet for Claude Code, Cursor, ChatGPT or Claude Desktop. - Interactive by design — AI actions stream and are never queued behind a background job system. - Separate sandbox and production tokens, so an agent can be tried without pointing it at live sites. ## Speed designed at the origin, not just at the edge A CDN only helps with what it can cache. We cache in three coordinated layers and keep them consistent. - **LSCache full-page cache** — LiteSpeed Enterprise serves cached pages directly, so the great majority of visits never reach PHP or MySQL at all. This is the layer that decides WordPress TTFB. - **Per-site Redis object cache** — Dynamic pages that genuinely must run PHP stay fast under load, because repeated database work is served from memory — per site, not shared across tenants. - **CDN and edge on top** — Static assets and cacheable HTML are served close to the visitor from the CDN account you choose, with purge coordinated against the origin rather than fired blindly. - **Smart auto-purge** — Edit a post and only the affected pages clear — on the server and at the CDN, in step. Tag-based invalidation is what makes aggressive caching safe to leave on. - **Safe-by-default exclusions** — Cart, checkout and logged-in sessions are never cached. Fast static pages that never break a purchase is the whole point of the WooCommerce tuning. - **Modern transport underneath** — NVMe storage, HTTP/3, per-site PHP version and extension selection, and our own branded authoritative DNS across the fleet. ## Isolation and containment, honestly described Density is only acceptable if one site's bad day stays that site's bad day. Here is exactly what is included and what is not. Every site runs inside a CloudLinux lightweight virtual environment with its own caps on CPU, memory, IO, IOPS, processes and entry processes. A site that runs away, or that is being attacked, is throttled inside its own cage rather than taking the server with it. CageFS gives each tenant an isolated filesystem view — it cannot see other tenants, other sites or sensitive system files, which contains a breach rather than letting it spread. MySQL Governor throttles per-site database usage, so heavy queries on one site do not become slow pages on another. Attack absorption is layered: Cloudflare at the edge for volumetric floods, L7 WAF, per-site rate limiting and managed challenges; provider protection at the network layer; and LiteSpeed connection throttling with Imunify360's network firewall and entry-process limits on the server itself. On malware we are precise about the boundary. Malware scanning, the proactive WAF that blocks exploits before a patch exists, and LVE and CageFS isolation are included for every site on every plan — an infected site threatens its neighbours and our IP reputation, so that protection is never optional. One-click malware cleanup and remediation is an add-on, sold per incident or by subscription, as are advanced protection tiers such as enhanced WAF rules, priority scanning, bot management and dedicated firewall rules. ## An engine we own, with no way to be trapped in it Being the operator rather than a reseller is what makes the rest of this page possible — and it is also why leaving is easy. - Every external dependency — payments, registrar, DNS, CDN, cloud, mail, translation, LLM, SEO data, malware scanning — sits behind an adapter with more than one implementation. No vendor is the brain. - Bring your own Cloudflare and CDN accounts. You keep ownership of the accounts, the domains and the DNS; we orchestrate them rather than hold them. - The public API is the same API the dashboard, CLI, Terraform provider and MCP server use, and no endpoint ships unless it is in the OpenAPI specification — so it is fully documented by construction. - Generated SDKs in TypeScript, Python, PHP and Go, plus a CLI and a Terraform provider, so your infrastructure can be code rather than clicks. - Free automated migrations in, over connector, FTP, cPanel or SSH, with automatic search-replace, verification, DNS cutover and rollback — and nothing stopping you migrating out. - Immutable, offsite, isolated per-site backups with tested restores, so your data is recoverable independently of any one system. ## Built for the whole world from the first line of code Internationalisation here is architecture, not a translation plugin added later. - **58 languages** — Every page, email, notification and knowledge base article is localisable into 58 languages, including full right-to-left support. Content changes re-translate automatically rather than waiting for someone to remember. - **Multi-currency pricing** — Prices are held in USD and converted, rounded sensibly and stored per currency — so you see a real price in your own currency, not a live conversion that shifts between page load and checkout. - **Your currency is yours to choose** — We default from your region, you can switch at any time, and the choice follows your account. A subscription locks its currency and price at signup so nothing moves under you. - **Multi-region infrastructure** — Regional placement and data residency are first-class, so sites can be hosted where their audience and their compliance requirements are. - **AI-answerable content** — Every public page is server-rendered with structured data and an LLM content map, so answer engines can read and cite it accurately — the same discipline we apply to your sites' SEO. - **One account, both product lines** — Footprint-Free bulk hosting and mainstream managed WordPress run on one engine and one login, so a portfolio can contain both without splitting your billing or your tooling. ## Plans are data, and the trial costs nothing No sales call, no card, no negotiation ladder. Footprint-Free Hosting runs on 42 tiers, sized by the number of sites you actually have, from PBN 5 at $6/mo up to PBN 2000 at $2000/mo. Every tier carries the identical entitlement set — footprint-free delivery, free SSL, 4 GB of disk and 100 GB of bandwidth per site with more available at any time, daily backups held 30 days with one-click restore, 106 managed footprints, free 10GB email per domain, Majestic metrics, automatic indexing checks and the domain checker. The only thing that changes as you move up is how many sites you may run. ## Frequently asked questions **What actually makes Zinn Digital® different?** Three structural things. We operate the platform ourselves rather than reselling someone else's, so the automation goes as deep as we need it to. We expose the whole platform over MCP, so any AI agent can drive it with your permissions and your audit trail. And we build the WordPress plugins that make caching and footprint control work, ship them free in every deploy, and hold them to WordPress.org directory standards. Everything on this page follows from those three. **Do I have to use AI to get value from the platform?** No. The dashboard gives you full control on its own, and every AI capability is optional and opt-in. The MCP server exists so that if you already work in Claude Code, Cursor or ChatGPT, your hosting is reachable from there rather than being a separate tab. Nothing is AI-only. **Is connecting an AI agent to live hosting safe?** It is bounded rather than unrestricted. An agent inherits exactly the permissions of the identity that authorised it and nothing more, tokens are scoped per tool and individually revocable, row-level security applies in the database itself, destructive actions such as deletion, suspension or spend require explicit confirmation, spend caps limit anything chargeable, and every action is audit-logged with its arguments and result. We would not describe any automation as risk-free, but the blast radius is defined and reviewable. **If a site gets hacked, do you clean it up?** Detection is included on every plan: malware scanning, a proactive WAF that blocks exploits before patches exist, and kernel-level isolation that keeps a compromise inside its own cage. Remediation is different — one-click malware cleanup is an add-on, available per incident or by subscription, alongside advanced protection tiers. We are deliberate about that split so you know what you have before you need it. **What happens if a site of mine is quarantined or suspended?** Quarantine is a containment state and it is not automatic to leave: the site returns only after the issue is cleaned up and the case is reviewed — a follow-up scan alone does not release it. Suspension is the account-level state, resolved by settling payment, fixing the underlying issue or a successful appeal, and it is the state where visitors see a branded holding page rather than a broken site. **Can I bring my own CDN and DNS accounts, or am I locked into yours?** Bring your own. You can add your own Cloudflare and CDN accounts alongside ours and choose which account each site deploys to, keeping ownership of the accounts and the domains. More broadly, every external service on the platform sits behind a swappable adapter, migrations in are free, and there is nothing preventing a migration out. **Is footprint-free hosting the same as multisite hosting?** The technology underneath is shared, the framing is not. Footprint-Free is for network operators and leads with CDN account rotation, the footprint plugin, static-HTML mode and Wayback restore. Multisite and agency hosting sell the same isolation and per-site delivery to people running a portfolio or client sites, without the network language. One caveat worth stating plainly: subdomains share their parent registrable domain and, under a wildcard certificate, a certificate — which makes them linkable through certificate transparency logs. Subdomains belong on the multisite and agency lines, not the footprint-free one. **How much is it, and can I try it before paying?** Footprint-Free runs from $6/mo for PBN 5 to $2000/mo for PBN 2000 across 42 tiers, shown in your currency. You can start with a 14-day, card-free trial on that line with up to five sites, one trial per identity. Paid plans carry a 30-day no-quibble money-back guarantee and free migrations. --- # Everything a WordPress care plan sells. Included, at no extra cost. URL: https://zinndigital.com/wp-care Updates, backups, malware scanning, uptime and performance monitoring, and a real person to ask. The maintenance industry charges from $59 a month for that list. Here it is not an add-on, not a tier and not a bolt-on — it is what hosting means. ## Why a care plan exists at all A WordPress site is not a thing you build once. Core ships security releases, plugins ship breaking changes, a backup nobody has ever restored is not a backup, and the first time most owners hear about any of it is when a customer emails to say the site is down. The maintenance industry grew up around exactly that gap, and it is a real gap. Our objection is not to the work. It is to the invoice. Every item on a typical care plan is something the platform hosting the site is already closest to — it knows when core shipped, it holds the backups, it runs the scanner, it is the first to notice the site is not answering. Charging a second monthly fee for the platform to use what it already has is a packaging decision, not a cost. So we made the opposite packaging decision. There is no WP Care plan to buy, there is no tier that unlocks it, and there is no page where you top it up. It is in the hosting. ## Line by line, against a typical care plan Every row on our side was checked against the running platform before this page was published, and the ones that are not universal say so rather than being rounded up to a tick. | | Zinn Digital® hosting | A typical WordPress care plan | | --- | --- | --- | | Monthly price for the care list | Included | from $59 | | WordPress core security and minor updates | Yes | Yes | | Plugin, theme and user management without wp-admin | Yes | Partial support | | Daily off-site backups | Yes | Yes | | Restore a backup yourself, without asking anyone | Yes | Partial support | | Malware scanning | Yes | Yes | | Uptime monitoring | 3 free, then $9/mo per 10 | Yes | | Core Web Vitals and resource monitoring, automatic | Yes | Partial support | | Function-level PHP request profiling | Yes | No | | Free SSL, renewed for you | Yes | Partial support | | Staging site | Partial support | Partial support | | Free migration on to the platform | Yes | No | | Uptime guarantee with credits, in writing | Yes | No | | The hosting itself | Yes | No | The $59 figure is the entry price we observed across the WordPress maintenance market in September 2026, not a quotation from any one supplier — prices move and this page does not track them. “Partial” means it depends on the plan or the supplier: staging is on some of our plans and not others, and each plan page says which. One row deserves its own sentence rather than a footnote: uptime checks are added BY YOU, per address — three free with any account, including addresses we do not host — and are not switched on automatically for every site you have with us. Core Web Vitals, bandwidth and resource use are measured automatically on the sites we host. Nothing else in the first column is a promise this platform does not already keep. ## What each of those actually means here - **Core updates, applied** — Sites on our own fleet are configured for WordPress security and minor core releases automatically. Major versions stay your decision, because an unannounced major upgrade is not maintenance, it is a surprise. - **WordPress without wp-admin** — Plugins, themes, users, updates and integrity checks from your Zinn® dashboard. You never have to hold a wp-admin password for a site you own to keep it patched. - **Backups you can prove** — Daily, off-site, and restorable by you from the dashboard. A restore you have to open a ticket for is a restore you find out about during an incident. - **Malware scanning** — Every site on our fleet is scanned, and a site we cannot scan reports why rather than quietly reporting nothing. - **Vitals, resources and uptime** — Core Web Vitals, bandwidth and resource use against your plan are measured automatically on every site we host. Uptime is a check you add per address — three free with any account, and they can watch addresses we do not host — because we watch what you ask us to watch rather than guessing at your list. - **Request profiling** — Function-level PHP profiling on every plan — the thing you actually need when a page is slow and the plugin list is long. - **SSL that renews itself** — Free certificates, issued and renewed by the platform. An expired certificate is the commonest self-inflicted outage there is. - **Somebody to ask** — Support is included and is not metered per incident. There is also a pre-sales assistant on this site that answers from our knowledge base and live price list before you buy. ## Moving an existing site over is the part we do for you The reason people stay on a care plan they resent is that moving sounds worse than paying. It is not: migration on to our platform is free and automated, it is verified rather than assumed, and it happens before anything is pointed at us — so you look at the site running here, and only then change a nameserver. If it goes wrong, nothing has changed for your visitors, because nothing was pointing at us yet. - Free, on every plan that lists free migrations - Verified against the source before you switch anything - Your old host keeps serving until you say otherwise ## Ask before you move You do not have to guess whether your site fits. Ask Zinn® answers from our knowledge base and our live price list — not from a sales script — and it will tell you when it does not know. - **Ask Zinn®** — Answers from the knowledge base and today's prices - **Email** — office@zinndigital.com - **Knowledge base** — Guides for everything above ## Frequently asked questions **Is this a plan I have to buy?** No. There is nothing on this page to add to a basket. Every item listed comes with hosting, and the plan pages say which of them apply to which plan. **What is the catch?** That you host with us. That is the whole of it — the list above is what the platform already does for a site it is hosting, and we have decided not to invoice for it separately. If you host elsewhere, none of it applies to you. **Do you update plugins automatically too?** Core security and minor releases are automatic on our own fleet. Plugins and themes are managed from your dashboard rather than blindly auto-updated, because a plugin update is the commonest cause of a broken site and the decision should be yours. Our AI Update Guard exists for exactly that call and will tell you what is likely to break before you press the button. **What if I want a human to do the updates for me?** That is a service rather than a feature, and it is bought as one — see our expert services. The distinction is deliberate: software that runs for you is included, and an engineer's time is not. **Is uptime monitoring included?** Three uptime checks are free with any account and you choose which addresses they watch — including addresses we do not host. It is deliberately not switched on automatically for every site you have with us: we watch what you ask us to watch, and a site you have not added is not being measured. More checks are $9 a month per ten. What IS automatic on the sites we host is Core Web Vitals, bandwidth and resource monitoring, in the dashboard, with alerts. **Where do I see the uptime guarantee?** On the SLA page. We engineer to a 99.99% uptime target and commit contractually to 99.9% with credits — the agreement is what counts if the two ever disagree. --- # The developer CLI for WordPress hosting URL: https://zinndigital.com/zinnector Zinnector® builds WordPress locally with nothing installed but Node — no Docker, no MAMP — then checks what you built against the hosting slot you are about to deploy to and tells you what will not match, before you push. It is free, MIT-licensed and built on the same public API as everything else here. ## Five commands, and the middle one is the point Most hosting CLIs start at deploy. Zinnector® starts before that — it builds the site with you, and then it checks your work against the machine you are about to send it to. The gap between “it ran on my laptop” and “it runs on the server” is where the afternoons go, and that gap is measurable. - **zinnector new** — Scaffold a site, a plugin or a block theme that boots immediately. No placeholder files, no TODOs — the plugin activates and the theme can be selected the moment it exists. - **zinnector dev** — A real WordPress on your machine in seconds, serving your own plugins and themes, with no Docker and no PHP on your PATH. Pick any PHP from 5.2 to 8.5 to develop against. - **zinnector check** — The pre-flight. Compares what you built against the slot you are about to deploy to and names every mismatch — and every check it could not make — before you push. - **zinnector push** — Pre-flight, push your commits, trigger the deploy and watch it to completion. If it fails, the build log is one command away. - **zinnector ai** — Ask the assistant from the terminal, with your project and your site as context. It runs on the platform against your own account, so no model key is ever stored on your machine. ## Test it works in two minutes, no account needed Six commands, in order, and what success looks like at each one. Everything here runs on your own machine; an API key is only needed when you reach a hosting slot. 1. **Install it** — Run npm install -g zinnector on Node 24 or newer. If npm prints EBADENGINE, your Node is older than 24 — install the current LTS from nodejs.org and run the install again. 2. **Check the version** — zinnector --version prints a version number such as 0.1.2. On a Node older than 24 it prints a message saying Node 24 or newer is needed, and exits. 3. **Read the help** — zinnector --help lists every command below with a one-line purpose. Every command also takes --help of its own. 4. **Scaffold a site** — zinnector new my-site creates a project that boots immediately — a zinnector.json, a wp-content tree and a README — and prints the next commands to run. 5. **Run it** — cd my-site, then zinnector dev. The first run asks once to download the WordPress runtime (about 570 MB, kept in the CLI’s own cache, never in your project). Success looks like “running at http://127.0.0.1:9400”. 6. **Open it in a browser** — http://127.0.0.1:9400 is a fresh WordPress site; /wp-admin opens the dashboard already signed in. Drop a plugin into wp-content/plugins and it is there on the next reload. 7. **Then, with a hosting slot** — zinnector login, zinnector link, zinnector check, zinnector push — pre-flight what you built against the slot, then deploy and watch it finish. ## The pre-flight, in detail You built on PHP 8.3. The slot runs 8.1. Nothing tells you until the site is white. That is the problem this command exists for, and it is the one the owner of this platform asked for by name. Zinnector® reads both environments and puts them side by side — then lets you deploy anyway, because you might have a reason. - **PHP, graded honestly** — A major-version gap is flagged high because it reliably breaks a site; a minor gap is flagged lower. Grading everything as critical just teaches people to skip the warning. - **Disk and file count, separately** — A WordPress tree is tens of thousands of small files, and a site can exhaust its inode allowance while sitting well under its disk cap. Both are checked against what is actually left on the slot, not against the plan. - **“Could not check” is its own answer** — A check that cannot see its subject reports unchecked, never passed. A clean run says how many things it could not verify, because a false all-clear is the one nobody looks at twice. - **Warns, never blocks** — Every finding is overridable with --force, and the summary says so. In CI the exit code is the gate instead, so a pipeline can be strict while a person stays in control. ## Two local runtimes, both real WordPress Playground is the default: PHP compiled to WebAssembly, running inside Node, so a laptop with nothing but Node installed goes from nothing to a running WordPress in about the time it takes to read this sentence. When you need a native PHP — an extension like imagick, a real MySQL — pass --runtime docker and get php-fpm and MariaDB containers instead. Both serve the same files from the same project, so switching between them changes the engine and nothing else. ## Everything else you already do in the panel Zinnector® is built on the same public API as the dashboard, so anything the panel can do, it can do — and every command is a documented operation in the OpenAPI spec rather than a private endpoint. - **Sites and deploys** — List sites, read everything the platform knows about one, redeploy, and read deploy history and build logs. - **Domains, DNS and mail** — List domains, read and change DNS records with the record shown before it is written, and read your mail services. - **PHP, quota, database and logs** — Switch PHP versions, read disk and inode usage against what your plan grants, get single-use links into phpMyAdmin, and tail access and error logs. - **WP-CLI and bulk operations** — Run allow-listed WP-CLI commands against a site, and purge caches or start malware scans across a whole selection in one call rather than one per site. ## Every command, exactly as --help lists it The full list, one line each. The complete reference — every flag, a runnable example and what each command prints — is generated from the CLI itself and lives in the developer docs and the knowledge base, so it cannot drift from the tool you have installed. - **zinnector new** — Scaffold a WordPress project you can run immediately. - **zinnector dev** — Run this project locally — no Docker required. - **zinnector login** — Sign in with a Zinn Digital® API key. - **zinnector logout** — Forget a stored API key. - **zinnector whoami** — Show who this CLI is authenticated as. - **zinnector sites** — List the sites this key can see. - **zinnector status** — Everything the platform knows about one site. - **zinnector share** — Give one person access to a single site — a developer, a designer, a client — with a role and a reason. - **zinnector collaborators** — See who has been given access to a site, their role, and whether they have accepted yet. - **zinnector unshare** — Take a person's access back, by email or grant id. - **zinnector invitations** — The invitations waiting for you, and accept one. - **zinnector link** — Point this project at a hosting slot (and connect its repository). - **zinnector pull** — Pull a hosted site's files into this project for local development, and re-run to re-sync. Takes the fast path when the site syncs to its own repository, otherwise works from the latest backup. - **zinnector sync** — Two-way sync between a hosted site's live files and its repository: see where it stands, switch it on, commit the site's changes, or choose which side wins. - **zinnector mcp** — A bridge to the Zinn Digital® MCP server for Claude Desktop and other AI clients that only start local servers. - **zinnector clone** — Make a local project from a hosted site in one step: clone its repository or pull its files, write the project file, and leave you ready to run zinnector dev. - **zinnector check** — Compare this project against the slot you are about to deploy to. - **zinnector push** — Pre-flight, push your commits, and deploy. - **zinnector deploy** — Redeploy what the platform already has, without pushing. - **zinnector deploys** — A site's deploy history. - **zinnector php** — Show or switch a site's PHP version. - **zinnector quota** — Disk, files and database usage against what the plan grants. - **zinnector db** — Database size, and single-use links into phpMyAdmin and the file manager. - **zinnector logs** — Tail a site's access and error logs. - **zinnector wp** — Run an allow-listed WP-CLI command on a site. - **zinnector backup** — List and take site backups. Subcommands: list, now. - **zinnector domains** — List the domains this key can see. - **zinnector dns** — Read and change DNS records. Subcommands: list, add, rm. - **zinnector mail** — List mail services. - **zinnector bulk** — Run one operation across many sites (cache_purge, malware_scan, sitemap, block_ip). - **zinnector ai** — Ask the Zinn Digital® assistant, with this project as context. ## Frequently asked questions **Do I need to be a Zinn Digital® customer to use it?** No. `zinnector new` and `zinnector dev` need no account at all — scaffold a plugin, a theme or a whole site and run it locally, free, forever. An API key is only needed for the commands that talk to your hosting. **Does it need Docker?** Not for the default runtime. WordPress Playground compiles PHP to WebAssembly and runs inside Node, so `zinnector dev` boots a real WordPress in seconds with nothing else installed. If you need a native PHP — to test an extension such as imagick or ionCube — `--runtime docker` gives you php-fpm and MariaDB containers instead. Both are supported; neither is a fallback. **What does the pre-flight check actually compare?** Your local PHP version against the slot’s, whether the slot can even switch to the version you built on, whether the slot’s PHP is past end of life and whether the machine has actually applied it, your project’s size and file count against the disk and inode headroom left, the WordPress versions on each side, whether the slot has finished provisioning, and whether a git repository is connected to deploy from. Anything it could not check is reported as unchecked rather than counted as a pass. **Can it stop me deploying?** No, and that is deliberate. Pre-flight warns and lets you through — `--force` deploys past any finding. You know things about your own site that a checker does not, and a tool that refuses to deploy is a tool people uninstall. **Is my API key safe?** The key is never read from the command line — only from a prompt or piped stdin — so it cannot end up in your shell history or in a process listing. It is stored in your own config directory with file mode 600, and Zinnector® re-asserts those permissions every time it writes. **Can I use it in CI?** Yes. Set `ZINNECTOR_TOKEN`, and every command takes `--json`. Human output goes to stderr and data to stdout, so pipes stay clean. `zinnector check` exits non-zero when it finds something, so it works as a pipeline gate, and `--strict` also fails when a comparison could not be made. --- # Affiliate Programme Terms URL: https://zinndigital.com/legal/affiliate-terms These terms govern the Zinn Digital® affiliate programme — how you earn commission for referring customers, how referrals are tracked and paid, and the promotion rules everyone in the programme agrees to. Availability: the programme is open. Apply from your dashboard — we review every application before a link goes live. ## About these terms Last updated: 22 July 2026. These Affiliate Programme Terms (the "affiliate terms") are an agreement between you (the "affiliate") and Zinn Digital® Ltd (Company No. 16385785, VAT No. GB 526 5236 92), 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom. They apply when you join the Zinn Digital® affiliate programme, and they sit on top of our Terms of Service, which continue to apply. The specific commission structure, cookie window and payout schedule that apply to you are published on your affiliate account and on the programme page; where a figure differs between a marketing page and your account, your account governs. The affiliate programme is separate from the customer-to-customer referral route, where existing customers refer others and both sides receive wallet credit against future invoices. These affiliate terms govern affiliate accounts; the referral route is governed by the Terms of Service and the reward shown at the time. ## 1. Eligibility and joining To be an affiliate you must be at least 18 (or the age of majority where you live), able to form a binding contract, and able to comply with these terms and the law that applies to you. You do not have to be a Zinn Digital® customer to join. - Apply through the affiliate sign-up; we may accept or decline an application, and may require identity or business details before activating an account or releasing a payout. - You are responsible for the accuracy of your account, tax and payout details, and for keeping them current. - You promote independently — nothing in these terms creates an employment, agency, partnership or joint-venture relationship, and you may not present yourself as able to bind or speak for Zinn Digital®. ## 2. Referral tracking and attribution When you join, your affiliate account issues unique referral links and codes tied to your organisation. A referral click sets a first-party cookie and is also recorded server-side through the platform's attribution layer, and the attribution is carried across from the marketing site to the app on signup and stored against the referred organisation as first-touch and last-touch. The cookie window — how long after a click a signup is still credited to you — is a configurable programme setting, published on your account rather than fixed in these terms. Because attribution is captured server-side and stored on the referred organisation, a referral is not lost the moment a browser clears its storage. A referral is valid only where it results from your genuine promotion under these terms; we determine attribution in good faith using our systems, and our records are the basis for calculating commission. ## 3. Commission Commission is applied by rule against the qualifying order or subscription of a validly referred customer. The rules that apply to you are shown on your affiliate account and may vary along several dimensions: - Percentage or fixed — a share of order value, or a set amount per conversion. - One-off or recurring — on the first payment only, or for as long as the referred subscription keeps renewing. - Per product line and per plan — different lines and plans may carry different rates. - Tiered by volume — a structure may step up as your referred volume grows. - All amounts are held in integer minor units with an explicit currency, so multi-currency earnings do not drift through rounding. ## 4. Holdback, clawback and qualifying referrals Earnings accrue to your affiliate balance and sit through a holdback period before they become payable, because a referral is only genuinely earned once the underlying payment has cleared and any refund window has passed. Commission on an order that is later refunded, charged back, or reversed is clawed back — money that did not stay with the business does not stay in your balance. A referral does not qualify, and no commission is due, where the signup is your own or a linked account, where it results from prohibited promotion under section 6, where it is fraudulent or made in breach of these terms, or where the customer was already attributed to another affiliate or was an existing customer. ## 5. Payouts and identity verification Payouts run through the platform's payment provider and wallet — the same audited engine that handles customer billing and refunds — on the programme's published schedule, once earnings clear their holdback period. Each payout comes with a statement itemising the conversions and any reversals behind it. - A minimum payout threshold and the available payout methods are published on your account; a balance below the threshold rolls over to the next period. - Above a defined earnings threshold, identity verification (KYC) is required before a payout is released — a normal condition of paying real money, and a protection for legitimate affiliates against the fraud that gets programmes closed. - You are responsible for any taxes on your commission and for providing valid tax and payout information; we may withhold a payout where the law requires or where verification is outstanding. ## 6. Promotion rules — what you must not do You may promote Zinn Digital® honestly, on channels you control or are permitted to use. The following are prohibited and void the affected referrals, and may end your participation: - Spam — unsolicited bulk email, messaging or comments — and posting your links where you do not have permission to post. - Bidding on, or using in ad copy or domains, the Zinn Digital® name or trademarks (including obvious misspellings) in paid search, unless we have agreed in writing. - Cookie stuffing, forced clicks, self-referrals, incentivised or fake signups, and any attempt to manufacture or misattribute referrals. - Misleading, false or unsubstantiated claims about the platform, its pricing, or its capabilities, and impersonating Zinn Digital® or implying an official or exclusive relationship. - Promoting on sites that host unlawful, infringing or adult content, or in any way that breaches the Acceptable Use Policy or the law (including advertising, consumer-protection and disclosure rules — you must disclose the affiliate relationship where required). - Offering unauthorised discounts, rebates or coupons, or presenting your referral link as an official Zinn Digital® offer. ## 7. Use of our brand and assets We grant you a limited, non-exclusive, revocable, non-transferable licence to use the marketing assets we make available in the affiliate asset library, and the Zinn Digital® name and logo, solely to promote the platform under these terms and in line with any brand guidance we provide. You gain no other rights in our trademarks or content, and all goodwill from your use belongs to us. We may ask you to change or remove any promotion, and the licence ends when your participation does. ## 8. Changes, suspension and ending participation We may update these terms, the commission structure, the cookie window, and the payout schedule as the programme develops. Material changes are published to your account and, where they significantly affect you, notified by email or in the dashboard; continuing in the programme after a change takes effect means you accept it. Changes are not retrospective on commission already validly earned and cleared. Either of us may end your participation at any time. We may suspend or terminate an affiliate account — and withhold or reverse commission — for breach of these terms, fraud or abuse, or a legal requirement. On termination your licence to use our brand and assets ends and you must stop using your referral links; validly earned, cleared commission above the payout threshold remains payable subject to verification. ## 9. Liability and governing law The limitations and exclusions of liability in the Terms of Service apply to these affiliate terms. To the fullest extent permitted by law, we are not liable to you for indirect or consequential loss or for lost profits, and our total liability to you in connection with the programme in any 12-month period is limited to the commission validly payable to you in that period. These affiliate terms are governed by the laws of England and Wales, and you and we submit to the exclusive jurisdiction of its courts. If you are a consumer, this does not deprive you of the protection of the mandatory consumer laws of the country where you live. ## 10. How to contact us The affiliate programme is operated by Zinn Digital® Ltd (Company No. 16385785, VAT No. GB 526 5236 92), 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom. For any question about the programme or these terms, reach us through the contact page at zinndigital.com/contact, or email office@zinndigital.com. ## Frequently asked questions **What commission will I earn?** Commission is set as a rule and can differ by product line, by plan and by your referred volume, and can be one-off or recurring. The structure that applies to you is shown on your affiliate account — these terms govern how it works, not a single fixed number. **How long is the referral cookie?** The cookie window is a configurable programme setting published on your account, not a fixed period baked into these terms. Attribution is also captured server-side and stored against the referred organisation, so a referral is not lost the moment a browser clears its cookies. **What happens if a customer I referred refunds or charges back?** The commission is clawed back. Earnings sit through a holdback period before payout precisely so that a later refund or chargeback can be deducted — you keep commission on payments that stay with the business, not ones that are reversed. **Can I bid on the Zinn Digital® brand in Google Ads?** No, not without our written agreement. Bidding on our name or trademarks (or obvious misspellings) in paid search, or using them in ad copy or domains, is prohibited and voids the affected referrals. Promote on channels you control and disclose the affiliate relationship where the law requires. **Do I have to verify my identity to get paid?** Above a defined earnings threshold, yes — identity verification is required before a payout is released. It is a standard condition of paying real money at scale and it protects legitimate affiliates from fraud. You are also responsible for any taxes on your commission. **Is this the same as referring a friend as a customer?** No. Customers can use the customer-to-customer referral route, where both sides get wallet credit against future invoices — that is simpler and needs no payout setup. These affiliate terms are for affiliate accounts aimed at publishers, agencies and partners driving referral volume. --- # Acceptable Use Policy URL: https://zinndigital.com/legal/aup This policy sets out what you may and may not do with Zinn Digital® hosting, domains and related services. It protects every customer on the platform, and accepting our Terms of Service means accepting it. ## About this policy Last updated: 6 October 2026. This Acceptable Use Policy (the "policy") is part of, and incorporated into, the Terms of Service between you and Zinn Digital® Ltd (Company No. 16385785, VAT No. GB 526 5236 92), 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom. It applies to everyone who uses the service — customers, resellers, agencies managing sites for clients, and members invited into another customer's account — and to every site, application, domain, mailbox and API call in your account. You are responsible for your own use of the service and for the use made by anyone you give access to, including your clients and team members. Where this policy and the Terms of Service overlap, they are read together; where a signed agreement with your organisation says otherwise, that agreement takes precedence to the extent of any conflict. ## 1. Content you must not host or distribute You must not use the service to host, publish, store, transmit or link to any of the following. This list gives examples; it is not exhaustive, and unlawful content is prohibited whether or not it appears here. - Child sexual abuse material, or any content that sexualises or endangers a minor. - Content that infringes another party's intellectual property, trade secrets, privacy or publicity rights, including pirated software, media or counterfeit goods. - Content that is unlawfully defamatory, harassing, or that threatens, incites or glorifies violence, terrorism or serious self-harm. - Material that promotes unlawful discrimination or hatred against people because of a protected characteristic. - Fraudulent, deceptive or misleading content, including phishing pages, fake stores, and schemes designed to obtain money or credentials dishonestly. - Malware, exploit kits, ransomware, or content whose purpose is to damage, disable or gain unauthorised access to any system or data. - Content that a court order, valid legal notice or applicable law requires us to remove. ## 2. Network, security and system abuse The platform is multi-tenant and shared. Activity that attacks or degrades it, other customers, or third parties is prohibited regardless of where the target sits. - Attempting to access, probe, scan or breach any account, system, network or data you are not authorised to use, including attempts to escape the isolation of your own environment. - Denial-of-service activity, whether launched from or aimed at the platform, and hosting the command-and-control, proxy or staging infrastructure for attacks. - Distributing malware, running botnets, credential-stuffing or brute-force tooling, or operating open relays and open proxies. - Cryptocurrency mining, and other workloads that exist mainly to consume shared compute, unless we have agreed to them in writing. - Circumventing, disabling or interfering with the platform's security, rate limits, isolation or metering — including our abuse and fraud controls. - Falsifying headers, identifiers or origin information to disguise the source of activity. ## 3. Email, messaging and outbound traffic Outbound communication from the platform must be wanted by the people who receive it and must comply with the anti-spam and electronic-communications laws that apply to you and your recipients. - No unsolicited bulk or commercial messaging (spam), by email or any other channel, and no sending to purchased, harvested or non-consenting lists. - No forging of sender or routing information, and no evading unsubscribe requests or spam filters. - Bulk and transactional senders must maintain valid authentication (SPF, DKIM, DMARC where applicable), honour opt-outs promptly, and keep complaint and bounce rates low. - We may apply outbound rate limits and, where a deliverability provider is used, its sending rules also apply. ## 4. Fair and intended use of resources Each plan is sized for a particular workload. Use that degrades the service for others, or that a plan is not designed to carry, is not permitted. - No sustained abusive load, runaway processes, or use that materially degrades shared infrastructure or other customers' sites. - No using a plan for a purpose it is not sold for — for example, running a public file-distribution, streaming or backup service on a standard hosting plan. - Reselling or making the service available to third parties only through the reseller, agency and white-label features we provide for that purpose. - Where a plan states limits or a fair-use expectation, staying within them; we will always try to talk to you before acting on an overage. - A plan or feature described as “unlimited” is unlimited for the normal operation of the websites that plan is sold for, under this fair-usage policy, and is not a promise of unlimited physical resources. If an account’s use is far above what is typical for its plan and affects the service for others, we will contact you first to agree a suitable plan or add-on before restricting anything. ## 5. SEO, footprint-free hosting and search engines Footprint-Free Hosting exists to host private blog networks and portfolio sites without a shared technical fingerprint. That is a legitimate use of the platform, and hosting such sites is not itself a breach of this policy. What is prohibited is using the service for activity that is unlawful, that deceives users, or that breaches a third party's rights — for example, hosting content that infringes copyright, that impersonates a real person or business to deceive, or that facilitates fraud. Managing your own network's technical footprint is allowed; using the platform to break the law, or another platform's rights, is not. You must not use the crawler-management features to interfere with the operation of search engines in a way that is unlawful, or to hide unlawful content from detection. ## 6. How we enforce this policy We do not pre-screen customer content, but we investigate suspected abuse and act on valid legal notices. What we do depends on how serious the problem is and how quickly it must be contained. - For most issues we contact you first and give you a reasonable chance to fix the problem. - Where a problem is serious or ongoing — illegal content, active abuse, malware, or a threat to shared infrastructure or other customers — we may suspend the affected site, feature or account immediately and tell you afterwards. - We may restrict, throttle, quarantine, suspend or terminate access in whole or in part, remove or disable specific content, and preserve or disclose information where the law requires it. - We keep a record of enforcement actions. Where an issue is resolved and it is safe to do so, access is restored. ## 7. Reporting abuse If you believe a site or account on our platform is breaching this policy, tell us. Email office@zinndigital.com with the URL or account concerned and enough detail for us to investigate, or use the contact page at zinndigital.com/contact. We treat abuse reports seriously and act on them proportionately. Reports about your own account and its content are always handled through your dashboard and support tickets. ## 8. Changes to this policy We may update this policy as the platform, the law, or the abuse landscape changes. When we make a material change we update the date at the top of this page and, where the change significantly affects you, give reasonable notice by email or in the dashboard. Continuing to use the service after a change takes effect means you accept the updated policy. ## 9. How to contact us This policy forms part of the agreement between you and Zinn Digital® Ltd (Company No. 16385785, VAT No. GB 526 5236 92), 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom. For any question about acceptable use, or to report abuse, reach us through the contact page at zinndigital.com/contact, or email office@zinndigital.com. ## Frequently asked questions **Is footprint-free / PBN hosting allowed?** Yes. Hosting private blog networks and portfolio sites without a shared technical fingerprint is a core, legitimate use of the platform. What is not allowed is using any site — footprint-free or not — for something unlawful, deceptive, or that breaches someone else's rights. **Will you read or monitor my site's content?** We do not pre-screen customer content. We investigate when we receive an abuse report or a valid legal notice, or when our automated security and abuse controls flag something. We act proportionately to what we find. **What happens if my site is compromised by an attacker?** Being hacked is not itself a breach of this policy. We will alert you, help contain it, and — if the compromised site is actively harming others (serving malware or phishing) — we may suspend it until it is cleaned, then restore it. Our isolation is designed so one compromised site does not reach another customer. **Can I send marketing email from my hosting?** You can send email your recipients have agreed to receive, with valid authentication and a working unsubscribe. Unsolicited bulk email (spam), purchased lists and forged senders are prohibited, and outbound sending is rate-limited to protect deliverability for everyone. **How do I report a site that breaks these rules?** Email office@zinndigital.com with the URL or account and the details, or use zinndigital.com/contact. We investigate every credible report and act proportionately. --- # Cookie Policy URL: https://zinndigital.com/legal/cookies We set a handful of first-party cookies, and Google sets its own on our domains for analytics and for measuring our own adverts. This page lists every one of them by name and explains the choices you have. ## Your choices, by region We measure how our websites are used with PostHog (EU region) and Google Analytics 4, and we use Google's advertising signals to measure and improve our own adverts. In the European Economic Area, the United Kingdom and Switzerland none of this runs until you choose: a banner asks, with Accept all, Reject all and Settings (one choice for analytics, one for advertising). Everywhere else it is on from the first page, and you can change your choice at any time. - In the EEA, the UK and Switzerland, Google's analytics storage, ad storage, ad user data and ad personalisation start switched off (Google Consent Mode), and PostHog does not run, until you accept. - Outside those regions they start switched on. No banner is shown, and the "Privacy choices" link at the foot of every page opens the same choices. - Your answer is kept in the zinn_consent cookie and is honoured on zinndigital.com, our product sites and our plugin sites. Reject all switches every signal off; Settings lets you allow analytics or advertising on its own. - Your theme, currency and attribution cookies work the same whatever you choose. ## Every cookie we set Every cookie below is set on our own domains, and we do not sell or share their contents. Google's cookies are used for analytics and, where you allow it, to measure and personalise our own adverts. - **zinn_consent — your privacy choices (1 year)** — Remembers your answer: 'granted' (everything), 'denied' (nothing), or 'analytics' or 'ads' (one purpose only). It is set only when you answer the banner or the Privacy choices panel. - **zinn_attr — attribution (90 days)** — If you arrived from an ad or a campaign link, this stores the campaign parameters that were already in the URL you clicked (utm_source, utm_medium, utm_campaign, utm_term, utm_content, and the gclid/fbclid/ttclid/msclkid click ids). It lets us credit a signup to the campaign that produced it for our own accounting. It holds no behavioural profile and nothing you did not already send us in the address bar. - **zinn_theme — preference (1 year)** — Remembers whether you chose the light theme, the dark theme, or to follow your operating system. Strictly necessary for the preference to persist. - **zinn_currency — preference (1 year)** — Remembers which currency you asked to see prices in. Strictly necessary for the preference to persist. - **_ga and _ga_ — Google Analytics 4 (up to 2 years)** — Set by Google Analytics on our domains to tell one visit from another and count returning visitors. Set only where analytics is allowed: by default outside the EEA, the UK and Switzerland, and inside them only after you accept. - **_gcl_au — Google Ads conversion measurement (90 days)** — Set by Google's tag where advertising is allowed, to connect a visit to the Google advert that led to it so we can tell which of our adverts work. Not set if you refuse advertising. ## What analytics measures PostHog runs on its EU cloud (eu.i.posthog.com), so that data stays in the EU, alongside Google Analytics 4. We deliberately send both far less than they are capable of collecting. - We record events we defined in advance — which page was viewed, which button was clicked, how far down a page people read. - Autocapture is off. We do not send the text of whatever you clicked, and we never record your screen or session. - We never send personal data: no name, email address, phone number, postal address, password, payment detail, form field value or search term. A denylist strips those keys before anything leaves your browser, as a backstop to the types that already forbid them. - Search terms are replaced by their shape. A domain search sends the TLD and how many characters you typed — never the domain itself, which is often your own name or an unannounced project. - Anonymous visitors get no persistent PostHog profile. - The analytics code is downloaded only once the page has finished its work, so it cannot slow down what you came for. ## Your rights and how to reach us Zinn Digital® Ltd (Company No. 16385785, VAT No. GB 526 5236 92), 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom, is the data controller for the cookies described on this page. You have the right to access, correct or erase the data we hold about you, to restrict its processing, and to change your privacy choices at any time (the Privacy choices link at the foot of every page). You may also complain to the UK Information Commissioner's Office (ico.org.uk). For anything on this page, or to exercise any of those rights, email office@zinndigital.com. ## Frequently asked questions **How do I change my choices?** Use the "Privacy choices" link at the foot of any page: Accept all, Reject all, or allow only analytics or only advertising. You can also block cookies for our sites in your browser. The site works the same either way, and your theme and currency preferences keep working. **Why do some visitors see a banner and others do not?** In the European Economic Area, the United Kingdom and Switzerland the law requires us to ask before analytics or advertising cookies are set, so visitors there see a banner and nothing is set until they choose. Elsewhere these run from the first page, and the same choices are one click away in the footer. **Do you use advertising or cross-site tracking cookies?** We run no third-party advertising networks or cross-site trackers. Where you allow advertising, Google's tag measures which of our own Google adverts led to a visit or a sign-up, and can personalise our adverts to you; Reject all or Settings turns this off. We never sell your data. **Why does the attribution cookie not need consent?** It stores only the campaign parameters that were already present in the URL you clicked, in order to account for a commercial relationship — it builds no profile of your behaviour and tracks you across no other site. We list it here anyway, because telling you about every cookie we set matters more than only listing the ones we are obliged to. **Where is the data stored?** PostHog data goes to its EU cloud region (eu.i.posthog.com) and stays in the EU. Google Analytics data is processed by Google. The preference cookies are stored only in your own browser. --- # Data Processing Agreement URL: https://zinndigital.com/legal/dpa When we host a site for you, the personal data inside it stays yours — you are the controller and we are your processor. This agreement sets out how we handle that data on your behalf under the UK and EU GDPR. ## About this agreement Last updated: 22 July 2026. This Data Processing Agreement (the "DPA") forms part of the Terms of Service between you (the "customer") and Zinn Digital® Ltd (Company No. 16385785, VAT No. GB 526 5236 92), 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom ("Zinn Digital®", "we", "us"). It applies where, in providing the hosting and related services, we process personal data on your behalf — principally the personal data contained inside the websites and applications you host with us. It reflects Article 28 of the UK GDPR and the EU GDPR. For personal data where we are the controller — your account, billing and our own website-visitor data — our Privacy Policy applies instead of this DPA. If your organisation needs this DPA signed as a standalone document, contact us and we will arrange it. ## 1. Definitions and roles Terms such as personal data, processing, controller, processor, sub-processor, data subject, personal data breach and supervisory authority have the meanings given in applicable data protection law (the UK GDPR, the EU GDPR, and the UK Data Protection Act 2018). - For the personal data inside your hosted sites and applications ("customer personal data"), you are the controller and Zinn Digital® is the processor. - Where your own end users' data is itself controlled by a third party for whom you act, you confirm you have the authority to instruct us on their behalf. - Zinn Digital® remains the controller for account, billing and our own website-analytics data, governed by our Privacy Policy. ## 2. Scope, duration and our instructions We process customer personal data only to provide, secure, support and maintain the hosting and related services you have bought, and only on your documented instructions — which include your configuration of the service and your use of its features. Using the service is itself an instruction to process the data it contains for those purposes. The subject matter is the operation of your hosting; the duration is the term of your agreement plus any wind-down period in section 9. The nature and purpose of processing is hosting, storage, transmission, backup, security and support. The types of data and categories of data subject are whatever you choose to place on the service, which you control. We will tell you if, in our opinion, an instruction infringes data protection law, and we do not use customer personal data for our own purposes or to train models. ## 3. Confidentiality We ensure that the people authorised to process customer personal data are bound by an appropriate duty of confidentiality, and we limit access to those who need it to deliver or support the service. Access to production systems is least-privilege and logged. ## 4. Security measures We implement appropriate technical and organisational measures to protect customer personal data against accidental or unlawful destruction, loss, alteration, and unauthorised disclosure or access, appropriate to the risk. These include: - Encryption of data in transit with TLS across our services. - Per-tenant isolation so one customer's environment cannot reach another's, enforced down to the database with row-level security. - Least-privilege access controls, with secrets held in a dedicated secrets manager rather than in code or configuration files. - An auditable trail of privileged and administrative actions. - Continuous monitoring, malware scanning, and a defined process for detecting, handling and reporting security incidents. - Regular backups, with restoration testing, according to the retention window of your plan. ## 5. Sub-processors You give general authorisation for us to engage sub-processors to help deliver the service. We impose data protection obligations on each sub-processor that are no less protective than this DPA, and we remain responsible to you for their performance. We currently use sub-processors in the following categories: - Infrastructure and cloud providers that host the platform and its data. - Payment providers, to take payment and prevent fraud (they receive billing data, not the contents of your sites). - A transactional email provider, to send account and service messages. - A product-analytics provider (PostHog), used on our own websites only and only with the visitor's consent. - Domain registries and DNS, CDN and security providers, where your plan uses them. ## 6. Changes to sub-processors We keep the categories above current and will make a list of specific sub-processors available on request. Where we intend to add or replace a sub-processor that processes customer personal data, we will give you a way to be informed and a reasonable opportunity to object on legitimate data protection grounds. If we cannot resolve a reasonable objection, you may terminate the affected part of the service. ## 7. Assisting you with data subject rights Taking into account the nature of the processing, we help you respond to requests from data subjects to exercise their rights — access, rectification, erasure, restriction, portability and objection — by providing the appropriate technical and organisational measures, and the tools in the service, insofar as this is possible. If we receive a request directly from one of your data subjects, we will not respond to it ourselves except on your instruction or as legally required, and we will pass it to you where we can identify that it relates to your data. ## 8. Personal data breaches We maintain a defined incident process. On becoming aware of a personal data breach affecting customer personal data, we notify you without undue delay and provide the information you reasonably need to meet your own notification duties to a supervisory authority and to data subjects — including the nature of the breach, the likely consequences, and the measures taken or proposed. We also assist you, taking into account the information available to us, with your obligations to keep processing secure, to carry out data protection impact assessments, and to consult supervisory authorities where required. ## 9. International transfers We are based in the United Kingdom and prefer to keep data in the UK and the European Economic Area. Where customer personal data is transferred outside the UK or EEA — whether by us or a sub-processor — we rely on a lawful transfer mechanism such as an adequacy decision, the UK International Data Transfer Agreement or Addendum, or the EU Standard Contractual Clauses, together with additional safeguards where needed, so the data keeps an essentially equivalent level of protection. ## 10. Return and deletion on termination On the end of the service, and at your choice, we make customer personal data available for you to export for a reasonable period, and then delete or return it and delete existing copies, unless the law requires us to keep it. Data held in backups is deleted on the ordinary backup-expiry cycle. Where retention is legally required, we keep only what the law requires and continue to protect it under this DPA. ## 11. Audits and demonstrating compliance We make available the information reasonably necessary to demonstrate our compliance with this DPA, and allow for and contribute to audits, including inspections, conducted by you or an auditor you mandate. To protect the security and confidentiality of the shared platform and other customers, audits are on reasonable prior notice, at reasonable frequency, subject to confidentiality, and we may satisfy an audit request by providing our documentation, security descriptions and any third-party reports we hold. ## 12. Liability and precedence Each party's liability under this DPA is subject to the limitations and exclusions of liability in the Terms of Service. If there is a conflict between this DPA and the Terms of Service on the processing of customer personal data, this DPA prevails; if there is a conflict between this DPA and the Standard Contractual Clauses (where they apply), the clauses prevail. ## 13. How to contact us The processor under this DPA is Zinn Digital® Ltd (Company No. 16385785, VAT No. GB 526 5236 92), 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom. For any data protection question, to exercise your rights, or to request this DPA as a signed standalone document, reach us through the contact page at zinndigital.com/contact, or email office@zinndigital.com. We route data protection requests to the person responsible for them. ## Frequently asked questions **When does this DPA apply, and when does the Privacy Policy apply?** This DPA applies to the personal data inside the sites and applications you host with us, where you are the controller and we are your processor. Our Privacy Policy applies to the data we control in our own right — your account, your billing, and our own website-visitor analytics. **Do I need to sign anything?** This DPA already forms part of your Terms of Service, so it is in force without a separate signature. If your organisation's procurement needs it executed as a standalone document, contact us and we will arrange it. **Who are your sub-processors?** We use sub-processors in defined categories — infrastructure and cloud, payments, transactional email, product analytics (on our own sites only), and domain/DNS/CDN/security providers where your plan uses them. We will provide the specific list on request and give you a way to be informed of changes and to object. **Do you use my hosted data to train AI models?** No. We process the personal data inside your sites only to run the hosting on your documented instructions. We do not use it for our own purposes, and we do not use it to train models. **What happens to my data if I leave?** We make it available for export for a reasonable period, then delete or return it and delete our copies, except anything the law requires us to keep. Backups are deleted on their ordinary expiry cycle. --- # Privacy Policy URL: https://zinndigital.com/legal/privacy This policy explains what personal data Zinn Digital® collects, why, the legal bases we rely on, who we share it with, and the rights you have over it. ## Who we are Last updated: 10 October 2026. Zinn Digital® Ltd (Company No. 16385785, VAT No. GB 526 5236 92), 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom ("Zinn Digital®", "we", "us" or "our") is the data controller for the personal data described in this policy, unless we are acting as a processor on your behalf as explained below. We take privacy seriously and only process the data we need to run our hosting and SEO platform, bill for it, support you, keep it secure, and meet our legal obligations. This policy covers our websites, dashboards and APIs; our Cookie Policy covers cookies and similar technologies in detail. ## 1. The data we collect The personal data we hold falls into a few clear groups. - **Account data** — The details you give us when you register and use the platform: your name, email address, organisation, login credentials and multi-factor settings, and the roles and team members you set up. Authentication is handled through our identity provider. - **Billing data** — What we need to charge you and issue invoices: billing name and address, country, tax identifiers, the plan you bought, and a payment mandate. Card payments are handled by our payment providers — we never receive or store your full card number or security code. - **Usage and analytics data** — How you interact with our own websites and dashboards: pages viewed, features used, device and browser information, and IP address. On our marketing sites this is measured from the first page with PostHog and Google Analytics 4, configured not to receive personal data or your search terms; Google's advertising signals are used only to measure and improve our own adverts. In the EEA, the UK and Switzerland none of this runs until you accept; elsewhere it runs by default, and you can change your choice at any time as our Cookie Policy explains. - **Support and communications** — The content of tickets, emails and messages you send us, so we can help you and keep a record of what was agreed. - **Customer site data (as processor)** — The websites and applications you host with us may themselves contain personal data about your own users and customers. We process that data only to operate the hosting on your behalf — see section 4. ## 2. How we use your data We use personal data to: - Provide, operate, secure and improve the platform and its features. - Create and administer your account and authenticate you. - Take payment, issue invoices, and meet tax and accounting obligations. - Provide support and respond to your requests. - Send you service messages — renewals, security notices, and important changes — and, where you have opted in, product and marketing updates you can unsubscribe from at any time. - Monitor for abuse, fraud and security threats, and enforce our terms. - Understand how our own websites are used so we can make them better, using analytics you can opt out of at any time. - Show our own advertising on Google to people who are or were our customers, leave existing customers out of advertising meant for new ones, and measure which of our adverts led to sign-ups and purchases (see section 5). - Comply with the law and respond to valid legal requests. ## 3. Our lawful bases Under the UK GDPR and the EU GDPR, we rely on one or more of these lawful bases whenever we process your personal data: - Contract — to provide the service you have signed up for and to bill for it. - Legitimate interests — to secure the platform, prevent abuse and fraud, run and improve our business, and market our own services to people who are or were our customers (including the Google advertising described in section 5), balanced against your rights and freedoms. - Legal obligation — to keep tax, accounting and other records the law requires. - Consent — for marketing where consent is required; you can withdraw consent at any time without affecting processing already carried out. Website analytics relies on our legitimate interest in understanding how our sites are used, and you can object to it at any time. ## 4. When we act as a processor When we host your website or application, it may contain personal data about your own visitors, users or customers. For that data you are the controller and we are your processor: we handle it only on your documented instructions and only to provide the hosting service — we do not use it for our own purposes. We keep that data logically separated between tenants, apply least-privilege access controls, and help you meet your own obligations, including responding to the data-subject requests and security-incident duties that fall on you as the controller. If you need a separate data-processing agreement, contact us. ## 5. Sharing and sub-processors We do not sell your personal data. We share it only with service providers that help us run the platform, each under a contract that limits them to our instructions, and each sitting behind an adapter so it can be replaced. These include: - Payment providers, to take payment and prevent fraud. - Infrastructure and cloud providers that host the platform and its data. - A transactional email provider, to send account and service messages. - Product-analytics providers (PostHog, and Google Analytics 4), used on our own websites to measure how they are used, and (Google) to measure our own adverts where you allow advertising. - Google, for our own advertising: a one-way encrypted (hashed) form of your e-mail address and, where you have given them, your name, country and postcode, as explained below. - Domain registries and DNS, CDN and security providers, where your plan uses them. - Professional advisers and authorities, where we are legally required to disclose data. Advertising on Google. If you have an account with us, we may share a one-way encrypted (hashed) form of your e-mail address — and, where you have given them, your name, country and postcode — with Google so that we can show our own advertising to existing customers, leave existing customers out of advertising meant for new ones, and measure which of our adverts led to sign-ups and purchases (Google Customer Match and enhanced conversions). Google uses this data only for our advertising account. It is never shared if you unsubscribe from our marketing e-mails (the link at the foot of every marketing e-mail) or ask us at office@zinndigital.com; when you do, we remove you from the lists we keep with Google at the next daily update. Our legal basis is our legitimate interest in marketing our own services to people who are or were our customers. We choose sub-processors that offer appropriate security and privacy protections, and we keep the categories above current. We may also disclose data if required by law, to enforce our terms, or to protect the rights, safety and property of Zinn Digital®, our customers or the public. ## 6. International transfers We are based in the United Kingdom and prefer to keep data in the UK and the European Economic Area where we can — our website analytics, for example, use an EU region. Some of our providers may process data in other countries. Where personal data is transferred outside the UK or EEA, we rely on a lawful transfer mechanism — an adequacy decision, the UK International Data Transfer Agreement or Addendum, or the EU Standard Contractual Clauses — together with additional safeguards where needed, so your data keeps an equivalent level of protection. ## 7. How long we keep data We keep personal data only as long as we need it for the purposes in this policy. Account data is kept while your account is active. After you close it, we keep what we must to meet legal, tax and accounting duties and to resolve disputes, then delete or anonymise the rest. Billing and invoice records are retained for the period tax law requires. Website content and backups follow the retention window described in your plan. Analytics data is retained for a limited period and holds no direct identifiers. ## 8. Your rights Subject to the conditions in data-protection law, you have the right to: - Access the personal data we hold about you and get a copy. - Correct data that is inaccurate or incomplete. - Erase your data where there is no overriding reason for us to keep it. - Restrict or object to our processing, including profiling and direct marketing. - Receive your data in a portable, machine-readable format, and have it sent to another provider where technically feasible. - Withdraw consent at any time, where we rely on consent, without penalty. To exercise any of these rights, contact us using the details below; we will respond within the time limit the law sets. Exercising your rights is free and carries no penalty. If you are unhappy with how we handle your data you can complain to the UK Information Commissioner's Office at ico.org.uk, or to your local supervisory authority in the EEA, though we would welcome the chance to put things right first. ## 9. Cookies and analytics Our websites use a small number of first-party cookies for preferences (such as your locale, currency and theme) and analytics cookies for PostHog and Google Analytics 4, which, in the EEA, the UK and Switzerland, run only after you accept and elsewhere run from the first page you view. Where you allow advertising, Google's tag measures our own adverts; we run no third-party advertising networks or cross-site trackers. Our separate Cookie Policy lists every cookie by name, what it does and how long it lasts, and explains how to opt out of analytics. ## 10. How we protect data Security is built into the platform. We do not claim any particular compliance certificate here, but we maintain strong technical and organisational measures and can describe our practices to buyers on request. - Encryption of data in transit with TLS across our services. - Per-tenant isolation so one customer's environment cannot reach another's. - Least-privilege access to systems, with secrets held in a dedicated secrets manager rather than in code. - An auditable trail of privileged and administrative actions. - Continuous monitoring, malware scanning and a defined process for handling security incidents. ## 10a. AI apps you connect (MCP) You can connect an AI app such as Claude or ChatGPT to your account through our MCP server. You approve each app yourself, on a page of ours after you sign in, and you choose the organisation and the permissions it gets. The app can then act only within those permissions, only through our MCP server, and only until you disconnect it. - What we keep: the app you connected, which organisation and permissions you granted, who approved it, when it was last used, and a record of every action it takes, in your organisation’s activity log. - Tokens: the app receives an access token that lasts one hour and a refresh token that changes each time it is used. We store only one-way hashes of them, never the tokens themselves. - What the app receives: only the answers to the requests it makes on your behalf. The company that makes the app handles that data under its own privacy policy, not ours. - Your control: you can see and disconnect every connected app at any time under Settings, AI tools; a disconnected app stops working immediately. Connection records are kept for as long as your organisation’s activity log. ## Zinn® SEO for Google Docs™ and Google user data The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements. - The add-on reads only the document you have open, and only when you use it: it asks Google for access to the current document alone (the documents.currentonly permission), never to your other files. - It sends that document — its text, headings, title and the SEO fields you fill in — only to your own WordPress site, the address you connected it to. It never sends it to Zinn Digital® or to anyone else. - In your Google account it keeps two settings for the add-on: your site's address and the key you made in WordPress. Nothing else from your document is stored by the add-on. - The SEO and readability check runs in the Zinn® SEO plugin on your site, without any AI model. Your Google user data is never used to create, train or improve any generalised AI or machine-learning model. - Your Google user data is never sold or transferred to anyone, and never used for advertising. Read Google's policy: Google API Services User Data Policy — https://developers.google.com/terms/api-services-user-data-policy ## 11. Children The service is intended for businesses and adults. It is not directed at children, and we do not knowingly collect personal data from children. If you believe a child has given us personal data, contact us and we will delete it. ## 12. Changes to this policy We may update this policy as our platform, providers or legal obligations change. When we make a material change we will update the date at the top of this page and, where appropriate, tell you by email or in the dashboard. Please review it from time to time. ## 13. How to contact us The data controller is Zinn Digital® Ltd (Company No. 16385785, VAT No. GB 526 5236 92), 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom. For any privacy question, or to exercise your rights, reach us through our contact page at zinndigital.com/contact, or email office@zinndigital.com for formal data-protection requests. We will route your request to the person responsible for data protection. ## Frequently asked questions **Who is responsible for my data?** Zinn Digital® Ltd (Company No. 16385785, VAT No. GB 526 5236 92), 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom is the data controller for your account, billing and website-visitor data. When we host a site for you, we act as a processor for the personal data inside that site — you remain the controller for it. **Do you sell my personal data?** No. We never sell your personal data or your visitors' data, and we do not share it for third-party advertising. We share it only with the sub-processors that help us run the service, and only as much as they need. **What are my rights?** Under the UK GDPR and, where it applies, the EU GDPR, you can ask to access, correct, erase, restrict or object to our use of your personal data, ask for a portable copy, and withdraw consent at any time. Contact us and we will respond within the statutory time limit. You can also complain to the UK Information Commissioner's Office at ico.org.uk. **Where is my data stored and processed?** We host and process data in data centres chosen for the service and, for our website analytics, in PostHog's EU cloud region. Where data moves outside the UK or EEA, we rely on the legal safeguards described in this policy, such as adequacy decisions and standard contractual clauses. **How long do you keep my data?** We keep account and billing records for as long as you have an account and afterwards only as long as the law requires — for example, to meet tax and accounting obligations. Website content and backups are kept for the retention window described in your plan and then deleted. --- # Refund Policy URL: https://zinndigital.com/legal/refund New paid hosting plans come with a 30-day money-back guarantee, and many plans offer a card-free trial first. This page sets out exactly what is refundable, what is not, and how to ask for a refund. ## About this policy Last updated: 22 July 2026. This Refund Policy is part of the Terms of Service between you and Zinn Digital® Ltd (Company No. 16385785, VAT No. GB 526 5236 92), 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom, and expands on the refund terms there. It explains how refunds work across our hosting plans, domains, add-ons and other charges. Nothing in it affects the statutory rights you have as a consumer. ## 1. The 30-day money-back guarantee New paid hosting plans come with a 30-day money-back guarantee. If the service is not right for you, contact us within 30 days of your first payment for that plan and we will refund that first payment in full. The guarantee covers the first payment for a new plan on your account. It is intended for genuine evaluation of the service, not repeated sign-up-and-refund cycles on the same or linked accounts, which we may decline. Many plans also offer a card-free trial, so you can evaluate the platform before you pay at all — where a trial is available, that is the lowest-risk way to try before buying. ## 2. What the guarantee covers Within the 30-day window, the money-back guarantee applies to the first payment for: - New Footprint-Free (PBN) hosting plans. - New mainstream hosting plans — managed WordPress, WooCommerce, PHP, static and application hosting. - New reseller and agency hosting plans. ## 3. What is not covered Some charges are pass-through or consumption-based, so they cannot fall under the money-back guarantee. The following are non-refundable except where the law says otherwise: - Domain registrations, renewals and transfers — these are billed by, and passed straight through to, the registry the moment they are processed, and we cannot recover the cost. - Other third-party pass-through charges, such as premium TLS certificates or paid services activated on a third-party account on your instruction. - Usage- or consumption-based charges that have already been incurred (for example, metered add-on usage or resources already consumed). - Renewal charges after the initial 30-day window (see section 5). - Charges on an account suspended or terminated for breach of the Terms of Service or the Acceptable Use Policy. ## 4. Add-ons, extras and services One-off services and extras — such as a managed migration, malware cleanup, or a professional-services task — are refundable before the work has started. Once we have begun or delivered the work, the charge reflects work done and is not refundable, except where the law provides otherwise or the delivered work was materially not as described. Recurring add-ons attached to a subscription follow the same treatment as the plan they are attached to: cancelling stops the next renewal, and the add-on runs to the end of the period already paid for. ## 5. Renewals and cancellation We email you before each renewal, so a charge is never a surprise, and you can cancel at any time from your dashboard. Cancelling stops the next renewal; your plan then runs to the end of the period you have already paid for, and is not cut short. Renewal charges after the first 30-day window are not automatically refundable, because you have already had the benefit of the earlier period and been reminded before the renewal. We do, however, look at individual circumstances in good faith — for example, an unused renewal reported quickly, or a clear billing error — and we will always correct a mistake on our side. ## 6. How to request a refund Ask us — refunds are handled by our team rather than a self-service button, so we can confirm eligibility and get it right. Open a support ticket from your dashboard, or email office@zinndigital.com, telling us the account, the plan or charge, and the reason. For the money-back guarantee, contact us within 30 days of the first payment. We aim to review refund requests promptly. We may ask a question or two to understand the issue, and where a request falls outside this policy we will explain why and look for a fair resolution. ## 7. How refunds are paid Approved refunds are returned to the original payment method wherever possible. Where that is not possible — for example, an expired card or a closed wallet — we agree an alternative with you, which may include credit to your account wallet that you can spend against future invoices. Refunds are issued in the currency of the original payment. Once we issue a refund it is usually settled within a few business days, though the exact timing depends on your bank or payment provider. Any difference caused by exchange-rate movement between payment and refund is a matter for your provider, not something we control. ## 8. Disputes and chargebacks If something looks wrong on your bill, please contact us first — almost every billing issue is faster to fix directly than through a card dispute, and we would always rather put it right. Raising a chargeback without contacting us may lead to the related services being suspended while the dispute is resolved. Nothing in this policy affects your right to dispute a charge with your bank or card provider where you are genuinely entitled to. ## 9. Your statutory rights If you are a consumer, you may have additional rights under the consumer-protection law of your country, including rights to cancel and to a refund in certain circumstances. This policy does not limit or replace those rights; it sits alongside them. Where your statutory rights give you more than this policy, your statutory rights apply. ## 10. How to contact us Refunds under this policy are provided by Zinn Digital® Ltd (Company No. 16385785, VAT No. GB 526 5236 92), 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom. To request a refund or ask a question about one, open a ticket from your dashboard, use the contact page at zinndigital.com/contact, or email office@zinndigital.com. ## Frequently asked questions **How does the 30-day money-back guarantee work?** Contact us within 30 days of your first payment for a new paid hosting plan and we will refund that first payment in full. It is meant for genuine evaluation of one new plan, not repeated sign-up-and-refund cycles. **Are domains refundable?** No. Domain registrations, renewals and transfers are billed straight through to the registry the moment they are processed, and we are charged for them immediately, so they cannot be refunded. If you are unsure about a domain, ask us before you buy it. **Can I get a refund on a renewal?** Renewals after the first 30 days are not automatically refundable, because you have had the earlier period and we remind you before every renewal. We do look at individual circumstances in good faith, and we always fix a genuine billing error on our side. **How do I actually request a refund?** Open a support ticket from your dashboard or email office@zinndigital.com with the account, the charge and the reason. Refunds are reviewed by our team so we can confirm eligibility and handle it correctly. **How long does a refund take to arrive?** We aim to process approved refunds quickly, back to your original payment method in the original currency. Once issued it is usually settled within a few business days, though the final timing depends on your bank or payment provider. **What if I already have a card-free trial available?** Then use it — a trial lets you evaluate the platform before paying anything, which is the lowest-risk way to try it. The money-back guarantee is there for plans that do not have a trial, or if you decide to buy straight away. --- # Uptime Service Level Agreement URL: https://zinndigital.com/legal/sla We guarantee that the sites we host for you are reachable 99.9% of every calendar month. When we miss it, you get a service credit on your account — worked out by us, visible in your dashboard, and claimed with one click. No ticket, no argument. ## About this agreement Effective 5 September 2026. This Service Level Agreement is part of the Terms of Service between you and Zinn Digital® Ltd (Company No. 16385785, VAT No. GB 526 5236 92), 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom. It sets out the availability we commit to for the sites we host, how we measure it, what you are owed when we fall short, and how to claim. Nothing in it affects the statutory rights you have as a consumer. ## 1. The commitment We commit to 99.9% availability, measured over each calendar month, for every site we host for you. On a 30-day month, 99.9% allows about 43 minutes of unavailability. Anything beyond that is a miss, and a miss earns a service credit under section 3. ## 2. How we measure it Availability is measured by our own uptime monitoring, which fetches your site from outside our network on a schedule and records whether it answered. ⛔ It is added per address and is not switched on automatically: every account includes three addresses free, and you choose which of your sites we watch. A site you have not added is not being measured, so no month can be adjudicated for it — add it from Uptime & speed in your dashboard, where you can also see every reading, hour by hour. A month's figure is the share of the checks we made that succeeded. Hours in which we made no check are left out of that calculation rather than counted as successes — we do not grade ourselves on the hours we did not look. If we measured less than 95% of a month, we do not consider that month measured at all, and we will not use our own thin coverage to tell you the commitment was met. In that case you choose which of the credit tiers in section 3 matches what you experienced, and we honour it. The gap in our monitoring is ours to carry, not yours to prove. ## 3. Service credits When we miss the commitment for a site in a calendar month, you are entitled to a service credit calculated as a percentage of that site's monthly fee: - Below 99.9% availability — 10% of that site's monthly fee. - Below 99% availability — 25% of that site's monthly fee. - Below 95% availability — 50% of that site's monthly fee. - Below 90% availability — 100% of that site's monthly fee. Credits are applied to your Zinn Digital® account balance and can be spent on anything we sell. They are not paid as cash and are not refundable. The total credit for any one site in any one month will never exceed 100% of that site's monthly fee for that month. Where a site is billed annually, its monthly fee for this purpose is the annual fee divided by twelve. ## 4. How to claim Open Uptime & speed in your dashboard. Each finished month is listed with the availability we measured and, where a credit is due, a button to claim it. We have already done the arithmetic; you press the button. Claims must be made within 30 days of the end of the month they relate to. Each month may be credited once per site. You will see the deadline alongside each month, so you are never refused by a rule you could not see. ## 5. What is not covered Four things do not count towards unavailability under this agreement: - Planned maintenance that we announced at least 24 hours in advance. - Unavailability caused by your own code, content, plugins, configuration or third-party services. - Events beyond any party's reasonable control — war, natural disaster, or a nationwide failure of internet infrastructure. - Time while the site is suspended or quarantined by us — for non-payment or for a breach of the Acceptable Use Policy — because that downtime is our enforcement action and not a failure of the service. If you think a month was wrongly affected, talk to us. There is deliberately no exclusion for failures of our suppliers. You bought hosting from Zinn Digital® and you did not choose our infrastructure partners, so whose equipment failed is our problem and not yours. If your site was not reachable, it was not reachable. ## 6. Scope This agreement covers the availability of sites hosted on the Zinn Digital® platform. It does not cover addresses we monitor for you but do not host — the uptime product is happy to watch a site anywhere, and we cannot guarantee somebody else's infrastructure. Service credits are the sole and exclusive remedy for any failure to meet the availability commitment set out here. ## 7. The 99.99% you will see elsewhere on this site Across zinndigital.com you will see 99.99% described as our uptime assurance. That is the standard we engineer and operate the platform to: per-site isolated compute, horizontally scalable stateless services, and separate failure domains. This agreement is the different and narrower thing. 99.9% is the level we commit to contractually and pay service credits against. The two are not in conflict — we build above what we promise, which is what you would want of any host — and where they differ, this document is the one that binds. ## Frequently asked questions **Do I have to open a ticket to get a credit?** No. We measure every month for every site we host and monitor for you, and the credit is a button in your dashboard. Most providers make you notice the outage yourself and then argue it with support; we have already worked it out. **What if you did not monitor my site for the whole month?** Then we do not treat that month as measured. If we covered less than 95% of it, you choose the credit tier that matches what you experienced and we honour it. We will not use a gap in our own monitoring as a reason to say the commitment was met. **Is the credit cash?** No — it is credit on your Zinn Digital® account, which you can spend on hosting, domains, add-ons or anything else we sell. It is not refundable as cash. **What if my hosting was down because of my own plugin?** Unavailability caused by your own code, content, plugins or configuration is not covered. If you are not sure what caused an outage, claim anyway and tell us — we would rather look at it than have you not ask. **Does this cover sites you only monitor for me?** No. We are happy to watch any address in the world, including one we do not host, but the guarantee applies only to sites hosted with us. **Why does the site say 99.99% and this page say 99.9%?** 99.99% is the standard we build and run the platform to; 99.9% is what we commit to contractually and pay credits against. We deliberately engineer above what we promise. If the two ever disagree about what you are owed, this agreement is what counts. --- # Terms of Service URL: https://zinndigital.com/legal/terms These terms are the agreement between you and Zinn Digital® for your use of our hosting and SEO platform. Please read them — using the service means you accept them. ## About these terms Last updated: 6 October 2026. The service is operated by Zinn Digital® Ltd (Company No. 16385785, VAT No. GB 526 5236 92), 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom ("Zinn Digital®", "we", "us" or "our"). Zinn Digital® is a registered trademark (EUIPO no. 018672629). These Terms of Service (the "terms") set out the rules for using our websites, dashboards, APIs, hosting, and related services (together, the "service"). These terms apply to everyone who uses the service, whether as a customer, a reseller, an agency managing sites for clients, or a member invited into another customer's account. Where a separate signed agreement, order form or service-level agreement exists between us and your organisation, that agreement takes precedence over these terms to the extent they conflict. ## 1. Acceptance By creating an account, buying a plan, or otherwise using the service, you agree to these terms and to our Privacy Policy and Cookie Policy, which are incorporated by reference. If you do not agree, please do not use the service. If you are entering into these terms on behalf of a company, client or other organisation, you confirm that you have the authority to bind that organisation, and "you" refers to that organisation. ## 2. The service Zinn Digital® is an AI-first, multi-tenant hosting and SEO platform. Depending on the product line and plan you choose, the service may include managed WordPress, WooCommerce, PHP, static and Node hosting; footprint-free hosting for bulk and SEO networks; domain registration and DNS; content delivery, caching and security features; SEO tooling; and an AI assistant. We may add, change, or remove features over time to improve the platform, keep it secure, or comply with the law. Where a change materially reduces a core feature of a plan you are paying for, we will give you reasonable notice. We describe each plan and its included features on our pricing and product pages; those descriptions form part of these terms for the plan you buy. ## 3. Accounts and eligibility You must be at least 18 years old, or the age of majority where you live, and able to form a binding contract, to open an account. You are responsible for keeping your login credentials secure and for all activity that happens under your account. - Give accurate, current account and billing information, and keep it up to date. - Protect your password and enable the multi-factor authentication we offer; tell us promptly if you suspect unauthorised access. - Do not share, sell or transfer your account without our consent, except through the reseller, agency and team features we provide for that purpose. - You are responsible for the actions of anyone you invite into your account, including your own clients and team members. ## 4. Acceptable use Our platform is shared infrastructure serving many customers. These rules keep it safe, fast and lawful for everyone. You agree not to use the service, or allow anyone else to use it, to: - Host, publish or distribute anything unlawful — including child sexual abuse material, content that infringes intellectual property or privacy rights, or content that is defamatory, fraudulent or promotes violence or terrorism. - Send spam or unsolicited bulk messaging, run phishing pages, distribute malware, or host command-and-control or other infrastructure for attacks. - Attempt to breach, probe or disrupt the security of the platform, other customers' sites, or any third-party system — including unauthorised access, denial-of-service activity, or attempts to escape the isolation of your own environment. - Consume resources in a way that degrades the service for other customers, such as sustained abusive load, cryptomining, or running workloads a plan is not designed for. - Misrepresent your identity, impersonate others, or use the service to deceive search engines or users in ways that violate applicable law. - Resell or provide the service to third parties except through the reseller, agency or white-label features we offer for that purpose. You are responsible for the content and conduct of every site, application and mailbox in your account. We do not pre-screen customer content, but we may investigate suspected abuse and act under the Suspension and termination section below. We may also be required to act on valid legal notices and requests from competent authorities. Where a plan or feature is described as “unlimited”, it is unlimited for the normal operation of the websites that plan is sold for, subject to the fair-usage terms in section 4 of our Acceptable Use Policy; it is not a promise of unlimited physical resources. ## 5. Fees, billing and renewals Prices are shown on our pricing pages in the currencies we support, and you choose your currency at checkout. Unless stated otherwise, prices exclude taxes; we add any VAT or other taxes that apply to your country and, where required, show them on your invoice. Most plans are sold on a recurring subscription. You authorise us to charge your chosen payment method the plan price at the start of each billing period until you cancel. We drive renewals from our own engine using the payment mandate you place on file — we do not hand your subscription to a payment provider to manage. - We email you before each renewal so a charge is never a surprise. - You can cancel at any time from your dashboard; cancellation stops the next renewal and your plan runs to the end of the period already paid for. - If a payment fails, we retry it and contact you; we may suspend or downgrade the service if it stays unpaid after a reasonable dunning period. - Domain registrations, renewals and transfers are billed as one-off charges at the price shown and are passed through to the registry immediately. ## 6. Refunds and the money-back guarantee New paid hosting plans come with a 30-day money-back guarantee. If the service is not right for you, contact us within 30 days of your first payment for that plan and we will refund that payment. Some plans also offer a card-free trial so you can evaluate the platform before you pay at all. Domains and other third-party pass-through charges (such as registrations, renewals and transfers) are non-refundable once the registry or provider has processed them, because we are billed for them immediately and cannot recover the cost. Renewal charges after the initial 30-day window are not automatically refundable, but we look at individual circumstances in good faith and nothing here affects any statutory refund or cancellation rights you have as a consumer. ## 7. Suspension and termination You may close your account at any time. We may suspend or terminate your access, in whole or in part, if you materially breach these terms (including the acceptable use rules), if your account is significantly overdue, if we are required to by law, or if your use poses a security or stability risk to the platform or other customers. Where it is safe and lawful to do so, we will give you notice and a chance to put things right before suspending. In urgent cases — active abuse, illegal content, or a threat to shared infrastructure — we may act immediately and tell you afterwards. On termination your right to use the service ends; we will make your data available for export for a reasonable period, after which it may be deleted in line with our Privacy Policy. ## 8. Your content and data You keep all ownership of the websites, applications, files and data you host with us ("your content"). You grant us only the limited permission we need to store, process, back up, transmit and display your content in order to operate the service and provide support. You are responsible for having the rights and any consents needed for your content, and for keeping your own copies. We provide backups as described in your plan, but you remain responsible for maintaining an independent copy of anything you cannot afford to lose. Where we handle personal data on your behalf as a processor, that relationship is described in our Privacy Policy. ## 8a. AI apps you connect (MCP) You may connect AI apps such as Claude or ChatGPT to your account through our MCP server, using the permissions you choose when you approve them. - An action an app takes with the permissions you granted is treated as an action taken by you, under these terms and our acceptable use policy. - Actions that delete, overwrite or spend money ask for a confirmation in the app first, and paid actions stay within any spending limit on the connection. - You are responsible for which apps you connect and for disconnecting one you no longer trust, under Settings, AI tools. - We may suspend or disconnect an app that is abused, that endangers the platform or other customers, or when the account is not in good standing. - The AI app itself is provided by its own maker under its own terms; we are not responsible for what it says or does outside our platform. ## 9. Service levels and disclaimers We work hard to keep the platform available, fast and secure, and we describe the availability we aim for in the relevant plan and any service-level agreement. Except for commitments we make expressly in writing, the service is provided "as is" and "as available", and we do not warrant that it will be uninterrupted, error-free, or that it will meet a purpose we have not agreed with you. Nothing in these terms excludes or limits any liability that cannot be excluded or limited under applicable law, including your statutory rights as a consumer. ## 10. Limitation of liability To the fullest extent permitted by law, Zinn Digital® is not liable for indirect, incidental, special or consequential loss, or for loss of profits, revenue, goodwill, or data, arising out of or relating to the service. To the fullest extent permitted by law, our total aggregate liability for all claims arising in any 12-month period is limited to the amount you paid us for the service in that period. These limits do not apply to liability that cannot be limited by law — such as liability for death or personal injury caused by negligence, or for fraud. ## 11. Your responsibility for claims You agree to cover reasonable losses, damages and costs we incur from third-party claims that arise out of your content or your use of the service in breach of these terms or the law. We will tell you promptly about any such claim and give you the chance to help manage it. ## 12. Changes to these terms We may update these terms from time to time — for example, to reflect new features, legal requirements, or changes to how the platform works. When we make a material change we will update the date at the top of this page and, where the change significantly affects your rights, give you reasonable advance notice by email or in the dashboard. Continuing to use the service after a change takes effect means you accept the updated terms. If you do not agree to a change, you may cancel before it takes effect. ## 13. Governing law These terms and any dispute arising from them are governed by the laws of England and Wales, and you and we submit to the exclusive jurisdiction of the courts of England and Wales. If you are a consumer, this does not deprive you of the protection of the mandatory consumer laws of the country where you live. If any part of these terms is found to be unenforceable, the rest remains in force. Our not enforcing a right on one occasion is not a waiver of that right. ## 14. How to contact us These terms are between you and Zinn Digital® Ltd (Company No. 16385785, VAT No. GB 526 5236 92), 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom. For any question about these terms, reach us through our contact page at zinndigital.com/contact, or email office@zinndigital.com for formal legal notices. ## Frequently asked questions **Do I need to accept these terms to use Zinn Digital®?** Yes. Creating an account, buying a plan or using any part of the platform means you accept these terms. If you are agreeing on behalf of a company or client, you confirm you are authorised to bind them. **Can I get a refund?** Paid plans are covered by a 30-day money-back guarantee: if the service is not right for you, contact us within 30 days of your first payment for that plan and we will refund it. Domain registrations, renewals and transfers are non-refundable once the registry has processed them, because we are charged for them immediately. Renewals after the first 30 days are not automatically refundable, but we will always look at individual circumstances. **When am I charged?** You are charged the price shown for your plan at the start of each billing period, in the currency you selected at checkout, until you cancel. We email you before a renewal and you can cancel at any time from your dashboard to stop the next charge. **What happens if I break the acceptable use rules?** Depending on severity we may ask you to fix the problem, suspend the affected site, or in serious cases (illegal content, malware, or activity that threatens shared infrastructure or other customers) suspend or close the account. We aim to warn first where it is safe to do so, but we act immediately where the law or other customers require it. **Which country's law governs the agreement?** These terms are governed by the laws of England and Wales, and disputes fall to the courts of England and Wales. This does not remove consumer-protection rights you may have under the law of your own country. --- # Run AI features on your hosting without renting a GPU URL: https://zinndigital.com/hosting/ai Serverless inference on open models, billed by the thousand tokens against one balance you can see and cap. Bring your own provider key or spend Zinn® AI credits — either way it is the same meter, and your application sits on the same account. ## Plans and pricing - **Zinn® AI Start** — $14.99 a month, or $149.90 a year. NVMe storage: 25 GB, Bandwidth: 1 TB, Database size: 2.5 GB per site. - **Zinn® AI Builder** — $28.99 a month, or $289.90 a year. NVMe storage: 100 GB, Bandwidth: 5 TB, Database size: 2.5 GB per site. - **Zinn® AI Scale** — $99.99 a month, or $999.90 a year. NVMe storage: 500 GB, Bandwidth: 25 TB, Database size: 2.5 GB per site. ## Where your site lives Choose the data centre your site lives in: Helsinki, Finland (European Union), Singapore, Ashburn, eastern United States, and Hillsboro, western United States. ## Frequently asked questions **Do I need a GPU, or do you rent me one?** Neither. Inference runs on serverless open-model endpoints and is billed per 1,000 tokens, so there is no machine to reserve and nothing to pay for while it is idle. Dedicated GPU capacity is not something we sell today — we would rather tell you that than rent you one you do not need. **Can I use my own OpenAI or Anthropic key?** Yes. Add it under AI credentials and requests are made with your key, billed to you by that provider. Your Zinn® credit balance is untouched. You can switch between your key and our credits at any time without changing your code. **How do I know what it is costing me before the bill arrives?** Usage is metered per 1,000 tokens and the running total is on your dashboard as it happens, not at the end of the month. You set a cap; when it is reached, spending stops rather than continuing and surprising you. **Is my data used to train anybody's model?** No. Requests go through our gateway to the model provider and are not contributed to training. If you bring your own key, the terms you agreed with that provider apply to those requests. **What is not included yet?** One-click AI environments such as Jupyter, PyTorch and Ollama, and hosting for long-running agents, are not part of these plans. They need a machine you have root on rather than a shared hosting account, so they belong on Zinn® Private Cloud and we would rather leave them off this page than sell you something this plan cannot run. --- # Push to Git. Your Node.js, Python or Ruby app is live. URL: https://zinndigital.com/hosting/apps Connect a GitHub, GitLab or Bitbucket repository and every push becomes a release: dependencies installed and your build run first, then switched live. Roll back in one click, preview every branch on its own address, and keep your secrets out of your repository. ## Plans and pricing - **Zinn® Dev Start** — $14.99 a month, or $149.90 a year. NVMe storage: 25 GB, Bandwidth: 1 TB. - **Zinn® Dev Pro** — $28.99 a month, or $289.90 a year. NVMe storage: 100 GB, Bandwidth: 5 TB. - **Zinn® Dev Scale** — $99.99 a month, or $999.90 a year. NVMe storage: 500 GB, Bandwidth: 25 TB. ## Where your site lives Choose the data centre your site lives in: Helsinki, Finland (European Union), Singapore, Ashburn, eastern United States, and Hillsboro, western United States. ## Frequently asked questions **Which languages and frameworks can I run?** Node.js 24 with any framework that listens on the port it is given, such as Express or Fastify, started from app.js. Python 3.14 through WSGI, such as Django or Flask, from wsgi.py. Ruby 4.0 through Rack, such as Sinatra or Rails, from config.ru. Dependencies come from your package.json, requirements.txt or Gemfile and are installed on every deploy. **Can I run containers, Go, or Kubernetes?** Not on these plans. They run each app in an isolated account on our shared fleet, which has no container runtime. Containers, Go and Rust binaries and Kubernetes belong on a Zinn® Private Cloud server, where you have root and can run anything. **What about FastAPI and other ASGI apps?** The Python runner speaks WSGI. An ASGI app runs behind an adapter such as a2wsgi, which is a one-line change to your entry file. If you need native ASGI or long-lived WebSockets, a Zinn® Private Cloud server is the better fit. **Where do my API keys and database passwords go?** Into the environment variables panel for the site. Values are stored in a secret store, never shown again after you save them, and handed to both your build and your running app. Saving restarts the app so it picks them up. **How many branch previews can I have?** Two live previews on Dev Start, ten on Dev Pro and fifty on Dev Scale. Redeploying a branch replaces its preview rather than using another one, and you can take a preview down from the Releases card at any time. **Can I attach a database or a cache?** Yes. Zinn® Managed Databases give you PostgreSQL or MySQL with backups, reachable only from addresses you allow, and every site can use a Redis cache fenced to that site alone. Put the connection details in your environment variables. --- # A managed vector database that is just PostgreSQL URL: https://zinndigital.com/hosting/vector Store embeddings and search them by meaning, on pgvector we run and back up for you. No new datastore to learn, no cluster to size — create an index, write your vectors, and query it with the API key you already have. ## Plans and pricing - **Zinn® Vector Start** — $12.99 a month, or $129.90 a year. NVMe storage: 10 GB, Database size: 1 GB per site. - **Zinn® Vector Growth** — $19.99 a month, or $199.90 a year. NVMe storage: 50 GB, Database size: 1 GB per site. - **Zinn® Vector Scale** — $55.99 a month, or $559.90 a year. NVMe storage: 250 GB, Database size: 1 GB per site. ## Frequently asked questions **Which embedding models does this work with?** Any of them. You send us the numbers your model produced, so OpenAI, Cohere, Voyage, a Sentence-Transformers model on your own machine and anything else are all the same to us. You tell us the width when you create the index — 384, 768, 1024, 1536 and 3072 are all common, and so is something in between. **Can I change an index's width or distance function later?** No, and we would rather say so plainly than let you discover it. Both decide where your vectors are physically stored and how they are ranked, so changing either would silently invalidate everything already in the index. If you switch to a different embedding model, create a second index and write into it — the same thing every vector database asks of you, and for the same reason. **Is there anything different about very wide vectors?** Yes, and it is worth knowing. Above 2,000 dimensions the values are stored at half precision, because PostgreSQL's HNSW index does not accept a full-precision column wider than that. For 3072-dimension models this is the approach pgvector itself recommends and the effect on ranking is negligible — but it is a real trade-off and you should hear it from us rather than infer it. **Do I get a database connection string?** Not today. You reach your index over HTTPS with your Zinn® API key, scoped so a key that can search cannot do anything else in your account. That is what lets us meter queries honestly and keep one tenant's rows unreachable from another's. If a direct connection is what you need, tell us — we would rather build it because someone asked than guess. **How is it metered, and can I check the numbers myself?** On two meters: how much you store and how many searches you run in a calendar month. Both are on your dashboard as they happen. Storage is a published formula rather than a physical table size — row overhead, plus the stored width, plus the length of your own ids and metadata — precisely so you can reproduce the figure we are billing you for instead of taking our word for it. --- # Course hosting sized for video from the first plan URL: https://zinndigital.com/hosting/lms Choose WordPress with LearnDash or Tutor, or choose Moodle. Either way you get storage sized for course video rather than for a brochure site, and student pages that are never served from a cache. ## Plans and pricing - **Zinn® LMS Start** — $19.99 a month, or $199.90 a year. NVMe storage: 50 GB, Bandwidth: 2 TB, MySQL databases: 5, Database size: 1 GB per site. - **Zinn® LMS Academy** — $55.99 a month, or $559.90 a year. NVMe storage: 250 GB, Bandwidth: 10 TB, MySQL databases: Unlimited, Database size: 1 GB per site. - **Zinn® LMS Institution** — $189.99 a month, or $1,899.90 a year. NVMe storage: 1000 GB, Bandwidth: 50 TB, MySQL databases: Unlimited, Database size: 1 GB per site. - **Zinn® LMS Moodle** — $14.99 a month, or $149.90 a year. NVMe storage: 25 GB, Bandwidth: Unlimited, MySQL databases: Unlimited, Database size: 1 GB per site. ## Where your site lives Choose the data centre your site lives in: Helsinki, Finland (European Union), Singapore, Ashburn, eastern United States, and Hillsboro, western United States. ## Frequently asked questions **Should I pick WordPress or Moodle?** If you already have a WordPress site and want courses as part of it, pick WordPress with LearnDash or Tutor. If you are running structured cohorts with gradebooks, or your teaching staff already know Moodle, pick Moodle. You are not locked in either way — we will migrate you free of charge if you change your mind. **Will my course videos actually fit?** The entry plan is 50 GB, which is roughly 25 to 50 hours of compressed lesson video, and the plans go to 1 TB. If your library is larger than that, or you need several quality levels for students on slower connections, host the video with a streaming provider and embed it — that is the right answer at every scale and we will say so rather than sell you storage. **Why does caching matter for a course site?** A cache hands the same stored page to everyone who asks for it. On a course site that means a student can be shown somebody else's progress bar, or their own from an hour ago. We keep per-student pages out of the page cache and use a Redis object cache instead, which speeds up the database work an LMS does without ever showing one student another student's page. **Can I sell courses and take payment?** Yes. LearnDash and Tutor both handle payments through WooCommerce or their own checkouts, and Moodle supports enrolment payments. We host it; the payment relationship is between you and your provider. **Do you migrate my existing courses?** Yes, free, on every plan. Course content, student accounts and progress come across together — a migration that moves the lessons but loses who completed what is not a migration. --- # Fast, secure WordPress hosting — fully managed for you URL: https://zinndigital.com/hosting/wordpress LiteSpeed servers, a global CDN, daily backups, malware protection, staging and free SSL on every plan. We handle updates and security so you can grow your site. Try it free for 14 days — no card needed. ## Plans and pricing - **Start** — $2.99 a month, or $29.90 a year. NVMe storage: 5 GB, MySQL databases: Unlimited, Database size: 2 GB per site. - **Grow** — $7.99 a month, or $79.90 a year. NVMe storage: 15 GB, MySQL databases: Unlimited, Database size: 2 GB per site. - **Scale** — $14.99 a month, or $149.90 a year. NVMe storage: 30 GB, MySQL databases: Unlimited, Database size: 2 GB per site. - **Business** — $29.99 a month, or $299.90 a year. NVMe storage: 50 GB, MySQL databases: Unlimited, Database size: 2 GB per site. - **Pro+** — $99.99 a month, or $999.90 a year. NVMe storage: 500 GB, Bandwidth: 25 TB, MySQL databases: Unlimited, Database size: 2 GB per site. - **Enterprise** — $249.99 a month, or $2,499.90 a year. NVMe storage: Unlimited, Bandwidth: Unlimited, MySQL databases: Unlimited, Database size: 2 GB per site. ## Everything included ### Built for speed - Anycast CDN caching on every site - Automatic image and asset optimisation at the edge - Edge cache and traffic statistics - Switch PHP version whenever you need to - Full control of PHP settings and extensions ### Security, on by default - Free SSL certificate on every domain - SSL issued and renewed automatically - Force HTTPS across the whole site - Daily malware scanning - Malware findings reported in your dashboard - Security headers applied at the edge - Password-protect any directory - Block visitors by IP or country - Hotlink protection for your images and files ### WordPress, managed properly - WordPress manager built into your dashboard - Install, update and remove plugins - Install, update and switch themes - Core, plugin and theme updates handled for you - Manage WordPress users - Search, edit and optimise the WordPress database - Safe search-and-replace across the database - Core file checksum reports, so a tampered file shows up - Change WordPress settings without logging into wp-admin ### For developers - SSH and SFTP access - Deploy from Git - FTP access - phpMyAdmin for direct database access - Scheduled tasks (cron jobs) - Browser-based file manager - Set file and directory permissions - Maintenance mode while you work ### Backups and recovery - Daily backups - Timeline backups — restore a site to a point in time - Timeline Backups Pro, with a longer history and finer restore points ### Applications - Application manager for one-click installs and updates - Every application we add in future, included - Reinstall the platform from scratch whenever you want ### Business email included - Mailboxes - Mailbox size: 10 GB - Mail forwarders: Unlimited - Auto-responders: Unlimited - Webmail, with contacts, filters and out-of-office replies - IMAP sync from your old provider - DKIM signing configured for you - Guided DMARC setup - Spam and virus filtering on every mailbox ### Know what your site is doing - Bandwidth usage, per site - Disk usage, per site - Access and error logs you can read yourself - Automatic diagnostics when something looks wrong - Usage against your allowance, always visible ## Where your site lives Choose the data centre your site lives in: Helsinki, Finland (European Union), Singapore, Ashburn, eastern United States, and Hillsboro, western United States. ## Frequently asked questions **Is WordPress pre-installed?** Yes. WordPress is a one-click install and can be set up when your account is created, with the latest release and a database provisioned for it. **How many databases do I get?** As many MySQL databases as your sites need, on every plan. Each site's database has a size allowance, and you can raise it at any time from your dashboard. **Can I run WooCommerce on it?** Yes — WooCommerce is a WordPress plugin, so it installs on this platform like any other. If you are building a shop as the main event, our WooCommerce hosting page covers what changes. **Do you offer staging?** Yes, on every plan. You can create a staging copy of a site in one click, work on it, and push it live when you are ready. **Where will my site be hosted?** In the data centre you pick when you create the site. Today you can choose from: Helsinki, Finland (European Union), Singapore, Ashburn, eastern United States, and Hillsboro, western United States. **Can you move my existing site?** Yes. Send us the details of your current host and our team performs the migration for you — we do not ask you to run it yourself. --- # WooCommerce hosting for shops that intend to grow URL: https://zinndigital.com/hosting/woocommerce The same managed WordPress platform, set up for a shop: edge caching that knows to leave a basket alone, and staging on every plan so you never test a checkout change on live customers. ## Plans and pricing - **Start** — $2.99 a month, or $29.90 a year. NVMe storage: 5 GB, MySQL databases: Unlimited, Database size: 2 GB per site. - **Grow** — $7.99 a month, or $79.90 a year. NVMe storage: 15 GB, MySQL databases: Unlimited, Database size: 2 GB per site. - **Scale** — $14.99 a month, or $149.90 a year. NVMe storage: 30 GB, MySQL databases: Unlimited, Database size: 2 GB per site. - **Business** — $29.99 a month, or $299.90 a year. NVMe storage: 50 GB, MySQL databases: Unlimited, Database size: 2 GB per site. - **Pro+** — $99.99 a month, or $999.90 a year. NVMe storage: 500 GB, Bandwidth: 25 TB, MySQL databases: Unlimited, Database size: 2 GB per site. - **Enterprise** — $249.99 a month, or $2,499.90 a year. NVMe storage: Unlimited, Bandwidth: Unlimited, MySQL databases: Unlimited, Database size: 2 GB per site. ## Everything included ### Built for speed - Anycast CDN caching on every site - Automatic image and asset optimisation at the edge - Edge cache and traffic statistics - Switch PHP version whenever you need to - Full control of PHP settings and extensions ### Security, on by default - Free SSL certificate on every domain - SSL issued and renewed automatically - Force HTTPS across the whole site - Daily malware scanning - Malware findings reported in your dashboard - Security headers applied at the edge - Password-protect any directory - Block visitors by IP or country - Hotlink protection for your images and files ### WordPress, managed properly - WordPress manager built into your dashboard - Install, update and remove plugins - Install, update and switch themes - Core, plugin and theme updates handled for you - Manage WordPress users - Search, edit and optimise the WordPress database - Safe search-and-replace across the database - Core file checksum reports, so a tampered file shows up - Change WordPress settings without logging into wp-admin ### For developers - SSH and SFTP access - Deploy from Git - FTP access - phpMyAdmin for direct database access - Scheduled tasks (cron jobs) - Browser-based file manager - Set file and directory permissions - Maintenance mode while you work ### Backups and recovery - Daily backups - Timeline backups — restore a site to a point in time - Timeline Backups Pro, with a longer history and finer restore points ### Applications - Application manager for one-click installs and updates - Every application we add in future, included - Reinstall the platform from scratch whenever you want ### Business email included - Mailboxes - Mailbox size: 10 GB - Mail forwarders: Unlimited - Auto-responders: Unlimited - Webmail, with contacts, filters and out-of-office replies - IMAP sync from your old provider - DKIM signing configured for you - Guided DMARC setup - Spam and virus filtering on every mailbox ### Know what your site is doing - Bandwidth usage, per site - Disk usage, per site - Access and error logs you can read yourself - Automatic diagnostics when something looks wrong - Usage against your allowance, always visible ## Where your site lives Choose the data centre your site lives in: Helsinki, Finland (European Union), Singapore, Ashburn, eastern United States, and Hillsboro, western United States. ## Frequently asked questions **Is WooCommerce a one-click install?** No, and we would rather say so plainly: WooCommerce is a WordPress plugin, not a separate application. You install WordPress in one click and add WooCommerce from the plugin manager in your dashboard. **Will caching break my basket or checkout?** No. Basket, checkout and account pages are dynamic and are not served from cache; the catalogue and content pages are, which is where the speed comes from. **Can I test changes before customers see them?** Yes, on every plan. Create a staging copy in one click, make the change, and push it live when it works. **How much traffic can it take?** Every plan includes generous monthly traffic, and you can add bandwidth or a Performance Boost from your dashboard before a big sale. If your shop outgrows its plan, move up in one click; a very large shop belongs on a cloud server. **Do I get an SSL certificate?** Yes, free, issued and renewed automatically. You cannot take card payments without one, so it is not an upsell. **Can you migrate my existing shop?** Yes. Our team handles the migration, including the database, so orders and customers come across intact. --- # Linux hosting with room to actually build something URL: https://zinndigital.com/hosting/linux Drupal, Joomla, Laravel, Nextcloud and the rest of our application catalogue installed in a click — or your own PHP, static or Node code — with SSH, Git deployment and scheduled tasks, on our own LiteSpeed servers. ## Plans and pricing - **Linux Basic** — $2.99 a month. NVMe storage: 1 GB, Bandwidth: Unlimited, MySQL databases: 2, Database size: 400 MB per site. - **Linux Business** — $7.99 a month. NVMe storage: 10 GB, Bandwidth: Unlimited, MySQL databases: 2, Database size: 400 MB per site. - **Linux Pro** — $14.99 a month. NVMe storage: 25 GB, Bandwidth: Unlimited, MySQL databases: Unlimited, Database size: 400 MB per site. ## Everything included ### Built for speed - Anycast CDN caching on every site - Automatic image and asset optimisation at the edge - Edge cache and traffic statistics - Switch PHP version whenever you need to - Full control of PHP settings and extensions ### Security, on by default - Free SSL certificate on every domain - SSL issued and renewed automatically - Force HTTPS across the whole site - Daily malware scanning - Malware findings reported in your dashboard - Security headers applied at the edge - Password-protect any directory - Block visitors by IP or country - Hotlink protection for your images and files ### WordPress, managed properly - WordPress manager built into your dashboard - Install, update and remove plugins - Install, update and switch themes - Core, plugin and theme updates handled for you - Manage WordPress users - Search, edit and optimise the WordPress database - Safe search-and-replace across the database - Core file checksum reports, so a tampered file shows up - Change WordPress settings without logging into wp-admin ### For developers - SSH and SFTP access - Deploy from Git - FTP access - phpMyAdmin for direct database access - Scheduled tasks (cron jobs) - Browser-based file manager - Set file and directory permissions - Maintenance mode while you work ### Backups and recovery - Daily backups - Timeline backups — restore a site to a point in time - Timeline Backups Pro, with a longer history and finer restore points ### Applications - Application manager for one-click installs and updates - Every application we add in future, included - Reinstall the platform from scratch whenever you want ### Business email included - Mailboxes - Mailbox size: 10 GB - Mail forwarders: Unlimited - Auto-responders: Unlimited - Webmail, with contacts, filters and out-of-office replies - IMAP sync from your old provider - DKIM signing configured for you - Guided DMARC setup - Spam and virus filtering on every mailbox ### Know what your site is doing - Bandwidth usage, per site - Disk usage, per site - Access and error logs you can read yourself - Automatic diagnostics when something looks wrong - Usage against your allowance, always visible ## Where your site lives Choose the data centre your site lives in: Helsinki, Finland (European Union), Singapore, Ashburn, eastern United States, and Hillsboro, western United States. ## Frequently asked questions **What can I install in one click?** Every application our installer ships, including Drupal, Joomla, Laravel, PrestaShop, OpenCart, Moodle, Matomo, SuiteCRM, Nextcloud and phpBB — each installed with its database and tuned for our servers. Our applications index lists every one with what it does. **How many databases do I get?** Linux Basic and Linux Business include two MySQL databases each; Linux Pro has no database cap. **Do I get SSH access?** Yes, SSH and SFTP, plus Git deployment and scheduled tasks. This is a plan you can develop on, not just publish to. **Which PHP versions can I run?** You can switch PHP version yourself at any time, and control the settings and extensions from your dashboard. **Can I host more than one site?** Each plan is for one website, with subdomains included — two on Linux Basic, four on Linux Business and as many as you need on Linux Pro. Each further website needs a plan of its own. **Is Magento available?** Not on this plan. Magento needs a search stack that shared hosting cannot give it properly, so we offer it as a cloud server with Elasticsearch rather than pretend it fits here. --- # A VPS with room to grow URL: https://zinndigital.com/hosting/vps Five sizes, Start to Pro, on AMD EPYC servers with twice the disk of the same Zinn® Cloud size. Root on the whole machine, in Europe or Singapore, and a bigger size a few minutes away. ## Plans and pricing - **VPS Start** — $36.99 a month, or $369.90 a year. vCPU cores: 2, Memory: 4 GB, NVMe storage: 80 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany) · 1 TB (Singapore). - **VPS Grow** — $66.99 a month, or $669.90 a year. vCPU cores: 4, Memory: 8 GB, NVMe storage: 160 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany) · 2 TB (Singapore). - **VPS Scale** — $129.99 a month, or $1,299.90 a year. vCPU cores: 8, Memory: 16 GB, NVMe storage: 320 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany) · 3 TB (Singapore). - **VPS Business** — $187.99 a month, or $1,879.90 a year. vCPU cores: 12, Memory: 24 GB, NVMe storage: 480 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany) · 4 TB (Singapore). - **VPS Pro** — $239.99 a month, or $2,399.90 a year. vCPU cores: 16, Memory: 32 GB, NVMe storage: 640 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany) · 5 TB (Singapore). ## Where your site lives Choose the data centre your site lives in: Falkenstein, Germany (European Union), Nuremberg, Germany (European Union), Helsinki, Finland (European Union), and Singapore. ## Frequently asked questions **What is the difference between a VPS and shared hosting?** On shared hosting your sites share one server with other customers' sites. A VPS is a virtual server of your own with root access: the memory and disk listed are yours, and you install what you like. **Can I pay yearly?** Yes. Every size is sold monthly or yearly, and a year costs ten months. **Can I resize later?** Yes, up or down, from the server's page. It takes a few minutes and one restart, and your disk and data stay. **Is it managed?** It is yours to run: root access and your choice of operating system. Add managed care if you want us to patch and watch it, and automatic backups if you want a copy every day. **Where are the servers?** In our own data centres. Each size lists the cities it is sold in today, and you pick one when you order. **VPS or Zinn® Cloud?** Zinn® Cloud is the lowest price for the same cores and memory. VPS gives you twice the disk, AMD processors, Singapore, and sizes in stock when the budget range is not. --- # Zinn® Cloud — budget cloud servers, upgraded in minutes URL: https://zinndigital.com/hosting/cloud Four sizes, Start to Business, on servers we run ourselves in Europe. You get root on the whole machine. Add a Plesk control panel, CloudLinux, LiteSpeed, managed care or daily backups when you order or later, and move up or down a size from your dashboard. ## Plans and pricing - **Zinn® Cloud Start** — $11.99 a month, or $119.90 a year. vCPU cores: 2, Memory: 4 GB, NVMe storage: 40 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). - **Zinn® Cloud Grow** — $19.99 a month, or $199.90 a year. vCPU cores: 4, Memory: 8 GB, NVMe storage: 80 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). - **Zinn® Cloud Scale** — $34.99 a month, or $349.90 a year. vCPU cores: 8, Memory: 16 GB, NVMe storage: 160 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). - **Zinn® Cloud Business** — $64.99 a month, or $649.90 a year. vCPU cores: 16, Memory: 32 GB, NVMe storage: 320 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). ## Frequently asked questions **Is Zinn® Cloud managed?** Not unless you want it to be. You get root and run the server your way. Add managed care and we patch and watch it for you; add automatic backups and it is copied every day. **Can I add Plesk?** Yes. Choose Plesk Web Pro or Web Host when you order, or add it to a running server from its page. The licence is billed monthly with the server. **How long does an upgrade take?** A few minutes and one restart. The cores and memory change; your disk and data stay as they are, so you can always move back down. **Where are the servers?** In our own data centres in Germany and Finland. For Singapore choose VPS; for the United States choose Zinn® Private Cloud. **How is it billed?** Monthly, or yearly at ten times the monthly price. You can also pay by the hour from your account balance. **Do I ever see another company's control panel?** No. Everything is in our dashboard, under our name. A Plesk panel you add is yours, on your own server. --- # Zinn® Private Cloud — a whole machine, and root on it URL: https://zinndigital.com/hosting/compute Machines we source and run ourselves rather than resell. You get root over the whole box: no control panel, no managed layer, nothing installed that you did not ask for. What a machine costs depends on the city it runs in, so every figure here is the lowest we sell that size at. ## Where your site lives Choose the data centre your site lives in: Falkenstein, Germany (European Union), Nuremberg, Germany (European Union), Helsinki, Finland (European Union), Singapore, Ashburn, eastern United States, and Hillsboro, western United States. ## Frequently asked questions **Is Zinn® Private Cloud managed?** Not by default. You get root on the whole machine with nothing of ours running on top — no control panel, no agent. Backups, updates and patching are yours, unless you add managed care or automatic backups to the server. **Why does the same size cost different amounts in different cities?** Because it costs us different amounts. The same machine costs several times more in Singapore or the United States than in Europe, so each city is priced on its own rather than averaged into one figure that would overcharge most customers. Every price on this page is the cheapest city for that size, which is why it is written as a “from” — you see the exact figure for the city you pick. **Can I send email from a Zinn® Private Cloud machine?** Not directly on port 25: outbound SMTP is closed on this range, as it is at most providers, because an open port 25 on a fresh machine is what turns a network into a spam source. Send through our relay on port 587 with your own credentials — the same route an application would normally use — and your mail goes out authenticated. **What do I need before my first machine?** Two things: a confirmed email address on the account, and a card, which your bank confirms when you add it. Nothing is charged until you order. We only ask for proof of identity when something about an account looks wrong. New accounts also start with limits on how many machines they can run and how much they can spend each month; your dashboard shows them before you order, and they rise as the account builds a history, or sooner if you ask. **Is the city I want always available?** Not always. Stock moves, and a size can be unbuildable in one city for a day and back the next. The cities listed against a size are the ones we sell it in; what can actually be built is checked live at the moment you order, so you are never sold a machine that cannot be created. **Do you run anything on the machine?** Nothing. We run the network, the storage and the console; everything above the operating system is yours, including what you install and who you let in. That is what unmanaged means here, and it is why the range is priced the way it is. **What happens if one of my machines is reported for abuse?** Reports about a machine come to us, because we hold the account it runs under. We pass them to the account owner, and a machine that is causing harm is powered off, with its disk kept, until the problem is fixed. You are responsible for keeping your machine secure, and our Acceptable Use Policy sets out what is not allowed. --- # AWS, without the AWS console URL: https://zinndigital.com/hosting/cloud/aws Amazon's network and Amazon's reach, with the server built, tuned, patched and managed by us — and every control in our dashboard rather than in a cloud console you have to learn. ## Plans and pricing - **Zinn® Cloud AWS Micro** — $13.99 a month, or $139.90 a year. vCPU cores: 2, Memory: 1 GB, NVMe storage: 20 GB. - **Zinn® Cloud AWS Small** — $22.99 a month, or $229.90 a year. vCPU cores: 2, Memory: 2 GB, NVMe storage: 20 GB. - **Zinn® Cloud AWS Medium** — $45.99 a month, or $459.90 a year. vCPU cores: 2, Memory: 4 GB, NVMe storage: 20 GB. - **Zinn® Cloud AWS Large** — $87.99 a month, or $879.90 a year. vCPU cores: 2, Memory: 8 GB, NVMe storage: 20 GB. - **Zinn® Cloud AWS X Large** — $172.99 a month, or $1,729.90 a year. vCPU cores: 4, Memory: 16 GB, NVMe storage: 20 GB. - **Zinn® Cloud AWS 2X Large** — $342.99 a month, or $3,429.90 a year. vCPU cores: 8, Memory: 32 GB, NVMe storage: 20 GB. - **Zinn® Cloud AWS 4X Large** — $787.99 a month, or $7,879.90 a year. vCPU cores: 16, Memory: 64 GB, NVMe storage: 20 GB. - **Zinn® Cloud AWS 8X Large** — $1,572.99 a month, or $15,729.90 a year. vCPU cores: 32, Memory: 128 GB, NVMe storage: 20 GB. ## Frequently asked questions **What does it cost?** The prices above are the real, published monthly and yearly prices for each size, and they are read from the same catalogue our billing engine charges from. Storage and bandwidth beyond what the size includes are extra and depend on what you use, so those are quoted rather than printed — but the machine itself has a price and it is on this page. **Which region will my server be in?** You tell us when you order and we build it there. AWS operates regions on every populated continent; we do not publish a list here because it is Amazon's to change and a stale list on our page would send somebody to a region that has moved. Ask before you order if a specific region matters — it usually does for latency and for where data sits. **Which application stacks are available?** The same set as our other managed servers: PHP, WordPress, WooCommerce, Magento, Laravel, Joomla, Node.js and .NET Core, each with the caching or search components that stack needs. **Do I need an AWS account?** No. The account, the billing and the operations are ours. You get a managed server and a single invoice from us. **Can I move to this from shared hosting?** Yes, and it is a common path. Migration on to the platform is automated and verified before anything is pointed at us, so you see the site running here first. Talk to us about the workload and we will tell you honestly whether you need this yet — most sites do not, and a managed server you do not need is money spent on headroom. --- # Google Cloud, run for you URL: https://zinndigital.com/hosting/cloud/google Google's network and Google's reach, with the server built, tuned, patched and managed by us — and nothing to configure in a cloud console. ## Plans and pricing - **Zinn® Cloud Google Micro** — $45.99 a month, or $459.90 a year. vCPU cores: 1, Memory: 3.75 GB, NVMe storage: 20 GB. - **Zinn® Cloud Google Small** — $119.99 a month, or $1,199.90 a year. vCPU cores: 2, Memory: 8 GB, NVMe storage: 20 GB. - **Zinn® Cloud Google Medium** — $236.99 a month, or $2,369.90 a year. vCPU cores: 4, Memory: 16 GB, NVMe storage: 20 GB. - **Zinn® Cloud Google Large** — $471.99 a month, or $4,719.90 a year. vCPU cores: 8, Memory: 32 GB, NVMe storage: 20 GB. - **Zinn® Cloud Google X Large** — $941.99 a month, or $9,419.90 a year. vCPU cores: 16, Memory: 64 GB, NVMe storage: 20 GB. - **Zinn® Cloud Google 2X Large** — $1,880.99 a month, or $18,809.90 a year. vCPU cores: 32, Memory: 128 GB, NVMe storage: 20 GB. - **Zinn® Cloud Google 4X Large** — $2,819.99 a month, or $28,199.90 a year. vCPU cores: 48, Memory: 192 GB, NVMe storage: 20 GB. - **Zinn® Cloud Google 8X Large** — $3,758.99 a month, or $37,589.90 a year. vCPU cores: 64, Memory: 256 GB, NVMe storage: 20 GB. ## Frequently asked questions **What does it cost?** The prices above are the real, published monthly and yearly prices for each size, read from the same catalogue our billing engine charges from. Storage and bandwidth beyond what the size includes depend on what you use and are quoted, but the machine itself has a price and it is on this page. **Which region will my server be in?** You tell us when you order and we build it there. Google Cloud operates regions on every populated continent; we do not print a list because it is Google's to change and a stale list here would send somebody to a region that has moved. Ask before you order if a specific region matters. **Which application stacks are available?** PHP, WordPress, WooCommerce, Magento, Laravel, Joomla, Node.js and .NET Core, each with the caching or search components that stack needs. **Do I need a Google Cloud account?** No. We hold the account and operate the platform; you get a managed server and one invoice from us. **How is this different from Zinn® Cloud?** Reach and price. Zinn® Cloud is our own fleet in a small number of European and Asian locations and is the cheapest machine we sell; Google Cloud reaches far more of the world and costs more for the same specification. If your visitors are where our own cloud already is, that is the one to take. --- # The tier where we control the whole stack URL: https://zinndigital.com/hosting/premium WordPress and WooCommerce running on hardware we own and operate — per-site isolation, our own caching layer, our own backups and our own monitoring, with nothing between us and the problem when you report one. ## Plans and pricing - **Start** — $2.99 a month, or $29.90 a year. NVMe storage: 5 GB, MySQL databases: Unlimited, Database size: 2 GB per site. - **Grow** — $7.99 a month, or $79.90 a year. NVMe storage: 15 GB, MySQL databases: Unlimited, Database size: 2 GB per site. - **Scale** — $14.99 a month, or $149.90 a year. NVMe storage: 30 GB, MySQL databases: Unlimited, Database size: 2 GB per site. - **Business** — $29.99 a month, or $299.90 a year. NVMe storage: 50 GB, MySQL databases: Unlimited, Database size: 2 GB per site. - **Pro+** — $99.99 a month, or $999.90 a year. NVMe storage: 500 GB, Bandwidth: 25 TB, MySQL databases: Unlimited, Database size: 2 GB per site. - **Enterprise** — $249.99 a month, or $2,499.90 a year. NVMe storage: Unlimited, Bandwidth: Unlimited, MySQL databases: Unlimited, Database size: 2 GB per site. ## Where your site lives Choose the data centre your site lives in: Helsinki, Finland (European Union), Singapore, Ashburn, eastern United States, and Hillsboro, western United States. ## Frequently asked questions **How is this different from your other WordPress plans?** It is the same platform and the same managed stack — every WordPress plan runs on hardware we own and operate. Pro+ and Enterprise add room for many sites, priority support and a migration done for you. **Can I order it today?** Yes. Choose Pro+ or Enterprise below and your account is ready straight away; for a large estate we plan the migration with you. **What does Enterprise add over Pro+?** Enterprise removes the site count and disk limit, adds 90-day backup retention and a named contact, and keeps everything Pro+ includes. Generous use is covered by our fair-usage policy. **Should I start smaller?** If you run a handful of sites, Scale or Business does the same job for less, and you can move up in one click when you need to. **Can you move all my sites for me?** Yes. On Pro+ and Enterprise our team migrates your whole estate and checks each site before you switch DNS. --- # Node.js hosting on a server of your own URL: https://zinndigital.com/hosting/nodejs A cloud server of your own — the whole machine, with root, from a clean operating system or a ready Docker or Kubernetes stack. You install and run Node.js exactly as you want it; we run the hardware, the network and the provisioning, and back it up every day if you switch backups on. ## Plans and pricing - **Zinn® Cloud Start** — $11.99 a month, or $119.90 a year. vCPU cores: 2, Memory: 4 GB, NVMe storage: 40 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). - **Zinn® Cloud Grow** — $19.99 a month, or $199.90 a year. vCPU cores: 4, Memory: 8 GB, NVMe storage: 80 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). - **Zinn® Cloud Scale** — $34.99 a month, or $349.90 a year. vCPU cores: 8, Memory: 16 GB, NVMe storage: 160 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). - **Zinn® Cloud Business** — $64.99 a month, or $649.90 a year. vCPU cores: 16, Memory: 32 GB, NVMe storage: 320 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). ## Frequently asked questions **Do I get root access?** Yes. It is your machine — you have root over the whole thing, so you install what you like, run whatever process manager you prefer, and are never waiting on us to enable something. **Is Node.js already installed when the server arrives?** No, and we would rather say so. You get a clean managed machine with root, and you install the runtime the way your application needs it — the version, the process manager, the reverse proxy. We deliberately do not claim a pre-tuned stack: we checked what a newly built server actually contains, and promising otherwise would be a claim you could disprove in your first SSH session. **Where can the server be?** Eight data centres: Dallas, Los Angeles, Miami and Washington DC in North America; London, Frankfurt and Amsterdam in Europe; and Singapore in Asia. You pick the city when you build the server. **Can I resize it later?** Yes. Sizes run from one core and 1 GB of memory up to forty-eight cores and 128 GB, and you move between them as the application grows rather than rebuilding on a bigger box. **Is it managed, or am I on my own?** The machine, the network and the provisioning are ours, and the daily backups too once you switch them on. What runs on top of it is yours — which is the arrangement most teams building an application actually want, because the deploy is the part they do not want anybody else touching. **Can I pay yearly?** Yes. Every size is sold monthly or yearly, and the yearly price is the cheaper of the two. You can start monthly and switch. --- # Magento hosting on a server of your own URL: https://zinndigital.com/hosting/magento Magento is a demanding application and it does not belong on shared hosting. This is a whole cloud server of your own, with root access, daily backups one switch away, and sizes for a real catalogue. ## Plans and pricing - **Zinn® Cloud Start** — $11.99 a month, or $119.90 a year. vCPU cores: 2, Memory: 4 GB, NVMe storage: 40 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). - **Zinn® Cloud Grow** — $19.99 a month, or $199.90 a year. vCPU cores: 4, Memory: 8 GB, NVMe storage: 80 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). - **Zinn® Cloud Scale** — $34.99 a month, or $349.90 a year. vCPU cores: 8, Memory: 16 GB, NVMe storage: 160 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). - **Zinn® Cloud Business** — $64.99 a month, or $649.90 a year. vCPU cores: 16, Memory: 32 GB, NVMe storage: 320 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). ## Frequently asked questions **Which size should a Magento store start on?** Higher than you would expect. Magento wants memory more than it wants cores, and a real catalogue with indexers running is not comfortable on the smallest sizes. Because you can move up the ladder without rebuilding, starting mid-range and watching it is a better plan than guessing high. **Is Magento already installed when the server arrives?** No, and we would rather say so. You get a clean managed machine with root, and the installation and its configuration are yours to run and yours to control. We deliberately do not claim a pre-built Magento stack: we checked what a newly built server actually contains, and a promise you could disprove in your first SSH session is worth less than none. **Is Magento available on your shared hosting?** No, and we would rather say so than sell you something that will disappoint you. Magento is not one of the applications our shared platform installs in a click, and it is not an application that behaves well when it shares a machine. This range exists for it. **Where can the server be?** Eight data centres: Dallas, Los Angeles, Miami and Washington DC in North America; London, Frankfurt and Amsterdam in Europe; and Singapore in Asia. You pick the city when you build the server. **Can I run more than one storefront on it?** Yes. Multiple websites, stores and store views from one installation is a Magento feature rather than a hosting one, and having the whole machine is what makes running several of them on it practical. **Can I pay yearly?** Yes. Every size is sold monthly or yearly, and the yearly price is the cheaper of the two. You can start monthly and switch. --- # Laravel hosting — three ways to run it, on one platform URL: https://zinndigital.com/hosting/laravel Install Laravel in one click on our shared Linux platform, take a managed Laravel plan with SSH, Git, Composer and scheduled tasks already in place, or take a whole cloud server with root access from a clean operating system or a ready Docker stack. Same platform, same dashboard, same support — and moving between them is a migration we do for you. ## Plans and pricing - **Zinn® Cloud Start** — $11.99 a month, or $119.90 a year. vCPU cores: 2, Memory: 4 GB, NVMe storage: 40 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). - **Zinn® Cloud Grow** — $19.99 a month, or $199.90 a year. vCPU cores: 4, Memory: 8 GB, NVMe storage: 80 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). - **Zinn® Cloud Scale** — $34.99 a month, or $349.90 a year. vCPU cores: 8, Memory: 16 GB, NVMe storage: 160 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). - **Zinn® Cloud Business** — $64.99 a month, or $649.90 a year. vCPU cores: 16, Memory: 32 GB, NVMe storage: 320 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). ## Everything included ### Built for speed - Anycast CDN caching on every site - Automatic image and asset optimisation at the edge - Edge cache and traffic statistics - Switch PHP version whenever you need to - Full control of PHP settings and extensions ### Security, on by default - Free SSL certificate on every domain - SSL issued and renewed automatically - Force HTTPS across the whole site - Daily malware scanning - Malware findings reported in your dashboard - Security headers applied at the edge - Password-protect any directory - Block visitors by IP or country - Hotlink protection for your images and files ### For developers - SSH and SFTP access - Deploy from Git - FTP access - phpMyAdmin for direct database access - Scheduled tasks (cron jobs) - Browser-based file manager - Set file and directory permissions - Maintenance mode while you work ### Backups and recovery - Daily backups - Timeline backups — restore a site to a point in time - Timeline Backups Pro, with a longer history and finer restore points ### Applications - Application manager for one-click installs and updates - Every application we add in future, included - Reinstall the platform from scratch whenever you want ### Business email included - Mailboxes - Mailbox size: 10 GB - Mail forwarders: Unlimited - Auto-responders: Unlimited - Webmail, with contacts, filters and out-of-office replies - IMAP sync from your old provider - DKIM signing configured for you - Guided DMARC setup - Spam and virus filtering on every mailbox ### Know what your site is doing - Bandwidth usage, per site - Disk usage, per site - Access and error logs you can read yourself - Automatic diagnostics when something looks wrong - Usage against your allowance, always visible ## Where your site lives Choose the data centre your site lives in: Helsinki, Finland (European Union), Singapore, Ashburn, eastern United States, and Hillsboro, western United States. ## Frequently asked questions **Do I get root access?** On a cloud server, yes — it is your machine and you have root over the whole thing. On the Linux platform and on a managed plan you get SSH, Git and cron rather than root, because the server is shared and we keep it patched. If your deploy needs root, the cloud range is the rung to take. **Is Laravel already installed?** It depends on the rung. On a managed plan, yes — the account is provisioned with the application on it. On a Linux platform plan it is one click from your dashboard whenever you want it. On a cloud server, no, and we would rather say so: you get a clean machine with root, from a clean operating system or a ready Docker stack, and you install PHP, Composer and Laravel the way your application needs them. Choosing a profile records what the machine is for; it does not install software. **Where will it be hosted?** A managed plan runs on our own server fleet, in the data centre you choose — the cities on offer today are listed on this page. A cloud server can be built in eight: Dallas, Los Angeles, Miami and Washington DC in North America; London, Frankfurt and Amsterdam in Europe; and Singapore in Asia. You pick the city when you order. **Can I move up later?** Yes, in every direction. The shared rungs step up as the application grows, and cloud sizes run from one core and 1 GB of memory to forty-eight cores and 128 GB. Moving from a shared plan to a server of your own is a migration we do for you. **Is it managed, or am I on my own?** That is what the three rungs are for. On the Linux platform and on a managed plan we run the server and the platform — updates, caching, SSL, malware scanning and backups are ours; the difference between those two is only whether the application is already installed when you arrive. On a cloud server the machine and the network are ours, daily backups are one switch away, and the deploy is yours, which is what most teams shipping a Laravel application want. **Can I pay yearly?** Yes, on every rung. Every platform plan, every managed plan and every server size is sold monthly or yearly, and each plan shows both prices with any saving worked out for you — so you are never doing the arithmetic yourself. You can start monthly and switch later, and the price you sign up at is the price you renew at. --- # Joomla hosting — three ways to run it, on one platform URL: https://zinndigital.com/hosting/joomla Install Joomla in one click on our shared Linux platform, take a managed Joomla plan with it already running and patched for you, or take a whole cloud server with root access from a clean operating system or a ready Docker stack. Same platform, same dashboard, same support — move between them whenever the site outgrows the rung it is on. ## Plans and pricing - **Zinn® Cloud Start** — $11.99 a month, or $119.90 a year. vCPU cores: 2, Memory: 4 GB, NVMe storage: 40 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). - **Zinn® Cloud Grow** — $19.99 a month, or $199.90 a year. vCPU cores: 4, Memory: 8 GB, NVMe storage: 80 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). - **Zinn® Cloud Scale** — $34.99 a month, or $349.90 a year. vCPU cores: 8, Memory: 16 GB, NVMe storage: 160 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). - **Zinn® Cloud Business** — $64.99 a month, or $649.90 a year. vCPU cores: 16, Memory: 32 GB, NVMe storage: 320 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). ## Everything included ### Built for speed - Anycast CDN caching on every site - Automatic image and asset optimisation at the edge - Edge cache and traffic statistics - Switch PHP version whenever you need to - Full control of PHP settings and extensions ### Security, on by default - Free SSL certificate on every domain - SSL issued and renewed automatically - Force HTTPS across the whole site - Daily malware scanning - Malware findings reported in your dashboard - Security headers applied at the edge - Password-protect any directory - Block visitors by IP or country - Hotlink protection for your images and files ### For developers - SSH and SFTP access - Deploy from Git - FTP access - phpMyAdmin for direct database access - Scheduled tasks (cron jobs) - Browser-based file manager - Set file and directory permissions - Maintenance mode while you work ### Backups and recovery - Daily backups - Timeline backups — restore a site to a point in time - Timeline Backups Pro, with a longer history and finer restore points ### Applications - Application manager for one-click installs and updates - Every application we add in future, included - Reinstall the platform from scratch whenever you want ### Business email included - Mailboxes - Mailbox size: 10 GB - Mail forwarders: Unlimited - Auto-responders: Unlimited - Webmail, with contacts, filters and out-of-office replies - IMAP sync from your old provider - DKIM signing configured for you - Guided DMARC setup - Spam and virus filtering on every mailbox ### Know what your site is doing - Bandwidth usage, per site - Disk usage, per site - Access and error logs you can read yourself - Automatic diagnostics when something looks wrong - Usage against your allowance, always visible ## Where your site lives Choose the data centre your site lives in: Helsinki, Finland (European Union), Singapore, Ashburn, eastern United States, and Hillsboro, western United States. ## Frequently asked questions **Do I get root access?** On a cloud server, yes — it is your machine and you have root over the whole thing. On the Linux platform and on a managed Joomla plan you get SSH, Git, cron and phpMyAdmin rather than root, because the server is shared and we keep it patched for you. If you need root, the cloud range is the rung to take. **Is Joomla already installed?** It depends on the rung, and we would rather say so than let you find out. On a managed Joomla plan, yes — the account is provisioned with Joomla on it and you log in and start. On a Linux platform plan it is one click from your dashboard, whenever you want it, along with the rest of our application catalogue. On a cloud server, no: you get a clean machine with root, from a clean operating system or a ready Docker stack, and you install PHP and Joomla the way your site needs them. Choosing a profile records what the machine is for; it does not install software. **Where will it be hosted?** A managed plan runs on our own server fleet, in the data centre you choose — the cities on offer today are listed on this page. A cloud server can be built in eight: Dallas, Los Angeles, Miami and Washington DC in North America; London, Frankfurt and Amsterdam in Europe; and Singapore in Asia. You pick the city when you order. **Can I move up later?** Yes, in every direction. The Linux platform and the managed Joomla plans step up as the site grows, and cloud sizes run from one core and 1 GB of memory to forty-eight cores and 128 GB. Moving up from a shared plan to a server of your own is a migration we do for you. **Is it managed, or am I on my own?** That is what the three rungs are for. On the Linux platform and on a managed plan we run the server and the software — updates, caching, SSL, malware scanning and backups are ours; the difference between those two is only whether Joomla is already installed when you arrive. On a cloud server the machine, the network and the provisioning are ours, daily backups are one switch away, and the software on top is yours. **Can I pay yearly?** Yes, on every rung. Every platform plan, every managed plan and every server size is sold monthly or yearly, and each plan shows both prices with any saving worked out for you — so you are never doing the arithmetic yourself. You can start monthly and switch later, and the price you sign up at is the price you renew at. --- # Hosting built for agencies managing many client sites URL: https://zinndigital.com/hosting/agency Run every client site from one place — and run the business around it. Agency hosting includes a full client invoicing suite, time tracking that turns logged hours into a draft invoice, a project board per client you can share with them, and a white-label dashboard your clients see instead of ours. On the engine we built to host hundreds of thousands of sites. ## Plans and pricing - **Agency Start** — $49.00 a month. NVMe storage: 100 GB, Database size: 400 MB per site. - **Agency Growth** — $99.00 a month. NVMe storage: 300 GB, Database size: 400 MB per site. - **Agency Scale** — $199.00 a month. NVMe storage: 750 GB, Database size: 400 MB per site. ## Where your site lives Choose the data centre your site lives in: Helsinki, Finland (European Union), Singapore, Ashburn, eastern United States, and Hillsboro, western United States. ## Frequently asked questions **Can I manage all my clients from one account?** Yes. Your agency sits at the top of a hierarchy, with each client and their sites underneath. You manage the whole portfolio from one account, group sites however suits you, and run bulk actions across a group at once. **How does team access work?** Team access uses role-based seats. Each member gets a role — owner, billing, developer or read-only — and that access can be scoped to specific organisations or individual sites, so people only see and change what they should. **Can I white-label the platform for my clients?** Yes. You can present the platform under your own agency brand so clients see you rather than Zinn Digital®. White-label applies across product lines. **Do you offer staging for client sites?** Yes. You can clone any site to a staging copy, make and review changes safely away from the live site, then push to live in a single step when you are ready. **Will you migrate our existing client sites?** Yes. Migrations are free — we move your existing client sites onto the platform for you, so switching does not mean re-doing your work. **What do the three tiers cover, and is there a trial?** Agency hosting has three tiers — Start, Growth and Scale, for 25, 75 and 200 client sites. The comparison table above is read from the live catalogue, current rates are shown in your own currency, and every tier can be started with a card-free 14-day trial. **Do I get anything to run the client work itself, not just the hosting?** Yes. Zinn® Boards is included in your dashboard: a project board per client, with a view you can share with that client so they can follow progress without an account of their own. It sits beside the sites it is about, so the work and the hosting are not in two different tools. **Can I invoice my own clients from the platform?** Yes, and it is included on every agency tier. The invoicing suite lets you save your clients, build an invoice from your own lines or from logged hours, apply your own tax rates, and send it as a branded PDF with a payment link. It uses your business name, your numbering and your tax registration — it is your document, not ours. **How does time tracking turn into an invoice?** Your team logs time against a client's project with a note of what they did. A rate resolves automatically — the most specific rate wins, so a task rate beats a project rate, which beats a client rate, which beats your default. Unbilled time then becomes a draft invoice: manually, as soon as it is logged, on a chosen day of the month, or once a client passes an amount you set. You review the draft before anything is sent. **Do you take a cut of what I charge my clients?** No. Invoices you raise are between you and your client: payments settle into your own Stripe, PayPal or crypto account and never pass through Zinn Digital®. You pay us for the hosting plan, and what you charge for your work is entirely yours. --- # Sell hosting under your own brand URL: https://zinndigital.com/hosting/reseller Sell hosting under your own brand on the engine we built to host 100,000+ PBN sites. Sub-accounts, a white-label panel, per-client isolation, bulk provisioning and one consolidated bill — you set the pricing, we run the infrastructure. ## Plans and pricing - **Reseller Launch** — $99.00 a month. NVMe storage: 150 GB, Database size: 400 MB per site. - **Reseller Pro** — $249.00 a month. NVMe storage: 500 GB, Database size: 400 MB per site. - **Reseller Scale** — $499.00 a month. NVMe storage: 1200 GB, Database size: 400 MB per site. ## Where your site lives Choose the data centre your site lives in: Helsinki, Finland (European Union), Singapore, Ashburn, eastern United States, and Hillsboro, western United States. ## Frequently asked questions **What is reseller hosting?** Reseller hosting lets you sell hosting under your own brand. You create sub-accounts for your clients, manage their sites from a white-label panel, and set your own pricing — while Zinn Digital® runs the underlying infrastructure. **How are my clients kept separate from each other?** Every client is a separate tenant in a hierarchical reseller-to-client-to-site tree. Row-level security keeps each tenant's data isolated, and per-site compute isolation using containers and namespaces means one compromised site cannot reach another. **Can I set my own prices?** Yes. You set your own markup per plan and bill your clients as you choose. The platform tracks the margin between wholesale cost and your sell price for you, and gives you a single consolidated bill across all your clients. **Which hosting types can I resell?** White-label works across every product line on the engine — footprint-free hosting, mainstream managed WordPress, WooCommerce and multisite — all from one account. **Can I move my existing clients over?** Yes — migrations are free and we will move your existing client sites onto the platform at no cost. **Is there a free trial?** Not on reseller plans. They are billed monthly with a 30-day money-back guarantee, so the smallest tier is the low-risk way to start rather than a trial. Agency hosting does include a card-free 14-day trial if that suits you better. **Can I sell to clients who do not speak English?** Yes, and this is the part most white-label programmes do not have. Your clients' control panel, their emails, their invoices and their notifications are already written in 58 languages, including five that read right to left — Arabic, Hebrew, Persian, Urdu and Pashto — with the whole interface mirrored rather than merely translated. It is included in every reseller plan at no extra cost and there is nothing to translate yourself. You choose which of the 58 your clients are offered and which one a new client account starts in, so if you sell into one market their panel is simply in that language. Translating your own material — your website, your own marketing — is separate: you can connect your own AI provider key and pay that provider directly for it. **Will this work with the billing system I already use?** If you run WHMCS or HostBill, yes — we publish free modules for both, so an order in your panel provisions the hosting for you. If you run something else, there is a single-file PHP client you can call from it. See /integrations for all three. --- # .NET hosting — three ways to run it, on one platform URL: https://zinndigital.com/hosting/netcore Install a .NET Core application in one click on our shared Linux platform, take a managed .NET plan on a platform that already runs it, or take a whole cloud server with root access from a clean operating system or a ready Docker stack and choose the runtime, the reverse proxy and the service manager yourself. ## Plans and pricing - **Zinn® Cloud Start** — $11.99 a month, or $119.90 a year. vCPU cores: 2, Memory: 4 GB, NVMe storage: 40 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). - **Zinn® Cloud Grow** — $19.99 a month, or $199.90 a year. vCPU cores: 4, Memory: 8 GB, NVMe storage: 80 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). - **Zinn® Cloud Scale** — $34.99 a month, or $349.90 a year. vCPU cores: 8, Memory: 16 GB, NVMe storage: 160 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). - **Zinn® Cloud Business** — $64.99 a month, or $649.90 a year. vCPU cores: 16, Memory: 32 GB, NVMe storage: 320 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). ## Everything included ### Built for speed - Anycast CDN caching on every site - Automatic image and asset optimisation at the edge - Edge cache and traffic statistics - Switch PHP version whenever you need to - Full control of PHP settings and extensions ### Security, on by default - Free SSL certificate on every domain - SSL issued and renewed automatically - Force HTTPS across the whole site - Daily malware scanning - Malware findings reported in your dashboard - Security headers applied at the edge - Password-protect any directory - Block visitors by IP or country - Hotlink protection for your images and files ### For developers - SSH and SFTP access - Deploy from Git - FTP access - phpMyAdmin for direct database access - Scheduled tasks (cron jobs) - Browser-based file manager - Set file and directory permissions - Maintenance mode while you work ### Backups and recovery - Daily backups - Timeline backups — restore a site to a point in time - Timeline Backups Pro, with a longer history and finer restore points ### Applications - Application manager for one-click installs and updates - Every application we add in future, included - Reinstall the platform from scratch whenever you want ### Business email included - Mailboxes - Mailbox size: 10 GB - Mail forwarders: Unlimited - Auto-responders: Unlimited - Webmail, with contacts, filters and out-of-office replies - IMAP sync from your old provider - DKIM signing configured for you - Guided DMARC setup - Spam and virus filtering on every mailbox ### Know what your site is doing - Bandwidth usage, per site - Disk usage, per site - Access and error logs you can read yourself - Automatic diagnostics when something looks wrong - Usage against your allowance, always visible ## Where your site lives Choose the data centre your site lives in: Helsinki, Finland (European Union), Singapore, Ashburn, eastern United States, and Hillsboro, western United States. ## Frequently asked questions **Do I get root access?** On a cloud server, yes — it is your machine and you have root over the whole thing. On the Linux platform and on a managed plan you get SSH, Git and cron rather than root, because the server is shared and we keep it patched. If you need to choose the runtime version yourself, the cloud range is the rung to take. **Is the .NET runtime already there?** It depends on the rung. On a managed plan, yes — the account is provisioned with the application on a platform that runs it. On a Linux platform plan the .NET Core installer is one click from your dashboard. On a cloud server, no, and we would rather say so: you get a clean machine with root, from a clean operating system or a ready Docker stack, and you install the runtime or SDK your application targets. Choosing a profile records what the machine is for; it does not install software, and a .NET application is built against a specific version where the wrong choice is worse than none. **Where will it be hosted?** A managed .NET plan runs on our own server fleet, in the data centre you choose — the cities on offer today are listed on this page. A cloud server can be built in eight data centres: Dallas, Los Angeles, Miami and Washington DC in North America; London, Frankfurt and Amsterdam in Europe; and Singapore in Asia. You pick the city when you order. **Can I move up later?** Yes, in every direction. The shared rungs step up as the application grows, and cloud sizes run from one core and 1 GB of memory to forty-eight cores and 128 GB. Moving from a shared plan to a server of your own is a migration we do for you. **Is it managed, or am I on my own?** That is what the three rungs are for. On the Linux platform and on a managed plan we run the server and the platform — updates, caching, SSL, malware scanning and backups are ours. On a cloud server the machine and the network are ours, daily backups are one switch away, and the runtime and the application are yours, which is what a team deploying a compiled application generally wants. **Can I pay yearly?** Yes, on every rung. Every platform plan, every managed plan and every server size is sold monthly or yearly, and each plan shows both prices with any saving worked out for you — so you are never doing the arithmetic yourself. You can start monthly and switch later, and the price you sign up at is the price you renew at. --- # PHP hosting on a server of your own URL: https://zinndigital.com/hosting/php A cloud server of your own — the whole machine, with root, from a clean operating system or a ready Docker or Kubernetes stack. You install PHP and whatever runs on it exactly as you want them; we run the hardware, the network and the provisioning, and back it up every day if you switch backups on. ## Plans and pricing - **Zinn® Cloud Start** — $11.99 a month, or $119.90 a year. vCPU cores: 2, Memory: 4 GB, NVMe storage: 40 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). - **Zinn® Cloud Grow** — $19.99 a month, or $199.90 a year. vCPU cores: 4, Memory: 8 GB, NVMe storage: 80 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). - **Zinn® Cloud Scale** — $34.99 a month, or $349.90 a year. vCPU cores: 8, Memory: 16 GB, NVMe storage: 160 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). - **Zinn® Cloud Business** — $64.99 a month, or $649.90 a year. vCPU cores: 16, Memory: 32 GB, NVMe storage: 320 GB, Bandwidth: 20 TB (Falkenstein, Germany; Helsinki, Finland; Nuremberg, Germany). ## Where your site lives Choose the data centre your site lives in: Helsinki, Finland (European Union), Singapore, Ashburn, eastern United States, and Hillsboro, western United States. ## Frequently asked questions **Do I get root access?** Yes. It is your machine — you have root over the whole thing, so you install what you like, run whatever you prefer, and are never waiting on us to enable something. **What is installed when the server arrives?** A clean managed machine with root, which you configure. We deliberately do not pre-install a particular PHP version or set of extensions, because an application that already exists targets specific ones — and replacing the wrong defaults takes longer than starting from a clean machine. **Where can the server be?** Eight data centres: Dallas, Los Angeles, Miami and Washington DC in North America; London, Frankfurt and Amsterdam in Europe; and Singapore in Asia. You pick the city when you build the server. **Can I resize it later?** Yes. Sizes run from one core and 1 GB of memory up to forty-eight cores and 128 GB, and you move between them as the application grows rather than rebuilding on a bigger box. **Is it managed, or am I on my own?** The machine, the network and the provisioning are ours, and the daily backups too once you switch them on. The stack on top of it is yours. If you would rather not manage a server at all, our shared platform runs PHP for you with the versions and extensions already available — this range is for teams who want root. **Can I pay yearly?** Yes. Every size is sold monthly or yearly, and the yearly price is the cheaper of the two. You can start monthly and switch. ## WordPress plugins included 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. - [Zinn® Cache](https://zinndigital.com/wordpress-plugins/zinn-cache): Preinstalled on every WordPress site we host. Zinn® Cache Pro is an optional paid upgrade, from $49.00 a year, with a 14-day free trial. - [Zinn® Chat](https://zinndigital.com/wordpress-plugins/zinn-chat): Preinstalled on every WordPress site we host. Zinn® Chat Pro is an optional paid upgrade, from $189.00 a year, with a 14-day free trial. - [Zinn® Footprint](https://zinndigital.com/wordpress-plugins/zinn-footprint): Preinstalled on every WordPress site we host. ### Pro plugins: 50% off for hosting customers Every Zinn® hosting customer gets 50% off the first payment of any Zinn® Pro plugin, with a personal code from the dashboard. - Page Builder Sandwich Pro: From $79.00 a year. As a hosting customer, your first payment is $39.50. - Tranzly™ Pro: From $89.00 a year. As a hosting customer, your first payment is $44.50. - Zinn® Backups Pro: From $49.00 a year. As a hosting customer, your first payment is $24.50. - Zinn® Cache Pro: From $49.00 a year. As a hosting customer, your first payment is $24.50. - Zinn® Chat Pro: From $189.00 a year. As a hosting customer, your first payment is $94.50. - Zinn® SEO Pro: From $49.00 a year. As a hosting customer, your first payment is $24.50. One personal code for each Pro plugin, for your first payment only: renewals are at the normal price. A code lasts 30 days, and you can ask for a new one if it runs out unused. You need a paid hosting plan in good standing; free trials do not qualify. [How the hosting-customer discount works](https://zinndigital.com/kb/hosting-customer-pro-plugin-discount) --- # Know the moment a site stops answering URL: https://zinndigital.com/uptime-monitoring We watch any web address you give us — hosted with us or anywhere else — and check from more than one place on the internet that it is still answering. When it stops, you hear about it in minutes, on the channel you already read. Three addresses are free on every account, with no hosting and no plan required. A monitor for any address, not just the ones we host Most uptime monitoring is sold as a feature of something else — a line item on a hosting plan you already pay for, watching only the sites that sit on it. This is not that. You give us a web address and we watch it, whether it runs on our fleet, on a competitor's, on a server in your own office, or on a platform you do not control at all. That matters because the sites you most need to hear about are often the ones you inherited: a client's old shop on somebody else's hosting, a landing page a marketing agency put up, an API your business depends on and nobody owns. You should not have to move a site to us in order to find out when it breaks. Every monitor covers availability and speed together, because a site that answers slowly is on its way to not answering at all. Availability, from more than one place We request the page on a schedule and record whether it answered. A single failed check from a single location is not an outage, so we confirm from another vantage point before we tell you anything. Real page-load speed We measure how long the page actually takes to become useful to a visitor, not just how fast the server returned a byte. You can see a site getting slower over weeks, before customers start complaining. Alerts where you already are Email, Telegram, Slack or your own webhook endpoint. Webhook deliveries are signed with an HMAC over a timestamp and the body, so your endpoint can verify they came from us, and a delivery that fails is recorded on your account. Recovery notices, not just alarms You are told when an address comes back as well as when it goes down. An alert with no all-clear leaves somebody refreshing a browser tab to find out whether the problem is over. History you can point at Hour-by-hour uptime and response times, and every outage with how long it lasted, are kept for as long as you watch the address — so you can answer 'was it down on Tuesday' with a record rather than a memory. Useful when a client asks, and useful when a supplier says it was fine. Readable by your own tools Monitors can be created, listed, paused and removed over our REST API, so your own dashboard or scripts can read their state. Access uses an API key scoped to your organisation, and each key can be revoked. There is nothing to install on the site being watched. It does not need to be a WordPress site, and it does not need to be ours. Add an address Paste in any public URL. No agent, no plugin, no DNS change and no access to the server it runs on. We check it on a schedule Requests go out from outside our hosting network on a fixed cadence, and a failed check is repeated at once with a fresh request, usually from a different location, before it counts. You hear about it Connect the channels each person wants — Telegram on the on-call engineer's phone, a Slack room for the team, a webhook for your own systems. Three addresses are free on every account, forever, with no hosting plan and no card. Beyond that you buy addresses in packs, and the packs stack — if you need thirty, that is three packs, not a bigger tier with things you did not ask for. Three addresses Three monitored addresses on any account, checked on the standard cadence. No plan required and no card. Monitoring is set up from your dashboard — create an account and add your first three addresses free, or talk to us if you are watching enough of them that you would rather we quoted you. Paid addresses are checked more often than free ones, so you hear about a problem sooner. Packs stack, and you can add or remove them whenever you like. Because we are the ones who get woken up. Every technique here — checking from several places before believing a failure, watching load time as an early warning rather than waiting for a hard down, sending the all-clear as well as the alarm — comes from running a fleet of our own and learning which alerts are worth a person's attention at three in the morning. And because the monitoring is not the point. If an address you watch is one of ours, the same signals are already wired to the people who can fix it, and to the diagnostics that run before you have finished writing a support ticket. If it is not one of ours, you still get the alert, and you still get to decide what to do about it. Do I have to host with you to use this? No. You need an account, which is free, and that is all. The three free monitors work with no hosting plan attached, and the paid packs are bought on their own. Plenty of people use this to watch sites that run somewhere else entirely. How quickly will I know that something is down? Within minutes. A failed check is confirmed from a second location before we alert you, which costs a little time and removes almost all the false alarms — an alert you have learned to ignore is worse than no alert. Paid addresses are checked more frequently than free ones, so they detect a problem sooner. What can you actually monitor? Any address that answers a public HTTP request: a website, a landing page, a login screen, an API endpoint, a status page. It does not need to be WordPress, it does not need to be on our infrastructure, and we do not need any access to the server behind it. How do the alerts reach me? Through whichever channels you connect — email, Telegram, Slack, or your own webhook. Preferences are set per organisation and per person, so the on-call engineer's phone and the team's chat room do not have to receive the same things. Webhook deliveries are signed, and a delivery that fails is recorded on your account. SMS and phone calls are not offered. What happens if I need more than the free three? You buy a pack of additional addresses, and packs stack — thirty addresses is simply three packs. There is no upgrade cliff where you have to move to a bigger plan to get a higher number, and no bundle of features you did not want attached to the count you did. Is this the same as your status page? No, and they answer different questions. This tells you about your addresses. Our status page tells you about our platform, and it is deliberately hosted off our own infrastructure in a separate failure domain — a status page running on the thing it reports on is useless at exactly the moment you need it. Start with three addresses, free Create an account, paste in the URLs you would hate to find broken, and choose where the alerts should go. No hosting plan, no card, and nothing to install on the sites you are watching. ## Frequently asked questions **Do I have to host with you to use this?** No. You need an account, which is free, and that is all. The three free monitors work with no hosting plan attached, and the paid packs are bought on their own. Plenty of people use this to watch sites that run somewhere else entirely. **How quickly will I know that something is down?** Within minutes. A failed check is confirmed from a second location before we alert you, which costs a little time and removes almost all the false alarms — an alert you have learned to ignore is worse than no alert. Paid addresses are checked more frequently than free ones, so they detect a problem sooner. **What can you actually monitor?** Any address that answers a public HTTP request: a website, a landing page, a login screen, an API endpoint, a status page. It does not need to be WordPress, it does not need to be on our infrastructure, and we do not need any access to the server behind it. **How do the alerts reach me?** Through whichever channels you connect — email, Telegram, Slack, or your own webhook. Preferences are set per organisation and per person, so the on-call engineer's phone and the team's chat room do not have to receive the same things. Webhook deliveries are signed, and a delivery that fails is recorded on your account. SMS and phone calls are not offered. **What happens if I need more than the free three?** You buy a pack of additional addresses, and packs stack — thirty addresses is simply three packs. There is no upgrade cliff where you have to move to a bigger plan to get a higher number, and no bundle of features you did not want attached to the count you did. **Is this the same as your status page?** No, and they answer different questions. This tells you about your addresses. Our status page tells you about our platform, and it is deliberately hosted off our own infrastructure in a separate failure domain — a status page running on the thing it reports on is useless at exactly the moment you need it. --- # Never lose a domain to a date nobody was watching URL: https://zinndigital.com/domain-monitoring We watch every domain you have with us, every domain pointed at your hosting, and any other domain you add — wherever it is registered. You hear before it expires, when it renews, and the moment its registrar, nameservers or registry status change. It costs nothing. A watchlist that starts already filled in Most domain monitors begin as an empty box and ask you to type in everything you own — which is exactly the domain you forget that costs you. Yours begins full: every domain registered with us is on it, and so is every domain pointed at hosting with us, whoever it is registered with. You add the rest. It is not limited to domains we sell you. A domain sitting at another registrar with a renewal date you have never checked is the one this is for, and watching it here costs you nothing and tells us nothing we would not already learn the day it broke. Six things, each one a question somebody only asks after it has gone wrong. Expiry, five times over At 60, 30, 14, 7 and one day out — once each, so a re-check cannot re-send. Renew it and the whole ladder re-arms for the new date. Renewals confirmed When the expiry date moves forward we say so. It is the one piece of good news in the list, and it is how you know an auto-renew at somebody else's registrar actually fired. Registrar changes If the registrar of record changes, you hear. On a domain you did not move, that is the earliest warning of a transfer you did not authorise. Nameserver changes Compared against what the registry held last time. A delegation that changes without you is either a mistake or somebody else, and both are worth a message. Registry status clientHold, redemptionPeriod, pendingDelete and the rest, as the registry publishes them. These are the states that decide whether a domain is recoverable, and they are invisible in most control panels. Gone If the registry stops answering for a name it used to answer for, we confirm it with a second check before telling you — because a registry blip and a deletion look identical the first time. Three steps, and you have already done the first one. Your domains are added for you Register a domain with us, or point one at your hosting here, and it joins your watchlist the same day. Nothing to switch on. Add anything else Type any domain into the watchlist and we start checking it daily, whoever it is registered with. There is nothing to connect and no credential to hand over. Mute or remove, whenever Silence a domain you already know about without losing its history, or take it off the list entirely. A domain you remove stays removed — nothing puts it back. Nothing, and there is a reason we can say that plainly. Free, on any account Every domain registered with us and every domain attached to your hosting is watched at no charge, with a free allowance for domains registered elsewhere. The registry data behind it is public and costs us nothing to read, so there is no per-check price to pass on. Alerts arrive by email and through whichever channels you already use for account notifications. Any single domain can be muted without leaving the list. Losing a domain is one of the few things on a hosting platform that is genuinely unrecoverable. Past redemption there is no support ticket that fixes it, and the customers it happens to are almost never the ones who were careless — they are the ones whose renewal notice went to an address nobody reads any more. So this watches the domains you did not buy from us too. It would be easy to monitor only our own and call it a feature; it would also be useless on the exact domain most likely to lapse. Does it work for domains registered somewhere else? Yes, and that is the point of it. We read the public registry record, so a domain at Namecheap, GoDaddy, Porkbun, Cloudflare or anywhere else is watched the same way as one of ours. You do not connect an account or give us a password. Do I have to add my own domains? No. Every domain registered with us is added automatically, and so is every domain pointed at hosting with us — even one somebody else registered. You only type in the extras. What happens if I cancel the hosting? A domain that was only on the list because of that hosting comes off it. One you registered with us, or added yourself, stays — your site went away, your domain did not, and its renewal date still matters. Can I turn off the alerts for one domain? Yes. Muting a domain suppresses its alerts and keeps checking it, so the history stays unbroken and un-muting does not bury you in everything that happened meanwhile. If I remove a domain, will it come back? No. A domain you remove stays removed, even if it is registered with us and even if you provision new hosting on it. Putting it back is something only you can do. How often is it checked? Daily, for every domain on every watchlist. Registry records change on the order of days, so a daily read catches everything worth telling you about without hammering registries that publish this data for free. Put your domains on the list Open the watchlist in your dashboard — the domains you already have with us are on it. Add the ones that are not. ## Frequently asked questions **Does it work for domains registered somewhere else?** Yes, and that is the point of it. We read the public registry record, so a domain at Namecheap, GoDaddy, Porkbun, Cloudflare or anywhere else is watched the same way as one of ours. You do not connect an account or give us a password. **Do I have to add my own domains?** No. Every domain registered with us is added automatically, and so is every domain pointed at hosting with us — even one somebody else registered. You only type in the extras. **What happens if I cancel the hosting?** A domain that was only on the list because of that hosting comes off it. One you registered with us, or added yourself, stays — your site went away, your domain did not, and its renewal date still matters. **Can I turn off the alerts for one domain?** Yes. Muting a domain suppresses its alerts and keeps checking it, so the history stays unbroken and un-muting does not bury you in everything that happened meanwhile. **If I remove a domain, will it come back?** No. A domain you remove stays removed, even if it is registered with us and even if you provision new hosting on it. Putting it back is something only you can do. **How often is it checked?** Daily, for every domain on every watchlist. Registry records change on the order of days, so a daily read catches everything worth telling you about without hammering registries that publish this data for free. --- # Aged domains with real history, ready to buy URL: https://zinndigital.com/aged-domains Search our live catalogue of expired and aged domains by Domain Rating, Trust Flow, referring domains, age, language and price. Order the one you want and our team buys it and moves it to you. What an aged domain is, and why people buy one An aged domain is a domain that has been registered before, often for years, and has come back on the market. It keeps the links other sites pointed at it, its age and its history, which is why people building a new site, a brand or a private blog network start from one instead of a fresh name. Our catalogue is refreshed every night from our domain supplier. Each domain carries its metrics (Domain Rating, Domain Authority, Trust Flow, Citation Flow, referring domains and the year it was first seen) so you can judge it before you order, and a domain that has sold leaves the list on the next refresh. Every filter the catalogue has, in the same app you use for your sites. Filter by the metrics that matter Set a minimum and a maximum for DR, DA, Trust Flow, Citation Flow, referring domains, first-seen year and price. Search by name, language and niche Search domain names and descriptions, and narrow the list by extension, language and category. Signals you can check Show only domains that are indexed in Google, have a Wikipedia link or have appeared in Google News. Sort the way you shop Sort by any metric, by price or by age, highest or lowest first. A domain with no measurement sorts last, never first. Daily alerts for new stock Save a search and get one e-mail a day with the new domains that match it, and the ones that became at least 10% cheaper. Order in one click An order opens a ticket with the domain, its price and its metrics. Our team checks it is still available, buys it and moves it to you. Three steps from a search to a domain in your hands. Create a free account Sign up and open Aged domains in the app. The full list, with every domain name, is there. Search and order Filter, sort and pick a domain, then press Order. You can add a note for our team. We buy it and move it to you Our team confirms the order on your ticket, completes the purchase and moves the domain to you. Point it at a site on our hosting, or anywhere else. Every domain has its own price, set by its metrics and history, and shown beside it in the list in US dollars. There is no plan and no subscription: searching the catalogue is free, and you pay only for the domain you order. Prices are before VAT, which is added where it applies. Because the domain and the hosting meet in one place. A domain you buy here can go straight onto a site on our platform, including the Footprint-Free hosting built for networks of sites, without moving between providers. And because the list is kept honest: it is refreshed every night, a sold domain leaves it, and the figures on this page are counted live from the catalogue rather than typed into the copy. What is the difference between an aged and an expired domain? An expired domain is one its previous owner did not renew; an aged domain is one that was first registered a long time ago. Most domains in our catalogue are both: registered years ago, then released, with their backlinks and history intact. Which metrics can I see before I buy? Domain Rating (DR), Domain Authority (DA), Trust Flow (TF), Citation Flow (CF), referring domains, the year it was first seen, its language and categories, and whether it is indexed in Google, linked from Wikipedia or seen in Google News. Why are the domain names hidden on this page? A domain named on a public page can be bought from under you. The full list, with every name, is in the app as soon as you create a free account. What happens after I order? Your order opens a support ticket with the domain, its price and its metrics. Our team checks the domain is still available, completes the purchase, moves it to you and keeps you posted on the ticket. Can I use an aged domain for a private blog network? Yes. Many buyers use aged domains for PBN sites, and our Footprint-Free hosting is built to host a network of them without tying the sites together. How fresh is the list? It is refreshed every night from our supplier's catalogue. A domain that has sold disappears on the next refresh, so what you see is what is on sale. Find your aged domain Create a free account to see every domain name, save searches and order in one click. ## Frequently asked questions **What is the difference between an aged and an expired domain?** An expired domain is one its previous owner did not renew; an aged domain is one that was first registered a long time ago. Most domains in our catalogue are both: registered years ago, then released, with their backlinks and history intact. **Which metrics can I see before I buy?** Domain Rating (DR), Domain Authority (DA), Trust Flow (TF), Citation Flow (CF), referring domains, the year it was first seen, its language and categories, and whether it is indexed in Google, linked from Wikipedia or seen in Google News. **Why are the domain names hidden on this page?** A domain named on a public page can be bought from under you. The full list, with every name, is in the app as soon as you create a free account. **What happens after I order?** Your order opens a support ticket with the domain, its price and its metrics. Our team checks the domain is still available, completes the purchase, moves it to you and keeps you posted on the ticket. **Can I use an aged domain for a private blog network?** Yes. Many buyers use aged domains for PBN sites, and our Footprint-Free hosting is built to host a network of them without tying the sites together. **How fresh is the list?** It is refreshed every night from our supplier's catalogue. A domain that has sold disappears on the next refresh, so what you see is what is on sale. --- # Google Ads management that asks before it spends URL: https://zinndigital.com/ad-management Zinn® Ads audits your ad accounts every day, finds the money being wasted and fixes it — every change approved by you first, held under the spending ceiling you set and undoable for 30 days. Start free, upgrade when the autopilot has earned it. What Zinn® Ads is Zinn® Ads is ad management software for businesses and agencies that run their own pay-per-click accounts. You connect an ad account, and every day it reads what you paid for: the search terms, the keywords, the placements and the clicks that never turned into a customer. It turns that into a short list of changes — block this wasteful search term, pause that keyword, move budget to what sells — and waits for you. Approve one, approve them all, or switch individual kinds of change to automatic once you trust them. Nothing ever spends past the ceiling you set. The features below are the core of every plan; Simple mode and ads written in 58 languages are rolling out now and switch on in your account as they go live. The plan you choose decides how many accounts you connect, how much spend it manages and whether the autopilot can act on its own. Connect many ad accounts Connect as many ad accounts per company as your plan allows, each kept separate, with its own settings, ceilings and history. Agencies manage every client from one login. Approve-first by default Every change starts as a suggestion with the reason and the expected effect written out. Nothing changes in your account until you press approve. Spending ceilings that hold Set a daily and a monthly ceiling per account. Zinn® Ads never makes a change that would take you past them, whatever the autopilot suggests. Undo any change for 30 days Every change is logged with who made it and why, and can be reversed in one click for 30 days. The daily e-mail carries an Undo button beside each one. An autopilot you switch on Turn on automatic changes one kind at a time — wasteful search terms, paused keywords, budget moves — and keep the rest approve-first. A kill switch stops everything at once. Simple mode No ads yet? Give it your website, a budget and the countries you sell to, and it drafts the whole account — campaigns, keywords, ads and negatives — for you to approve on one screen, with a plain-words forecast. Smarter negative keywords Small search terms are grouped by the pattern they share — free, how-to, jobs, another brand, the wrong language — so waste that hides in hundreds of one-click terms is found and blocked as one. A daily e-mail, not another dashboard One message a day: what changed, what needs you, and what it saved. Approve or undo straight from your inbox, in your own language. Never blocks what converts Before any search term or keyword is blocked, Zinn® Ads checks it has never brought you a sale or sign-up, and waits until a term has enough clicks to judge. A click-fraud shield, free with every Zinn® hosting plan Bots, click farms and competitors clicking your ads cost real money. The Zinn® Ads click shield spots invalid clicks and keeps repeat offenders away from your ads. On a site hosted with Zinn® it runs on the server, so there is nothing to install — and it is included free with every hosting plan. Anywhere else it is a small tag or our WordPress plugin, as an add-on. Ads written in 58 languages Zinn® Ads writes responsive search ads from what your own pages actually say — never invented claims — and translates them into any of the 58 languages we support, so a new country is a setting rather than a project. Use your own AI provider key, or Zinn® credits from your account. If an AI provider has an outage, it tells you which one and when to retry. Google Ads first, more networks on the way Google Ads connects today. Microsoft Advertising, Meta, LinkedIn, TikTok, X, Pinterest and Amazon Ads join as each network approves our connection — each one appears in your account the day it does, with one spending ceiling across them all. Smart features rolling out to every account These are being built now and switch on in your account as each one goes live — no upgrade and no extra charge on the plans that include the autopilot. Site-down pause Your ads pause the moment your site or checkout stops answering, and resume when it is back. Out-of-stock pause Ads for WooCommerce products that have sold out pause until they are back in stock. Paid-versus-organic saver Where you already rank at the top for free, it tests whether the paid click is still worth buying. Shared fraud network A click farm caught on one site we host is blocked across every site we host, anonymously. Copy your winners An ad that sells in one account or country is offered to the others, translated. Matching landing pages A landing page per ad group that says what the ad promised, on Zinn® hosting. Ask your ads Ask in plain words why sales fell or what to change, and get an answer from your real data — with a fix you can undo. Refund claims A monthly, pre-filled refund claim for invalid clicks, with the credit tracked. Competitor watch An alert when someone starts bidding on your brand name. Next-country advisor Which country to advertise in next, from search volumes and costs. Quality Score fixer What is holding a Quality Score down, including page speed on Zinn® hosting. Lost-money report How many sales your budget and ad rank left on the table. Site scan for ideas Ideas for keywords, ad extensions and landing pages from your own website. Ad policy pre-check Ads checked against the network's policies before they are submitted. Tracking health check An alert when conversion tracking stops recording. Seasonal planner The busy weeks for your market, per country, before they arrive. Budget pacing Spend kept on pace through the month instead of running out early. Placement guard Display placements that only waste money are excluded for you. From sign-up to the first approved change in a few minutes. Connect your ad account Create a free Zinn® account and connect Google Ads in one click. We read your account; nothing changes yet. Read the first audit Within a day you get a list of what is wasting money and what to change, each with the reason written out. Approve, or let it run Approve the changes you agree with, set your ceilings, and switch on the autopilot for the kinds of change you trust. Start free with one account and every change approved by you. Paid plans add the autopilot, more accounts and more managed spend. Bought in your Zinn® account, cancel any time. Prices are per month in US dollars, shown in your currency where we can; tax is added at checkout where it applies. Annual billing is available on the paid plans. Most ad tools either only report, or change your account without asking. Zinn® Ads does the work and keeps you in charge: every change has a reason, a ceiling it cannot cross and an undo button. It is built by Zinn Digital®, the hosting company — so on Zinn® hosting it can see what an ad tool alone cannot: whether your site was up, how fast the landing page was, and which clicks were bots. What is Zinn® Ads? Zinn® Ads is ad management software that audits your Google Ads accounts every day, finds wasted spend and fixes it with your approval. Every change is held under the spending ceiling you set and can be undone for 30 days. Will Zinn® Ads change my account without asking? No. Every change is approve-first by default. You can switch individual kinds of change to automatic on a paid plan, and a kill switch stops all automatic changes at once. Which ad networks does Zinn® Ads support? Google Ads connects today. Microsoft Advertising, Meta, LinkedIn, TikTok, X, Pinterest and Amazon Ads join as each network approves our connection. Is the click-fraud shield included? It is free with every Zinn® hosting plan, where it runs on the server with nothing to install. For a site hosted elsewhere it is available as an add-on. Can Zinn® Ads write my ads in other languages? Yes. It writes ads from what your own pages say and translates them into any of 58 languages, using your own AI provider key or Zinn® credits. Can an agency manage client accounts? Yes. The Agency plan connects up to 25 client ad accounts, keeps each client separate and adds white label (your own domain and logo), a client approval portal, client reports and priority support. Does Zinn® Ads need my site to be hosted with Zinn®? No. It works with any website. Hosting with Zinn® adds the free click shield and lets Zinn® Ads pause your ads when your site is down. Stop paying for clicks that never buy Connect your first ad account free and read your first audit tomorrow. ## Frequently asked questions **What is Zinn® Ads?** Zinn® Ads is ad management software that audits your Google Ads accounts every day, finds wasted spend and fixes it with your approval. Every change is held under the spending ceiling you set and can be undone for 30 days. **Will Zinn® Ads change my account without asking?** No. Every change is approve-first by default. You can switch individual kinds of change to automatic on a paid plan, and a kill switch stops all automatic changes at once. **Which ad networks does Zinn® Ads support?** Google Ads connects today. Microsoft Advertising, Meta, LinkedIn, TikTok, X, Pinterest and Amazon Ads join as each network approves our connection. **Is there a free plan?** Yes. The Free plan connects one ad account, runs the daily audit, drafts a Simple mode plan and sends a weekly report, and needs no card. Every change on it is approved by you. **Is the click-fraud shield included?** It is free with every Zinn® hosting plan, where it runs on the server with nothing to install. For a site hosted elsewhere it is available as an add-on. **Can Zinn® Ads write my ads in other languages?** Yes. It writes ads from what your own pages say and translates them into any of 58 languages, using your own AI provider key or Zinn® credits. **Can an agency manage client accounts?** Yes. The Agency plan connects up to 25 client ad accounts, keeps each client separate and adds white label (your own domain and logo), a client approval portal, client reports and priority support. **Does Zinn® Ads need my site to be hosted with Zinn®?** No. It works with any website. Hosting with Zinn® adds the free click shield and lets Zinn® Ads pause your ads when your site is down. --- # Original images for your sites, generated on demand URL: https://zinndigital.com/ai-images Stock photography looks like stock photography, and your readers can tell. Generate original images for your websites from a plain description, in the same dashboard you already use to run the site. Buy credits and spend them as you generate, or connect your own provider key and pay your provider directly. What it is Image generation built into the hosting dashboard rather than bolted on beside it. You describe the picture you need, choose a model, and the image is generated and stored against the site it belongs to. There is no separate account to open, no second bill to reconcile and no copying files between tools. It is aimed at the ordinary, constant need of running a content site: a feature image for the post you just published, a header for a landing page, a picture for a product that does not have one. Generating it takes a sentence and a few seconds, and the result is yours rather than a photograph three hundred other sites are also using. Everything below is part of the product, in the dashboard, for every site in your account. A range of models Generate with models from Google, OpenAI and xAI, and switch between them from one generation to the next. Different models suit different jobs, so you are not locked into one house style. Plain-language prompts Describe what you want in a sentence and generate. There is nothing to install and no separate editor to learn. Credits that follow the model Each generated image spends credits from your balance, and the amount depends on the model you picked. Lighter models stretch a pack further; heavier ones cost more per image. Bring your own key Connect your own provider API key instead of buying credits, and pay that provider directly at their rates. Everything else about the product works the same way. Generated for a purpose An image is created against the thing that needs it — a blog post's feature image, for example — rather than dropped into a general pile. The link between the picture and its job is kept. Stored with the site Generated images are stored against the site they were made for, so they are where you expect them the next time you look. Nothing has to be downloaded and re-uploaded to be used. Three steps, all of them inside the dashboard you already sign in to. Choose how you pay Buy a credit pack, or connect your own provider API key and pay your provider directly. You can change your mind later. Describe the image Write what you want in ordinary language and pick the model you want to generate with. The credit cost of that model is shown before you commit to it. Use it on the site The image is generated and stored against the site it was made for, ready to place in the post or page that needed it. Image generation is sold as credit packs. You buy a pack, each generated image spends credits from the balance, and different models spend different amounts — so the model you choose decides how many images a pack produces. Packs come in several sizes, and credits are spent only when you actually generate something. If you would rather pay a provider directly, connect your own API key and skip credits entirely. It is available in your dashboard today — talk to us and we will set you up. Because the credit cost is per model rather than per pack, you can mix a cheaper model for routine images with a heavier one for the pages that matter, out of the same balance. Most image tools sit outside the thing you are actually building. You generate somewhere else, download a file, upload it again, and lose track of which picture belongs to which page. Putting generation next to the site removes that round trip and keeps the image attached to the job it was made for. We also did not want to force a single provider on you. Models move quickly, they are good at different things, and prices change. Offering a range across Google, OpenAI and xAI — and letting you use your own key if you already have an account with one of them — means your imagery does not depend on one vendor's roadmap or one vendor's pricing. How much does an AI image cost? Image generation is sold in credit packs rather than per month. You buy a pack, and each image you generate spends credits from that balance, with the amount depending on which model you used. Current pack sizes and credit costs are shown in the dashboard before you buy or generate. Can I use my own OpenAI or Google API key? Yes. If you already have an account with a provider, connect your own API key and the generations are billed to you by that provider at their rates, not by us in credits. Everything else — the prompt box, the model choice, storing the image against the site — works exactly the same way. Which image models can I generate with? There is a range of models from Google, OpenAI and xAI available in the dashboard, and you can pick a different one for each image. They differ in style, speed and credit cost, so it is worth trying two or three on the same prompt to see which suits your site. The live list and the credit cost of each model are shown at the point you generate. What happens to an image after it is generated? It is stored against the site it was generated for, and linked to the purpose it was created for — a blog post's feature image, for example. That means you can find it again from the site rather than hunting through a downloads folder, and reuse it without regenerating and spending credits twice. What happens when my credits run out? Generation stops until you top up, so there is no surprise overspend. You can buy another pack at any size, or connect your own provider API key and carry on paying that provider directly. Choosing a lighter model also makes a given balance go considerably further. Generate your first image Image generation sits in the same dashboard as your sites. Buy a credit pack or connect your own provider key, describe what you need, and put an original picture on the page that was waiting for one. ## Frequently asked questions **How much does an AI image cost?** Image generation is sold in credit packs rather than per month. You buy a pack, and each image you generate spends credits from that balance, with the amount depending on which model you used. Current pack sizes and credit costs are shown in the dashboard before you buy or generate. **Can I use my own OpenAI or Google API key?** Yes. If you already have an account with a provider, connect your own API key and the generations are billed to you by that provider at their rates, not by us in credits. Everything else — the prompt box, the model choice, storing the image against the site — works exactly the same way. **Which image models can I generate with?** There is a range of models from Google, OpenAI and xAI available in the dashboard, and you can pick a different one for each image. They differ in style, speed and credit cost, so it is worth trying two or three on the same prompt to see which suits your site. The live list and the credit cost of each model are shown at the point you generate. **What happens to an image after it is generated?** It is stored against the site it was generated for, and linked to the purpose it was created for — a blog post's feature image, for example. That means you can find it again from the site rather than hunting through a downloads folder, and reuse it without regenerating and spending credits twice. **What happens when my credits run out?** Generation stops until you top up, so there is no surprise overspend. You can buy another pack at any size, or connect your own provider API key and carry on paying that provider directly. Choosing a lighter model also makes a given balance go considerably further. --- # Connect your own accounts and run them from one dashboard URL: https://zinndigital.com/connect-your-own Some services are yours already, and some can only honestly be yours. Connect your own Gcore, CDN, DNS, SEO data, deploy and AI accounts, and the dashboard drives them for you. Each provider bills you directly; we charge nothing for the connection. What connecting means You bring a key from an account you hold. We test it with the provider before anything is saved, keep it encrypted in our secrets vault, and delete it when you disconnect. Every connection is managed under Integrations in the dashboard. Some of these we could never sell you. Gcore's video streaming, WAAP and AI inference are available only on your own Gcore account, because Gcore's terms do not allow them to be resold — so the contract and the bill stay with Gcore, and Gcore must have the product enabled on your account. Each page explains what the connection does, what the key needs and which guide to follow. Video streaming on your Gcore account See your live streams and stored videos from your own Gcore account, in the dashboard. Web application firewall on your Gcore account List the domains your own Gcore WAAP protects and switch a domain's protection mode. AI inference on your Gcore account See your inference deployments and the GPU flavours available to your own Gcore account. Your own CDN Cloudflare, Bunny CDN, CDN77, KeyCDN, Fastly, Gcore, Amazon CloudFront or Akamai, driven from each site's CDN tab. Your own DNS Nine DNS providers, with zone read, record read and record edit tested before the key is saved. Your own SEO data key Authority metrics from Majestic, Ahrefs, Moz or DataForSEO, fetched on your own key and quota. Deploy to your own host Netlify, Vercel, Render, Azure Static Web Apps or AWS Amplify, built from GitHub, GitLab or Bitbucket. Your own domain registrar Connect the registrar account your domains are registered with. The guide walks through it. Your own AI key Use an AI provider key you hold instead of our credits. The overview guide explains how. The same three rules apply to every connection. Tested before saving A key is checked with the provider before it is stored. A key that cannot do the job is refused, and you are told why. Encrypted in our secrets vault A key that passes is kept encrypted in our secrets vault, never in a database column or a log line. Deleted when you disconnect Disconnecting deletes the stored key. Whatever lives on the provider's side stays exactly where it is. We charge nothing for connecting an account. Each provider bills you directly, on your own account and at its own prices, for what you use there. Your Zinn Digital® hosting plan is billed as normal. Can I buy Gcore streaming, WAAP or inference from you? No. They are available only by connecting your own Gcore account, because Gcore's terms do not allow them to be resold. The account, the contract and the bill are between you and Gcore, and Gcore must have the product enabled on your account. Do you charge for connecting an account? No. The provider bills you directly for what you use on your account with them, and your hosting plan is billed as normal. How are my keys kept? Every key is tested with the provider before it is saved. A key that passes is stored encrypted in our secrets vault, and disconnecting deletes it. Where do I connect an account? Under Integrations in the dashboard. Each connection is tested there before it is saved, and the Gcore services appear under Your own services once connected. What happens when I disconnect? The stored key is deleted. Your account with the provider, and everything in it, is untouched. Connect your first account Create an account, open Integrations and paste in a key. We test it before we save it. ## Frequently asked questions **Can I buy Gcore streaming, WAAP or inference from you?** No. They are available only by connecting your own Gcore account, because Gcore's terms do not allow them to be resold. The account, the contract and the bill are between you and Gcore, and Gcore must have the product enabled on your account. **Do you charge for connecting an account?** No. The provider bills you directly for what you use on your account with them, and your hosting plan is billed as normal. **How are my keys kept?** Every key is tested with the provider before it is saved. A key that passes is stored encrypted in our secrets vault, and disconnecting deletes it. **Where do I connect an account?** Under Integrations in the dashboard. Each connection is tested there before it is saved, and the Gcore services appear under Your own services once connected. **What happens when I disconnect?** The stored key is deleted. Your account with the provider, and everything in it, is untouched. --- # Run your own video streaming by connecting your Gcore account URL: https://zinndigital.com/video-streaming Connect the Gcore account you already hold and see your live streams and stored videos in the dashboard, under Integrations → Your own services. The streaming runs on your Gcore account, under your contract with Gcore, and Gcore bills you for it directly. What it is A connection, not a resale. You bring an API key from your own Gcore account with the streaming product enabled, and the dashboard lists the live streams and stored videos that account holds, under Integrations → Your own services. We do not sell, price or provide Gcore streaming. Gcore's terms do not allow it to be resold, and we would rather say so plainly than wrap it in a markup: the account, the contract and the bill stay between you and Gcore. Your streaming account, visible from the same place you run your sites. Your live streams, listed Every live stream on the connected account appears in the dashboard, so you can see what exists without switching to another control panel. Your stored videos, listed Videos uploaded to the account are listed beside the live streams, on the same screen. Checked before it is saved The key is tested against Gcore before anything is stored. A key that cannot read your streaming account is refused with the reason, rather than saved and failing later. Stored encrypted A key that passes is kept encrypted in our secrets vault, never in a database column or a log line. Disconnect removes the key Disconnecting deletes the stored key. Your streams and videos stay exactly where they are, on your Gcore account. Three steps, and none of them moves your video anywhere. Enable streaming with Gcore Streaming must be switched on for your own Gcore account. If it is not, Gcore has to enable it before the connection can see anything. Connect an API key Create an API key in your Gcore account and paste it into Integrations in the dashboard. We test it before saving it. Open Your own services Your live streams and stored videos appear under Integrations → Your own services. There is no Zinn Digital® price for streaming, because we do not sell it. We charge nothing for the connection. Gcore bills you directly, on your own account and at Gcore's own prices, for the streaming you use. Your Zinn Digital® hosting plan is billed as normal. Streaming prices, limits and availability are set by Gcore. Check them in your Gcore account — we cannot change them and we never add to them. Some services cannot honestly be resold. Gcore's agreement does not permit its streaming to be resold, so the only straight way to offer it is to let you connect the account you hold with them. Your contract, your usage and your streaming invoice all stay with Gcore, where they belong — and you can see your streams without opening another control panel. Do you sell Gcore video streaming? No. Gcore streaming is available here only by connecting your own Gcore account. We do not resell, price or provide it — Gcore's terms do not allow resale — so the account, the contract and the bill are between you and Gcore. Who bills me for streaming? Gcore does, directly, on your own account. We charge nothing for the connection itself, and your Zinn Digital® hosting plan is billed as normal. What if streaming is not enabled on my Gcore account? The connection cannot see streams on an account where the product is switched off. Ask Gcore to enable streaming on your account first, then connect the key. How is my API key kept? It is tested against Gcore before it is saved, and a key that passes is stored encrypted in our secrets vault. Disconnecting the account deletes the stored key. What happens to my videos if I disconnect? Nothing. They live on your Gcore account and stay there. Disconnecting only removes the key we held and the listing in the dashboard. Connect your Gcore account Create an account, open Integrations and paste in a key from your Gcore account. Your streams and videos appear under Your own services. ## Frequently asked questions **Do you sell Gcore video streaming?** No. Gcore streaming is available here only by connecting your own Gcore account. We do not resell, price or provide it — Gcore's terms do not allow resale — so the account, the contract and the bill are between you and Gcore. **Who bills me for streaming?** Gcore does, directly, on your own account. We charge nothing for the connection itself, and your Zinn Digital® hosting plan is billed as normal. **What if streaming is not enabled on my Gcore account?** The connection cannot see streams on an account where the product is switched off. Ask Gcore to enable streaming on your account first, then connect the key. **How is my API key kept?** It is tested against Gcore before it is saved, and a key that passes is stored encrypted in our secrets vault. Disconnecting the account deletes the stored key. **What happens to my videos if I disconnect?** Nothing. They live on your Gcore account and stay there. Disconnecting only removes the key we held and the listing in the dashboard. --- # Protect your sites with your own Gcore WAAP URL: https://zinndigital.com/web-application-firewall Connect your own Gcore account and manage its web application and API protection from the dashboard: see which domains are protected and switch a domain's protection mode without opening another control panel. The protection runs on your Gcore account, and Gcore bills you for it directly. What it is Gcore WAAP is Gcore's web application and API protection. Connect an API key from your own Gcore account with WAAP enabled, and the dashboard lists the domains that account protects, under Integrations → Your own services. We do not sell, price or provide Gcore WAAP. Gcore's terms do not allow it to be resold, so it is available here only on your own account: your contract with Gcore, and your bill from Gcore. The firewall controls you reach for most, next to the sites they protect. Protected domains, listed Every domain the connected WAAP account protects appears in the dashboard with its current protection mode. Switch the protection mode Move a domain between blocking attacks, monitor only and off from the dashboard — useful while testing a release or chasing a false positive. Locked settings stay locked Where Gcore has locked a domain's mode, the dashboard says so and points you to your Gcore control panel instead of pretending to change it. Checked before it is saved The key is tested against Gcore before anything is stored, and a key that cannot read your WAAP account is refused with the reason. Stored encrypted, deleted on disconnect A key that passes is kept encrypted in our secrets vault, and disconnecting deletes it. Your WAAP configuration stays on your Gcore account. Your rules and domains stay in Gcore; the dashboard gives you the switch you use most. Enable WAAP with Gcore WAAP must be enabled for your own Gcore account, with your domains added there. Connect an API key Paste an API key from your Gcore account into Integrations. It is tested before it is saved. Manage protection Open Your own services to see your protected domains and change a domain's protection mode. There is no Zinn Digital® price for WAAP, because we do not sell it. We charge nothing for the connection. Gcore bills you directly, on your own account and at Gcore's own prices, for the protection you use. Your Zinn Digital® hosting plan is billed as normal. WAAP plans, limits and prices are set by Gcore and shown in your Gcore account. We never add to them. A firewall is a contract with whoever runs it. Gcore's agreement does not permit WAAP to be resold, so connecting your own account is the honest way to put it beside your sites. Switching a domain to monitor only during a release, then back to blocking, is the change people make most often. Having that switch in the same dashboard as the site saves a context switch at exactly the moment it matters. Do you sell Gcore WAAP? No. It is available only by connecting your own Gcore account. We do not resell, price or provide it — Gcore's terms do not allow resale. Which protection modes can I choose? Blocking attacks, monitor only or off, per domain. If Gcore has locked a domain's mode, the dashboard shows it as locked and you change it in your Gcore control panel. Who bills me for WAAP? Gcore, directly, on your own account. The connection costs nothing from us, and your hosting plan is billed as normal. Do I need WAAP enabled first? Yes. The connection reads the WAAP product on your Gcore account, so it has to be enabled there, with your domains added, before they appear in the dashboard. How is my API key kept? It is tested against Gcore before it is saved, stored encrypted in our secrets vault, and deleted when you disconnect. Connect your Gcore WAAP account Create an account, open Integrations and paste in a key from your Gcore account, then manage your domains' protection from Your own services. ## Frequently asked questions **Do you sell Gcore WAAP?** No. It is available only by connecting your own Gcore account. We do not resell, price or provide it — Gcore's terms do not allow resale. **Which protection modes can I choose?** Blocking attacks, monitor only or off, per domain. If Gcore has locked a domain's mode, the dashboard shows it as locked and you change it in your Gcore control panel. **Who bills me for WAAP?** Gcore, directly, on your own account. The connection costs nothing from us, and your hosting plan is billed as normal. **Do I need WAAP enabled first?** Yes. The connection reads the WAAP product on your Gcore account, so it has to be enabled there, with your domains added, before they appear in the dashboard. **How is my API key kept?** It is tested against Gcore before it is saved, stored encrypted in our secrets vault, and deleted when you disconnect. --- # Run AI inference on your own Gcore account URL: https://zinndigital.com/ai-inference Connect your own Gcore account and see your inference deployments and the GPU flavours available to that account — A100, H100 and L40S class — from the dashboard. The GPUs run on your Gcore account, and Gcore bills you for them directly. What it is Gcore runs GPU inference for AI models. Connect an API key from your own Gcore account with inference enabled, and the dashboard lists the deployments on that account and the GPU flavours it can use, under Integrations → Your own services. We do not sell, price or provide Gcore inference. Gcore's terms do not allow it to be resold, so the GPUs, the contract and the bill are all on your own Gcore account. Your inference account, readable from the same dashboard as your sites. Your deployments, listed Every inference deployment on the connected account appears in the dashboard, so you can see what is running without another login. The GPU flavours you can use The flavours available to your account are listed — A100, H100 and L40S class, where Gcore offers them to you. What appears depends on your account and region. Prices from Gcore, never from us What a GPU costs is Gcore's price on your account. We do not set it, mark it up or quote a figure of our own. Checked before it is saved The key is tested against Gcore before anything is stored, and a key that cannot read your inference account is refused with the reason. Stored encrypted, deleted on disconnect A key that passes is kept encrypted in our secrets vault, and disconnecting deletes it. Your deployments stay on your Gcore account. Your models run where you put them. The dashboard shows you what is there. Enable inference with Gcore Inference must be enabled for your own Gcore account before a key can see it. Connect an API key Paste an API key from your Gcore account into Integrations. It is tested before it is saved. See deployments and flavours Open Your own services to see your deployments and the GPU flavours available to the account. There is no Zinn Digital® price for GPU inference, because we do not sell it. We charge nothing for the connection. Gcore bills you directly, on your own account and at Gcore's own GPU prices, for the inference you run. Your Zinn Digital® hosting plan is billed as normal. GPU prices and availability are Gcore's and vary by account and region. Read them in your Gcore account — they are Gcore's figures, never ours. GPU capacity is expensive and billed by use, and a reseller's markup on it buys you nothing. Gcore's terms also do not allow resale, so your own account is both the cheaper route and the honest one. Keeping your deployments visible beside your sites means an idle GPU is something you notice in the dashboard you already open, not something you discover on an invoice. Do you sell GPU inference? No. Gcore inference is available here only by connecting your own Gcore account. We do not resell, price or provide it. Which GPUs will I see? The flavours Gcore makes available to your account — A100, H100 and L40S class where offered. The list comes from Gcore for your account, so it can differ between accounts and regions. Where do the prices come from? From Gcore. Any GPU price is Gcore's price on your account. We never set, quote or add to it. Do I need inference enabled first? Yes. The product must be enabled on your Gcore account, or the key has nothing to read. How is my API key kept? It is tested against Gcore before it is saved, stored encrypted in our secrets vault, and deleted when you disconnect. Connect your Gcore inference account Create an account, open Integrations and paste in a key from your Gcore account to see your deployments and GPU flavours under Your own services. ## Frequently asked questions **Do you sell GPU inference?** No. Gcore inference is available here only by connecting your own Gcore account. We do not resell, price or provide it. **Which GPUs will I see?** The flavours Gcore makes available to your account — A100, H100 and L40S class where offered. The list comes from Gcore for your account, so it can differ between accounts and regions. **Where do the prices come from?** From Gcore. Any GPU price is Gcore's price on your account. We never set, quote or add to it. **Do I need inference enabled first?** Yes. The product must be enabled on your Gcore account, or the key has nothing to read. **How is my API key kept?** It is tested against Gcore before it is saved, stored encrypted in our secrets vault, and deleted when you disconnect. --- # Put your sites on your own CDN URL: https://zinndigital.com/own-cdn Already pay for a CDN? Connect your own Cloudflare, Bunny CDN, CDN77, KeyCDN, Fastly, Gcore, Amazon CloudFront or Akamai account, and a site's CDN tab can move the site onto it, purge its cache and change its settings. We test the key's permissions before we save it. What it is A connection to the CDN account you already hold. You create a key with your provider, paste it into Integrations, and we check exactly what it is allowed to do before anything is saved. Once connected, the account is available on a site's CDN tab: move the site onto your CDN, purge its cache and change its settings from the dashboard. The CDN contract and bill stay with your provider. Eight providers, one set of controls. Eight providers Cloudflare, Bunny CDN, CDN77, KeyCDN, Fastly, Gcore, Amazon CloudFront and Akamai, each on your own account. Permissions tested first Before saving, we check what the key can do: read zones, read a zone's detail, purge the cache, change zone settings and manage geo rules. You see each result, so a missing permission is caught when you connect, not in the middle of a change. Move a site onto your CDN A site's CDN tab can put the site behind the account you connected. Purge from the dashboard Clear a site's cache on your CDN without opening your provider's control panel. Change CDN settings Adjust a site's CDN settings from the same tab. Kept encrypted, deleted on disconnect A key that passes is stored encrypted in our secrets vault, and disconnecting deletes it. Connect once, then use it site by site. Create a key with your provider Create an API key or token in your CDN account. Each provider's guide lists the permissions it needs. Connect it in Integrations Paste it in. We test its permissions and show you what passed before saving it. Use it on a site Open a site's CDN tab to move the site onto your CDN, purge its cache or change its settings. Using your own CDN account is not an add-on. We charge nothing for the connection. Your CDN provider bills you directly, on your own account, for the traffic it serves. Your Zinn Digital® hosting plan is billed as normal. Bandwidth, request and feature prices are your provider's, on your account. We never add to them. Many teams already have a CDN contract, negotiated rates or settings they trust. Asking them to give that up to host with us would be the wrong trade, so the dashboard drives the account they already have. Testing permissions before saving is the difference between a connection that works and one that fails the first time you purge in a hurry. A key that cannot do the job is refused while you still have your provider's page open. Which CDNs can I connect? Cloudflare, Bunny CDN, CDN77, KeyCDN, Fastly, Gcore, Amazon CloudFront and Akamai, each on your own account. What permissions does my key need? Enough to read zones and a zone's detail, purge the cache, change zone settings and manage geo rules. We test each of these before saving and show you the result, so you know what the key can and cannot do. Who pays for the CDN traffic? Your CDN provider bills you directly, on your own account. We charge nothing for the connection, and your hosting plan is billed as normal. How is my key stored? Only after it passes the permission test, and then encrypted in our secrets vault. Disconnecting deletes it. What happens if I disconnect? The stored key is deleted, so we can no longer purge or change settings on that account. Your CDN account, and everything configured in it, stays with your provider. Connect your CDN account Create an account, open Integrations and paste in a key from your CDN provider. You will see its permissions tested before it is saved. ## Frequently asked questions **Which CDNs can I connect?** Cloudflare, Bunny CDN, CDN77, KeyCDN, Fastly, Gcore, Amazon CloudFront and Akamai, each on your own account. **What permissions does my key need?** Enough to read zones and a zone's detail, purge the cache, change zone settings and manage geo rules. We test each of these before saving and show you the result, so you know what the key can and cannot do. **Who pays for the CDN traffic?** Your CDN provider bills you directly, on your own account. We charge nothing for the connection, and your hosting plan is billed as normal. **How is my key stored?** Only after it passes the permission test, and then encrypted in our secrets vault. Disconnecting deletes it. **What happens if I disconnect?** The stored key is deleted, so we can no longer purge or change settings on that account. Your CDN account, and everything configured in it, stays with your provider. --- # Serve DNS from your own account URL: https://zinndigital.com/own-dns Keep your zones where they are. Connect your own Cloudflare, deSEC, Hetzner DNS, ClouDNS, Bunny DNS, Azure DNS, Amazon Route 53, DigitalOcean DNS or Gcore account, and the records your sites need are written to it. We test the key before we save it. What it is A connection to the DNS account where your zones already live. Paste a key into Integrations and we test that it can read your zones, read their records and edit a record before anything is saved. Your zones and your provider contract stay exactly where they are. The dashboard works on the account you connected, rather than asking you to move a domain's DNS to us. Nine providers, all tested the same way. Nine providers Cloudflare, deSEC, Hetzner DNS, ClouDNS, Bunny DNS, Azure DNS, Amazon Route 53, DigitalOcean DNS and Gcore. Three permissions, tested Zone read, record read and record edit are each checked before the key is saved, and you see which passed. Your zones stay put Connecting does not move your zones. They stay on your own account with your provider. Stored encrypted A key that passes is kept encrypted in our secrets vault, never in a database column or a log line. Disconnect deletes the key Disconnecting removes the stored key. Your zones and records remain with your provider. Three steps, and your zones never leave your account. Create a key with your provider Create an API token in your DNS account with access to the zones you want to use. Each provider's guide shows how. Connect it in Integrations Paste it in. Zone read, record read and record edit are tested before it is saved. Use it for your sites Once connected, the records your sites need are written to your own zones on that account. Using your own DNS account is not an add-on. We charge nothing for the connection. Your DNS provider bills you directly, on your own account, if it charges at all. Your Zinn Digital® hosting plan is billed as normal. Query, zone and feature prices are your provider's, on your account. We never add to them. DNS is what every visit to a domain depends on, and plenty of teams have good reasons to keep it with a provider they chose. Driving that account from the dashboard means you do not have to move it to host with us. Record edit is tested before saving because DNS failures are quiet: a key that can read but not write looks fine until the first change silently does not happen. Which DNS providers can I connect? Cloudflare, deSEC, Hetzner DNS, ClouDNS, Bunny DNS, Azure DNS, Amazon Route 53, DigitalOcean DNS and Gcore, each on your own account. What permissions does the key need? Zone read, record read and record edit. We test all three before saving and show you the result. Do my zones move to you? No. The key works on the zones already in your account, and they stay with your provider. Who bills me for DNS? Your DNS provider, directly, if it charges. The connection costs nothing from us, and your hosting plan is billed as normal. How is my key stored? Only after it passes the tests, and then encrypted in our secrets vault. Disconnecting deletes it. Connect your DNS account Create an account, open Integrations and paste in a token from your DNS provider. Zone read, record read and record edit are tested before it is saved. ## Frequently asked questions **Which DNS providers can I connect?** Cloudflare, deSEC, Hetzner DNS, ClouDNS, Bunny DNS, Azure DNS, Amazon Route 53, DigitalOcean DNS and Gcore, each on your own account. **What permissions does the key need?** Zone read, record read and record edit. We test all three before saving and show you the result. **Do my zones move to you?** No. The key works on the zones already in your account, and they stay with your provider. **Who bills me for DNS?** Your DNS provider, directly, if it charges. The connection costs nothing from us, and your hosting plan is billed as normal. **How is my key stored?** Only after it passes the tests, and then encrypted in our secrets vault. Disconnecting deletes it. --- # Use your own SEO data key URL: https://zinndigital.com/own-seo-data-keys Connect your own Majestic, Ahrefs, Moz or DataForSEO key, and the authority metrics for your domains are fetched on your key and your quota rather than ours. We check the key before we save it. What it is If you already subscribe to an SEO data provider, you can put that subscription to work here. Connect its API key in Integrations and the authority metrics for your domains are fetched with it. The requests run against your account with the provider, so they count against your plan's quota and the provider bills you under your own agreement. Your subscription, used where you already work. Four providers Majestic, Ahrefs, Moz and DataForSEO. Your key, your quota Metrics are fetched with the key you connected, so they draw on your own plan with the provider. Checked before it is saved The key is tested with the provider before anything is stored, and a key the provider refuses is not saved. Stored encrypted, deleted on disconnect A key that passes is kept encrypted in our secrets vault, and disconnecting deletes it. Three steps from the key you already have. Copy your API key Copy the API key from your Majestic, Ahrefs, Moz or DataForSEO account. Connect it in Integrations Paste it in. It is tested with the provider before it is saved. Fetch metrics on your key Authority metrics for your domains are then fetched on your own key and quota. Using your own SEO data key is not an add-on. We charge nothing for the connection. Your SEO data provider bills you directly, under your own plan, for the requests made with your key. Your Zinn Digital® hosting plan is billed as normal. Each request counts against your quota with the provider, at the provider's prices. We never add to them. An SEO data subscription is often one of a team's larger tool bills, and paying twice for the same metrics makes no sense. Using the key you already hold means the dashboard draws on data you have already paid for. It also means the numbers come from the provider you trust, within the limits of the plan you chose. Which providers are supported? Majestic, Ahrefs, Moz and DataForSEO. Whose quota do the requests use? Yours. Metrics are fetched with the key you connected, so every request counts against your own plan with that provider. Do you charge for this? No. The connection costs nothing from us. Your provider bills you under your own agreement, and your hosting plan is billed as normal. How is my key stored? It is tested with the provider before saving, stored encrypted in our secrets vault, and deleted when you disconnect. Which metrics are fetched? Domain authority metrics from the provider you connected — the figures that provider publishes for a domain, under its own names and scales. Connect your SEO data key Create an account, open Integrations and paste in your key to fetch authority metrics on your own quota. ## Frequently asked questions **Which providers are supported?** Majestic, Ahrefs, Moz and DataForSEO. **Whose quota do the requests use?** Yours. Metrics are fetched with the key you connected, so every request counts against your own plan with that provider. **Do you charge for this?** No. The connection costs nothing from us. Your provider bills you under your own agreement, and your hosting plan is billed as normal. **How is my key stored?** It is tested with the provider before saving, stored encrypted in our secrets vault, and deleted when you disconnect. **Which metrics are fetched?** Domain authority metrics from the provider you connected — the figures that provider publishes for a domain, under its own names and scales. --- # Deploy to your own Netlify, Vercel, Render, Azure Static Web Apps or AWS Amplify URL: https://zinndigital.com/deploy-to-your-own-host Connect your GitHub, GitLab or Bitbucket account and your own hosting account, and publish to Netlify, Vercel, Render, Azure Static Web Apps or AWS Amplify from the dashboard. The hosting account and its bill are yours. What it is A connection to the static and front-end hosts you already use. Connect the repository provider your code lives in — GitHub, GitLab or Bitbucket — and the host account you want to publish to. Some of these hosts are available only on your own account, and we say why. Vercel's Hobby plan is for non-commercial, personal use, so connect a paid Vercel team for a commercial site. AWS Amplify bills per gigabyte and per build minute, so it runs only on your own AWS account. Five hosts and three repository providers. Five hosts Netlify, Vercel, Render, Azure Static Web Apps and AWS Amplify, each on your own account. From your repository Connect GitHub, GitLab or Bitbucket so the host builds from the repository your code already lives in. Vercel, the commercial way Vercel's Hobby plan is restricted to non-commercial, personal use. For a commercial site, connect a paid Vercel team. AWS Amplify on your own account Amplify bills per gigabyte and per build minute, so it is offered only on your own AWS account, where those charges are yours to see and control. Checked before it is saved Each credential is validated with the provider before anything is stored. Stored encrypted, deleted on disconnect A credential that passes is kept encrypted in our secrets vault, and disconnecting deletes it. Connect the two accounts, then publish. Connect your repository provider Connect your GitHub, GitLab or Bitbucket account. Connect your host Connect your Netlify, Vercel, Render, Azure Static Web Apps or AWS Amplify account. It is validated before it is saved. Deploy Publish your site to the host you connected, on your own account. Deploying to your own host is not an add-on. We charge nothing for the connection. Your host bills you directly, on your own account and plan, for what it builds and serves. Your Zinn Digital® hosting plan is billed as normal. Build minutes, bandwidth and plan limits are your host's. Check its terms for commercial use — Vercel's Hobby plan does not allow it. Front-end teams often have a host they already know. Deploying to it from the same dashboard as the rest of your estate means you keep that host and still manage everything in one place. We name the terms that bite, because a site taken down for breaching a free plan's terms costs more than a paragraph of small print now. That is why Vercel needs a paid team for commercial work and Amplify runs only on your own AWS account. Which hosts can I deploy to? Netlify, Vercel, Render, Azure Static Web Apps and AWS Amplify, each on your own account. Which repository providers work? GitHub, GitLab and Bitbucket. Can I use Vercel's Hobby plan? Only for a non-commercial, personal site. Vercel's Hobby plan is restricted to non-commercial, personal use, so connect a paid Vercel team for anything commercial. Why is AWS Amplify only on my own account? Amplify bills per gigabyte and per build minute. Those charges belong on the account of whoever runs the site, so Amplify is offered only on your own AWS account. Who bills me for hosting on these platforms? The platform does, directly, on your own account. We charge nothing for the connection, and your Zinn Digital® hosting plan is billed as normal. How are my credentials stored? They are validated with the provider before saving, stored encrypted in our secrets vault, and deleted when you disconnect. Connect your repository and host Create an account, open Integrations, connect GitHub, GitLab or Bitbucket and the host you publish to, and deploy from the dashboard. ## Frequently asked questions **Which hosts can I deploy to?** Netlify, Vercel, Render, Azure Static Web Apps and AWS Amplify, each on your own account. **Which repository providers work?** GitHub, GitLab and Bitbucket. **Can I use Vercel's Hobby plan?** Only for a non-commercial, personal site. Vercel's Hobby plan is restricted to non-commercial, personal use, so connect a paid Vercel team for anything commercial. **Why is AWS Amplify only on my own account?** Amplify bills per gigabyte and per build minute. Those charges belong on the account of whoever runs the site, so Amplify is offered only on your own AWS account. **Who bills me for hosting on these platforms?** The platform does, directly, on your own account. We charge nothing for the connection, and your Zinn Digital® hosting plan is billed as normal. **How are my credentials stored?** They are validated with the provider before saving, stored encrypted in our secrets vault, and deleted when you disconnect. --- # An AI chat agent that answers your visitors from your own website URL: https://zinndigital.com/ai-chat-agent Put an assistant on your site that answers questions from your own pages, in your visitor's language, and links to the page each answer came from. When your pages do not say, it says so and hands the conversation to you instead of guessing. What it is A chat assistant that lives on your own website and knows only what your website says. You add it to a site, it reads that site's pages, and from then on a visitor can ask a question in the chat window and get a short answer drawn from those pages, with a link to the page it used. It is built for the questions a site gets asked every day — opening hours, delivery, what a service includes, how to get in touch — so a visitor gets an answer at the moment they want one rather than an email address and a wait. It never invents a price, a policy or a phone number; if your pages do not contain the answer, it tells the visitor and offers to pass them to you. Everything below is included with the chat agent on the site you add it to. Answers from your own pages Every answer is drawn from the pages it has read, and nothing else. It does not use general knowledge about your business, so it cannot contradict what your site says. A link to the source Each answer links to the page it came from, so a visitor can read the full detail and you can see exactly why it said what it said. Every page, not just the linked ones On a site we host it reads the site directly, including every page listed in the site's sitemap, so pages that nothing links to are still known. On any other site it reads the pages it can reach by following links. Your visitors' languages It replies in the language the visitor writes in, even when your pages are written in only one. Your name and your colours Choose what it calls itself, the first thing it says, how it should answer and the colour of the chat button, so it looks like part of your site rather than somebody else's product. Fast pages stay fast The snippet loads a small button and nothing else until a visitor clicks it, so it does not slow your pages down or hurt your Core Web Vitals. Three steps, all of them in the dashboard you already use for your sites. Add it to a site Choose the site in your dashboard and add the chat agent. On a site we host it starts reading that site's pages straight away. Try it and make it yours Ask it questions from the dashboard to see exactly what a visitor would get, then set its name, greeting, tone and colour. Put it on the page Paste one line of code before the closing body tag, or let us place it on a site we host. It only appears on the web addresses you allow. The chat agent is a monthly add-on for one site, and it includes a monthly allowance of answered messages. It runs on Zinn® AI credit, or on your own AI provider key if you connect one, in which case the model usage is billed to you by that provider. It is available in your dashboard today — talk to us and we will set you up. The allowance counts answered messages, including the ones you ask yourself while trying it. When it is reached the agent stops answering until the next month rather than running up a bill. Most website chatbots are separate services that crawl your site from the outside, miss the pages nothing links to, and answer with confidence whether or not they know. Because we host the site, the agent reads it the way we serve it, and because it is only allowed to answer from what it read, an honest "I could not find that" beats a confident wrong answer. It is also built to stay out of the way. A chat widget is one of the most common reasons a page gets slower, so this one loads nothing but a button until somebody actually wants to talk, and it only answers on the web addresses you list, so nobody can put your agent on their site at your expense. What does the AI chat agent answer from? Only from the pages of your website that it has read, plus any notes you add yourself. It does not use general knowledge about your business or the internet, and every answer links to the page it used. If the answer is not in those pages, it says so and offers to pass the visitor to you. Will it slow my website down? No. The code you add loads a small chat button and nothing else until a visitor clicks it, so it does not add weight to your pages or affect how quickly they load. Which languages does it answer in? It replies in the language the visitor writes in. Your pages can be written in one language and a visitor can still ask, and be answered, in theirs. Can I use my own AI provider key? Yes. Connect your own key in the dashboard and the agent's model usage is billed to you by that provider. If your key stops working, the dashboard tells you which provider refused it and where to fix it, while your visitors simply see that the chat cannot answer right now. Does it work on a website you do not host? Yes. On a site hosted elsewhere it reads the pages it can reach by following links from the address you give it. On a site we host it reads the site directly, including pages that nothing links to. What happens when it cannot answer? It tells the visitor it could not find the answer on your site and, if you have handover switched on, offers to pass them to a person. It is designed never to guess at a price, an opening time or a policy. Put an AI chat agent on your site Add it to a site from your dashboard, try it with your own questions, and put it on the page when you are happy with what it says. ## Frequently asked questions **What does the AI chat agent answer from?** Only from the pages of your website that it has read, plus any notes you add yourself. It does not use general knowledge about your business or the internet, and every answer links to the page it used. If the answer is not in those pages, it says so and offers to pass the visitor to you. **Will it slow my website down?** No. The code you add loads a small chat button and nothing else until a visitor clicks it, so it does not add weight to your pages or affect how quickly they load. **Which languages does it answer in?** It replies in the language the visitor writes in. Your pages can be written in one language and a visitor can still ask, and be answered, in theirs. **Can I use my own AI provider key?** Yes. Connect your own key in the dashboard and the agent's model usage is billed to you by that provider. If your key stops working, the dashboard tells you which provider refused it and where to fix it, while your visitors simply see that the chat cannot answer right now. **Does it work on a website you do not host?** Yes. On a site hosted elsewhere it reads the pages it can reach by following links from the address you give it. On a site we host it reads the site directly, including pages that nothing links to. **What happens when it cannot answer?** It tells the visitor it could not find the answer on your site and, if you have handover switched on, offers to pass them to a person. It is designed never to guess at a price, an opening time or a policy. --- # S3-compatible storage, without the bill for reading your own data URL: https://zinndigital.com/object-storage Create S3-compatible buckets from your dashboard or the API and point your existing tools straight at them. Storage is backed by Cloudflare R2, so getting data back out does not carry an egress charge the way it does on AWS S3. An allowance comes with your hosting plan, and you are metered only above it. What it is Object storage for the files a website accumulates: images and video, downloads, user uploads, exports and backups. Buckets are created and managed from the dashboard or through the API, and they speak the S3 protocol, so the SDKs, CLIs and plugins you already use will talk to them without being rewritten. It is backed by Cloudflare R2. The practical consequence is egress: with most object storage, serving a popular file is a charge that grows with your traffic, which quietly discourages you from actually using the storage you pay for. Here, reading your data back out does not carry that fee. Storage that behaves like the S3 you already know, managed from the same place as your sites. S3-compatible Buckets speak the S3 API, so existing SDKs, backup tools, CLIs and WordPress offload plugins work against them. There is no proprietary client to adopt. Full bucket control Create a bucket, list your buckets, inspect one and delete it — from the dashboard or programmatically through the API. Provisioning storage does not require a support ticket. No egress fees Backed by Cloudflare R2, so reading data back out is not charged by the gigabyte. Serving a file that becomes popular does not turn into a bill that grows with its popularity. Media offload Move images, video and downloads off the web server and serve them from storage instead. The origin gets smaller and faster, and deployments stop dragging a media library around with them. Backups and archives A natural destination for database dumps, site archives and anything you need to keep but not serve. It is durable, off the web server, and reachable by any S3-aware tool. User uploads and static files Take uploads from your visitors straight into a bucket instead of onto the application server, and serve static assets through the CDN in front of it. From nothing to a working bucket in three steps. Create a bucket Make one from the dashboard, or call the API if you would rather have it created as part of your provisioning scripts. Point your tooling at it Configure your existing S3-compatible client, offload plugin or backup tool with the bucket details. Nothing about your application code has to change to accommodate a new protocol. Store and serve Write your files and read them back as often as you like, with static assets served through the CDN. Usage counts against your plan's allowance and is metered above it. Object storage is not a separate subscription. Every hosting plan includes a storage allowance, and you are metered only for what you use above it — so most sites never see a storage line at all. That means there is nothing extra to sign up for, and nothing to cancel if your usage drops back down. Storage comes with your hosting plan — see the plans page, or talk to us and we will set you up. There is no egress fee on top, so the amount you serve does not change what you pay. Only the amount you keep does. Storage is only useful when you are willing to use it. Charging per gigabyte read is what makes teams hesitate before serving media from object storage, keep large files on the web server where they do not belong, or leave a CDN misconfigured because a cache miss costs money. Removing egress charges removes that hesitation. We priced it as an allowance inside the plan rather than an add-on for the same reason. A separate storage subscription is one more decision, one more invoice and one more thing to forget to cancel, for a capability that nearly every site needs some of. Including it means storage is simply there when you reach for it. Will my existing S3 tools work with it? Yes — the buckets are S3-compatible, so the AWS SDKs, S3-aware CLIs, backup tools and WordPress media-offload plugins you already use will talk to them. In most cases you are changing an endpoint and a set of credentials in a config file, not rewriting application code. If a tool can speak to S3, it can speak to this. Are there egress fees for reading my data? No. The storage is backed by Cloudflare R2, whose defining property is that reading data back out is not billed by the gigabyte. This is the main practical difference from AWS S3, where serving a popular file produces a bill that scales with its traffic — and it is why offloading media here does not become more expensive as a site succeeds. How is object storage billed? It is included in your hosting plan as an allowance rather than sold as a standalone subscription, and you are metered only on the storage you use above that allowance. There is no separate signup and no minimum commitment. Your plan's allowance is shown on the plans page. What do people actually use it for? The four common jobs are offloading a site's images and video off the web server, holding backups and archives, receiving uploads from visitors, and serving static files through the CDN. All four keep large files off the application server, which makes deployments smaller and the origin faster. You can use one bucket for all of it or separate buckets per job. Where is my data actually stored? On Cloudflare R2, which sits behind the S3-compatible interface you connect to. You manage buckets through our dashboard and API, and your tools talk S3, so the underlying platform is not something you have to work with directly. Create your first bucket Your plan already includes a storage allowance. Create a bucket from the dashboard, point your existing S3 tooling at it, and get the media off your web server this afternoon. ## Frequently asked questions **Will my existing S3 tools work with it?** Yes — the buckets are S3-compatible, so the AWS SDKs, S3-aware CLIs, backup tools and WordPress media-offload plugins you already use will talk to them. In most cases you are changing an endpoint and a set of credentials in a config file, not rewriting application code. If a tool can speak to S3, it can speak to this. **Are there egress fees for reading my data?** No. The storage is backed by Cloudflare R2, whose defining property is that reading data back out is not billed by the gigabyte. This is the main practical difference from AWS S3, where serving a popular file produces a bill that scales with its traffic — and it is why offloading media here does not become more expensive as a site succeeds. **How is object storage billed?** It is included in your hosting plan as an allowance rather than sold as a standalone subscription, and you are metered only on the storage you use above that allowance. There is no separate signup and no minimum commitment. Your plan's allowance is shown on the plans page. **What do people actually use it for?** The four common jobs are offloading a site's images and video off the web server, holding backups and archives, receiving uploads from visitors, and serving static files through the CDN. All four keep large files off the application server, which makes deployments smaller and the origin faster. You can use one bucket for all of it or separate buckets per job. **Where is my data actually stored?** On Cloudflare R2, which sits behind the S3-compatible interface you connect to. You manage buckets through our dashboard and API, and your tools talk S3, so the underlying platform is not something you have to work with directly. --- # Your website in 58 languages URL: https://zinndigital.com/website-translation We translate your pages, posts, metadata and URL slugs into 58 languages and serve each one on its own indexable URL with correct hreflang. Every language is included in every tier — the words are bought up front, so there is no per-language charge to add later. You decide which languages your visitors are shown, and your site picks up a language you switch on within the hour. What it is Website Translation is a pipeline rather than a one-off job. It reads your site, translates your page copy and post bodies, and the free Zinn® Translate plugin on your WordPress site publishes each language as a real, crawlable version of your site. It is an SEO product as much as a translation product. Each language lives at its own URL and carries hreflang annotations pointing back to every sibling version, including x-default, so a search engine can index your Spanish or Japanese pages exactly as readily as your English ones. One pipeline, wired into the content lifecycle, covering the parts of a site that translation tools usually leave in English. All 58 languages, in every tier Tiers are sized by how much content you have, never by how many languages you want. The full set of 58 is translated on every tier. Translated, then served on your terms Translating and serving are two separate things: everything is translated, and you choose which languages visitors actually see. Turning one on needs no new order and no re-run, and your site picks it up within the hour. Translated URL slugs Each locale gets its own readable, keyword-carrying path rather than an English slug behind a language code — and the old address keeps working: we hold the last five slugs per page and 301 the untranslated path to the localised one. Metadata, not just body copy Meta titles and descriptions, OpenGraph and Twitter cards, JSON-LD name, headline and description, image alt text, breadcrumb labels, category names and your site title and tagline. It works through Yoast, Rank Math, All in One SEO and SEOPress by their own filters rather than fighting them for the canonical. Incremental re-translation Edit a page and only the strings that actually changed are re-translated, automatically. Everything else is served from a content-hash cache, so a typo fix does not re-run your whole site. hreflang, done properly On your pages and posts, every published language is annotated with hreflang links to each of its siblings and an x-default, and the page declares its own lang, so search engines can discover and attribute each version correctly instead of reading them as duplicates. Archives and category pages are being added and are not covered yet. Three steps. Two are ours, and one is a free plugin you install on your site — without it the translations exist and no visitor ever sees them. Connect your site We read your content over the WordPress API and count the words, which is what determines your tier. Nothing on your live site changes at this stage. Translate everything The pipeline translates your pages and posts into all 58 languages, including metadata and slugs, and caches each result against a hash of its source text — so editing a page without changing a word costs nothing. Install the plugin, choose your languages Install the free Zinn® Translate plugin on your WordPress site, paste the site ID and an API key from your dashboard, then switch on the languages you want on the site's Translation tab. Each one goes live on its own URL with hreflang already in place. One subscription per site, tiered by word count — a small site, a content-heavy site, and a large shop or enterprise site. Every tier includes all 58 languages, so the only question is how much content you have, not how far you want to reach. Add Website Translation to a site from your dashboard, or talk to us and we will size the tier with you. Tiers are sized by the number of translatable words on the site. There is no per-language charge and no charge for switching a language on. Most translation products bill per language, which quietly turns reaching a new market into a purchasing decision. We translate the whole set up front and let you publish on judgement rather than on budget — try a market, watch the traffic, keep it or hide it again. Translation is only half of it. A translated page ranks because it has its own URL and its own slug, metadata a search engine can read in the reader's language, an hreflang graph that ties the versions together, a per-language sitemap, and a source that stays in step as you edit — and because the words are rendered by your own site rather than injected by a script a crawler may never run. Do I pay per language? No. Every tier includes all 58 languages, and pricing is set by the amount of content on the site instead. Switching a language on or off costs nothing and changes nothing about your subscription. What is the difference between a language being translated and being served? Translated means the words exist, stored and cached against your content. Served means visitors and search engines can reach that version at its own URL. Everything is translated; you decide what is served, and a language you have not published is simply not visible. Will search engines index the translated pages? That is the design. Each published language is server-rendered by your own WordPress site at its own URL and annotated with hreflang tags linking it to every sibling version, and each language gets its own sitemap at /zinn-sitemap-.xml, indexed from /zinn-sitemap-index.xml and announced in robots.txt. Crawlers see distinct, indexable pages rather than one page with a client-side language switcher. What happens when I edit a page after it has been translated? The changed strings are marked stale and re-translated automatically; untouched strings are served from cache. A small edit costs a small amount of work, so your translations do not drift behind your source content while you wait for a manual re-run. Which parts of my site are translated? Your page copy, post bodies and excerpts, your meta titles and descriptions, OpenGraph and Twitter cards, JSON-LD, image alt text, breadcrumb labels, category names, menu items and your URL slugs — served at a locale-prefixed URL with hreflang and the right lang attribute, with the old address 301ing to the new one. How do I know which tier I need? Tiers are set by translatable word count across the site: a brochure site, a content-heavy publisher, and a large shop or enterprise estate. We count your words when you connect the site, so you can see which tier applies before you commit. Publish in every market you want Connect a site, see its word count and tier, install the free plugin and publish your first additional language the same day. The other 57 are already translated and waiting behind a switch. ## Frequently asked questions **Do I pay per language?** No. Every tier includes all 58 languages, and pricing is set by the amount of content on the site instead. Switching a language on or off costs nothing and changes nothing about your subscription. **What is the difference between a language being translated and being served?** Translated means the words exist, stored and cached against your content. Served means visitors and search engines can reach that version at its own URL. Everything is translated; you decide what is served, and a language you have not published is simply not visible. **Will search engines index the translated pages?** That is the design. Each published language is server-rendered by your own WordPress site at its own URL and annotated with hreflang tags linking it to every sibling version, and each language gets its own sitemap at /zinn-sitemap-.xml, indexed from /zinn-sitemap-index.xml and announced in robots.txt. Crawlers see distinct, indexable pages rather than one page with a client-side language switcher. **What happens when I edit a page after it has been translated?** The changed strings are marked stale and re-translated automatically; untouched strings are served from cache. A small edit costs a small amount of work, so your translations do not drift behind your source content while you wait for a manual re-run. **Which parts of my site are translated?** Your page copy, post bodies and excerpts, your meta titles and descriptions, OpenGraph and Twitter cards, JSON-LD, image alt text, breadcrumb labels, category names, menu items and your URL slugs — served at a locale-prefixed URL with hreflang and the right lang attribute, with the old address 301ing to the new one. **How do I know which tier I need?** Tiers are set by translatable word count across the site: a brochure site, a content-heavy publisher, and a large shop or enterprise estate. We count your words when you connect the site, so you can see which tier applies before you commit. --- # Managed PostgreSQL and MySQL, with or without a site URL: https://zinndigital.com/managed-databases Standalone managed databases: you do not need to host a website with us to run a database with us. PostgreSQL or MySQL, three tiers by size on each, with automatic failover from the medium tier upward. We verify restores by connecting to the restored database rather than trusting that a backup job finished. What it is Zinn® Managed Databases is PostgreSQL or MySQL that we run for you, sold on its own. Nothing about it assumes you also host a site here: point an application at it from wherever that application lives, and treat it as a database service rather than an add-on to a hosting plan. There are three sizes on each engine. The small tier is a single instance. The medium and large tiers add automatic failover, so a lost node is a failover event rather than an outage you find out about from your users. What failover costs differs by engine — PostgreSQL arbitrates between two instances, while MySQL needs a three-member group and a pair of routers to reach a quorum — which is why the MySQL tiers are priced a little higher at every size. Managed PostgreSQL and MySQL with the operational parts done properly, and stated plainly enough that you can plan around them. Standalone, no site required Buy a database without buying hosting. Your application can run anywhere; the database is a product in its own right. Automatic failover from the medium tier Medium and large run with automatic failover. The step up from small is a change in availability, not only a change in size. A single-instance small tier The small tier runs one instance, which suits development, staging and lighter production workloads where a short recovery window is acceptable. Point-in-time recovery on PostgreSQL On PostgreSQL, recovery is to a moment rather than to last night's snapshot, which is what lets you undo a bad migration or a mistaken delete without losing the day around it. MySQL databases are backed up nightly and kept for fourteen nights. Restores verified by connecting A backup job reporting success is not evidence that a database can be restored. We verify restores by connecting to the restored database and reading from it. Three sizes on either engine Every tier runs the engine you chose. Moving up changes the vCPU, memory and disk allocation and, from medium, adds automatic failover. Provision it, connect to it, and let us carry the operational half. Pick a tier Choose PostgreSQL or MySQL, then small, medium or large by how much CPU, memory and disk you need and whether you want automatic failover. Connect your application You get credentials and a connection endpoint. The application can sit on our estate or on somebody else's; the database does not care. We run and prove it We back up on a schedule and check that the backups restore by connecting to the result, so recoverability is measured rather than assumed. On PostgreSQL that schedule is continuous, so recovery is to a point in time. Three tiers on each engine, billed monthly, sized by vCPU, memory and disk — with automatic failover included from the medium tier. Tier prices are computed from measured infrastructure unit rates and re-derived when those rates move. Provision a managed database from your dashboard, or talk to us and we will pick the tier with you. Prices track measured infrastructure rates rather than being set once and left, so the tier you are on stays proportionate to what it actually costs to run. Plenty of hosts will run a database for you, provided you also buy the hosting. This one is sold on its own, which means you can put your database with us and your application wherever it makes sense, without restructuring your stack to fit a bundle. The two claims that matter most in a database product are the ones easiest to make loosely: that it fails over, and that it restores. Here, failover is a stated property of the medium and large tiers, and restores are verified by connecting to the restored database rather than by reading a green job log. Do I need to host a website with you to use this? No. Managed Databases is standalone. Your application can run on your own servers, on another provider, or on our estate — the database is provisioned and billed independently. Which tiers have high availability? Medium and large run with automatic failover. Small is a single instance, which is why the step from small to medium is an availability decision rather than only a capacity one. How do backups and restores work? Both engines are backed up and both are restore-tested by connecting to the result. They differ in how far back you can aim: PostgreSQL archives continuously, so you can recover to a moment — which matters most after a bad migration or an accidental delete, where you want everything up to the second before the mistake. MySQL is backed up nightly, with the last fourteen nights kept. How do you know the backups actually restore? We restore them and connect to the result. A backup job reporting success only tells you a job finished; connecting to the restored database and reading from it tells you the data is there and usable. That is the check we run. Can I move up a tier as the database grows? Yes. The tiers run the same engine you started on, so moving up changes the vCPU, memory and disk allocation and, from medium, adds automatic failover. Talk to us before a large migration and we will plan the move with you. Put your database somewhere it is looked after Pick an engine and a tier, connect your application, and get automatic failover from the medium tier upward — whether or not anything else of yours is hosted here. ## Frequently asked questions **Do I need to host a website with you to use this?** No. Managed Databases is standalone. Your application can run on your own servers, on another provider, or on our estate — the database is provisioned and billed independently. **Which tiers have high availability?** Medium and large run with automatic failover. Small is a single instance, which is why the step from small to medium is an availability decision rather than only a capacity one. **How do backups and restores work?** Both engines are backed up and both are restore-tested by connecting to the result. They differ in how far back you can aim: PostgreSQL archives continuously, so you can recover to a moment — which matters most after a bad migration or an accidental delete, where you want everything up to the second before the mistake. MySQL is backed up nightly, with the last fourteen nights kept. **How do you know the backups actually restore?** We restore them and connect to the result. A backup job reporting success only tells you a job finished; connecting to the restored database and reading from it tells you the data is there and usable. That is the check we run. **Can I move up a tier as the database grows?** Yes. The tiers run the same engine you started on, so moving up changes the vCPU, memory and disk allocation and, from medium, adds automatic failover. Talk to us before a large migration and we will plan the move with you. --- # One address your whole team works from URL: https://zinndigital.com/private-network A private, encrypted network for your team, with a dedicated static IP address that belongs to you alone. Add that one address to the SSH and SFTP allow-lists on your servers, and everyone on the team reaches your estate from it — from the office, from home, from a hotel. It is access control for infrastructure, not an open door onto the internet. What it is Private Network gives your team an encrypted network with a static IP address reserved for your organisation. Every device you connect leaves that network from the same address, so the servers you administer see one consistent, known origin no matter where your people happen to be working. It exists to solve a specific problem: teams that manage many sites end up either sharing credentials or maintaining allow-lists full of home broadband addresses that change without warning. One dedicated address replaces both, and it does not change when somebody moves house or opens a laptop in an airport. A small product with a narrow, deliberate scope — team access to infrastructure you control. A dedicated static IP address The address is reserved for your organisation and not shared with other customers. What you allow-list is yours alone. Allow-list once Add the address to your servers' SSH and SFTP allow-lists a single time. Adding a colleague after that is a change on the network, not on every server. Encrypted for the whole team Traffic between each device and the network is encrypted, so administrative access does not depend on the café Wi-Fi somebody is using this week. Works from anywhere Office, home, coworking space or travelling — the source address your servers see is the same one every time, so nothing has to be re-approved. Devices included, packs to add more The subscription covers a set number of connected devices. When the team or the number of laptops and phones grows, add a device pack. Scoped to your estate, on purpose The network reaches the infrastructure you manage. It is not a general internet exit, and that boundary is a design decision rather than a limitation we are working around. Three steps, and the middle one is done once rather than per person. Subscribe and get your address Your organisation is assigned a dedicated static IP address on its own private encrypted network. Allow-list it on your servers Add that single address to the SSH and SFTP allow-lists across your estate, and remove the scattered personal addresses you have been maintaining. Connect your team's devices Each person connects their devices to the network. From then on they reach your servers from the allow-listed address wherever they are working. A base monthly subscription that includes your dedicated static IP address and a set number of devices, plus optional device packs when you need more connections. Set up a Private Network from your dashboard, or talk to us and we will size the device count with you. The base subscription covers the dedicated address and the included devices. Additional devices are bought in packs, so the cost follows the size of the team. Agencies and in-house teams managing dozens of sites usually hit the same wall: locking SSH down to known addresses is the right control, but nobody's home address stays still. A dedicated static address makes the right control practical, and it removes the temptation to leave administrative ports open to everyone. We do not sell this as a way to browse the internet from somewhere else, because running open internet exits would put the reputation of our address space at risk — and our customers' sites depend on that reputation. Keeping the network scoped to your own estate protects every customer on the platform, including you. Can I use this to browse the internet privately or watch region-locked services? No, and we would rather say so plainly than sell you the wrong product. This is not a general internet exit; it reaches the infrastructure you manage. If you want a consumer privacy or streaming VPN, buy one of those instead. Why isn't it a general-purpose VPN? Because open internet exits attract abuse, and abuse damages the reputation of the address space our customers' sites are served from. Restricting the network to your own estate is a deliberate design choice that keeps that reputation clean for everyone, including the sites you run. Is the IP address really mine alone? Yes. The static address is dedicated to your organisation and not shared with other customers, which is what makes allow-listing it meaningful. If it were shared, allowing it would allow other people's traffic too. How many devices can connect? The base subscription includes a set number of devices, and you add more in device packs as the team grows. Count devices rather than people — laptops, desktops and phones each take a connection. Does it work with servers hosted somewhere other than Zinn Digital®? It is built for reaching infrastructure you control, and it works wherever you are able to add our dedicated address to an allow-list. If part of your estate sits outside our network, ask us before you buy and we will tell you plainly whether it is in scope. Stop maintaining a list of home IP addresses Take one dedicated static address, allow-list it across your estate once, and give your team encrypted access to the servers they administer from wherever they are working. ## Frequently asked questions **Can I use this to browse the internet privately or watch region-locked services?** No, and we would rather say so plainly than sell you the wrong product. This is not a general internet exit; it reaches the infrastructure you manage. If you want a consumer privacy or streaming VPN, buy one of those instead. **Why isn't it a general-purpose VPN?** Because open internet exits attract abuse, and abuse damages the reputation of the address space our customers' sites are served from. Restricting the network to your own estate is a deliberate design choice that keeps that reputation clean for everyone, including the sites you run. **Is the IP address really mine alone?** Yes. The static address is dedicated to your organisation and not shared with other customers, which is what makes allow-listing it meaningful. If it were shared, allowing it would allow other people's traffic too. **How many devices can connect?** The base subscription includes a set number of devices, and you add more in device packs as the team grows. Count devices rather than people — laptops, desktops and phones each take a connection. **Does it work with servers hosted somewhere other than Zinn Digital®?** It is built for reaching infrastructure you control, and it works wherever you are able to add our dedicated address to an allow-list. If part of your estate sits outside our network, ask us before you buy and we will tell you plainly whether it is in scope. --- # Make your site fast, by people who do this every day URL: https://zinndigital.com/site-speedup A hands-on engineering pass over one site: caching, images, CSS and JavaScript, fonts and the database. We work on any site — it does not have to be hosted with us. Automation gets you most of the way. The rest needs judgement. Where the platform can apply a speed optimisation automatically, it already does — caching, compression and image handling are part of hosting with us and cost nothing extra. But every slow site is slow for its own reasons, and the last stretch is where an engineer beats a checkbox. This is that stretch. Somebody reads your site, measures what is actually costing you time, and fixes those things specifically — then tells you what they changed. Every tier includes the work below. Larger tiers add the handling a shop or a heavy, plugin-laden site needs on top. Cache layers, configured properly Page, object and browser caching set up for how your site is actually built — not switched on and hoped for. Images that weigh what they should Compression, modern WebP and AVIF formats, correct dimensions, and lazy loading below the fold. CSS and JavaScript that stop blocking Minification, deferral, and on the heaviest tier per-template critical CSS and per-page asset dequeuing. A font strategy Loading behaviour chosen so text is readable immediately instead of flashing in late. Cache rules a shop can survive Cart, checkout and account pages excluded correctly, cart-fragment and AJAX handling, and object-cache tuning. The database underneath Clean-up, slow-query identification and indexing, plus a plugin audit where plugin bloat is the real cause. Three steps, and the first one is free. Tell us the site Send us the URL. We measure it and tell you which tier it needs and what we expect to gain. We do the work An engineer applies the changes to your site, testing as they go rather than applying a template. You get the result and the reasoning We hand back the measured before-and-after. The heaviest tier includes a written report of what changed and what remains. A one-off fee, priced by how much site there is to work on. We tell you which tier applies before you buy — if we think you do not need this, we will say so. Tell us the site and we will measure it and quote the right tier. One-off, not a subscription. Hosting with us already includes automatic caching, compression and image optimisation at no extra cost — this is the hands-on work on top. Core Web Vitals are a ranking signal, and they are measured on real visits rather than in a lab. A slow site loses positions it has already earned, and loses the visitor before the page finishes arriving. The gap between an automatic pass and an expert one is usually the difference between a score that is acceptable and one that is good. That gap is judgement — knowing which plugin to dequeue on which template — and it is not something a switch can hold. Do I have to host with Zinn Digital®? No. We do this on any site, wherever it is hosted. You do not need to move anything to us, before or after. What score will I end up with? We do not promise a number, and you should be wary of anyone who does — the ceiling depends on your theme, your plugins and what your pages have to do. We measure first and tell you what we expect to reach before you spend anything. My site is a shop. Is that different? Yes, and it is priced differently for that reason. A shop or membership site needs cart, checkout and account pages deliberately excluded from caching, plus cart-fragment and AJAX handling. Caching those pages is how a speed-up breaks a checkout. Will this break anything? An engineer does the work rather than a bulk script, and tests as they go. On the heaviest tier you also get a written record of every change, so anything can be traced and undone. What if the real problem is my hosting? Then we will tell you that instead of taking your money for tuning around it. Some sites are slow because of where they live, and no amount of front-end work fixes a server that is out of headroom. Is this a subscription? No. It is a one-off piece of work. If you want the gains kept under review over time, that is what our monitoring products are for. Send us a URL We will measure your site and tell you what we would do, which tier it falls into, and what we expect to gain — before you decide. ## Frequently asked questions **Do I have to host with Zinn Digital®?** No. We do this on any site, wherever it is hosted. You do not need to move anything to us, before or after. **What score will I end up with?** We do not promise a number, and you should be wary of anyone who does — the ceiling depends on your theme, your plugins and what your pages have to do. We measure first and tell you what we expect to reach before you spend anything. **My site is a shop. Is that different?** Yes, and it is priced differently for that reason. A shop or membership site needs cart, checkout and account pages deliberately excluded from caching, plus cart-fragment and AJAX handling. Caching those pages is how a speed-up breaks a checkout. **Will this break anything?** An engineer does the work rather than a bulk script, and tests as they go. On the heaviest tier you also get a written record of every change, so anything can be traced and undone. **What if the real problem is my hosting?** Then we will tell you that instead of taking your money for tuning around it. Some sites are slow because of where they live, and no amount of front-end work fixes a server that is out of headroom. **Is this a subscription?** No. It is a one-off piece of work. If you want the gains kept under review over time, that is what our monitoring products are for. --- # Your site is infected. We clean it, repair it and harden it. URL: https://zinndigital.com/malware-cleanup A compromised site, dealt with by people rather than a scanner: the malware removed, the damage repaired, and the way in closed behind us. Any site, hosted anywhere. Scanning finds it. Cleaning it up is a different job. Malware scanning, a proactive firewall and per-site isolation are included on every plan we sell, and they run continuously at no extra cost. What they do is tell you something is wrong and stop it spreading. Getting an already-infected site back is separate work, and it is manual. Injected files have to be told apart from legitimate ones, the damage has to be undone without losing your content, and whatever let the attacker in has to be found — or you will be buying this twice. One fixed price for the whole job, however long it takes us. The malware removed Injected code, backdoors, dropped files and modified core files identified and cleared, rather than blindly deleted. The damage repaired Defaced pages, spam content, redirects and altered configuration put back the way they should be. The way in closed We look for how it happened — an outdated plugin, a weak credential, a writable path — because a clean site with the door still open is a temporary result. Hardened afterwards Permissions, credentials and update posture tightened once the site is clean, so the same route does not work twice. Tell us it is infected and we start. You do not need an account with us first. Send us the site Give us the URL and access. If you are not sure whether you are infected, say so — we will look before you buy anything. We clean and repair An engineer works through the site, removing what does not belong and restoring what was altered. We harden and hand back We close the route in, tighten the site, and tell you what we found and what we changed. One fixed price per site, regardless of how bad it turns out to be. We would rather quote you once than meter an emergency. Tell us the site and we will look before you pay anything. Scanning, the proactive firewall and per-site isolation are included on every hosting plan at no extra cost. This is the remediation service you buy on top when a site is already compromised. Automated cleaners work by pattern. They are good at the malware everyone has seen and blind to anything shaped slightly differently, and their usual failure is to delete a file your site needed — trading an infected site for a broken one. The part that actually matters is the last part. If nobody works out how the attacker got in, the site is reinfected within days and the cleanup was rented, not bought. Do I have to host with Zinn Digital®? No. We clean sites wherever they are hosted, and there is no requirement to move to us afterwards. How do I know if I am actually infected? Common signs are search results showing pages you never wrote, visitors redirected somewhere unexpected, browser or search-engine warnings, or your host suspending the account. If you are unsure, ask us and we will look first. Will I lose my content? That is precisely what the manual approach is for. Injected code is separated from your legitimate files rather than removed in bulk, because the fast automated version of this job is the one that takes your site down with the malware. What stops it happening again? Finding the way in is part of the work, not an extra. We close it and harden the site afterwards — and if you move the site to us, scanning, the firewall and per-site isolation then run on it continuously as part of the plan. Tell us about the site Send us the URL. We will look at it and tell you what we are dealing with before you commit to anything. ## Frequently asked questions **Do I have to host with Zinn Digital®?** No. We clean sites wherever they are hosted, and there is no requirement to move to us afterwards. **How do I know if I am actually infected?** Common signs are search results showing pages you never wrote, visitors redirected somewhere unexpected, browser or search-engine warnings, or your host suspending the account. If you are unsure, ask us and we will look first. **Will I lose my content?** That is precisely what the manual approach is for. Injected code is separated from your legitimate files rather than removed in bulk, because the fast automated version of this job is the one that takes your site down with the malware. **What stops it happening again?** Finding the way in is part of the work, not an extra. We close it and harden the site afterwards — and if you move the site to us, scanning, the firewall and per-site isolation then run on it continuously as part of the plan. **Will it come back?** Not from the same hole, because the point of the job is finding how it got in rather than deleting what it left. A cleanup that removes the files and not the entry is a cleanup you buy again in a fortnight, and we would rather you did not. **Do I have to move my site to you for this?** No. We will clean a site hosted anywhere we can be given access to. If you do move it here afterwards, the platform scans it daily from then on — but that is a separate decision and this service does not depend on it. **Google has flagged my site. Can you get that lifted?** We clean the site, verify it is clean, and prepare the review request with the evidence the reviewer asks for. The decision and the timing are Google's, and anyone who promises you a delisting date is guessing. --- # Certificate work for the cases automation cannot reach URL: https://zinndigital.com/ssl-setup Most certificates should install themselves, and on our platform they do — free, automatically renewed, no involvement from you. This is the hands-on service for the certificates that do not fit that path. If your certificate is ordinary, do not buy this Automatic HTTPS is included on every plan we sell. Certificates are issued, installed and renewed without anyone asking, and that covers the overwhelming majority of sites — so for most customers this service is unnecessary and we will tell you so. It exists for the rest: a certificate you bought elsewhere and must use, an intermediate chain that does not resolve cleanly, an EV or wildcard requirement, or an edge configuration with its own rules. That work is fiddly, it fails in ways that are hard to read, and it is worth an engineer's half hour rather than your afternoon. A one-off piece of certificate work, done and verified. Certificates you already own A purchased, EV, wildcard or organisation-validated certificate installed and bound correctly to your site. Chains that do not resolve Missing or misordered intermediates diagnosed and fixed — the usual cause of a certificate that works in one browser and fails in another. Edge and origin requirements Configuration where the CDN edge and the origin each need their own certificate behaviour, including strict origin validation. Verified, not assumed We check the installed result from outside as a browser sees it, rather than confirming that a file was uploaded. Tell us what you need and we will tell you whether you need it. Describe the certificate Tell us what you have and what it has to do. If automatic provisioning would cover it, we will say so and you keep your money. We install and configure An engineer installs the certificate, resolves the chain and applies the configuration your setup requires. We verify it externally We confirm the certificate serves correctly and the chain validates from outside, then hand it back with what we did. A one-off fee for the piece of work. It does not include the price of a certificate you buy from someone else. Tell us what the certificate has to do and we will confirm whether this service applies. Ordinary HTTPS is free and automatic on every plan, including renewal. Pay for this only when your certificate falls outside that. A certificate that is subtly wrong does not fail loudly. It validates in the browser you tested and fails in an app, an older client or a payment callback — so the first report usually arrives from a customer who could not check out. Chain problems in particular are invisible from the machine that installed them, because that machine already holds the intermediate it is failing to send. Verifying from outside is the whole job. Do I need this if I host with you? Almost certainly not. HTTPS is issued, installed and renewed automatically on every plan at no cost. Buy this only when you have a certificate or a requirement that falls outside automatic provisioning. Do you sell the certificate itself? No — this is the work of installing and configuring one. If you have bought a certificate elsewhere, or you need a specific issuer for compliance reasons, this is how it gets put in place properly. My site says 'not secure' in some browsers but not others. That is the classic symptom of an incomplete intermediate chain: browsers that already cache the intermediate accept it and the rest do not. It is exactly what this service fixes, and it cannot be diagnosed reliably from the server itself. Does this cover renewals? It is a one-off installation. Certificates issued automatically on our platform renew themselves indefinitely; a certificate you supply renews on whatever terms you bought it under. Tell us what the certificate has to do Describe your setup and we will tell you whether automatic HTTPS already covers it — and if it does not, exactly what we would do. ## Frequently asked questions **Do I need this if I host with you?** Almost certainly not. HTTPS is issued, installed and renewed automatically on every plan at no cost. Buy this only when you have a certificate or a requirement that falls outside automatic provisioning. **Do you sell the certificate itself?** No — this is the work of installing and configuring one. If you have bought a certificate elsewhere, or you need a specific issuer for compliance reasons, this is how it gets put in place properly. **My site says 'not secure' in some browsers but not others.** That is the classic symptom of an incomplete intermediate chain: browsers that already cache the intermediate accept it and the rest do not. It is exactly what this service fixes, and it cannot be diagnosed reliably from the server itself. **Does this cover renewals?** It is a one-off installation. Certificates issued automatically on our platform renew themselves indefinitely; a certificate you supply renews on whatever terms you bought it under. **Can you do this for a site hosted somewhere else?** Yes, and that is one of the main reasons to buy it. On a site we host, free certificates are issued and renewed automatically, so an expired certificate is not a thing that happens there. This service is for a certificate on a server we do not host, or one with requirements the automatic path does not cover. **What kinds of certificate does this cover?** The awkward ones: a certificate you already bought and cannot get installed, a wildcard or multi-domain certificate that has to match a specific chain, a legacy device or appliance that will not take the ordinary path, and a mixed-content problem where the certificate is fine and the site still shows a warning. **How long does it take?** Usually the same working day once we have access, because the work is short and the waiting is nearly always the certificate authority rather than us. We tell you what we are waiting for rather than leaving it quiet. --- # Straight to the front — and a pair of hands, not just an answer URL: https://zinndigital.com/priority-support Your tickets jump the queue and are dealt with first. And it goes further than answering: small code changes and fixes are included, and where a problem is bigger than that we diagnose it and tell you exactly what needs doing. What it adds to the support you already have Support is included with every plan: the desk is open 24 hours a day, a person answers, you can write in any of our 58 languages and we reply in yours, and nothing is metered per incident. Priority support does not replace any of that — it is built on top of it. What it adds is two things. Your ticket is pulled to the front of the queue and dealt with first, and the person who picks it up can go in and make small code changes and fixes — which ordinary support does not do, because ordinary support answers questions rather than editing your site. A monthly subscription on the account, applying to every ticket you raise. Front of the queue Your tickets are pulled ahead of the standard queue automatically — you do not have to ask for it, explain yourself, or write URGENT in the subject line. Small fixes actually done Small code changes and fixes are included: a broken template tag, a redirect that is not firing, a snippet in the wrong place, a rule overriding the wrong thing. Ordinary support tells you what is wrong. This fixes it. A diagnosis for the bigger ones When something is too big to fix inside a ticket, we still find out what is actually wrong and write it down — what is broken, why, and what needs doing — so you or your developer start from a brief instead of a symptom. Every ticket, not just the bad days It applies to everything you raise, a billing question included, and it is a monthly subscription with no term — so it can follow a busy season rather than the other way round. There is nothing to configure. Add it to your account Buy it once and it applies to the account, not to a single site or a single ticket. Raise tickets as normal The same dashboard and the same inbox. The queue jump happens behind the scenes, on everything you send. Ask for the fix, not just the answer Say what you want done rather than only what is wrong. If it is small we do it; if it is not, you get the diagnosis and the list of what needs doing. A flat monthly fee on the account, covering every ticket you raise while it is active. Ask us and we will set it up on your account. Per account, not per site or per ticket. Support itself is included on every plan at no charge — this adds the queue jump and the hands-on fixes on top of it. It earns its keep wherever somebody else is waiting on your answer — an agency answering to its own clients, a shop in its trading season, a network where one small breakage is the same small breakage on forty sites. And it earns it wherever there is nobody to hand the fix to. If you have no developer on call, the difference between being told what is wrong and having it put right is the whole afternoon. What is in normal support, then? Everything you would expect of support, free, on every plan: the desk is open 24 hours a day, a person answers, you can write in any of our 58 languages and we reply in yours, and nothing is counted or capped per incident. Priority takes nothing away from that — it adds the queue jump and the small fixes on top. What counts as a small code change? Things that are a few minutes' work for somebody who knows the platform: a broken template tag, a redirect that is not firing, a snippet in the wrong place, a setting that has to be changed in code, a style rule overriding the wrong element. If it is bigger than that we say so before spending your time on it. And if it is bigger than that? You get the diagnosis anyway, which is the part that usually costs the most to buy elsewhere. We find out what is actually wrong and write down what is broken, why, and what needs doing — so whoever does the work starts with a brief rather than a guess. Is this development work? No, and we would rather be exact than vague about it: small changes and fixes, not new features, a redesign or a build. Anything of that size is quoted as development work, which we also do — priority support is the thing that keeps the small stuff from becoming a project. Add priority support Turn it on from your dashboard, or ask us and we will apply it to your account. It takes effect on the next ticket you raise. ## Frequently asked questions **What is in normal support, then?** Everything you would expect of support, free, on every plan: the desk is open 24 hours a day, a person answers, you can write in any of our 58 languages and we reply in yours, and nothing is counted or capped per incident. Priority takes nothing away from that — it adds the queue jump and the small fixes on top. **What counts as a small code change?** Things that are a few minutes' work for somebody who knows the platform: a broken template tag, a redirect that is not firing, a snippet in the wrong place, a setting that has to be changed in code, a style rule overriding the wrong element. If it is bigger than that we say so before spending your time on it. **And if it is bigger than that?** You get the diagnosis anyway, which is the part that usually costs the most to buy elsewhere. We find out what is actually wrong and write down what is broken, why, and what needs doing — so whoever does the work starts with a brief rather than a guess. **Is this development work?** No, and we would rather be exact than vague about it: small changes and fixes, not new features, a redesign or a build. Anything of that size is quoted as development work, which we also do — priority support is the thing that keeps the small stuff from becoming a project. **Is it per site or per account?** Per account. However many sites you run with us, every ticket you raise is pulled to the front of the queue while the subscription is active, and the small fixes apply to any of them. **How is this different from emergency support?** Priority is standing: it shortens everything you send and includes the small fixes. Emergency is a one-off for a site that is down right now, with an engineer on it within four hours. If you expect to need help more than occasionally, priority is much cheaper per incident; if a site goes down once a year, it is not. **Can I cancel it?** From your dashboard, at any time, and it stops at the end of the period you have paid for. There is no minimum term and nothing to phone anybody about. --- # Backups for WordPress sites we do not host URL: https://zinndigital.com/external-backups Back up any WordPress site, wherever it lives, to storage we run on Cloudflare R2. Connect it with our connector plugin or over SSH, choose a size tier, and your site is protected somewhere other than the server it runs on. Connect over SSH and restoring is one click. What it is A standalone backup product for WordPress sites hosted anywhere. You do not need to be a hosting customer, move your site or change anything about how it is served. You connect the site, we take copies of it, and those copies live on infrastructure that has nothing to do with the server your site runs on. That last part is the whole point. A backup stored on the same machine as the site protects you from your own mistakes and from very little else. Keeping copies somewhere separate is what makes them useful on the day the host, the disk or the account itself is the problem. Written plainly, including the limitation that matters most. Any host, not just ours Works with WordPress sites wherever they are hosted. Nothing has to move and nothing about your current hosting has to change. Two ways to connect Connect with our WordPress connector plugin, or over SSH. The plugin is quicker to set up; SSH gives you more, and the difference is explained below. One-click restore over SSH When a site is connected over SSH, putting a backup back is a single action. The plugin can take backups but cannot perform a restore, because a plugin cannot run inside a WordPress installation that is too broken to load. Stored on Cloudflare R2 Backups are held on Cloudflare R2, off your web server and out of your host's blast radius. If the server is gone, the copies are not. Tiers by size Three tiers, one per site, chosen by how big that site is: up to 1 GB, 10 GB or 50 GB. Every tier takes a backup daily and keeps each copy for 30 days. A soft landing if you move Every stored copy can be downloaded as an archive of the site's files and database, so you always hold a complete copy to move from, whichever host you choose next. Setting up takes a few minutes and does not touch how your site is served. Connect the site Install the connector plugin on the WordPress site, or give us SSH access to the server it runs on. SSH is the option to pick if you want one-click restore. Backups run and are stored A fresh copy is taken every day and uploaded straight from your server to Cloudflare R2, away from the server the site runs on. Each copy is kept for 30 days. Restore when you need it With SSH connected, restoring a backup is one click. If you connected with the plugin only, your backups are still held and intact — adding SSH is what turns on one-click restore. External backups are priced per site, by the size of that site: one tier covers one site up to 1 GB, 10 GB or 50 GB. Daily backups, 30-day retention, downloads and one-click restore over SSH are included in every tier, with nothing charged per restore. It is available in your dashboard today — talk to us and we will set you up. If a site outgrows its tier, buy the larger tier for that site; it replaces the smaller one rather than adding to it, and nothing about how the site is connected changes. We built this for people who are not our hosting customers, which is unusual and deliberate. Most sites that lose data lose it on a host that offered backups nobody had ever tested, stored on the same infrastructure that failed. Holding copies somewhere genuinely separate is the part that does the work, and it should not require you to change host first. It also changes what moving host feels like. With a current off-site copy already held, and downloadable at any time, the site's files and database are ready the day you decide to move, to us or anywhere else. We would rather earn that move by being useful to you beforehand than by making your data awkward to take elsewhere. Can I use this if my site is not hosted with Zinn Digital®? Yes — that is what it is for. It backs up WordPress sites wherever they are hosted, and you do not need to be a hosting customer or move anything. You connect the site with our plugin or over SSH, and it carries on being served exactly as it is today. What is the difference between connecting by plugin and by SSH? The plugin can back your site up, but it cannot restore it. That is not a feature we have held back: a restore has to run when WordPress itself is broken or missing, and a plugin lives inside the WordPress installation being restored, so it cannot be the thing that repairs it. SSH connects to the server rather than to WordPress, which is why one-click restore requires SSH — if you want restores as well as backups, connect over SSH. So can I still recover a site I connected with the plugin? Your backups are taken, stored and intact either way, so nothing is lost. What the plugin cannot do is perform the restore for you at the click of a button. Adding SSH access to that site turns one-click restore on, and it is the change we would suggest making before you need it rather than after. How much does it cost? It is priced per site, by the size of that site: a tier covers one site up to 1 GB, 10 GB or 50 GB, and the prices are listed above. Every tier includes daily backups kept for 30 days. If a site outgrows its tier, you buy the larger tier for that site without changing how anything is connected. Where are my backups actually stored? On Cloudflare R2, which is separate from the server your site runs on and separate from your current host. That separation is the point: a backup kept on the same machine as the site does not help when that machine or that account is the problem. What happens if I move my site to Zinn Digital® later? Sites on Zinn Digital® hosting are backed up by the hosting plan itself, so once the site has moved you can cancel its external-backup tier. Until then, your latest off-site copy can be downloaded at any time, which gives the move a complete, recent copy of the files and database to start from. Protect a site you host elsewhere Connect your WordPress site with the plugin or over SSH, pick the size tier that fits, and have off-site copies of it today. Connect over SSH and restoring is one click. ## Frequently asked questions **Can I use this if my site is not hosted with Zinn Digital®?** Yes — that is what it is for. It backs up WordPress sites wherever they are hosted, and you do not need to be a hosting customer or move anything. You connect the site with our plugin or over SSH, and it carries on being served exactly as it is today. **What is the difference between connecting by plugin and by SSH?** The plugin can back your site up, but it cannot restore it. That is not a feature we have held back: a restore has to run when WordPress itself is broken or missing, and a plugin lives inside the WordPress installation being restored, so it cannot be the thing that repairs it. SSH connects to the server rather than to WordPress, which is why one-click restore requires SSH — if you want restores as well as backups, connect over SSH. **So can I still recover a site I connected with the plugin?** Your backups are taken, stored and intact either way, so nothing is lost. What the plugin cannot do is perform the restore for you at the click of a button. Adding SSH access to that site turns one-click restore on, and it is the change we would suggest making before you need it rather than after. **How much does it cost?** It is priced per site, by the size of that site: a tier covers one site up to 1 GB, 10 GB or 50 GB, and the prices are listed above. Every tier includes daily backups kept for 30 days. If a site outgrows its tier, you buy the larger tier for that site without changing how anything is connected. **Where are my backups actually stored?** On Cloudflare R2, which is separate from the server your site runs on and separate from your current host. That separation is the point: a backup kept on the same machine as the site does not help when that machine or that account is the problem. **What happens if I move my site to Zinn Digital® later?** Sites on Zinn Digital® hosting are backed up by the hosting plan itself, so once the site has moved you can cancel its external-backup tier. Until then, your latest off-site copy can be downloaded at any time, which gives the move a complete, recent copy of the files and database to start from. --- # Things you can buy from us without hosting anything with us URL: https://zinndigital.com/products Not everything we make is a hosting feature. These are products in their own right — you can buy them on their own, point them at sites and systems that live somewhere else entirely, and never open a hosting plan. Each one is built on the same platform our own fleet runs on. Monitor and protect Know when something breaks, and be able to put it back — whoever is hosting it. Uptime monitoring Watch any web address, hosted with us or anywhere else, and hear about it within minutes when it stops answering. Three addresses free on any account. External backups Off-site backups for WordPress sites we do not host. Connect over SSH and restoring is one click. Private network A dedicated static IP address for your team. Allow-list it once and everyone reaches your servers from it, from anywhere. Reach more people More markets, better pages to show them, and an answer for everyone who arrives. Website translation Your whole site in 58 languages, each on its own indexable URL with hreflang. Every language is included, and you choose which are served. AI images Generate original imagery for your sites from a plain description, using models from Google, OpenAI and xAI, in the dashboard you already use. Infrastructure The pieces an application needs behind it, run properly and sold separately. Managed databases Managed PostgreSQL and MySQL sold on their own, with automatic failover from the medium tier and restores we verify by connecting to them. Object storage S3-compatible buckets on Cloudflare R2, with no egress fee for reading your own data back. An allowance comes with every hosting plan. Start with whichever one you need Every product here is bought on its own and works on its own. Create an account and you can be using one this afternoon, whether or not anything of yours is hosted with us. ## Frequently asked questions **Do I need a hosting plan to buy these?** No. Sign up for a free account and buy any of them on their own. Several are used by people who host nothing with us at all — the uptime monitor and the SEO tools in particular, because a monitor that only watches your own provider's servers is the one monitor you should not trust. **How am I billed?** On one invoice with everything else you have with us, in your own currency, with the tax your country requires. Monthly products renew monthly and can be cancelled from your dashboard; one-off services are charged once when the work is agreed. **What is included with hosting instead?** Updates, daily off-site backups, malware scanning, SSL, a CDN, free migrations, Core Web Vitals and request profiling — the list a WordPress care plan charges a monthly fee for. The WP Care page compares the two line by line and says what that fee typically is. **Can I try one before paying?** The uptime monitor has a free tier — three addresses on any account, including addresses we do not host. For the rest, ask us: we would rather tell you a product is wrong for you than sell it and have you cancel. --- # Simple pricing, scale to anything URL: https://zinndigital.com/pricing Prices in USD by default — pick your currency in the header. Start free, no card. [object Object] Talk to us --- # Talk to us URL: https://zinndigital.com/contact Hosting questions, migrations, or a development project — reach us however suits you. We reply fast. Get in touch Email Telegram Support tickets Prefer to scope a build? Tell us about your project on the development page — 25+ years of full-stack work, from full apps to WordPress plugins. --- # Tell us what you need built, and we will price it URL: https://zinndigital.com/quote Our developers have more than 25 years of full-stack work behind them, and they built the platform you are reading this on. Describe the job and you will get a real figure from a real person — not a rate card. A developer reads what you sent — not a sales person, and not a form-filler. We come back with a price and what it covers, usually within one working day. If we need to ask something first, we ask. If the number works for you, we book it in. If it does not, you owe us nothing and we will say honestly whether there is a cheaper way. Builds from scratch, rescue jobs on sites somebody else left behind, and stores that need to survive a busy week. Written to WordPress.org standards, translation-ready, and yours — not locked to us. Including sites we do not host and stacks we did not choose. Some of the best work we do is finding what three people before us could not. Python, PHP, .NET and Node — APIs, integrations, internal tools and the awkward automation nobody else wanted to take on. Does the quote cost anything? No. Quoting is free and there is no obligation to go ahead. If the job is not a good fit for us we will say so rather than pad a number. Do I have to host with Zinn Digital®? No. We will happily work on a site hosted anywhere. If moving it to us would make the job cheaper or faster we will tell you, and it is still your decision. How quickly will I hear back? Usually within one working day, by email, from the person who will do the work. If the job needs a conversation before we can price it, we will ask for one. ## Frequently asked questions **Does the quote cost anything?** No. Quoting is free and there is no obligation to go ahead. If the job is not a good fit for us we will say so rather than pad a number. **Do I have to host with Zinn Digital®?** No. We will happily work on a site hosted anywhere. If moving it to us would make the job cheaper or faster we will tell you, and it is still your decision. **How quickly will I hear back?** Usually within one working day, by email, from the person who will do the work. If the job needs a conversation before we can price it, we will ask for one. --- # Help and how-to guides URL: https://zinndigital.com/kb Straight answers to the questions our customers actually ask — DNS, email, WordPress, speed and billing. Every article is written by the team that runs the platform. Still stuck? Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours. --- # Find what hosting is right for your site URL: https://zinndigital.com/hosting/finder Six questions, no account, no sales call. We match your answers against what each plan actually grants and show you the reasoning — including anything that does not quite fit. How does the hosting finder decide? First it keeps only the kinds of hosting made for what you are building — a business site is never offered network (PBN) hosting, and a shop is never offered a plan built for a different app. Then it reads what each remaining plan actually grants — the site allowance, the traffic allowance, whether mailboxes and SSH are included, whether a domain comes with it — and ranks them, cheapest per month first when two fit equally well. Nothing is hardcoded, so a plan we change tomorrow is matched on its new terms. What if no plan covers everything I asked for? We say so rather than recommending something that will not do the job. A plan that cannot meet a hard requirement — fewer sites than you need, no SSH when you asked for it — is left out entirely. Anything else that does not quite fit is shown as a note on a plan we do still offer, so the decision stays yours. Do I have to buy what it recommends? No. The finder drops you onto that plan's configuration page with your answers already filled in, where you can change the term, the domain and anything else before you pay. Every managed plan also starts with a free trial, so you can put a real site on it first. ## Frequently asked questions **How does the hosting finder decide?** First it keeps only the kinds of hosting made for what you are building — a business site is never offered network (PBN) hosting, and a shop is never offered a plan built for a different app. Then it reads what each remaining plan actually grants — the site allowance, the traffic allowance, whether mailboxes and SSH are included, whether a domain comes with it — and ranks them, cheapest per month first when two fit equally well. Nothing is hardcoded, so a plan we change tomorrow is matched on its new terms. **What if no plan covers everything I asked for?** We say so rather than recommending something that will not do the job. A plan that cannot meet a hard requirement — fewer sites than you need, no SSH when you asked for it — is left out entirely. Anything else that does not quite fit is shown as a note on a plan we do still offer, so the decision stays yours. **Do I have to buy what it recommends?** No. The finder drops you onto that plan's configuration page with your answers already filled in, where you can change the term, the domain and anything else before you pay. Every managed plan also starts with a free trial, so you can put a real site on it first. --- # Which hosting is right for me? URL: https://zinndigital.com/hosting/compare Twelve kinds of hosting, one table. Find the line made for what you are building — then see what every plan includes and where it starts. What is the difference between WordPress hosting and app hosting? WordPress hosting is made for WordPress and WooCommerce: it adds staging, automatic updates and WordPress-tuned caching. App hosting gives each other application — Joomla, Drupal, PrestaShop, Moodle and more — a plan of its own, with that application installed and tuned for you. Should I use PBN hosting for my business site? No. Footprint-Free hosting exists to spread a network of link sites across separate footprints for SEO. A business site, blog or shop belongs on WordPress, app or Linux hosting, which our hosting finder will never swap for a PBN plan. When do I need a VPS instead of hosting? When you need to install your own server software, run background services all day, or control the whole machine. If you only need a website or a web app, a hosting plan is simpler, includes backups and email, and costs less. Can I change to another kind of hosting later? Yes. Moving up a plan within a line is one click, and moving a site to another kind of hosting is a migration we include free on most plans. What comes with every hosting plan? Free SSL and daily backups come with every plan. Sites on our hosting fleet are also protected from brute-force logins and from attacks that try to go round our CDN, and every plan with mailboxes includes virus and spam filtering and a backup mail server. Each line’s own page lists exactly what it includes. ## Frequently asked questions **What is the difference between WordPress hosting and app hosting?** WordPress hosting is made for WordPress and WooCommerce: it adds staging, automatic updates and WordPress-tuned caching. App hosting gives each other application — Joomla, Drupal, PrestaShop, Moodle and more — a plan of its own, with that application installed and tuned for you. **Should I use PBN hosting for my business site?** No. Footprint-Free hosting exists to spread a network of link sites across separate footprints for SEO. A business site, blog or shop belongs on WordPress, app or Linux hosting, which our hosting finder will never swap for a PBN plan. **When do I need a VPS instead of hosting?** When you need to install your own server software, run background services all day, or control the whole machine. If you only need a website or a web app, a hosting plan is simpler, includes backups and email, and costs less. **Can I change to another kind of hosting later?** Yes. Moving up a plan within a line is one click, and moving a site to another kind of hosting is a migration we include free on most plans. **What comes with every hosting plan?** Free SSL and daily backups come with every plan. Sites on our hosting fleet are also protected from brute-force logins and from attacks that try to go round our CDN, and every plan with mailboxes includes virus and spam filtering and a backup mail server. Each line’s own page lists exactly what it includes. --- # WordPress plugins URL: https://zinndigital.com/wordpress-plugins We publish 17 WordPress plugins. The free ones run on any WordPress site, and every WordPress site we host comes with 3 of them installed and activated. Pro editions are paid upgrades. Every release is installed and activated against WordPress 7.1 before it ships. No account and no sign-up. Each file is served from our own infrastructure with its SHA-256 checksum beside it, so you can confirm that what you downloaded is what we published. On a site we host, these plugins are configured to update themselves: they check with us and WordPress installs the new version for you, with the download verified against its published checksum first. On a WordPress we do not host, there is nothing to configure and nothing phones home — come back to this page when you want the newest version, or watch the plugin's GitHub releases. Every plugin here is released under the GNU General Public License and its full source is on GitHub, so you can read exactly what runs on your site before you install it. They are built to WordPress.org plugin-directory standards: coding standards, security review, no PHP notices, and translation-ready in every language we sell in. Are these plugins free? The free editions are: free to download and use, with no account, no sign-up and no licence key, under the GNU General Public License. The Pro editions are paid upgrades that unlock more with a licence key. Every WordPress site we host comes with 3 of the free plugins already installed. Do they work with the latest version of WordPress? Yes. Before any release is published we install and activate it on a fresh copy of the current stable WordPress, with WooCommerce alongside, and load the front end and the admin — a release that raises a single PHP notice does not ship. The "Tested up to" column above is that test, not an estimate. Do I have to host with you to use them? No. They install on any WordPress site on any host. Some features need our platform — the cache plugins need a LiteSpeed server with the LSCache module, and the connector and reseller toolkit talk to your Zinn® account — and each one degrades gracefully where a capability is absent. How do I know the download has not been tampered with? Each row shows the SHA-256 checksum of the file we published, and the download itself returns the same value in an X-Zinn-Package-SHA256 header. Compare it against the file you received. The plugins' own updater performs the same check automatically before WordPress installs anything. How do updates reach my site? It depends on where the site is. On a site we host, the plugin is already configured against our update service: it checks for a new version, verifies the download against the checksum we published, and WordPress installs it — you do nothing. On your own WordPress the plugin has no credentials for our service and does not contact us at all, so you update it the way you would any manually installed plugin: download the new zip from this page and upload it. We are building a self-service update channel for that case; until it ships, this page is the place to check. Can I read the source before installing? Yes — each plugin links to its public GitHub repository above, where the complete source, the licence and every release are available. ## Frequently asked questions **Are these plugins free?** The free editions are: free to download and use, with no account, no sign-up and no licence key, under the GNU General Public License. The Pro editions are paid upgrades that unlock more with a licence key. Every WordPress site we host comes with 3 of the free plugins already installed. **Do they work with the latest version of WordPress?** Yes. Before any release is published we install and activate it on a fresh copy of the current stable WordPress, with WooCommerce alongside, and load the front end and the admin — a release that raises a single PHP notice does not ship. The "Tested up to" column above is that test, not an estimate. **Do I have to host with you to use them?** No. They install on any WordPress site on any host. Some features need our platform — the cache plugins need a LiteSpeed server with the LSCache module, and the connector and reseller toolkit talk to your Zinn® account — and each one degrades gracefully where a capability is absent. **How do I know the download has not been tampered with?** Each row shows the SHA-256 checksum of the file we published, and the download itself returns the same value in an X-Zinn-Package-SHA256 header. Compare it against the file you received. The plugins' own updater performs the same check automatically before WordPress installs anything. **How do updates reach my site?** It depends on where the site is. On a site we host, the plugin is already configured against our update service: it checks for a new version, verifies the download against the checksum we published, and WordPress installs it — you do nothing. On your own WordPress the plugin has no credentials for our service and does not contact us at all, so you update it the way you would any manually installed plugin: download the new zip from this page and upload it. We are building a self-service update channel for that case; until it ships, this page is the place to check. **Can I read the source before installing?** Yes — each plugin links to its public GitHub repository above, where the complete source, the licence and every release are available. **How many plugins are there, and is this all of them?** There are 17 in total and every one has a page here. Most can be downloaded from this site and installed on any WordPress. Zinn® Footprint is not distributed separately: it comes installed on every WordPress site we host. The Pro editions are paid upgrades, delivered with a licence. --- # Billing-panel modules URL: https://zinndigital.com/integrations Sell Zinn® hosting from the billing system you already run. Free, GPL-licensed, no account needed to download — and no privileged back door: every call a module makes is a documented endpoint you could make yourself with your own API key. An order creates your client's Zinn® account and provisions their site. Your panel's own overdue-invoice automation suspends it. Marking the invoice paid releases it. Cancelling schedules the deletion — with the date shown to your client, because their data is not gone yet and telling them it is would be worse than telling them nothing. Your client presses “Log in to hosting” in your client area and lands in their control panel already signed in. The link is minted when they click it, is single-use, and expires in minutes — it is never rendered into a page where a cache or a log could keep it. A daily job refreshes each service's usage in your panel from ours. A figure we could not measure is left alone rather than written as zero — “no reading” and “used nothing” are different facts, and only one of them should show your customer an empty usage bar. No account and no sign-up. Each archive is served from our own infrastructure with its SHA-256 checksum beside it, so you can confirm that what you downloaded is what we published — which matters more than usual here, because this code holds an API key that can create and destroy your clients' hosting. Create a key in your Zinn® dashboard and give it seven permissions: org.create and org.read to open and read your client accounts, sites.create, sites.view and sites.delete for the service itself, and reseller.view and reseller.provision to list what you have sold, read usage, hold a client for non-payment and sign them in. Do not grant reseller.manage — a key pasted into a billing panel should never be able to rewrite your own payment-gateway credentials. One thing to do before your first order: sites your clients buy count against your own reseller plan's site allowance, so you need a plan with room in it. The module's connection test cannot tell you this — it reads your programme and provisions nothing, so it reports a healthy account that cannot yet sell. An order placed without an allowance is refused with a message that says exactly that. GPL-2.0-or-later, the same licence WHMCS's own module ecosystem uses, so you are free to read, modify and adapt any of this for your own installation. Authored by Neil Lock — CEO, Zinn Digital® Ltd. Do the modules cost anything? No. They are free to download and free to use, for ever, with no licence key and no per-installation fee. They are useful only if you are reselling Zinn® hosting, so the module is how we introduce ourselves rather than something we charge for. Which WHMCS versions are supported? The module declares WHMCS module API 1.1 and runs on PHP 8.2 or later, which covers every supported WHMCS release. It uses the standard provisioning-module interface — no core edits, no hooks into WHMCS internals and nothing to reapply after a WHMCS upgrade. Which Zinn® products can I sell through it? All of them. The product form takes any of our product lines — managed WordPress, footprint-free, application hosting, cloud servers, agency, reseller, managed databases and the rest — and the stack to build on each account, plus an optional application and PHP version. Anything the API sells, the module can order. I use Blesta, or my own in-house system. Download the PHP client. It is a single file with no dependencies and no panel assumptions: six methods that map onto the same six API calls the WHMCS module makes. If you are not writing PHP at all, the same calls are documented in our API reference and you can make them from anything. Does the module have privileged access to your platform? No, and that is deliberate rather than incidental. Every call it makes is a public, documented endpoint that any reseller can call with their own API key. If a module ever needed something the public API could not do, we would add the endpoint to the API rather than a back door to the module. How do I know the download has not been tampered with? Every archive is served over TLS from our own hostname, never redirected to a third-party host, and its SHA-256 checksum is printed beside the download link on this page. Compare it after downloading — on Linux or macOS, shasum -a 256 on the file; on Windows, certutil -hashfile with SHA256. ## Frequently asked questions **Do the modules cost anything?** No. They are free to download and free to use, for ever, with no licence key and no per-installation fee. They are useful only if you are reselling Zinn® hosting, so the module is how we introduce ourselves rather than something we charge for. **Which WHMCS versions are supported?** The module declares WHMCS module API 1.1 and runs on PHP 8.2 or later, which covers every supported WHMCS release. It uses the standard provisioning-module interface — no core edits, no hooks into WHMCS internals and nothing to reapply after a WHMCS upgrade. **Which Zinn® products can I sell through it?** All of them. The product form takes any of our product lines — managed WordPress, footprint-free, application hosting, cloud servers, agency, reseller, managed databases and the rest — and the stack to build on each account, plus an optional application and PHP version. Anything the API sells, the module can order. **I use Blesta, or my own in-house system.** Download the PHP client. It is a single file with no dependencies and no panel assumptions: six methods that map onto the same six API calls the WHMCS module makes. If you are not writing PHP at all, the same calls are documented in our API reference and you can make them from anything. **Does the module have privileged access to your platform?** No, and that is deliberate rather than incidental. Every call it makes is a public, documented endpoint that any reseller can call with their own API key. If a module ever needed something the public API could not do, we would add the endpoint to the API rather than a back door to the module. **How do I know the download has not been tampered with?** Every archive is served over TLS from our own hostname, never redirected to a third-party host, and its SHA-256 checksum is printed beside the download link on this page. Compare it after downloading — on Linux or macOS, shasum -a 256 on the file; on Windows, certutil -hashfile with SHA256. --- # Applications installed in one click, on our own servers URL: https://zinndigital.com/applications Every application on this page installs from your dashboard on our own servers, with its database created and its settings tuned for it. The list and the descriptions come straight from our installer, so what you see here is what you can install today. 27 applications, listed alphabetically. Popular choices The applications people most often come to us specifically to host. Every application Includes a database --- # Built to fit the books you already keep URL: https://zinndigital.com/accounting Your bookkeeper should not have to retype anything. Every invoice, credit note, payment and gateway fee we record can be downloaded in the shape Xero and QuickBooks import, for whatever period you ask for. What you can export Pick a date range and download it. Nothing is capped behind a bigger plan, and there is no extra charge for your own billing data. Sales invoices, with the customer, the date, the line description and the amount Credit notes as credit notes — not as negative invoices, which post to the wrong place Gateway fees, so what you actually received reconciles against what you were charged A complete period file with every document and every payment, for reconciling by hand Tax treatment carried on every line, ready for the day VAT registration applies Multi-currency throughout, with the exchange rate captured on the document itself What this is, and what it is not This is an export, not a live connection. We never link to your accounting account, we are never given access to it, and nothing is sent anywhere on its own — you download a file and import it yourself, when you choose. That is deliberate. A live sync writes into the ledger your accounts are filed from, where a mistake is corrected with a journal entry rather than a bug fix. We would rather hand your bookkeeper a file they can look at first. Who this matters to If you resell hosting, run an agency, or simply hand a folder to an accountant once a quarter, the question is always the same: will this fit my books? It will. And if your accountant wants something we do not produce yet, tell us — the format is ours to change, not a vendor's. ## Frequently asked questions **Do you integrate with Xero?** Not in the sense of a live connection, and we say so plainly. We produce files shaped for Xero's own imports, which your bookkeeper brings in themselves. We never connect to your Xero account and never see it. **Does it work with QuickBooks?** Yes. The same exports import into QuickBooks by mapping the columns during import, and the complete period file works with any package that accepts a CSV. **Are gateway fees included?** Yes, as a separate file, because a card or PayPal fee is an expense rather than part of a sale. Without it the money arriving in your bank never quite matches your invoices, which is the single most common reason a set of books will not balance. **What happens when you become VAT registered?** The tax rate on every exported line is a setting, not something baked into the software, so it changes on the day registration applies without waiting for a release. Every invoice already carries its own tax treatment. **Can I export more than one currency?** Yes. Amounts export in the currency the customer was charged, and each document keeps the exchange rate that applied when it was issued — so a closed period reports the same figures however rates move afterwards. **How far back can I export?** Any period you ask for. Invoices are never edited or deleted once issued, so a range you exported last year returns the same documents today. --- # Move your store to us, without losing your rankings URL: https://zinndigital.com/platform-transfer Replatforming is where most shops lose their search traffic — not because the products fail to copy across, but because every URL changes and nobody maps the old ones to the new. We do the data and the redirects together, by hand, and we check the result against your own pages before we hand it back. What “no SEO loss” actually means here It is not a promise, it is five things a person has to do — and our system will not let a migration be marked finished until all five are done. Every old URL mapped to its new one and served as a 301, so the links and rankings you already have keep working. Canonical tags checked on the new site, so two addresses for one page cannot split your authority. A fresh sitemap generated and resubmitted, so the new URLs are found in days rather than months. Product, review and article structured data carried across and validated, so rich results and AI answer engines still recognise your pages. A check against your own pages before handover — not a script that reports success and walks away. What comes across Products with their variants, options and images. Categories and collections. Customers, with their addresses and — where the source platform allows it — their passwords, so nobody has to reset. Orders with their line items and statuses, so your history and your reporting survive. Blog posts, pages and media. Where a platform will not release something, we say so before you pay, not after. What we will not claim We cannot move a design. Themes are built for the platform they run on, and anyone who tells you a Shopify theme can be copied to WooCommerce is describing a rebuild and calling it a migration. We also cannot move an app or a plugin — we can tell you which WooCommerce extension does the same job, and set it up. And we cannot promise your rankings will rise; what we can do is stop the drop that comes from broken URLs, which is the part that is actually in our control. Platforms we move stores from These are the ones with a page of their own. We handle more than sixty in total — if yours is not listed, ask us and we will quote it. ## Frequently asked questions **Will my shop go down while you move it?** No. We build the new store alongside the old one and you keep trading throughout. The only moment anything changes for your customers is the DNS switch at the end, which takes minutes and which you choose the timing of. **Will I lose my Google rankings?** Not from the move itself, provided the redirects are done properly — which is the part we will not sign off without. Your URLs change when your platform changes; a 301 from every old address to its new one is what tells Google the page moved rather than disappeared, and it carries the ranking with it. **What happens to my customers' passwords?** It depends on the platform you are leaving. Some release password hashes and we bring them across, so your customers never notice. Others do not release them at all, in which case we set up a password-reset flow and tell you in advance so you can warn people. We will tell you which case you are in before you pay. **How long does it take?** Five working days for a small catalogue, ten for a working shop, fifteen for a large or unusual one. Those are the packages, and the clock starts when we have access to your current store rather than when you order. **Can you move my design too?** Not as-is — a theme is written for one platform and does not port. We can rebuild it, and we will quote that separately so you can see what it costs and decide. Most shops take the move as the moment to refresh the design anyway. **What if something is missing after the migration?** Tell us and we fix it. The job is not marked complete until the redirect map, the canonical tags, the sitemap and the structured data have each been checked, and a specialist has walked your own pages — so a missing category or a broken product image is something we find before you do. --- # Renewable power where we can show it — and only there URL: https://zinndigital.com/sustainability Not offset after the fact, and not a pledge for 2030. Our servers in Finland and Germany run on renewable electricity today. For our United States and Singapore locations we have not verified the supply, so we make no claim for them. What we can actually show you Each of these is a fact about how our hosting is powered and operated, not a target. We have kept the list to things a sceptical reader can check. Hydropower on the servers we own and operate ourselves Zero water used for cooling on our own estate — air-cooled, on outside air alone for up to 98% of the year Facilities certified under EMAS, the European Union’s Eco-Management and Audit Scheme An eight-year average hardware lifespan through repair and reuse, with servers resold rather than scrapped What we will not claim We do not describe our hosting as carbon neutral or climate neutral, because it is not. Renewable electricity is a different claim from net-zero emissions, and the distance between the two is where most greenwashing lives. When the second one becomes true we will say so, and show the working. Why this is worth doing at all Data centres use a great deal of electricity, and increasingly a great deal of water. Choosing renewable supply, efficient facilities and air cooling is the part of that we control. Running hardware for eight years instead of three is the other part, and it matters more than most people expect. ## Frequently asked questions **Is Zinn Digital® hosting carbon neutral?** No, and we will not say it is. Our servers in Finland and Germany run on renewable electricity, which is a real and verifiable claim. Being carbon neutral is a much broader claim, and we cannot yet back it with evidence, so we do not make it. **What does renewable actually mean here?** The electricity supplied to our data centres in Finland and Germany comes from renewable generation, including hydropower. For our United States and Singapore locations we have not verified the supply, so we do not claim it there. **How efficient are the data centres?** They run at a power usage effectiveness of 1.1 to 1.2. A PUE of 1.0 would mean every watt reached the computers themselves, so this is close to the practical limit. **How much water does the cooling use?** On our own estate, none. Those facilities are air-cooled, and run on outside air alone for up to 98% of the year. Data centre water use is becoming the story that electricity was, so it is worth stating plainly. **Can I verify any of this independently?** Yes. Sites on our shared platform pass the Green Web Foundation's sustainability checks, which you can run yourself against any domain. Our own facilities are EMAS certified under the EU's Eco-Management and Audit Scheme. **What happens to old hardware?** It runs for about eight years — far longer than the industry norm — through repair and reuse, and is resold rather than scrapped when it finally comes out of service. Waste heat from those facilities is recovered to heat buildings. --- # Run client work where your clients can see it URL: https://zinndigital.com/boards A project board built for agencies and their customers. You keep the internal detail; they get a live view of progress, a place to ask, and a way to raise a request — from a link you paste anywhere. Automations, AI drafting, GitHub sync and a full API come with it. One board, two audiences Every other project tool makes you choose between a board your team can work on and a board your client is allowed to see. Zinn® Boards is one board with a visibility switch on every column, card and comment. Your notes, your blockers and your internal estimates stay yours; the client sees the stages, the work that is theirs to know about, and the questions you have asked them. That is the whole design, and it is why sharing is safe. A client link cannot show a client something you have not marked client-visible — the filtering happens in the database query, not in the interface, so there is no toggle anybody can get wrong at five to six on a Friday. Everything below is included in every paid tier. The free tier gives you one board to try it on. Share by link, no email Generate a copy-paste link and put it wherever your client already talks to you — WhatsApp, Slack, a message, an email you write yourself. We send nothing. A read-only link needs no account at all: they click, and the board opens. Links you can take back Every link expires, you can cap how many people may use it, and revoking one also removes anybody who joined through it. A link that went to the wrong channel is one click to undo. Client-visible by choice Columns, cards and comments each carry their own visibility. Mark a stage client-visible and they follow progress through it; leave a card internal and it does not exist as far as they are concerned. Questions and requests, in one place Ask the client a question against the card it belongs to and it waits for them on their board. Give them one intake column and they can raise a request without an email thread nobody can find later. Labels, archiving and a full history Label the way your team files work, and archive a board when the project ends rather than deleting it — the questions, the answers and the record of what was delivered stay readable. An archived board stops counting against your limit, so keeping your records costs you nothing. AI that drafts, summarises and tidies Turn a rambling client message into a card with a title and a body. Summarise a week of progress into something you can send. Ask what is stuck and why. Every change, attributed Who moved it, who commented, who answered, and when. The board keeps its own activity trail, and your client sees only the part of it that was theirs to see — so a question about what happened has an answer neither side has to remember. Full API and MCP Every board, card, comment and share link is drivable from our public API and from our MCP server — so an AI agent can read a board, add the work, move it and send the client a link, in one instruction. Three steps, and the third one is the point. Make a board Name it, point it at a client if it is theirs, and it arrives with a working pipeline. Rename the stages or keep ours. Do the work Cards, comments, checklists, due dates, labels. Mark what the client should see as you go, or leave everything internal and decide later. Send them a link One click makes a link. Paste it wherever they are. They open it and see exactly the board you meant them to see, on your branding, with no signup in the way. Flat monthly pricing per organisation. There is no per-seat charge and there never will be — inviting a client should not cost you anything, because inviting clients is the point. Free forever One board and five collaborators, on any account, with no hosting plan. Enough to run a real project and see whether this works for you. Every Agency Hosting and Reseller Hosting plan already includes Zinn® Boards at no extra cost — the board, the AI and the API. If you host with us, you may not need to buy this at all. Why we built it this way We host for agencies, and the same thing came up every time: the client wants to know where the work is, the agency does not want to show them everything, and the compromise is a weekly email somebody has to write. A board with per-item visibility removes the email without exposing the workshop. The invite link is the other half. Every tool that makes a client register an account before they can look at a picture of some cards is a tool the client stops opening. So the default link needs no account, grants read and nothing else, expires, and can be revoked along with anyone who used it. Does the person I send a link to need a Zinn® account? Not for a read-only link — they click it and the board opens, with no signup and no sign-in. They need a free account only to write: to comment, answer a question or raise a request. That takes one screen and the board is waiting on the other side. What can somebody with a link actually see? Exactly what your client sees in their own console, and nothing more. Internal columns, internal cards and internal comments are excluded by the database query that builds the page, so a link cannot leak something you did not mark client-visible. What happens if I paste a link in the wrong place? Revoke it. That kills the link and removes anybody who already joined the board through it, and it tells you how many people that was. Expiry is different on purpose: when a link simply ages out, people who already joined keep the board. Can I limit a link to one person? Yes — set it to single use and it stops working once somebody joins. You can also cap it at any number, and choose how long it lasts, up to three months. There is deliberately no never-expires option. Will my client see Zinn® branding? Not if you are on a plan with white-label branding. The shared board carries your name, your logo and your colour, and if a client does need to sign in they are sent to your own branded login rather than ours. Can I drive a board from code, or from an AI assistant? Yes. Every operation is in our public OpenAPI specification, with a generated TypeScript client, and there is an MCP server so an AI assistant can list boards, add and move cards, comment and create share links. It is included in Boards Business and in every Agency hosting plan. Does this replace Trello or Jira? For client-facing project work, yes — that is what it is for, and the per-item visibility and the no-account share link are things neither of those does. For a large internal engineering backlog it is not trying to be Jira, which is why the GitHub Projects sync exists instead. What happens to a board when a project ends? Archive it. The board, its history and every question and answer stay readable, and an archived board does not count against your board limit — so keeping your records costs you nothing. Start with one board, free No trial clock. Make a board, do a week of real work on it, and send your client a link. ## Frequently asked questions **Does the person I send a link to need a Zinn® account?** Not for a read-only link — they click it and the board opens, with no signup and no sign-in. They need a free account only to write: to comment, answer a question or raise a request. That takes one screen and the board is waiting on the other side. **What can somebody with a link actually see?** Exactly what your client sees in their own console, and nothing more. Internal columns, internal cards and internal comments are excluded by the database query that builds the page, so a link cannot leak something you did not mark client-visible. **What happens if I paste a link in the wrong place?** Revoke it. That kills the link and removes anybody who already joined the board through it, and it tells you how many people that was. Expiry is different on purpose: when a link simply ages out, people who already joined keep the board. **Can I limit a link to one person?** Yes — set it to single use and it stops working once somebody joins. You can also cap it at any number, and choose how long it lasts, up to three months. There is deliberately no never-expires option. **Will my client see Zinn® branding?** Not if you are on a plan with white-label branding. The shared board carries your name, your logo and your colour, and if a client does need to sign in they are sent to your own branded login rather than ours. **Can I drive a board from code, or from an AI assistant?** Yes. Every operation is in our public OpenAPI specification, with a generated TypeScript client, and there is an MCP server so an AI assistant can list boards, add and move cards, comment and create share links. It is included in Boards Business and in every Agency hosting plan. **Does this replace Trello or Jira?** For client-facing project work, yes — that is what it is for, and the per-item visibility and the no-account share link are things neither of those does. For a large internal engineering backlog it is not trying to be Jira, which is why the GitHub Projects sync exists instead. **What happens to a board when a project ends?** Archive it. The board, its history and every question and answer stay readable, and an archived board does not count against your board limit — so keeping your records costs you nothing. --- # Live chat that answers straight away and costs your pages nothing URL: https://zinndigital.com/live-chat A chat box for any website. It answers visitors straight away, hands the conversation to you when a person is needed, and emails you anything nobody picked up — and with the AI chat agent it answers from your own pages. The core is free, the plugin comes preinstalled on every WordPress site we host, and Premium is an upgrade when a site needs more. One chat box on every site, one inbox for all of them Zinn® Chat puts a small launcher in the corner of your website. A visitor opens it, asks a question and gets a reply in seconds — from the assistant, and from you when a person is needed. Add the AI chat agent and the assistant answers from your own pages. Every conversation, from every site you run, arrives in one inbox in your Zinn Digital® dashboard. It is sold on its own, so you do not need to host anything with us to use it: install the WordPress plugin, or paste one line of code into any other website. If you do host with us, Premium is already switched on for your account. Everything a small team needs to answer the people already on its website, without a second tool to learn. Answers first, and from your pages with the AI chat agent The assistant replies straight away and hands anything it cannot help with to you. With the AI chat agent on the site, it answers from what your website actually says and links to the page it used; when your pages have nothing to go on, it offers a person instead of guessing. Hands over to a person When the assistant cannot help, or the visitor asks for a person, the conversation is handed to you. As soon as you reply, the assistant steps back. Missed chats arrive by email When nobody is there, the visitor can leave an email address, and the whole conversation is emailed to you so you can reply later. One inbox for every site Conversations from all your websites land in one place in your dashboard, showing which page each visitor was on when they asked. Looks like your website Choose the colour, the corner it sits in, the name your visitors see and the first thing it says. On pages written right to left, it mirrors to suit them. Opening hours Set the days and hours you answer, in your own time zone. Outside them, visitors can leave their email address so you can reply when you are back. These are screenshots of the live product, not drawings of it. Built so your pages stay fast Most chat widgets add hundreds of kilobytes to every page, whether anybody opens them or not. This one was written to cost as close to nothing as a chat box can. About 9 KB on the page One small file, compressed, with no framework, no web fonts and no tracking. Measured from the exact file we serve. Loads after your page It waits until the browser has finished drawing your page, so it cannot hold up what your visitor came to see. No layout shift The launcher floats above your content, so nothing on your page moves when it appears. Sealed off from your styles Its styles live in a sealed box of their own, so your theme cannot break it and it cannot restyle your theme. It takes a few minutes, and nothing about your hosting has to change. Create your chat Sign up free, open Live chat in your dashboard, and add the web addresses the chat will run on. Add it to your website On WordPress, install the free Zinn® Chat plugin and paste in your chat key. On any other website, paste one line of code before the closing body tag. Answer from your dashboard Conversations arrive in your inbox as they happen, and anything you miss is emailed to you. Start free with no card. Upgrade a site to Premium when it needs more, whoever hosts it. On a WordPress site we host, the free plugin is already installed. Zinn® Chat The chat, the inbox, missed chats by email and the assistant, on any website, for as long as you like. Premium is priced per website, per month, on any website — hosted with us or anywhere else. The free Zinn® Chat plugin comes preinstalled on every WordPress site we host. Everything else on this page comes with both. Why it is fast, and why it is already on every site we host We host websites for a living, so we measure what every script costs a page. The chat widgets people were putting on the sites we host were among the heaviest things on them, and they were loading for every visitor, including the ones who never opened a chat. So we wrote one that does not. A website that answers its visitors keeps them, and a customer whose site keeps its visitors stays with us. That is why the free Zinn® Chat plugin comes preinstalled on every WordPress site we host, ready to switch on, and Premium is there when a site needs more. Put a chat on your website today Create a free account, add your website and start answering visitors in a few minutes. ## Frequently asked questions **Do I need to host my website with Zinn Digital® to use it?** No. Zinn® Chat works on any website. Create a free account, then install the WordPress plugin or paste one line of code into your site. On a WordPress site we host, the plugin is already installed, so you only switch the chat on. **What is the difference between Free and Premium?** Premium gives each site many more assistant answers a month, keeps conversations for as long as you want them, and lets you remove the “Powered by Zinn® Chat” line. The table above shows the exact figures. **Does the assistant make things up?** Without the AI chat agent it does not try to answer questions about your business: it replies, and brings in a person. With the agent it answers only from your own website's pages and links to the page it used, and when your pages do not answer the question it offers the visitor a person instead of guessing. **What happens when the monthly assistant answers run out?** The chat keeps working. New questions go straight to you instead of to the assistant until the month resets, and you can upgrade the site to Premium at any time. **Will it slow my website down?** It is built not to. The file is a few kilobytes compressed, it loads only after your page has finished drawing, and it cannot cause your layout to shift. **What if nobody is online to answer?** The visitor can leave an email address, and the conversation is emailed to the address you choose, so you can reply when you are back. You can also set opening hours, so the chat knows when your team is away. **Does it work on WordPress?** Yes. The free Zinn® Chat plugin adds the chat to your WordPress site — install it, paste in your chat key and switch it on. There is nothing to edit in your theme. **How is Premium billed?** Per website, per month, from your Zinn Digital® account, whoever hosts the website. Premium is an upgrade: it is not included with hosting. --- # WordPress site care with AI: malware clean-up, error logs, a safe database clean-up and tested updates URL: https://zinndigital.com/wordpress-site-care Site care in Zinn® SEO Pro finds malware and cleans it up, reads your error logs and says what to fix, clears out the database safely, writes small code fixes you approve and tries each update on a copy of your site before it goes live. Every change is backed up first, nothing is deleted, and everything can be undone in one click. ## Malware scan and clean-up Every WordPress, plugin and theme file is compared with the official copy, and your uploads, user accounts, settings and pages are checked for known malware, back doors, hidden administrators, injected scripts and spam links. Ask the AI about a file you are not sure of. Fix what you choose: a file goes to quarantine, a changed file is replaced by the official one, spam is removed from a page, and the site is checked again at once. ## Error logs read and explained Your PHP error log, debug.log and the fatal errors the plugin records are read for you. The same error is grouped into one line, the plugin or theme behind it is named, and the AI explains what it means and the best fix: an update, going back a version, a setting, switching a plugin off or a small code fix. Ask to hear about the next fatal error by e-mail. ## A safe database clean-up See what can go and how much space it takes before anything is removed: expired temporary data, old revisions, automatic drafts, spam and trash, data left behind by deleted pages and users, and old background tasks. The settings WordPress loads on every page are named with the plugin they belong to. It works in small batches, so a very large site stays fast. ## Small code fixes you approve When a problem needs code, the AI writes a small must-use plugin. It is checked against PHP and WordPress safety rules, you read it line by line, it is tested on requests your site sends to itself, and it runs only after you switch it on. If it ever causes an error it switches itself off, and you can remove it in one click. ## Safe updates Each waiting plugin, theme and WordPress update is checked against your WordPress, PHP, the plugins it needs and your WooCommerce, then tried on a copy of your site that visitors never see. Only what passes is installed, and after every update your pages are read again so a changed title, description or structured data is listed with before and after. ## The AI Update Guard: every update tried on a copy of your site first Open SEO, Safe updates in WordPress. Each plugin, theme and WordPress update is tried on a copy of your site that visitors never see, only what passes is installed, and an update that breaks your site is put back by itself. ### Checked before anything is tried Each waiting update shows Suits your site, Check first or Will not run here. It is checked against your WordPress and PHP, the plugins it needs, your WooCommerce, the PHP functions it calls and any version that already failed on your site. ### Tested on a copy of your site The new version and a copy of your database are set up where visitors never see them. Your home page, newest post and page, search, login, the dashboard and editor, your shop, cart and checkout, and the pages with forms are read with the version you have and with the new one. The copy is removed when the test ends. ### A plain-words report Each test says in one sentence whether the update passed, changed something or failed, then lists every page with what changed: an error, a page that stopped working, a form that is gone, a different layout or text, or what it tells search engines. PHP errors that came with the new version are listed with their file. ### Only what passes is installed The exact version that was tested is installed, the version before is kept, and your pages are read again at once. If anything broke, the version before goes straight back. An update that changed something asks you to confirm first. ### Put back by itself for 24 hours For 24 hours after every update, also the ones made on WordPress's Updates screen, a fatal error from the new version puts the version before back before the next page is built, and you get an e-mail. ### The AI explains a failed test and fixes it On a failed test, the AI says what went wrong and how to solve it. When a little code is the answer, it writes a fix for you to read and approve in Site care, Code fixes, and the update is tested again with it. About $0.002 per explained test on Zinn® credits, measured, or on your own AI provider's key, which your provider bills. ### On a schedule, if you want Test the waiting updates every day or week and install only the ones that pass, with one plain-words summary per round. While installs are automatic, WordPress's own automatic updates wait for the test. ## Backed up before every change Each change is recorded with its backup: the file as it was, the rows removed, the fields changed. Undo one change or a whole run from History and undo. ## Nothing is deleted Files go to quarantine. A file your site runs is moved only behind a before and after check of your home page, newest post, REST API and dashboard, and it is put back at once if the site stops answering. ## Your secrets never reach the AI Passwords, keys, tokens, e-mail and IP addresses and your server paths are masked before any code or log line is sent, and files such as wp-config.php and .env are never sent at all. ## A person approves every code fix You approve exactly the code you read. If it changes, you read it again, and AI agents connected to your site can never approve a fix for you. ## Fast on large sites too Measured on 16 October 2026 on a test site with 115,537 posts: the malware scan of 4,600 files and every post and setting took 8.5 seconds, the database preview 2.3 seconds, and the clean-up of old revisions, orphaned data and expired temporary data 19 seconds in background steps. Pages your visitors open stayed as fast as before. ## AI on your terms The AI's help runs on Zinn® credits, paid as you use it, or on your own AI provider's key. Requests are sent in batches to keep the cost down, and nothing is spent while your account is not in good standing. ## Rather have our team do it? If your site is already hacked and you would rather not touch it, our engineers can clean it up for you. You can order a clean-up from the Site care screen or from our malware clean-up page. ## Frequently asked questions **What does site care in Zinn® SEO Pro do?** It finds malware on your WordPress site and cleans it up, reads your PHP error logs and explains each error with the fix, cleans up the database safely, writes small code fixes you approve and tries each plugin, theme and WordPress update on a copy of your site before it is installed. It is part of Zinn® SEO Pro and works on any WordPress site, whoever hosts it. **Can a clean-up break my site?** Every change is backed up first and nothing is deleted: files go to quarantine. A file your site runs is moved only behind a check of your home page, newest post, REST API and dashboard, and it is put back at once if the site stops answering. You can undo one change or a whole run in one click. **Is my code or my password sent to the AI?** Only with your secrets removed. Passwords, keys, tokens, e-mail and IP addresses and your server paths are masked first, and files such as wp-config.php and .env are never sent at all. **What does the AI cost?** Site care comes with Zinn® SEO Pro. The AI's help runs on Zinn® credits, paid as you use it, or on your own AI provider's key, which your provider bills and we do not. Nothing is spent on credits while your account is not in good standing. **Does it replace a security plugin with a firewall?** No. A firewall blocks attacks as they happen; site care finds and cleans up what got in, and also reads your error logs, cleans up the database and fixes small code problems. You can run both on the same site. **Can AI agents use site care?** Yes. AI agents connected to your site through MCP can run scans, read the findings and clean up, with the permissions of the WordPress user they sign in as. Two things are kept for a person: approving a code fix and emptying the backups. **Can an update break my site while it is being tested?** No. The test runs on a copy of your site and its database that visitors never see, and the copy is removed afterwards. Only a version that passed is installed, and for 24 hours afterwards a fatal error from it puts the version before back by itself. --- # Zinn Digital® vs Kinsta: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/kinsta Entry plan against entry plan, read from Kinsta's own public pages on October 12, 2026. Where Kinsta does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Kinsta may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Kinsta ### Will you move my site from Kinsta? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Kinsta? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Kinsta? We read Kinsta's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Kinsta does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs WP Engine: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/wp-engine Entry plan against entry plan, read from WP Engine's own public pages on October 12, 2026. Where WP Engine does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. WP Engine may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from WP Engine ### Will you move my site from WP Engine? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave WP Engine? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with WP Engine? We read WP Engine's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything WP Engine does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs SiteGround: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/siteground Entry plan against entry plan, read from SiteGround's own public pages on October 12, 2026. Where SiteGround does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. SiteGround may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from SiteGround ### Will you move my site from SiteGround? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave SiteGround? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with SiteGround? We read SiteGround's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything SiteGround does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Hostinger: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/hostinger Entry plan against entry plan, read from Hostinger's own public pages on October 12, 2026. Where Hostinger does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Hostinger may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Hostinger ### Will you move my site from Hostinger? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Hostinger? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Hostinger? We read Hostinger's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Hostinger does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Cloudways: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/cloudways Entry plan against entry plan, read from Cloudways's own public pages on October 12, 2026. Where Cloudways does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Cloudways may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Cloudways ### Will you move my site from Cloudways? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Cloudways? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Cloudways? We read Cloudways's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Cloudways does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Bluehost: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/bluehost Entry plan against entry plan, read from Bluehost's own public pages on October 12, 2026. Where Bluehost does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Bluehost may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Bluehost ### Will you move my site from Bluehost? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Bluehost? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Bluehost? We read Bluehost's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Bluehost does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs DreamHost: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/dreamhost Entry plan against entry plan, read from DreamHost's own public pages on October 12, 2026. Where DreamHost does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. DreamHost may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from DreamHost ### Will you move my site from DreamHost? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave DreamHost? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with DreamHost? We read DreamHost's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything DreamHost does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs HostGator: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/hostgator Entry plan against entry plan, read from HostGator's own public pages on October 12, 2026. Where HostGator does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. HostGator may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from HostGator ### Will you move my site from HostGator? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave HostGator? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with HostGator? We read HostGator's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything HostGator does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs A2 Hosting: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/a2-hosting Entry plan against entry plan, read from A2 Hosting's own public pages on October 12, 2026. Where A2 Hosting does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. A2 Hosting may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from A2 Hosting ### Will you move my site from A2 Hosting? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave A2 Hosting? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with A2 Hosting? We read A2 Hosting's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything A2 Hosting does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Liquid Web: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/liquid-web Entry plan against entry plan, read from Liquid Web's own public pages on October 12, 2026. Where Liquid Web does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Liquid Web may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Liquid Web ### Will you move my site from Liquid Web? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Liquid Web? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Liquid Web? We read Liquid Web's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Liquid Web does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Nexcess: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/nexcess Entry plan against entry plan, read from Nexcess's own public pages on October 12, 2026. Where Nexcess does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Nexcess may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Nexcess ### Will you move my site from Nexcess? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Nexcess? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Nexcess? We read Nexcess's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Nexcess does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Pressable: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/pressable Entry plan against entry plan, read from Pressable's own public pages on October 12, 2026. Where Pressable does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Pressable may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Pressable ### Will you move my site from Pressable? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Pressable? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Pressable? We read Pressable's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Pressable does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs WPX: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/wpx Entry plan against entry plan, read from WPX's own public pages on October 12, 2026. Where WPX does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. WPX may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from WPX ### Will you move my site from WPX? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave WPX? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with WPX? We read WPX's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything WPX does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs o2switch: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/o2switch Entry plan against entry plan, read from o2switch's own public pages on October 12, 2026. Where o2switch does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. o2switch may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from o2switch ### Will you move my site from o2switch? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave o2switch? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with o2switch? We read o2switch's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything o2switch does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs LWS: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/lws Entry plan against entry plan, read from LWS's own public pages on October 12, 2026. Where LWS does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. LWS may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from LWS ### Will you move my site from LWS? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave LWS? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with LWS? We read LWS's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything LWS does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs IONOS: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/ionos Entry plan against entry plan, read from IONOS's own public pages on October 12, 2026. Where IONOS does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. IONOS may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from IONOS ### Will you move my site from IONOS? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave IONOS? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with IONOS? We read IONOS's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything IONOS does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Infomaniak: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/infomaniak Entry plan against entry plan, read from Infomaniak's own public pages on October 12, 2026. Where Infomaniak does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Infomaniak may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Infomaniak ### Will you move my site from Infomaniak? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Infomaniak? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Infomaniak? We read Infomaniak's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Infomaniak does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Gandi: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/gandi Entry plan against entry plan, read from Gandi's own public pages on October 12, 2026. Where Gandi does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Gandi may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Gandi ### Will you move my site from Gandi? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Gandi? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Gandi? We read Gandi's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Gandi does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs PlanetHoster: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/planethoster Entry plan against entry plan, read from PlanetHoster's own public pages on October 12, 2026. Where PlanetHoster does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. PlanetHoster may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from PlanetHoster ### Will you move my site from PlanetHoster? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave PlanetHoster? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with PlanetHoster? We read PlanetHoster's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything PlanetHoster does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs STRATO: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/strato Entry plan against entry plan, read from STRATO's own public pages on October 12, 2026. Where STRATO does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. STRATO may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from STRATO ### Will you move my site from STRATO? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave STRATO? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with STRATO? We read STRATO's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything STRATO does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs ALL-INKL.COM: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/all-inkl Entry plan against entry plan, read from ALL-INKL.COM's own public pages on October 12, 2026. Where ALL-INKL.COM does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. ALL-INKL.COM may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from ALL-INKL.COM ### Will you move my site from ALL-INKL.COM? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave ALL-INKL.COM? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with ALL-INKL.COM? We read ALL-INKL.COM's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything ALL-INKL.COM does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs netcup: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/netcup Entry plan against entry plan, read from netcup's own public pages on October 12, 2026. Where netcup does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. netcup may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from netcup ### Will you move my site from netcup? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave netcup? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with netcup? We read netcup's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything netcup does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Host Europe: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/host-europe Entry plan against entry plan, read from Host Europe's own public pages on October 12, 2026. Where Host Europe does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Host Europe may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Host Europe ### Will you move my site from Host Europe? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Host Europe? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Host Europe? We read Host Europe's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Host Europe does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs mittwald: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/mittwald Entry plan against entry plan, read from mittwald's own public pages on October 12, 2026. Where mittwald does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. mittwald may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from mittwald ### Will you move my site from mittwald? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave mittwald? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with mittwald? We read mittwald's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything mittwald does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs dogado: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/dogado Entry plan against entry plan, read from dogado's own public pages on October 12, 2026. Where dogado does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. dogado may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from dogado ### Will you move my site from dogado? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave dogado? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with dogado? We read dogado's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything dogado does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs webgo: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/webgo Entry plan against entry plan, read from webgo's own public pages on October 12, 2026. Where webgo does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. webgo may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from webgo ### Will you move my site from webgo? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave webgo? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with webgo? We read webgo's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything webgo does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs XServer: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/xserver Entry plan against entry plan, read from XServer's own public pages on October 12, 2026. Where XServer does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. XServer may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from XServer ### Will you move my site from XServer? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave XServer? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with XServer? We read XServer's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything XServer does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs ConoHa WING: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/conoha-wing Entry plan against entry plan, read from ConoHa WING's own public pages on October 12, 2026. Where ConoHa WING does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. ConoHa WING may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from ConoHa WING ### Will you move my site from ConoHa WING? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave ConoHa WING? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with ConoHa WING? We read ConoHa WING's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything ConoHa WING does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs ロリポップ！: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/lolipop Entry plan against entry plan, read from ロリポップ！'s own public pages on October 12, 2026. Where ロリポップ！ does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. ロリポップ！ may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from ロリポップ！ ### Will you move my site from ロリポップ！? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave ロリポップ！? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with ロリポップ！? We read ロリポップ！'s own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything ロリポップ！ does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs ColorfulBox: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/colorfulbox Entry plan against entry plan, read from ColorfulBox's own public pages on October 12, 2026. Where ColorfulBox does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. ColorfulBox may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from ColorfulBox ### Will you move my site from ColorfulBox? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave ColorfulBox? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with ColorfulBox? We read ColorfulBox's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything ColorfulBox does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs mixhost: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/mixhost Entry plan against entry plan, read from mixhost's own public pages on October 12, 2026. Where mixhost does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. mixhost may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from mixhost ### Will you move my site from mixhost? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave mixhost? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with mixhost? We read mixhost's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything mixhost does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs WEDOS: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/wedos Entry plan against entry plan, read from WEDOS's own public pages on October 12, 2026. Where WEDOS does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. WEDOS may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from WEDOS ### Will you move my site from WEDOS? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave WEDOS? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with WEDOS? We read WEDOS's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything WEDOS does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs FORPSI: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/forpsi Entry plan against entry plan, read from FORPSI's own public pages on October 12, 2026. Where FORPSI does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. FORPSI may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from FORPSI ### Will you move my site from FORPSI? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave FORPSI? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with FORPSI? We read FORPSI's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything FORPSI does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Active24: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/active24 Entry plan against entry plan, read from Active24's own public pages on October 12, 2026. Where Active24 does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Active24 may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Active24 ### Will you move my site from Active24? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Active24? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Active24? We read Active24's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Active24 does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Websupport: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/websupport Entry plan against entry plan, read from Websupport's own public pages on October 12, 2026. Where Websupport does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Websupport may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Websupport ### Will you move my site from Websupport? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Websupport? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Websupport? We read Websupport's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Websupport does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Endora: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/endora Entry plan against entry plan, read from Endora's own public pages on October 12, 2026. Where Endora does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Endora may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Endora ### Will you move my site from Endora? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Endora? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Endora? We read Endora's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Endora does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Webempresa: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/webempresa Entry plan against entry plan, read from Webempresa's own public pages on October 12, 2026. Where Webempresa does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Webempresa may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Webempresa ### Will you move my site from Webempresa? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Webempresa? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Webempresa? We read Webempresa's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Webempresa does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs dinahosting: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/dinahosting Entry plan against entry plan, read from dinahosting's own public pages on October 12, 2026. Where dinahosting does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. dinahosting may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from dinahosting ### Will you move my site from dinahosting? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave dinahosting? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with dinahosting? We read dinahosting's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything dinahosting does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Raiola Networks: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/raiola Entry plan against entry plan, read from Raiola Networks's own public pages on October 12, 2026. Where Raiola Networks does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Raiola Networks may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Raiola Networks ### Will you move my site from Raiola Networks? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Raiola Networks? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Raiola Networks? We read Raiola Networks's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Raiola Networks does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs cdmon: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/cdmon Entry plan against entry plan, read from cdmon's own public pages on October 12, 2026. Where cdmon does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. cdmon may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from cdmon ### Will you move my site from cdmon? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave cdmon? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with cdmon? We read cdmon's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything cdmon does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs BanaHosting: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/banahosting Entry plan against entry plan, read from BanaHosting's own public pages on October 12, 2026. Where BanaHosting does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. BanaHosting may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from BanaHosting ### Will you move my site from BanaHosting? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave BanaHosting? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with BanaHosting? We read BanaHosting's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything BanaHosting does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs TransIP: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/transip Entry plan against entry plan, read from TransIP's own public pages on October 12, 2026. Where TransIP does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. TransIP may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from TransIP ### Will you move my site from TransIP? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave TransIP? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with TransIP? We read TransIP's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything TransIP does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Hostnet: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/hostnet Entry plan against entry plan, read from Hostnet's own public pages on October 12, 2026. Where Hostnet does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Hostnet may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Hostnet ### Will you move my site from Hostnet? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Hostnet? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Hostnet? We read Hostnet's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Hostnet does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Mijndomein: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/mijndomein Entry plan against entry plan, read from Mijndomein's own public pages on October 12, 2026. Where Mijndomein does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Mijndomein may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Mijndomein ### Will you move my site from Mijndomein? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Mijndomein? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Mijndomein? We read Mijndomein's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Mijndomein does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs one.com: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/one-com Entry plan against entry plan, read from one.com's own public pages on October 12, 2026. Where one.com does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. one.com may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from one.com ### Will you move my site from one.com? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave one.com? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with one.com? We read one.com's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything one.com does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Antagonist: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/antagonist Entry plan against entry plan, read from Antagonist's own public pages on October 12, 2026. Where Antagonist does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Antagonist may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Antagonist ### Will you move my site from Antagonist? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Antagonist? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Antagonist? We read Antagonist's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Antagonist does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Vimexx: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/vimexx Entry plan against entry plan, read from Vimexx's own public pages on October 12, 2026. Where Vimexx does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Vimexx may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Vimexx ### Will you move my site from Vimexx? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Vimexx? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Vimexx? We read Vimexx's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Vimexx does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Aruba: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/aruba Entry plan against entry plan, read from Aruba's own public pages on October 12, 2026. Where Aruba does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Aruba may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Aruba ### Will you move my site from Aruba? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Aruba? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Aruba? We read Aruba's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Aruba does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Register.it: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/register-it Entry plan against entry plan, read from Register.it's own public pages on October 12, 2026. Where Register.it does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Register.it may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Register.it ### Will you move my site from Register.it? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Register.it? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Register.it? We read Register.it's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Register.it does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Keliweb: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/keliweb Entry plan against entry plan, read from Keliweb's own public pages on October 12, 2026. Where Keliweb does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Keliweb may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Keliweb ### Will you move my site from Keliweb? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Keliweb? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Keliweb? We read Keliweb's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Keliweb does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Serverplan: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/serverplan Entry plan against entry plan, read from Serverplan's own public pages on October 12, 2026. Where Serverplan does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Serverplan may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Serverplan ### Will you move my site from Serverplan? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Serverplan? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Serverplan? We read Serverplan's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Serverplan does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs iNET: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/inet Entry plan against entry plan, read from iNET's own public pages on October 12, 2026. Where iNET does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. iNET may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from iNET ### Will you move my site from iNET? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave iNET? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with iNET? We read iNET's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything iNET does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs P.A Việt Nam: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/pa-vietnam Entry plan against entry plan, read from P.A Việt Nam's own public pages on October 12, 2026. Where P.A Việt Nam does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. P.A Việt Nam may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from P.A Việt Nam ### Will you move my site from P.A Việt Nam? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave P.A Việt Nam? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with P.A Việt Nam? We read P.A Việt Nam's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything P.A Việt Nam does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Vietnix: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/vietnix Entry plan against entry plan, read from Vietnix's own public pages on October 12, 2026. Where Vietnix does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Vietnix may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Vietnix ### Will you move my site from Vietnix? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Vietnix? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Vietnix? We read Vietnix's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Vietnix does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Tenten: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/tenten Entry plan against entry plan, read from Tenten's own public pages on October 12, 2026. Where Tenten does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Tenten may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Tenten ### Will you move my site from Tenten? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Tenten? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Tenten? We read Tenten's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Tenten does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Mắt Bão: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/mat-bao Entry plan against entry plan, read from Mắt Bão's own public pages on October 12, 2026. Where Mắt Bão does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Mắt Bão may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Mắt Bão ### Will you move my site from Mắt Bão? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Mắt Bão? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Mắt Bão? We read Mắt Bão's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Mắt Bão does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs SuperHosting.BG: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/superhosting Entry plan against entry plan, read from SuperHosting.BG's own public pages on October 12, 2026. Where SuperHosting.BG does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. SuperHosting.BG may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from SuperHosting.BG ### Will you move my site from SuperHosting.BG? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave SuperHosting.BG? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with SuperHosting.BG? We read SuperHosting.BG's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything SuperHosting.BG does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Papaki: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/papaki Entry plan against entry plan, read from Papaki's own public pages on October 12, 2026. Where Papaki does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Papaki may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Papaki ### Will you move my site from Papaki? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Papaki? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Papaki? We read Papaki's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Papaki does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Top.Host: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/top-host Entry plan against entry plan, read from Top.Host's own public pages on October 12, 2026. Where Top.Host does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Top.Host may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Top.Host ### Will you move my site from Top.Host? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Top.Host? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Top.Host? We read Top.Host's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Top.Host does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs DNHOST: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/dnhost Entry plan against entry plan, read from DNHOST's own public pages on October 12, 2026. Where DNHOST does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. DNHOST may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from DNHOST ### Will you move my site from DNHOST? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave DNHOST? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with DNHOST? We read DNHOST's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything DNHOST does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Plus Hosting: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/plus-hosting Entry plan against entry plan, read from Plus Hosting's own public pages on October 12, 2026. Where Plus Hosting does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Plus Hosting may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Plus Hosting ### Will you move my site from Plus Hosting? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Plus Hosting? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Plus Hosting? We read Plus Hosting's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Plus Hosting does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs cyberfolks (Avalon): managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/avalon Entry plan against entry plan, read from cyberfolks (Avalon)'s own public pages on October 12, 2026. Where cyberfolks (Avalon) does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. cyberfolks (Avalon) may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from cyberfolks (Avalon) ### Will you move my site from cyberfolks (Avalon)? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave cyberfolks (Avalon)? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with cyberfolks (Avalon)? We read cyberfolks (Avalon)'s own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything cyberfolks (Avalon) does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs DotRoll: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/dotroll Entry plan against entry plan, read from DotRoll's own public pages on October 12, 2026. Where DotRoll does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. DotRoll may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from DotRoll ### Will you move my site from DotRoll? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave DotRoll? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with DotRoll? We read DotRoll's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything DotRoll does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Cafe24: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/cafe24 Entry plan against entry plan, read from Cafe24's own public pages on October 12, 2026. Where Cafe24 does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Cafe24 may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Cafe24 ### Will you move my site from Cafe24? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Cafe24? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Cafe24? We read Cafe24's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Cafe24 does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Exabytes: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/exabytes Entry plan against entry plan, read from Exabytes's own public pages on October 12, 2026. Where Exabytes does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Exabytes may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Exabytes ### Will you move my site from Exabytes? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Exabytes? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Exabytes? We read Exabytes's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Exabytes does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Rumahweb: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/rumahweb Entry plan against entry plan, read from Rumahweb's own public pages on October 12, 2026. Where Rumahweb does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Rumahweb may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Rumahweb ### Will you move my site from Rumahweb? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Rumahweb? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Rumahweb? We read Rumahweb's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Rumahweb does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Jagoan Hosting: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/jagoan-hosting Entry plan against entry plan, read from Jagoan Hosting's own public pages on October 12, 2026. Where Jagoan Hosting does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Jagoan Hosting may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Jagoan Hosting ### Will you move my site from Jagoan Hosting? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Jagoan Hosting? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Jagoan Hosting? We read Jagoan Hosting's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Jagoan Hosting does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs DomaiNesia: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/domainesia Entry plan against entry plan, read from DomaiNesia's own public pages on October 12, 2026. Where DomaiNesia does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. DomaiNesia may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from DomaiNesia ### Will you move my site from DomaiNesia? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave DomaiNesia? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with DomaiNesia? We read DomaiNesia's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything DomaiNesia does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Locaweb: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/locaweb Entry plan against entry plan, read from Locaweb's own public pages on October 12, 2026. Where Locaweb does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Locaweb may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Locaweb ### Will you move my site from Locaweb? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Locaweb? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Locaweb? We read Locaweb's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Locaweb does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs KingHost: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/kinghost Entry plan against entry plan, read from KingHost's own public pages on October 12, 2026. Where KingHost does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. KingHost may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from KingHost ### Will you move my site from KingHost? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave KingHost? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with KingHost? We read KingHost's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything KingHost does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs UOL Host: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/uolhost Entry plan against entry plan, read from UOL Host's own public pages on October 12, 2026. Where UOL Host does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. UOL Host may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from UOL Host ### Will you move my site from UOL Host? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave UOL Host? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with UOL Host? We read UOL Host's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything UOL Host does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs uPress: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/upress Entry plan against entry plan, read from uPress's own public pages on October 12, 2026. Where uPress does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. uPress may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from uPress ### Will you move my site from uPress? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave uPress? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with uPress? We read uPress's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything uPress does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs MilesWeb: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/milesweb Entry plan against entry plan, read from MilesWeb's own public pages on October 12, 2026. Where MilesWeb does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. MilesWeb may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from MilesWeb ### Will you move my site from MilesWeb? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave MilesWeb? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with MilesWeb? We read MilesWeb's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything MilesWeb does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs XeonBD: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/xeonbd Entry plan against entry plan, read from XeonBD's own public pages on October 12, 2026. Where XeonBD does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. XeonBD may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from XeonBD ### Will you move my site from XeonBD? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave XeonBD? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with XeonBD? We read XeonBD's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything XeonBD does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Turhost: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/turhost Entry plan against entry plan, read from Turhost's own public pages on October 12, 2026. Where Turhost does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Turhost may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Turhost ### Will you move my site from Turhost? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Turhost? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Turhost? We read Turhost's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Turhost does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Gabia: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/gabia Entry plan against entry plan, read from Gabia's own public pages on October 12, 2026. Where Gabia does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Gabia may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Gabia ### Will you move my site from Gabia? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Gabia? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Gabia? We read Gabia's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Gabia does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Dothome: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/dothome Entry plan against entry plan, read from Dothome's own public pages on October 12, 2026. Where Dothome does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Dothome may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Dothome ### Will you move my site from Dothome? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Dothome? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Dothome? We read Dothome's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Dothome does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Shinjiru: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/shinjiru Entry plan against entry plan, read from Shinjiru's own public pages on October 12, 2026. Where Shinjiru does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. Shinjiru may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Shinjiru ### Will you move my site from Shinjiru? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave Shinjiru? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Shinjiru? We read Shinjiru's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Shinjiru does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs ServerFreak: managed WordPress hosting compared URL: https://zinndigital.com/hosting/compare/serverfreak Entry plan against entry plan, read from ServerFreak's own public pages on October 12, 2026. Where ServerFreak does not publish something, we say so instead of guessing. Choose Zinn Digital® for LiteSpeed Enterprise on NVMe storage, daily backups, malware protection, staging and a CDN on every plan, support in 58 languages, servers in the EU and a team that moves your site for you. ServerFreak may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from ServerFreak ### Will you move my site from ServerFreak? Yes. Migration is free, with no limit on how many sites: move them yourself in minutes from your dashboard, or ask our team and we move them for you — free as well. ### Can I try Zinn Digital® before I leave ServerFreak? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with ServerFreak? We read ServerFreak's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything ServerFreak does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs SeekaHost: PBN hosting compared URL: https://zinndigital.com/hosting/footprint-free/vs/seekahost Entry plan against entry plan, read from SeekaHost's own public pages on October 12, 2026. Where SeekaHost does not publish something, we say so instead of guessing. Choose Zinn Digital® for an own CDN and own nameservers on every site, 106 footprints managed automatically, daily backups with Wayback restores, WordPress, static HTML or Joomla sites, and a network migration we do for you. SeekaHost may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from SeekaHost ### Will you move my network from SeekaHost? Yes. Send us the list of sites and our team moves the whole network for you, free. ### Can I try Zinn Digital® before I leave SeekaHost? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with SeekaHost? We read SeekaHost's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything SeekaHost does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Easy Blog Networks: PBN hosting compared URL: https://zinndigital.com/hosting/footprint-free/vs/easy-blog-networks Entry plan against entry plan, read from Easy Blog Networks's own public pages on October 12, 2026. Where Easy Blog Networks does not publish something, we say so instead of guessing. Choose Zinn Digital® for an own CDN and own nameservers on every site, 106 footprints managed automatically, daily backups with Wayback restores, WordPress, static HTML or Joomla sites, and a network migration we do for you. Easy Blog Networks may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Easy Blog Networks ### Will you move my network from Easy Blog Networks? Yes. Send us the list of sites and our team moves the whole network for you, free. ### Can I try Zinn Digital® before I leave Easy Blog Networks? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Easy Blog Networks? We read Easy Blog Networks's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Easy Blog Networks does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs Bulk Buy Hosting: PBN hosting compared URL: https://zinndigital.com/hosting/footprint-free/vs/bulk-buy-hosting Entry plan against entry plan, read from Bulk Buy Hosting's own public pages on October 12, 2026. Where Bulk Buy Hosting does not publish something, we say so instead of guessing. Choose Zinn Digital® for an own CDN and own nameservers on every site, 106 footprints managed automatically, daily backups with Wayback restores, WordPress, static HTML or Joomla sites, and a network migration we do for you. Bulk Buy Hosting may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from Bulk Buy Hosting ### Will you move my network from Bulk Buy Hosting? Yes. Send us the list of sites and our team moves the whole network for you, free. ### Can I try Zinn Digital® before I leave Bulk Buy Hosting? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with Bulk Buy Hosting? We read Bulk Buy Hosting's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything Bulk Buy Hosting does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs LaunchCDN: PBN hosting compared URL: https://zinndigital.com/hosting/footprint-free/vs/launchcdn Entry plan against entry plan, read from LaunchCDN's own public pages on October 12, 2026. Where LaunchCDN does not publish something, we say so instead of guessing. Choose Zinn Digital® for an own CDN and own nameservers on every site, 106 footprints managed automatically, daily backups with Wayback restores, WordPress, static HTML or Joomla sites, and a network migration we do for you. LaunchCDN may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from LaunchCDN ### Will you move my network from LaunchCDN? Yes. Send us the list of sites and our team moves the whole network for you, free. ### Can I try Zinn Digital® before I leave LaunchCDN? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with LaunchCDN? We read LaunchCDN's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything LaunchCDN does not publish is marked “Not published” instead of guessed. --- # Zinn Digital® vs PBN Pilot: PBN hosting compared URL: https://zinndigital.com/hosting/footprint-free/vs/pbn-pilot Entry plan against entry plan, read from PBN Pilot's own public pages on October 12, 2026. Where PBN Pilot does not publish something, we say so instead of guessing. Choose Zinn Digital® for an own CDN and own nameservers on every site, 106 footprints managed automatically, daily backups with Wayback restores, WordPress, static HTML or Joomla sites, and a network migration we do for you. PBN Pilot may still be the better fit if you already rely on its own tools, or need a plan larger than the entry plans compared here. Its current range is on its own pricing page. ## Questions about switching from PBN Pilot ### Will you move my network from PBN Pilot? Yes. Send us the list of sites and our team moves the whole network for you, free. ### Can I try Zinn Digital® before I leave PBN Pilot? Yes. Start a 14-day free trial with no card. Once you pay, a 30-day money-back guarantee applies. ### How did you compare Zinn Digital® with PBN Pilot? We read PBN Pilot's own public pricing and feature pages on October 12, 2026 and compared entry plan with entry plan. Every figure links to its source, and anything PBN Pilot does not publish is marked “Not published” instead of guessed. --- # PBN hosting compared URL: https://zinndigital.com/hosting/footprint-free/vs How Zinn Digital® Footprint-Free hosting compares with other PBN hosts on price per site, separation, footprints, backups and migration. Every figure is read from each host's own pages and dated. --- # SEO and Link Building from the Hosting Layer: A 2026 Operator's View URL: https://zinndigital.com/blog/seo-and-link-building-a-hosting-view Most SEO advice stops at the content and never asks what the site is served from. In 2026 the hosting layer decides more of your indexing and link equity than people admit — here is the honest version, with no magic and no guarantees. ## The infrastructure decides more of your SEO than you think SEO is usually discussed as if it were purely a content problem: write the right thing, target the right query, earn the right links. All of that matters, but it quietly assumes the page is served fast, renders without JavaScript, resolves reliably, and does not sit inside a pattern a search engine has learned to distrust. The moment any of those assumptions fails, good content underperforms for reasons that have nothing to do with the content — and those are all decisions made at the hosting layer. This is the honest framing we work from: hosting cannot make weak content rank, but it can stop good content being held back or thrown out. A crawler that hits a slow origin crawls fewer of your pages; a page that renders empty to a bot is invisible however good it reads to a human; a network that shares one IP range and one templated fingerprint gives a search engine a cheap reason to devalue the whole set. Getting the infrastructure right does not replace SEO — it removes the infrastructure-shaped ways SEO fails. ## Getting indexed, and staying indexed Indexing is treated as a one-time event — publish, request indexing, watch it appear — and that model has been wrong for years. Search engines routinely index a URL, hold it for a few weeks, then drop it when the page fails to justify the crawl budget it costs, with no notice and no action on your side. A page that ranked last month can be quietly gone this month. For a single site that is annoying; across a network where a few percent of URLs silently fall out every month, it is a slow, invisible bleed. The fix is to treat index status as a monitored signal, not a thing you spot-check by hand. Our platform runs automatic index checking across your sites and raises a drop alert when a URL falls out, so the transition from indexed to not-indexed surfaces as a notification within a day or two rather than at a quarterly audit. The workflow that follows matters: diagnose before you re-submit, because blindly re-indexing a page that was dropped for a reason — an accidental noindex, a soft 404, a canonical pointing elsewhere, thin or duplicate content — just gets it dropped again. Fix the cause, then request recrawl. ## Vet the domain before you build a link on it Half of a link-building problem is decided before any link is placed, at the point you choose the domain. An expired or auction domain can carry real authority or a history of spam, a manual action, a redirect chain, or a topic unrelated to what you intend to build. Building a money site or a network node on a poisoned domain, or pointing links at one, is the most expensive way to learn its history — so the vetting has to come first. Before you commit, pull the metrics and the history together: authority and backlink signals, the referring-domain profile, the anchor-text spread, and, critically, what the domain actually used to be. A domain with a clean, on-topic past that was genuinely indexed is worth far more than a high-number domain whose backlinks all point at pages that no longer exist. Our built-in domain checker and SEO metrics let you screen candidates inside the same dashboard you deploy from, so the vetting and the building are not two disconnected tools. ## Link building without leaving a footprint If you build or host a network to support your link building, the network itself is the risk. Links from a set of sites that all share one IP range, one nameserver, one CDN account and one templated fingerprint do not pass the value you want — they announce themselves as a network and invite the whole set to be devalued together. The link is only as good as the independence of the thing it comes from, and independence is a hosting property. Footprint-free design is the discipline of breaking that correlation at every layer at once: distributed, non-adjacent IPs, multiple DNS providers, a genuine multi-CDN pool rather than one shared account, per-site isolation, and stripping the on-site tells that group sites together — reapplied on every deploy rather than set once and left to drift. Our CDN and DNS account pools spread sites across many accounts and providers, our footprint remover cleans the on-site signals on each deploy, and you can bring your own aged accounts into the pool. We are candid about what this is: it is not a ranking trick, it is making each property stand on its own so the links it gives are judged on their merits rather than by the company they keep. ## The SEO tooling that actually helps There is an enormous amount of SEO software, and most of it overlaps. The parts that genuinely move an operator's day are narrow: knowing whether your pages are indexed and being told the moment they drop, being able to vet a domain's authority and history before you build on it, and having rank and audit data attached to the site rather than exported into yet another dashboard. Our SEO tools cover exactly that surface — automatic index checking, domain metrics, and rank and audit data — through a SEO-data layer that sits behind a swappable adapter, so the data source can change without your workflow changing. The reason it lives in the same place you deploy from is workflow, not bundling. When index status, domain vetting and site management are one surface, an agent can answer the question that actually matters for a network — which of my sites dropped out of the index this week — and open a ticket or trigger a recheck without you exporting CSVs from three tools and eyeballing them. Tooling helps when it shortens the loop between noticing a problem and fixing it; it does not help when it is one more screen to check. ## What hosting cannot do for your SEO It would be dishonest to end without the limits, because the infrastructure-shaped part of SEO is real but bounded. Hosting cannot write topical, genuinely useful content, and no amount of caching or isolation makes a thin or duplicate page deserve to rank. It cannot manufacture authority — a fast, clean, well-isolated site with nothing worth linking to still has nothing worth linking to. It cannot fix content that cannibalises itself, targets no real query, or ignores search intent. And it cannot promise rankings: anyone selling an SEO guarantee is selling you something they do not control. What hosting can do is make sure the pages that do have those qualities render fast, load cleanly, resolve reliably, stay indexed, and never carry an accidental noindex or a shared footprint that gets them devalued for reasons unrelated to their quality. Get the infrastructure honest and the content genuine, and the two stop working against each other. That is the whole claim — no more, and deliberately no less. ## Frequently asked questions **Does hosting really affect SEO?** Yes, but within limits. Hosting decides how fast your pages load, whether they render without JavaScript, how reliably they resolve, and whether a network of sites shares a footprint that gets it devalued — all of which affect crawling and indexing. It cannot make weak content rank or manufacture authority. The honest summary is that hosting removes the infrastructure-shaped ways good SEO fails; it does not replace the SEO. **How often should I check whether my pages are indexed?** Continuously, not on a schedule you run by hand. A page can be indexed one week and dropped the next with no action on your side, so the signal you want is the transition from indexed to not-indexed. Our automatic index checking watches your published URLs and raises a drop alert when one falls out, so you catch the loss within a day or two rather than at your next manual audit — then diagnose the cause before re-submitting. **Why does a link network's hosting footprint matter?** Because links from sites that share one IP range, one nameserver, one CDN account and one templated fingerprint announce themselves as a single network and invite the whole set to be devalued together. Footprint-free design — distributed IPs, multiple DNS providers, a real multi-CDN pool, per-site isolation, and on-site tells stripped on every deploy — makes each property stand on its own so its links are judged on their merits. It is not a ranking trick; it is removing an artificial reason to devalue them. **Can you guarantee my pages will rank?** No, and anyone who does is selling something they do not control. Rankings depend on content, intent, competition and authority — most of which sit outside hosting. What we can do is make sure pages that deserve to rank are served fast, render cleanly, resolve reliably, stay indexed, and never carry an accidental noindex or a shared footprint. We are deliberately clear about that boundary. --- # Making WordPress Fast and Secure: A Performance and Plugin Checklist URL: https://zinndigital.com/blog/wordpress-speed-security-and-plugins WordPress is only ever as fast and safe as what runs it. Here is the practical checklist we apply to every WordPress site we host — what to cache, what to secure, and which plugins earn their place versus the ones the platform makes redundant. ## WordPress is only as good as what runs it WordPress powers a large share of the web because it is flexible, but that flexibility is also how it gets slow and insecure: a default install queries the database dozens of times per page, broadcasts its version and stack to anyone who looks, and invites you to stack plugins until performance and attack surface both quietly balloon. None of that is a flaw in WordPress so much as a consequence of running it on infrastructure that does nothing to help. The good news is that the same handful of decisions fix most of it, and they are decisions about the stack rather than the content. Cache aggressively at the right layer, keep the database out of the hot path, run the few plugins that genuinely earn their place, keep everything patched, and isolate the site so a problem stays contained. This post is that checklist, in the order we apply it to every WordPress site on the platform. ## Cache at the server, not just in a plugin The biggest single lever on WordPress speed is not running WordPress at all for most visits. A standard request boots WordPress, runs your plugins and queries the database before it sends a byte; a full-page cache serves the finished page straight from the web server on the next hit, skipping that entire boot. Where that cache lives matters: a caching plugin sits inside PHP, so PHP still starts before the cache can answer, whereas a server-level cache answers earlier in the request and holds pages in a form the server can flush instantly. Every WordPress site we host runs on LiteSpeed Enterprise with server-level LSCache, and our own cache plugin wires WordPress to it correctly out of the box — pre-installed and auto-updated, so it is one less thing to configure or keep current. On a non-LiteSpeed origin the same plugin simply emits no full-page headers and stays out of the way while the object cache keeps working, so a migrated site is never left half-configured. The practical rule for your own checklist: one full-page cache, at the server, and do not stack a second caching plugin on top of it — they fight. ## The object cache and the database Not every request can be a static page. Logged-in sessions, the admin, search, carts and any personalised fragment have to run PHP, and for those the goal shifts from skipping the application to skipping the database. A per-site object cache — Redis, in our case — holds the results of repeated database reads in memory, so the same options, transients and lookups are not queried against the database on every hit. The effect shows up exactly where full-page cache cannot help: a faster admin, faster carts, and far lower database load under traffic. The word that matters is per-site. A shared object cache means one busy or badly-written site can evict everyone else's cached data and starve the database for its neighbours; a dedicated per-site cache, paired with per-site database limits, keeps that blast radius contained. On your checklist, treat a persistent object cache as non-optional for any site with logged-in users or a store, and be wary of hosting where it is shared across tenants. ## The plugins worth running — and the ones the platform replaces Every plugin you add is code that runs on requests and a door someone might one day walk through, so the honest goal is the fewest plugins that do the most. A good host removes the need for a whole category of them: with server-level caching, a managed object cache and platform backups, you do not need a caching plugin, a separate object-cache plugin, or a backup plugin — those jobs are done better below WordPress, and running them on top just adds conflict and overhead. What is left worth running is the small set that adds genuine capability: the plugins your site actually needs for its function, and — on our platform — the two repo-grade plugins we build and ship with every site. Our cache plugin connects WordPress to the server cache and handles smart purging so an edit clears only the pages it should. Our footprint plugin strips the tells a default WordPress install broadcasts — the version and generator tag, discovery endpoints, XML-RPC, pingbacks and the powered-by header — on every deploy, so a plugin or theme update cannot quietly put them back. Both are built to WordPress.org plugin-directory standards, are free, and update themselves. ## Keeping WordPress secure and current Most WordPress compromises are not clever; they are old. An out-of-date core, theme or plugin with a known, published vulnerability is the overwhelmingly common way sites get hit, which makes staying current the highest-value security work there is — and the most tedious, which is why it gets skipped. Managed hosting should take it off your plate: patching the stack beneath WordPress, and making core and plugin updates safe to apply by giving you a staging copy to test them on and a backup to roll back to. On top of currency, expect the boundaries to be enforced for you: malware scanning on by default so an infection is caught rather than discovered by a visitor, isolation so one compromised site cannot reach another, DDoS protection at the edge, and TLS everywhere with certificates renewed automatically. None of that replaces basic hygiene — strong credentials, least-privilege access, removing plugins you no longer use — but it means the infrastructure is not the weak link. On your checklist, the question for any host is simple: is security the default, or a bundle you buy? ## WooCommerce and the pages you must never cache A store is where aggressive caching earns its biggest win and does its worst damage if it is naive. The catalogue, product and category pages are the highest-traffic, most cacheable pages you have, and serving them from full-page cache is the single best thing you can do for a store's speed. But cart, checkout and account pages are personal and must never be served from a shared cache — do that and a shopper sees someone else's basket, which is both a broken store and a privacy failure. The way to have both is to cache the page and punch holes for the live parts. Edge Side Includes render the cart fragment, mini-cart totals and account state per request while the rest of the page is served from cache, and cart, checkout, my-account and any nonce or session pages are excluded by default. Freshness is handled by smart auto-purge that fires when a product, price or order changes, so a stale price never lingers. If you run WooCommerce, this is the part of the checklist to get exactly right: fast storefront from cache, live cart per user, nothing personal ever cached. ## Frequently asked questions **Do I still need a caching plugin like WP Rocket?** No. Full-page caching is handled at the web server by LiteSpeed's LSCache, our own cache plugin wires WordPress to it and handles smart purging, and a per-site Redis object cache sits behind it. Adding a second full-page caching plugin on top typically fights the server-level cache rather than helping, so it is neither needed nor recommended. **Which plugins does the platform make unnecessary?** Caching plugins, separate object-cache plugins and backup plugins are all redundant here, because those jobs are done below WordPress — server-level caching, a managed per-site object cache and platform backups. Removing them reduces conflicts and attack surface. What remains worth running is the plugins your site genuinely needs for its function, plus our two free cache and footprint plugins, which ship pre-installed. **Will caching break my WooCommerce cart or logged-in pages?** No. Cart, checkout, my-account and any nonce or session pages are excluded from cache by default, and Edge Side Includes keep the cart fragment and totals live on otherwise-cached pages. Shoppers always see their own basket and a working checkout while the storefront still loads from cache, and smart auto-purge clears affected pages when a product, price or order changes. **How do you keep WordPress secure without me managing it?** We patch the stack beneath WordPress, make core and plugin updates safe to apply with staging and one-click restore, run malware scanning and DDoS protection on by default, isolate each site so one compromise cannot spread, and issue and renew TLS certificates automatically. That removes the infrastructure as the weak link; basic hygiene like strong credentials and removing unused plugins is still on you. --- # How to Choose Managed Web Hosting in 2026: A Buyer's Guide URL: https://zinndigital.com/blog/choosing-managed-web-hosting-2026 Most hosting comparisons rank a spec sheet. What actually decides whether a host is good is what happens on the boring days — a migration, a restore, a traffic spike, a certificate that needs renewing — so this is a guide to buying for those. ## What “managed” should actually mean Almost everything calls itself managed hosting now, from a genuinely operated fleet to a cheap virtual machine with a control panel bolted on. The word has been stretched until it means very little, so it is worth pinning down. Managed should mean that the parts you do not want to think about — the web server, PHP versions, the database, caching, TLS certificates, security patching and backups — are run for you, correctly, by the host, and that when something goes wrong it is the host's problem to fix, not a support article pointing you at the command line. The test is not the feature list; it is who is accountable when the boring, load-bearing things break. On an unmanaged box a failed certificate renewal, a PHP upgrade that breaks a plugin, or a full disk is your 2am problem. On genuinely managed hosting those are handled before you notice, or handled for you when you report them. When you compare hosts, read past the adjectives and ask what the host actually operates versus what it merely gives you access to. ## Speed is a stack, not a checkbox Every host claims to be fast, and most back it with a single line item — SSD storage, or a bundled caching plugin. Real performance is a stack of layers that hand off to one another: a full-page cache at the web server so most visits never start PHP at all, an object cache so the requests that do run PHP do not hammer the database, a CDN edge so bytes travel a short distance to the visitor, and modern storage and transport underneath for the cache misses. Any one of those alone is a marketing bullet; together they are why one site feels instant and an identical site on a generic host does not. The thing to look for is whether these layers are the default on every plan or an upsell tier you have to assemble yourself. A host that ships server-level caching, a per-site object cache, NVMe storage and HTTP/3 as the baseline is making a different promise from one that sells you a fast plan and then a faster plan. It is also worth being clear about the division of labour: hosting owns time-to-first-byte and keeping the site fast under traffic, but the page's own weight — images, scripts, fonts — is yours. A host that claims to fix your Core Web Vitals entirely is overselling. ## Migrating in without downtime The single most revealing thing about a host is how it brings a site in. Migration is where cheap hosting quietly makes it your job: you get a knowledge-base article, an FTP login and a weekend. Good managed hosting does the migration for you, on a staging URL, so the copy is built and verified before a single visitor is affected — and only then is DNS moved across. Nothing should go dark while you wait for records to propagate. Ask the specifics before you buy. Will the host migrate existing sites for you, and at what cost? Can a site be built and tested on a temporary URL first, so you see it working before you commit the domain? How is the cutover handled — is there a window where the old and new sites disagree, or is it clean? We run migrations for you and let a site be verified on a temp URL before the domain is swung across, precisely because a migration that risks downtime is the kind of friction that keeps people on hosting they have outgrown. ## Backups, staging and being able to undo You will, at some point, break something — a bad plugin update, a botched edit, a theme change that looked fine and was not. What matters then is how quickly you can undo it, and that comes down to two features people underrate until they need them: automatic backups you can actually restore from in a click, and a staging environment where risky changes are tried before they touch the live site. Probe how real the backups are. Are they automatic and frequent, or something you must remember to trigger? Can you restore a single site quickly, or is it a support ticket and a wait? Is staging a genuine one-click copy of the live site that you can push back when you are happy, or a manual clone you assemble by hand? A host where staging and restore are first-class turns a broken change from a crisis into a shrug. ## Security and isolation that are on by default Security on shared hosting is decided by a boundary you never see: whether your site shares a filesystem and a process pool with its neighbours. When it does, one compromised or runaway site can reach across to the others, and a single spike can slow everyone on the box. Per-site isolation puts every site inside its own containment boundary so one site cannot touch another's files, processes or memory — which protects the sites you did not touch from the one that got hit. Beyond isolation, the baseline you should expect is unglamorous and non-negotiable: free TLS certificates issued and renewed automatically, malware scanning and DDoS protection on by default rather than sold as an add-on, and prompt patching of the stack. Certificates especially are a classic silent failure — a renewal that quietly stops working takes a site offline with a browser warning — so a host that owns certificate lifecycle end to end is removing a whole category of outage. Treat any of these being an upgrade, rather than the default, as a warning sign. ## Scaling from one site to a hundred The hosting that suits one site is often the worst possible fit for fifty, because the model does not scale: fifty logins, fifty manual setups, fifty places a footprint or a misconfiguration can creep in. If there is any chance you will run more than a handful of sites, buy for that from the start. Look for saved blueprints so a new site is a template rather than an afternoon, bulk operations so you act on many sites at once, and — if you run a network — genuine distribution across accounts and IPs rather than everything stacked on one. This is also where the platform underneath earns its keep. We host over 100,000+ PBN sites alongside mainstream managed WordPress on one engine, which means the same account can run a single blog or a large estate without changing tools, and an AI agent can drive the whole thing over our MCP server when the clicking becomes the job. Buying hosting that can only ever do the small version is how people end up migrating again a year later. Pick infrastructure that has headroom you are not yet using. ## Frequently asked questions **What is the difference between managed and unmanaged hosting?** On unmanaged hosting you are responsible for the operating system, the web server, PHP, the database, security patching, certificates and backups — the host only keeps the machine powered on. Managed hosting runs all of that for you and is accountable when it breaks. The honest test is who fixes a failed certificate renewal or a broken PHP upgrade at 2am: on managed hosting it is the host, ideally before you notice. **Will you migrate my existing site for me?** Yes. We run migrations for you and build the copy on a temporary URL first, so you can verify the site works before the domain is moved across — there is no window where the site goes dark waiting for DNS to propagate. Your first migration is included, which is deliberate: migration friction is the main reason people stay on hosting they have outgrown. **Do I need a separate caching or backup plugin?** No. Full-page caching is handled at the web server, a per-site object cache sits behind it, and automatic backups run at the platform level — so stacking a caching or backup plugin on top typically fights the built-in layers rather than helping. The point of managed hosting is that these are the default on every plan, not something you assemble from plugins. **How do I know if a host can scale with me?** Look past the headline plan at the operational features: saved blueprints so a new site is a template not a manual setup, bulk actions across many sites, real per-site isolation, and — if you run a network — distribution across accounts and IPs. We run a single blog and a large estate on the same engine, so growing does not mean migrating to a different product or a different tool. --- # Run Your Hosting From Your AI Tools: The Zinn Digital® MCP Server URL: https://zinndigital.com/blog/run-your-hosting-from-ai-tools-mcp Connect Claude, Cursor or ChatGPT to your account once, and let an agent provision sites, check indexing and move domains for you — safely, and inside your own permissions. ## Your hosting, drivable from the AI tool you already use Most hosting is still a point-and-click job: log into a panel, add a domain, wait, install WordPress, set the PHP version, copy a nameserver here, tick a box there. Fine for one site. Painful for fifty. If you run a network — we host 100,000+ PBN sites today — the clicking is the whole job. We took a different route. Zinn Digital® exposes a hosted MCP server, so the AI agent you already work in — Claude Code, Cursor, ChatGPT, Claude Desktop — can operate your account directly. You describe the outcome ("clone the store to staging, bump PHP to 8.3, deploy my branch"), the agent calls the same platform actions you would, and reports back. No new dashboard to learn, no scripting against a raw API. The tool you talk to becomes the tool that does the work. ## What an MCP server actually is MCP — the Model Context Protocol — is the open standard for connecting AI agents to real systems. It is what turns a chat window into something that can act. Instead of us building a bespoke plugin for every AI app that exists and every one that appears next year, we support the protocol once and every compliant agent can use it. An MCP server exposes three things. Tools are actions the agent can invoke — in our case, our full action catalogue: the exact same operations the dashboard and public API use, not a cut-down side channel. Resources are read-only context the agent can fetch before it acts: live site health, configuration, recent logs, metrics, uptime, account usage. Prompts are reusable workflow templates we publish, such as "diagnose this site" or "prepare a migration". Because the agent can read real state first and then act, it reasons about your actual sites, not a guess. ## How we expose it — OAuth, scopes and your own permissions Our MCP server is a thin protocol adapter sitting over the engine API. That matters for one reason: it inherits everything the API already enforces — your role-based permissions, tenant isolation via Postgres row-level security, and a full audit trail. The agent cannot reach data or actions your own login cannot. Connecting takes a minute. In the dashboard you open Connect AI tool, generate an MCP endpoint, and authorise it with OAuth 2.1 — the agent gets a token scoped to your organisation and your RBAC permissions, nothing broader. We hand you a paste-ready config snippet for Claude Code, Cursor, ChatGPT or Claude Desktop. Tokens are per-tool and revocable, with separate sandbox and production credentials, so you can let an agent experiment against a test scope before it ever touches live sites. There is a headless API-key option for your own automation too. The full connector spec lives on our MCP page at /ai-mcp. ## Workflow one — provision sites at scale Provisioning is where the time goes, and where an agent earns its keep. The Sites tools cover the whole lifecycle: create from a blueprint, migrate an existing site in, restore from a Wayback snapshot, clone to staging, push to live, restart, purge cache, take a static snapshot, delete. Blueprints are the multiplier — a saved template of plugins, theme and configuration — so "add these forty domains, each from my affiliate blueprint, WordPress with these plugins, PHP 8.3" is one instruction, not forty sessions. Because the platform runs long operations as durable, idempotent workflows underneath, a bulk provision that the agent kicks off will finish and self-heal on retry even if a step wobbles — it will not half-build a site and leave you guessing. The same catalogue lets an agent rebuild a lost site from an archived copy via /features/wayback-restore, or branch a live site into a safe copy through /features/staging before it changes anything. For our footprint-free line the agent also handles the network-specific setup — distinct IPs, CDN pool placement — that makes /hosting/footprint-free work at PBN scale. ## Workflow two — check indexing and move domains The SEO tools expose index status, rank data and audits through our SEO-data layer, so an agent can answer the question that actually matters for a network: "which of my sites dropped out of the index this week?" It fetches index state across the portfolio as a read-only resource, flags the drops, and — if you ask — opens a ticket or triggers a re-check. No exporting CSVs from three tools and eyeballing them. The same data powers our built-in SEO tooling at /seo-tools. Moving domains is the other classic time sink, and it is fully drivable. The Domains, DNS and SSL tools let an agent search and register domains, edit records, and issue or renew certificates; the platform's one-click change-domain and temporary-URL features mean a site can be built and verified on a temp URL before DNS resolves, then swung across cleanly. "Register this domain, point it at that site, issue the certificate, and add these TXT records" is a single conversational request. Bringing sites in from another host runs the same way through /features/migrations. ## Guardrails — an agent acting on live infrastructure Handing an AI the keys to production is only sane with real controls, so they are built in, not bolted on. Every MCP action is bounded by the connected identity's scopes — the agent can only do what you can do. Destructive or costly operations — delete, suspend, billing changes, large spend — require explicit confirmation or a human-approval policy; the agent cannot quietly wipe a site or buy an add-on. Rate limits and spend caps constrain AI-triggered paid actions specifically, and retries are idempotent so a hiccup never double-charges or double-provisions. Everything is logged. Every MCP call records the identity, the tool, the arguments and the result, feeding the same audit trail we keep for every privileged action. You can see exactly what your agent did, and revoke its token in one click if you change your mind. Staff use a separate internal MCP surface bounded by their own department role — the customer server never exposes ops tooling. Resellers get the same agent control across their client accounts via /hosting/agency, scoped by the tenancy hierarchy. ## Frequently asked questions **Which AI tools can I connect?** Any MCP-compatible agent. We publish paste-ready config for Claude Code, Cursor, ChatGPT and Claude Desktop, and because we support the open Model Context Protocol rather than a per-app plugin, new agents that adopt the standard work automatically. There is also a headless API-key option for your own scripts. **Can the AI do something destructive by mistake?** No. The agent is bounded by your own role-based permissions and tenant isolation, so it can never exceed what your login can do. Destructive or costly actions — delete, suspend, billing, large spend — require explicit confirmation or a human-approval policy, and spend caps plus rate limits constrain AI-triggered paid actions. Every call is fully audit-logged and every token is revocable in one click. **Is this the same as controlling my WordPress content with AI?** They are different surfaces. This MCP server is the platform control plane — provisioning, domains, DNS, SSL, backups, indexing and billing operations. Editing a site's own content over MCP ("write me an about page") is a separate per-site capability. This article is about running the hosting itself, not authoring the pages. **How do I connect it to my account?** In the dashboard, open Connect AI tool, generate an MCP endpoint, and authorise it with OAuth. You get a token scoped to your organisation and permissions, plus a config snippet to paste into your agent. Use a sandbox token to try it against a test scope first, then switch to production when you are comfortable. --- # What "footprint-free" PBN hosting actually means URL: https://zinndigital.com/blog/what-footprint-free-pbn-hosting-actually-means A footprint is any signal that links your sites to each other or to a hosting pattern search engines have learned to distrust — here is where those signals hide and how we design them out. ## A footprint is a correlation, not a single tell "Footprint-free" gets used loosely, so it is worth being precise. A footprint is any signal that lets a third party — a search engine, a competitor running a tool, a manual reviewer — group your sites together, or group them with a hosting pattern that is already associated with manipulation. Deindexing rarely comes from one damning artefact. It comes from correlation: a dozen sites that individually look fine but share the same generator tag, the same nameserver pair, the same /24, the same theme fingerprint and the same publishing cadence. Any one of those is noise. Stacked, they are a network. That reframes the whole problem. You are not hunting for a single thing to hide; you are trying to break correlation across every layer at once — the HTML the site emits, the network path it resolves through, the account that fronts it, and the blast radius it shares with its neighbours. Miss a layer and the others still line up. This is why bolting a CDN in front of a cheap shared box does almost nothing: it changes one variable while leaving the on-site fingerprint, the DNS pattern and the shared-fate isolation identical across the estate. ## On-site footprints: what the HTML gives away The cheapest footprints to detect are the ones a site announces in its own output. A default WordPress install broadcasts its version in a meta generator tag and in the query strings on its assets, links out to wp-json discovery endpoints and an XML-RPC interface, ships pingback headers, and returns an X-Powered-By header naming the stack. None of that is visible to a human reader, but all of it is trivially scriptable — you can fingerprint ten thousand sites for these tells in an afternoon. Our footprint remover strips exactly this surface on every deploy: the version and generator tag, the discovery links, XML-RPC, pingbacks and X-Powered-By all come off, so each site presents a clean, generic surface rather than a WordPress-shaped one. Because it runs as part of the deploy rather than as a one-time cleanup, a plugin update or a theme change cannot quietly reintroduce a header you thought you had removed. The point is not secrecy for its own sake — it is denying the cheapest, most scalable correlation signal there is. Theme and structure fingerprints matter too. A network where every site is the same theme with the same widget layout and the same footer text correlates on layout alone. Static-HTML delivery helps here: serving a site as flat HTML removes the live-stack tells entirely and lets each site's markup stand on its own. ## Network footprints: IPs, CDNs and DNS The layer most operators get wrong is the network. Hosting a hundred sites on one box puts them on one IP, in one /24, behind one reverse-DNS pattern — a textbook cluster. Spreading them across a handful of servers you own barely helps, because a small pool of IPs is still a pool. And routing everything through a single CDN account, or a single DNS provider, simply moves the cluster up a layer: now the correlation is the account, or the nameserver set, instead of the IP. Footprint-free network design means distribution across many accounts and many providers, not one. Our CDN and DNS account pools spread sites across multiple Cloudflare, bunny.net, CDN77 and KeyCDN accounts and across DNS providers including ClouDNS — and you can bring your own accounts into the pool as well. The distribution is recomputed from live account state at every deploy, so as the estate grows it does not quietly drift into a cluster on whichever account happened to be default. Origin IPs sit behind the CDN, so the server actually serving the content is never the thing a lookup returns. The word doing the work there is pool. A footprint-free network is not one clever hiding place; it is enough independent surfaces, assigned with enough intent, that no single account, nameserver or subnet accumulates a suspicious share of your sites. ## Why footprints must be managed per deploy, not set once Networks are not static. You add domains, retire others, migrate a batch in, change a theme, move a tier. Every one of those events is a chance for a footprint to creep back — a re-enabled XML-RPC endpoint, a new site landing on an over-used CDN account, a restored backup carrying an old generator tag. A footprint audit that was clean at launch is worthless six months and two hundred deploys later. This is why we treat footprint management as a property of the deploy pipeline rather than a checklist you run occasionally. The on-site removal, the account-pool balancing and the plugin baseline are reapplied every time a site is provisioned or changed, computed against the current state of the estate — not against a snapshot from setup. Balance is recalculated from live account data at each deploy, so the hundredth site is placed with full knowledge of where the previous ninety-nine went. Set-and-forget is the failure mode; continuous, per-deploy enforcement is the fix. ## Shared-fate isolation: the footprint of collapse There is a footprint that only shows itself under stress. If a hundred sites share one filesystem and one PHP pool, then one compromised site, one runaway process or one resource spike takes the neighbours down with it — and a whole subnet going soft-404 or slow at the same moment is itself a correlation signal, quite apart from the malware or the outage. Shared-fate hosting turns a single-site problem into a network-wide event. Per-site isolation puts every site inside its own containment boundary so one site cannot reach another's files, processes or memory, with malware scanning and DDoS protection on by default. That protects the sites you did not touch from the one that got hit, and it also means the estate does not fail as a block — which is both an availability property and, quietly, a footprint one. Caching plays a related role: with LiteSpeed Enterprise and a per-site object cache absorbing most traffic, a spike on one site rarely becomes a resource event that ripples outward in the first place. ## Bringing aged domains back without importing their footprint Aged expired domains are a staple of network building, and they carry their own footprint risk. Rebuilding one from a generic template throws away the very history that made the domain worth acquiring, and a cluster of expired domains all rebuilt on the same skeleton correlates on that skeleton. The cleaner approach is to restore the domain's original site from the Internet Archive and serve it as static HTML — the fastest route to getting an aged domain back online and re-indexed with its own real structure rather than a network-standard one. Restoring as static HTML has a footprint dividend too: there is no live CMS to fingerprint, no version to leak, no discovery endpoint to probe. The site presents as what it historically was. Combined with account-pool distribution and per-deploy on-site removal, a revived domain rejoins your network without inheriting the tells that would have grouped it with the rest of it. None of this is exotic. Footprint-free hosting is just the discipline of breaking correlation at every layer — HTML, network, account, isolation and history — and re-enforcing it on every change, at the scale of a real network rather than a handful of sites. ## Frequently asked questions **Does putting a CDN in front of my sites make them footprint-free?** No. A single CDN account in front of a shared server changes one variable — the IP a lookup returns — while leaving the on-site fingerprint, the DNS pattern and the shared-fate isolation identical across every site. Worse, routing a whole network through one CDN or DNS account just relocates the cluster to that account. Footprint-free design needs distribution across many accounts and providers, on-site removal, and per-site isolation working together, not a single proxy layer. **What on-site footprints does the footprint remover actually strip?** On every deploy it removes the WordPress version and generator tag, the wp-json discovery links, XML-RPC, pingbacks and the X-Powered-By header — the cheap, scriptable tells that let anyone fingerprint a WordPress estate at scale. Because it runs as part of the deploy rather than as a one-off cleanup, a plugin or theme update cannot quietly reintroduce a signal you had already removed. **Why does footprint management have to happen on every deploy?** Because networks change constantly — new domains, migrations, theme swaps, tier moves — and each change is a chance for a footprint to creep back or for a new site to land on an over-used account. A footprint audit that was clean at launch is meaningless after hundreds of later deploys. We reapply on-site removal, account-pool balancing and the plugin baseline on every provisioning event, computed against the live state of the estate rather than a setup-time snapshot. **Can I use my own Cloudflare or CDN accounts instead of your pool?** Yes. You can bring your own CDN and DNS accounts into the pool alongside ours, and distribution is still recomputed from live account state at every deploy so nothing drifts into a cluster. This suits operators who already hold aged or trusted accounts they want kept in rotation. --- # How we make WordPress fast: LiteSpeed Enterprise, LSCache and per-site Redis URL: https://zinndigital.com/blog/how-we-make-wordpress-fast-litespeed-lscache-redis The fastest WordPress request is the one that never runs — here is how our stack answers most visits from cache before PHP or MySQL is ever invoked, and what that means for Core Web Vitals. ## The fastest request is the one that never runs A standard WordPress request is expensive. The web server hands off to PHP, PHP boots WordPress, runs the plugins, queries MySQL a few dozen times, assembles HTML, and only then sends bytes back. On a busy site that whole dance happens for every visitor, and it is where almost all of your time-to-first-byte goes. Our answer is to make sure that, for most visits, none of it happens at all. Across the sites we host — over 100,000 PBN sites plus mainstream managed WordPress — the great majority of front-end page views are served as a pre-rendered full page straight from cache, without invoking PHP or touching the database. The rest of this post is about how the layers that make that true fit together, and where each one earns its place. The important framing is that these are not competing caches you pick between. Full-page cache, object cache and the CDN edge each catch a different class of request, and the value is in how they hand off to one another. ## LiteSpeed Enterprise + LSCache: the full-page layer Every site runs on LiteSpeed Enterprise with server-level LSCache. When a front-end response is cacheable, the web server stamps it with LiteSpeed cache-control and tag headers, and LiteSpeed serves the complete page directly on the next hit — no PHP process spawned, no MySQL query issued. That is the single biggest lever on WordPress TTFB, because it removes the entire application boot from the hot path. Because LSCache lives inside the web server rather than in a PHP plugin, it starts working earlier in the request lifecycle and holds pages in a form the server can flush instantly. A cache crawler keeps popular pages warm, so the first visitor after a purge is not the one who pays to regenerate the page. The result is a markedly lower and more consistent TTFB than a plugin-only cache bolted onto a generic stack, where the cache still sits behind PHP. Our own repo-grade cache plugin ships pre-installed and auto-updated on every site, wiring WordPress to LSCache correctly out of the box. On a non-LiteSpeed origin it simply emits no full-page headers and gets out of the way, while the object cache and exclusion rules keep doing their job — so a migrated site is never left in a broken half-configured state. ## Staying fast without serving stale: ESI and smart auto-purge Aggressive full-page caching has two classic failure modes: serving a logged-in user someone else's page, and serving anyone a page that should have changed. Both are solved at the caching layer rather than by caching less. ESI (Edge Side Includes) lets us cache the page while punching holes for the parts that must stay live. On a WooCommerce store the catalogue, product and category pages are served as full-page cache for the fastest possible TTFB, while ESI renders the cart fragment, mini-cart totals and account state per request. Cart, checkout, my-account and any nonce or session pages are excluded by default. Shoppers always see their own basket and a working checkout; everyone still gets the storefront from cache. Freshness is handled by smart auto-purge. Purge hooks fire automatically when content, products, prices or orders change, so the relevant cached pages refresh straight away rather than on a timer, and you can also purge on demand from the dashboard or from inside WordPress. Tag-based purging means editing one post clears that post and its archives — not the entire cache — so a single edit does not cold-start the whole site. ## Per-site Redis object cache: for what can't be a full page Not every request can be a static full page. Logged-in sessions, the WordPress admin, WooCommerce carts, search, and the dynamic fragments ESI leaves live all have to run PHP. For those, the goal shifts from 'skip the application' to 'skip the database'. Each site gets its own dedicated Redis object cache. WordPress caches the results of repeated database reads — options, transients, post and term lookups, WooCommerce product and session data — in memory, so the same query is not run against MySQL on every hit. The effect is most visible exactly where full-page cache cannot help: faster dashboards, faster carts, and far lower database load under traffic. The object cache is per-site, not shared, which matters for both performance and isolation. Combined with per-site database throttling, one site's heavy or badly-written queries cannot starve the database for its neighbours. You can read more about how the whole multi-layer setup fits together on our caching feature page, and about the boundaries between tenants under isolation. ## The edge and the transport underneath Cache that lives on the origin still has to cross the network. In front of the server sits the CDN edge, so static assets and cacheable pages are served from a point of presence near the visitor, and the origin stays quiet even under load. For our footprint-free hosting line the same edge is a multi-CDN pool spread across several providers, which serves a footprint goal as well as a performance one; on mainstream WordPress it is simply a fast, well-behaved layer that keeps origins idle. Underneath, the fundamentals are not skimped. Sites run on NVMe storage with HTTP/3, so the bytes the cache does send arrive over a modern, multiplexed transport with fast storage behind any cache miss. None of these layers is an add-on: LiteSpeed, LSCache, per-site Redis, NVMe and HTTP/3 are the baseline on every plan, not an upsell tier. ## What actually moves Core Web Vitals It is worth being precise, because hosting is often oversold on Core Web Vitals. TTFB is the part of the equation the server owns, and the caching stack above is what drives it down — a cached full page served over HTTP/3 from the edge is about as low as TTFB gets. Because TTFB is the leading edge of Largest Contentful Paint, a fast origin gives every downstream metric a head start it cannot otherwise have. But LCP, CLS and INP are mostly decided in the browser, by the page itself: an unoptimised hero image, render-blocking CSS and JavaScript, layout that shifts as fonts and ads load, and heavy main-thread work from plugins. No amount of server caching fixes a 2 MB hero or a theme that ships megabytes of JavaScript. Honest hosting makes the server contribution effectively free and consistent, then it is on the site to keep the front end lean. That division of labour is the useful mental model. We guarantee the request reaches the browser fast and stays fast under traffic; you keep the payload small and stable. Where the two meet — cache warm-up, edge delivery, and keeping the database responsive so dynamic pages do not stall — is exactly where our stack is tuned, and it is what makes managed WordPress on this platform quicker than the same site on a generic host. ## Frequently asked questions **Do I still need a caching plugin like WP Rocket?** No. Full-page caching is handled at the web server by LiteSpeed's LSCache, and our own cache plugin — pre-installed and auto-updated — wires WordPress to it correctly, with a per-site Redis object cache behind it. Stacking a second full-page caching plugin on top typically fights the server-level cache rather than helping, so it is not needed and not recommended. **Will caching break my WooCommerce cart or logged-in pages?** No. Cart, checkout, my-account and any nonce or session pages are excluded from cache by default, and ESI keeps the cart fragment and totals live on otherwise-cached pages. Shoppers always see their own basket and a working checkout while the storefront still loads from cache. **How does the cache stay fresh when I publish or edit?** Smart auto-purge fires on the relevant WordPress hooks, so publishing, editing content, or changing a product, price or order clears just the affected pages and their archives — not the whole cache — and a crawler warms them again. You can also purge on demand from the dashboard or from inside WordPress. **Can hosting alone give me perfect Core Web Vitals?** It gives you the best possible TTFB, which is the server's share and a head start for Largest Contentful Paint. But LCP, CLS and INP are largely decided by the page itself — image sizes, render-blocking assets, layout stability and main-thread JavaScript. Our stack makes the server contribution fast and consistent; keeping the front-end payload lean is what closes the rest of the gap. --- # Getting Pages Indexed and Keeping Them There: A 2026 Operator's Guide URL: https://zinndigital.com/blog/keeping-pbn-money-site-pages-indexed-2026 Indexing is not a one-time event — it is a state you maintain, and in 2026 the hosting layer decides as much of it as the content does. ## Indexing is a state you maintain, not a box you tick Most people treat indexing as a submit-and-forget step: publish the page, request indexing, watch it appear, move on. That model has been wrong for years and it is actively costly now. Search engines routinely index a URL, keep it for a few weeks, then quietly drop it when the page fails to justify the crawl budget it consumes. A page that ranked last month can be deindexed this month without any manual action, penalty notice, or change on your side. For anyone running a network, the maths is unforgiving. If three per cent of your URLs silently fall out of the index every month and you only spot-check by hand, you are always discovering the loss after the links have stopped passing value. The operators who keep networks healthy across 100,000+ PBN sites do not check indexing occasionally — they treat index status as a monitored signal, the same way you would monitor uptime or disk. The rest of this guide is about doing that deliberately rather than reactively. ## Check indexing continuously, and alert on the drop A one-off index check tells you whether a page is in the index today. It tells you nothing about tomorrow. The useful signal is the transition — the moment a URL that was indexed becomes not-indexed — because that is when a backlink stops counting and when a money-site page starts bleeding traffic. Catching that transition within a day or two is the difference between a quick fix and a slow, invisible decline. Our platform runs automatic index checking across your sites and raises a drop alert when a URL falls out, so the loss surfaces as a notification rather than a quarterly audit finding. The practical workflow is simple: let the checker watch every published URL, treat each drop alert as a triage item, and diagnose before you re-submit. Blind re-indexing of a page that was dropped for a reason — thin content, a soft 404, a canonical pointing elsewhere, a noindex left in a template — just gets it dropped again. Fix the cause first, then request recrawl. Common, fixable causes we see repeatedly: an accidental noindex or robots block shipped in a blueprint, pages that render empty to a crawler because the content needs JavaScript, near-duplicate pages competing for the same intent, and orphaned URLs with no internal links pointing at them. All of these are detectable, and all of them are cheaper to catch with a standing check than with a manual sweep. ## Vet the domain before you build on it Half of an indexing problem is decided before the first page is published, at the point you choose the domain. An expired or auction domain can carry real authority — or it can carry a history of spam, a manual action, a redirect chain, or a topic that has nothing to do with what you intend to build. Building a money site or a network node on a poisoned domain is the most expensive way to learn this. Before you commit, pull the metrics and the history together: authority and backlink signals, the referring-domain profile, the anchor-text spread, and — critically — what the domain actually used to be. A domain with a clean, on-topic past that was genuinely indexed is worth far more than a high-number domain whose backlinks all point at pages that no longer exist. Our built-in domain checker and SEO metrics let you screen candidates inside the same dashboard you deploy from, and our wider SEO tooling keeps that context attached to the site once it is live. ## Rebuild aged domains from the Wayback Machine When you buy an aged domain for its history, the fastest route back into the index is to give search engines the content they already knew at that URL. A domain whose original pages return 404s wastes most of its inherited authority — the backlinks point at addresses that resolve to nothing, and the crawler has no reason to treat the new site as a continuation of the old one. Wayback restore reconstructs the domain's original pages from public web-archive snapshots, so the historic URLs resolve to real content again and the inbound links land on live pages instead of error codes. That preserves the URL structure the backlinks expect, gives the crawler a coherent site to re-evaluate, and gets an aged domain productive in days rather than the weeks it takes to build out from scratch. Restore first to recover the equity, then edit and extend from a working base rather than an empty one. ## Footprint is an indexing signal now In 2026 the line between a footprint problem and an indexing problem has all but disappeared. A network that shares one IP range, one nameserver, one CDN account and one templated fingerprint does not just risk being classified as a network — it gives search engines a cheap reason to devalue and eventually stop indexing pages that would otherwise be fine. The isolation you build at the hosting layer is, in effect, part of your indexing strategy. This is the core of footprint-free hosting: every site should look like it stands alone. That means distributed, non-adjacent IPs, multiple DNS providers, a genuine multi-CDN pool rather than a single shared account, and per-site isolation so one site's configuration, cache and neighbours reveal nothing about the others. Our footprint remover strips the common tells that group sites together, our CDN pool spreads delivery across Cloudflare, bunny.net, CDN77 and KeyCDN with ClouDNS in front, and per-site isolation keeps each property independent at the compute level. None of this replaces good content — it stops good content being dragged down by the company it appears to keep. The same isolation that protects footprint also protects availability. A crawler that hits a slow or intermittently failing origin crawls less and indexes less; keeping each site fast and reliably reachable, behind cache, is a direct indexing input, not a nice-to-have. ## The signals that actually matter in 2026 Strip away the noise and the durable signals are unglamorous. Server-rendered content that a crawler can read without executing JavaScript still matters more than almost anything else — if the page is empty to a bot, nothing downstream helps. Fast, cached delivery keeps crawl budget flowing to your URLs instead of being spent waiting on a slow origin. Clean, stable URL structures with real internal linking give pages a reason to be re-crawled and kept. On top of that sit the content fundamentals that decide whether an indexed page stays indexed: genuine topical relevance, no near-duplicate cannibalisation, correct canonical and hreflang signals, and pages that answer a real query rather than pad a network. The hosting layer cannot manufacture those — but it can make sure the pages that have them render fast, load cleanly, resolve reliably, and never carry an accidental noindex or a shared footprint that gets them thrown out for reasons unrelated to their quality. Get the infrastructure honest and the content genuine, and staying indexed stops being a fight. ## Frequently asked questions **How often should I check whether my pages are indexed?** Continuously, not on a schedule you run by hand. A page can be indexed one week and dropped the next with no action on your side, so the signal you actually want is the transition from indexed to not-indexed. Our automatic index checking watches your published URLs and raises a drop alert when one falls out, so you catch the loss within a day or two rather than at your next manual audit. **My page was indexed and then dropped — what do I do first?** Diagnose before you re-submit. Blindly requesting re-indexing of a page that was dropped for a reason just gets it dropped again. Check for an accidental noindex or robots block, content that renders empty without JavaScript, a canonical pointing elsewhere, a soft 404, thin or duplicate content, and whether anything internally links to the page at all. Fix the cause, then request a recrawl. **Why restore an aged domain from the Wayback Machine instead of starting fresh?** An aged domain's value lives in its backlinks, and those links point at the domain's original URLs. If those URLs now return 404s, most of the inherited authority is wasted and the crawler has no reason to treat your new site as a continuation of the old one. Wayback restore rebuilds the historic pages from archive snapshots so the links land on live content and the URL structure the backlinks expect is preserved. **Does hosting really affect whether pages stay indexed?** Yes, in two ways. First, footprint: sites that share IP ranges, nameservers, a single CDN account and a templated fingerprint give search engines a cheap reason to devalue and deindex pages that would otherwise be fine, which is why distributed IPs, multiple DNS providers, a real multi-CDN pool and per-site isolation matter. Second, crawlability: server-rendered content, fast cached delivery and reliable origins keep crawl budget flowing to your URLs. Hosting cannot fix weak content, but it can stop good content being dropped for reasons unrelated to its quality. --- # AI & automation URL: https://zinndigital.com/blog/category/ai-automation Running and automating your hosting with AI. How to connect Claude, Cursor and ChatGPT to your account over the Model Context Protocol, drive provisioning, indexing and domains from an agent, and keep every automated action inside your own permissions and audit trail. Practical writing for operators who would rather describe an outcome than click through a panel fifty times. ## Posts in this topic - Run Your Hosting From Your AI Tools: The Zinn Digital® MCP Server (https://zinndigital.com/blog/run-your-hosting-from-ai-tools-mcp) --- # Hosting & performance URL: https://zinndigital.com/blog/category/hosting-performance How the stack is built for speed, and what actually moves the numbers. Server-level LiteSpeed caching, per-site Redis, ESI hole-punching, NVMe and HTTP/3 — plus a clear line between what hosting can guarantee (a fast, consistent time-to-first-byte) and what the page itself owns (LCP, CLS and INP). Deep dives for anyone who wants their WordPress genuinely fast rather than fast on a marketing slide. ## Posts in this topic - How we make WordPress fast: LiteSpeed Enterprise, LSCache and per-site Redis (https://zinndigital.com/blog/how-we-make-wordpress-fast-litespeed-lscache-redis) --- # PBN & footprints URL: https://zinndigital.com/blog/category/pbn-footprints Footprint-free network design for people who run sites at scale. Where the signals that group your sites together actually hide — on-site fingerprints, IP and CDN/DNS clustering, shared-fate isolation — and how to design them out on every deploy rather than once at launch. Honest, technical guides on building bulk networks that read as independent properties, from the team hosting 100,000+ PBN sites. ## Posts in this topic - What "footprint-free" PBN hosting actually means (https://zinndigital.com/blog/what-footprint-free-pbn-hosting-actually-means) - Getting Pages Indexed and Keeping Them There: A 2026 Operator's Guide (https://zinndigital.com/blog/keeping-pbn-money-site-pages-indexed-2026) --- # SEO & Link Building URL: https://zinndigital.com/blog/category/seo-link-building SEO, indexing and link building from a hosting operator's point of view. How the infrastructure layer decides as much of your indexing as the content does, how to keep pages indexed once they rank, how to vet aged domains before you build on them, and how to use the platform's built-in SEO tooling and footprint-free network capabilities honestly. No magic and no guarantees — just the parts we can actually influence. ## Posts in this topic - SEO and Link Building from the Hosting Layer: A 2026 Operator's View (https://zinndigital.com/blog/seo-and-link-building-a-hosting-view) --- # Web Hosting URL: https://zinndigital.com/blog/category/web-hosting General managed web hosting — the fundamentals done properly. Choosing a plan, migrating in without downtime, staging and backups, SSL and domains, and the day-to-day of running a fast, secure site on managed infrastructure. Written for owners and developers who want the hosting to get out of the way, whether they run one site or a hundred. ## Posts in this topic - How to Choose Managed Web Hosting in 2026: A Buyer's Guide (https://zinndigital.com/blog/choosing-managed-web-hosting-2026) --- # WordPress Hosting & Plugins URL: https://zinndigital.com/blog/category/wordpress Managed WordPress and the free, repo-grade plugins we build for it. Getting WordPress genuinely fast, keeping it secure and up to date, WooCommerce specifics, and how our own cache and footprint plugins wire a site to the platform correctly out of the box. Practical, no-hype guidance for running WordPress well at any scale. ## Posts in this topic - Making WordPress Fast and Secure: A Performance and Plugin Checklist (https://zinndigital.com/blog/wordpress-speed-security-and-plugins) --- # Domain prices URL: https://zinndigital.com/domains/pricing Registration, renewal and transfer prices for every extension we sell — all three on the same line, because the renewal price is the one you pay every year after the first. Search for an extension to see its price and the alternatives worth registering beside it. We sell 2,039 extensions. ## Prices by extension | Extension | Register | Renew | Transfer | | --- | --- | --- | --- | | .com | $16.99 | $14.99 | $14.99 | | .net | $21.99 | $16.99 | $16.99 | | .org | $11.99 | $15.99 | $15.99 | | .co.uk | $8.99 | $6.99 | $0.00 | | .co | $13.99 | $42.99 | $42.99 | | .io | $105.99 | $70.99 | $70.99 | | .xyz | $3.99 | $18.99 | $16.99 | | .online | $6.99 | $38.99 | $38.99 | | .shop | $6.99 | $42.99 | $42.99 | | .site | $49.99 | $38.99 | $38.99 | | .dev | $22.99 | $16.99 | $16.99 | | .app | $22.99 | $19.99 | $19.99 | | .store | $71.99 | $56.99 | $59.99 | | .tech | $84.99 | $69.99 | $69.99 | | .ai | $308.99 | $226.99 | $113.99 | | .5g.in | $9.99 | $5.99 | $5.99 | | .6g.in | $9.99 | $5.99 | $5.99 | | .aaa.pro | $314.99 | $177.99 | $177.99 | | .abc.br | $58.99 | $46.99 | $0.00 | | .abogado | $42.99 | $35.99 | $35.99 | | .abr.it | $24.99 | $4.99 | $5.99 | | .abruzzo.it | $24.99 | $4.99 | $5.99 | | .ac | $95.99 | $63.99 | $63.99 | | .ac.cn | $44.99 | $29.99 | $29.99 | | .ac.ke | $225.99 | $225.99 | $225.99 | | .ac.mu | $138.99 | $138.99 | $84.99 | | .ac.ni | $179.99 | $240.99 | $64.99 | | .ac.nz | $34.99 | $17.99 | $0.00 | | .ac.rw | $731.99 | $731.99 | $55.99 | | .ac.tz | $95.99 | $118.99 | $0.00 | | .ac.vn | $205.99 | $205.99 | $0.00 | | .aca.pro | $314.99 | $191.99 | $177.99 | | .academy | $30.99 | $59.99 | $59.99 | | .accountant | $53.99 | $28.99 | $28.99 | | .accountants | $61.99 | $140.99 | $140.99 | | .acct.pro | $314.99 | $177.99 | $177.99 | | .actor | $27.99 | $53.99 | $53.99 | | .ad | $158.99 | $158.99 | $79.99 | | .adm.ec | $56.99 | $27.99 | $27.99 | | .adult | $98.99 | $134.99 | $134.99 | ## Domain pricing questions **Why is the renewal price different from the first-year price?** Registries charge us a different wholesale price for a first registration than for a renewal, and on some extensions an introductory rate applies only to the first year. We show both prices on the same line so the price you pay every year after the first is never a surprise. **Are these prices per year?** Yes. Every figure is the price for one year. Most extensions can be registered for one to ten years at a time; the registry terms column shows the range for each one. **What does the transfer price cover?** Moving a domain to us from another registrar. For most extensions an inbound transfer also adds a year to the registration, so the transfer price buys both the move and a year. Where a registry does not work that way — .co.uk is the common example — the registry terms column says so. **Do I pay extra for WHOIS privacy?** WHOIS privacy is offered on every extension whose registry permits it, and its price is shown in your basket before you pay. A few registries publish registrant details by policy and cannot offer it at all; those extensions are marked in the registry terms column. **Are prices shown in my currency?** Yes. Prices are held in US dollars and converted for display using our stored exchange rates; the currency switcher in the header changes what you see. The amount you are charged is the converted price, exclusive of any tax that applies in your country. **Can I buy a domain without a hosting account?** Yes. Search for a name, add it to your basket and check out — we create your account at the end. Domains you register with us are managed alongside DNS, email and hosting if you later add them. --- # Register a .com domain URL: https://zinndigital.com/domains/com What a .com costs to register, renew and transfer, what the registry requires of you, and how to check whether the name you want is free. ## What a .com costs - Register: $16.99 - Renew: $14.99 - Transfer: $14.99 ## The .com registry's rules - Registration term: 1 to 10 years at a time - WHOIS privacy: Available on .com - Inbound transfer: Adds a year to the registration - Who may register: Anyone, anywhere --- # Register a .net domain URL: https://zinndigital.com/domains/net What a .net costs to register, renew and transfer, what the registry requires of you, and how to check whether the name you want is free. ## What a .net costs - Register: $21.99 - Renew: $16.99 - Transfer: $16.99 ## The .net registry's rules - Registration term: 1 to 10 years at a time - WHOIS privacy: Available on .net - Inbound transfer: Adds a year to the registration - Who may register: Anyone, anywhere --- # Register a .org domain URL: https://zinndigital.com/domains/org What a .org costs to register, renew and transfer, what the registry requires of you, and how to check whether the name you want is free. ## What a .org costs - Register: $11.99 - Renew: $15.99 - Transfer: $15.99 ## The .org registry's rules - Registration term: 1 to 10 years at a time - WHOIS privacy: Available on .org - Inbound transfer: Adds a year to the registration - Who may register: Anyone, anywhere --- # Register a .co.uk domain URL: https://zinndigital.com/domains/co.uk What a .co.uk costs to register, renew and transfer, what the registry requires of you, and how to check whether the name you want is free. ## What a .co.uk costs - Register: $8.99 - Renew: $6.99 - Transfer: $0.00 ## The .co.uk registry's rules - Registration term: 1 to 10 years at a time - WHOIS privacy: Available on .co.uk - Inbound transfer: Does not add a year — the .co.uk registry keeps the existing expiry date - Who may register: Anyone, anywhere --- # Register a .co domain URL: https://zinndigital.com/domains/co What a .co costs to register, renew and transfer, what the registry requires of you, and how to check whether the name you want is free. ## What a .co costs - Register: $13.99 - Renew: $42.99 - Transfer: $42.99 ## The .co registry's rules - Registration term: 1 to 10 years at a time - WHOIS privacy: Available on .co - Inbound transfer: Does not add a year — the .co registry keeps the existing expiry date - Who may register: Anyone, anywhere --- # Register a .io domain URL: https://zinndigital.com/domains/io What a .io costs to register, renew and transfer, what the registry requires of you, and how to check whether the name you want is free. ## What a .io costs - Register: $105.99 - Renew: $70.99 - Transfer: $70.99 ## The .io registry's rules - Registration term: 1 to 10 years at a time - WHOIS privacy: Available on .io - Inbound transfer: Does not add a year — the .io registry keeps the existing expiry date - Who may register: Anyone, anywhere --- # Register a .xyz domain URL: https://zinndigital.com/domains/xyz What a .xyz costs to register, renew and transfer, what the registry requires of you, and how to check whether the name you want is free. ## What a .xyz costs - Register: $3.99 - Renew: $18.99 - Transfer: $16.99 ## The .xyz registry's rules - Registration term: 1 to 10 years at a time - WHOIS privacy: Available on .xyz - Inbound transfer: Adds a year to the registration - Who may register: Anyone, anywhere --- # Register a .online domain URL: https://zinndigital.com/domains/online What a .online costs to register, renew and transfer, what the registry requires of you, and how to check whether the name you want is free. ## What a .online costs - Register: $6.99 - Renew: $38.99 - Transfer: $38.99 ## The .online registry's rules - Registration term: 1 to 10 years at a time - WHOIS privacy: Available on .online - Inbound transfer: Adds a year to the registration - Who may register: Anyone, anywhere --- # Register a .shop domain URL: https://zinndigital.com/domains/shop What a .shop costs to register, renew and transfer, what the registry requires of you, and how to check whether the name you want is free. ## What a .shop costs - Register: $6.99 - Renew: $42.99 - Transfer: $42.99 ## The .shop registry's rules - Registration term: 1 to 10 years at a time - WHOIS privacy: Available on .shop - Inbound transfer: Adds a year to the registration - Who may register: Anyone, anywhere --- # Register a .site domain URL: https://zinndigital.com/domains/site What a .site costs to register, renew and transfer, what the registry requires of you, and how to check whether the name you want is free. ## What a .site costs - Register: $49.99 - Renew: $38.99 - Transfer: $38.99 ## The .site registry's rules - Registration term: 1 to 10 years at a time - WHOIS privacy: Available on .site - Inbound transfer: Adds a year to the registration - Who may register: Anyone, anywhere --- # Register a .dev domain URL: https://zinndigital.com/domains/dev What a .dev costs to register, renew and transfer, what the registry requires of you, and how to check whether the name you want is free. ## What a .dev costs - Register: $22.99 - Renew: $16.99 - Transfer: $16.99 ## The .dev registry's rules - Registration term: 1 to 10 years at a time - WHOIS privacy: Not offered — the .dev registry publishes registrant details - Inbound transfer: Adds a year to the registration - Who may register: Anyone, anywhere --- # Register a .app domain URL: https://zinndigital.com/domains/app What a .app costs to register, renew and transfer, what the registry requires of you, and how to check whether the name you want is free. ## What a .app costs - Register: $22.99 - Renew: $19.99 - Transfer: $19.99 ## The .app registry's rules - Registration term: 1 to 10 years at a time - WHOIS privacy: Available on .app - Inbound transfer: Adds a year to the registration - Who may register: Anyone, anywhere --- # Register a .store domain URL: https://zinndigital.com/domains/store What a .store costs to register, renew and transfer, what the registry requires of you, and how to check whether the name you want is free. ## What a .store costs - Register: $71.99 - Renew: $56.99 - Transfer: $59.99 ## The .store registry's rules - Registration term: 1 to 10 years at a time - WHOIS privacy: Available on .store - Inbound transfer: Adds a year to the registration - Who may register: Anyone, anywhere --- # Register a .tech domain URL: https://zinndigital.com/domains/tech What a .tech costs to register, renew and transfer, what the registry requires of you, and how to check whether the name you want is free. ## What a .tech costs - Register: $84.99 - Renew: $69.99 - Transfer: $69.99 ## The .tech registry's rules - Registration term: 1 to 10 years at a time - WHOIS privacy: Available on .tech - Inbound transfer: Adds a year to the registration - Who may register: Anyone, anywhere --- # Register a .ai domain URL: https://zinndigital.com/domains/ai What a .ai costs to register, renew and transfer, what the registry requires of you, and how to check whether the name you want is free. ## What a .ai costs - Register: $308.99 - Renew: $226.99 - Transfer: $113.99 ## The .ai registry's rules - Registration term: 1 to 10 years at a time - WHOIS privacy: Available on .ai - Inbound transfer: Does not add a year — the .ai registry keeps the existing expiry date - Who may register: Anyone, anywhere