Provisioning & hardening
- Compute sized to measured traffic, not a guess
- Minimal OS image, SSH keys only, root login disabled
- Host firewall + fail2ban + kernel live-patching
- Tuned Nginx, HTTP/2 + HTTP/3, Brotli compression
You do not get a control panel and a knowledge base. You get a team that provisions, hardens, monitors, patches, backs up and scales your infrastructure, and answers when it matters.
The word "managed" is used loosely in this industry. This is the exact list of what we take responsibility for on every plan, starting with Core.
Resources are dedicated to you from Scale upwards. Core runs in an isolated container on managed compute that we never oversell.
| Specification | Core | Scale | Ecosystem |
|---|---|---|---|
| Compute | 2 vCPU · 4 GB, isolated container | 4 vCPU · 8 GB, dedicated | 8+ vCPU · 32 GB, multi-node pool |
| Storage | 40 GB NVMe | 160 GB NVMe | 500 GB NVMe, expandable |
| Architecture | Single node | Single node + managed DB | Load-balanced app tier, separate DB, failover |
| Production sites | 1 | Up to 5 | Unlimited |
| Transfer | 1 TB / mo + CDN | 5 TB / mo + CDN | Unmetered fair use + CDN |
| Staging environment | On request | Included, per site | Included, plus preview per branch |
| Backups | Daily · 14-day retention | Hourly · 30-day retention | Point-in-time · 90-day retention |
| Monitoring | 60 s · 3 regions | 60 s · 6 regions + real-user | 30 s · 6 regions + real-user + synthetic journeys |
| Uptime SLA | 99.9% | 99.9% | 99.99% |
| Regions | EU (Germany, Finland, Netherlands), Middle East (UAE, Bahrain) and US on request. Data residency honoured per client. | ||
Full feature comparison, including the engineering and growth layers, is on the plans page →
An expired domain or a mail server on a blocklist does more damage than any outage. We treat both as infrastructure, with monitoring and ownership rules to match.
p=reject, with DMARC reports monitoredSmall and mid-size businesses are breached through boring things: an un-patched plugin, a reused admin password, a backup that was never tested. The model below is built around those boring things.
Managed rulesets against OWASP top-10 patterns, bot filtering, rate limiting on login and API routes, DDoS absorption before traffic reaches your origin.
TLS 1.2+ only, modern ciphers, HSTS, OCSP stapling, certificates issued and renewed automatically and monitored for expiry.
Origin accepts traffic only from the CDN, SSH by key via bastion, automatic security updates, intrusion detection, immutable container images.
Dependency and CMS updates tested on staging then promoted, weekly vulnerability scans, malware scanning and file-integrity monitoring on Scale and above.
2FA enforced on every admin panel, role-based access, shared credential vault, quarterly access review, SSO on Ecosystem.
Encrypted off-site backups, scheduled restore drills, documented recovery time and recovery point objectives, tested failover on Ecosystem.
We have moved sites off shared cPanel hosts, page builders, agency servers and abandoned cloud accounts. The process is the same every time and the cut-over happens at DNS, so nobody notices.
Every domain, record, mailbox, database, cron job and integration documented before anything moves.
The full stack is rebuilt on new infrastructure and tested against production data behind a private hostname.
Final delta sync of files and databases, DNS TTLs lowered 48 hours in advance, email cut-over coordinated separately.
DNS switched, old host kept warm for 14 days as a fallback, monitoring watched closely for 72 hours.
By default in the EU, in Germany or Finland, with the CDN serving cached content from the edge closest to each visitor. Middle East regions are available for clients with data-residency requirements, and US regions on request. You choose at onboarding and we document it.
WordPress and WooCommerce, yes, with a hardened configuration and a strict update policy. Static sites, Next.js, Laravel, Django and containerised applications, yes. Shopify and other hosted platforms are not hosted by us, but we build, integrate and operate the rest of the ecosystem around them, including DNS, email, analytics and headless storefronts.
We provision on Hetzner and DigitalOcean for most workloads, AWS where a client needs specific managed services or regions, and Cloudflare for DNS, CDN and the web application firewall. We choose per client and the account is opened in your name. Our stack page lists everything.
On Scale and Ecosystem, yes: the virtual machines are yours alone. Core runs in an isolated container on compute that we size conservatively and never oversell; it is not shared cPanel hosting with hundreds of neighbours.
Every account is already in your name, so you revoke our access. We hand over a current credential vault, an infrastructure document and a full export, and keep the old environment available for 30 days after cancellation. There is no exit fee. See the refund and cancellation policy.
Yes. Every plan is hosting and operations first; the build and the growth layer are included because clients almost always need them, but if you already have a site and a team you can use Core or Scale purely as managed infrastructure. Tell us on the order form.
We read your DNS, hosting, TLS, email configuration and site performance and send back a written report. No access needed for the first pass.