Technology
What's under the hood, no fluff.
We publish how our hosting works. Where a number isn't set yet we say so, and tell you when we'll publish it.
The platform
Six choices that make the difference.
nginx in front of everything
Pages are served by nginx with a full-page cache. PHP only works when it really has to.
Four cache layers
Full page (nginx), objects (per-site Redis), PHP code (OPcache) and static files on the CDN.
NVMe for files and database
NVMe disks on every server. Disk is often WordPress's bottleneck: here it's the fastest part.
Every site on its own
Redis, users and permissions are separate per site: a hacked site can't read the others' files.
A real mail server
Mail with antispam and antivirus, and sending goes through a dedicated service so it doesn't land in spam.
Try, check, roll back
When you update WordPress the panel checks that the site responds. If it doesn't, it rolls back.
Data and security
Where your data lives and how we defend it.
Encrypted, compressed copies
Copies are encrypted, deduplicated and kept on a different server. A copy also sits with a second provider.
Firewall and login blocking
A firewall on the server and an automatic block for anyone who gets the password wrong too often.
Antivirus file scanning
Site files are scanned and suspicious ones flagged.
Attack protection
Network anti-DDoS on the server and bot and abuse filtering on the CDN in front of your site.
Transparency
What we publish, and when.
We don't like «unlimited» with no written limits. Every number that matters ends up on a public page.
| What | Where to find it | When |
|---|---|---|
| CPU, RAM and process limits per plan | This page | Before launch |
| Supported PHP versions | This page | Before launch |
| Backup retention | Terms and this page | Before launch |
| Measured uptime and incidents | Status page | From launch, in real time |
| Speed tests, with method and data | This page | During the beta |
What isn't here yet
What we're still finishing.
Coming before launch
- SSH access and Git repositories
- Complete WordPress firewall
- Automatic Cloud scaling
- HTTP/3 on sites, to be confirmed after tests
We say it before you do
On the Comparisons page we put competitors' entries next to ours, even where they beat us, and mark our own features that aren't ready yet.
FAQ
Technology questions
How many visits can my plan handle?
It depends on how the site is built more than on the number of visits. CPU, RAM and process limits per plan will be written down before launch. Caching, the CDN and moving to Cloud exist precisely to handle peaks.
Which PHP version do you use? Can I change it?
We'll publish the list of supported versions before launch, and you'll be able to choose the version for each site from the panel.
Can I use FTP, SSH or Git?
Files are managed from the panel and WP-CLI is available. SSH and Git are coming before launch: you'll find them marked in the plan tables.
Do I need a caching plugin?
No. The server already has page caching (nginx), object caching (per-site Redis) and OPcache. A second caching plugin is usually unnecessary and can conflict: if you already have one, write to us.
What is a CDN and do I need to switch it on?
It's a network of nodes that serves pages and images from the point closest to the visitor. It's already included and switches on by itself when your domain points to us. See the Network page.
Can caching or the CDN break a shop's cart or checkout?
No. Catalogue pages are served from cache, but cart, checkout and account pages always stay dynamic, so nobody sees someone else's cart.
How do I make my WordPress site faster?
Start with light images, few plugins and a well-built theme: the server does the rest with caching and the CDN. Then measure with our free tools and compare before and after.
How often are backups made and how long are they kept?
Backups are daily, kept on a different server from your site, and you can take one on demand (on Grow and Geek). We write the retention period into the terms and on the Technology page before launch.
Want a look inside?
Write to us and we'll tell you how it's built, or try it with your own site.