HOSTING
MAXIMUM
- $75–300 a month
- data centres in Europe
High-load projects and traffic peaks: load balancing, the database on its own machine, extended protection, priority response to incidents. For stores where a sale takes an ordinary server down.
WHO IS IT FOR?
Three situations where hosting stops being a line on the invoice
- .01
THE PROJECT IS READY WITH NOWHERE TO PUT IT
The site or the service is built, and now it has to run somewhere. The choice gets made on price, because there is no way to tell one plan from another by its description. The difference surfaces later: at the moment something falls over, and it turns out that configuring the server, installing the certificates and working out the backups are down to you.
- .02
THERE IS HOSTING AND IT KEEPS CAUSING TROUBLE
The site goes down now and then, updates ship with the site offline, and support answers from a template a day later. Who has access to the server is a question with no clear answer. Hence the real loss: the developer, the host and whoever fixes things are three separate parties, and each of them explains that it is not their end.
- .03
THE PROJECT GREW, THE SERVER DID NOT
Traffic went up, the catalogue got heavier, and a sale or a mailing brings every user in at once. An ordinary plan copes right up until the first day like that. The problem is almost never raw power. It is how the load is spread, what gets served from cache, and what happens to the database at the peak.
WHAT'S INCLUDED
We do not build below this line
- - Dedicated servers in Europe.01
- - Attacks filtered at the edge.02
- - SSL certificates and their renewal.03
- - Daily backups.04
- - Round-the-clock monitoring.05
- - Updates with no downtime.06
- - A staging environment.07
- - Migration and setup.08
- - Renewals and billing handled by us.09
- THIS IS THE FLOOR, NOT A PACKAGE
Everything listed is part of every plan, the entry one included. The plans differ in power, traffic allowance and depth of protection — not in what they can do.
- ONE CONTRACTOR FOR ALL OF IT
The infrastructure is run by someone with twenty years behind them, alongside the same team that built the project. Nobody has to work out whose responsibility a thing is — the site’s, the server’s or the database’s.
- YOU CAN ALWAYS GO BACK
Every version of the site is kept separately. If an update goes wrong, rolling back to the previous one takes minutes rather than a restore from yesterday’s backup.
Keep it short and to the point
WHAT'S INSIDE
EUROPEAN DATA CENTRES, OUR OWN ARCHITECTURE
Projects live on dedicated servers in data centres in Germany, France and Switzerland — with industrial-grade connectivity, backup power and protection at the facility level. That is the part you cannot build yourself, and do not need to: what matters is what sits on top of it. The architecture we design and maintain ourselves rather than renting a ready-made control panel from a reseller. Which has a direct consequence: different power, a separate machine for a bot, the database on a host of its own — those get configured, instead of running into whatever the provider happened to allow for.
AN ATTACK STOPS BEFORE IT REACHES THE SITE
Traffic is filtered at the entrance to the infrastructure rather than on the server itself: what should reach the application does, and everything else is cut off earlier. The level of protection rises with the plan — on the higher configurations the load is spread across machines as well, so a spike never lands in one place.
AN UPDATE DOES NOT STOP THE WORK
A new version is rolled out alongside the old one and switched over once it is ready: users see neither a maintenance page nor an error. Every release is kept separately — going back to the previous one is possible at any moment. Next to it lives a staging environment: changes are checked there, not on the live site.
STATIC FILES AND THE DATABASE ARE KEPT APART
Images, files and pages are served from cache, and the database only does the thing it is actually there for. That is what decides the speed of a site on an ordinary day and its survival on the day of a sale — more than the number of cores in the plan.
CATEGORIES
Three levels. Yours is the one you recognise yourself in
STARTER
WHEN IS THIS YOUR CASE?
A site, a landing page, a corporate site or a small store with steady traffic. Everything basic, in full: dedicated resources, protection from attacks, certificates, daily backups, monitoring, updates with no downtime, a staging environment, migration and setup. Nothing stripped out — just without the headroom you do not need yet.
BOOSTED
WHEN IS THIS YOUR CASE?
A store or a service with constant traffic, where an hour of downtime is already counted in money. It adds power and traffic headroom, deeper attack filtering, faster delivery of static files and media, and a longer backup history. This is also where projects move when bots, integrations or internal services live alongside the site.
MAXIMUM
WHEN IS THIS YOUR CASE?
A project the business rests on: a large catalogue, thousands of users at once, sales and mailings that bring everyone in together. The load is spread across machines, the database moves to a host of its own, caching is tuned to your scenarios, and protection runs at its highest level. On top of that: priority response to incidents, and delivery from the region closest to the user when the audience is spread across countries.
FAQ
Answers to the most popular questions
$75, $150 or $300 a month depending on the plan. The difference is in power, traffic headroom and the level of protection; what the plans can do is the same across all three. Migration and setup are included in the price.
It depends on the load, not on the size of the company. A site with ordinary traffic, the entry plan. A store or a service people use every day, the boosted one. A project with a large catalogue, spikes from sales or an audience across several countries, the top one. We look at the project and say what is actually needed: selling you headroom for its own sake is a bad deal for us too.
Moving between levels happens with no migration and no downtime — it is the same infrastructure, only the resources change. We watch the load in monitoring and warn you in advance, rather than after the site has gone down.
Yes, the migration and the setup are on us. What we need from you is access to the current host and the domain. The old site keeps running until the new one has proved itself — the switch happens once everything has been checked.
Yes. We look at what the project is built on and tell you what moves across as is and what will need work. If a project is technically incompatible with our infrastructure, we say so before the migration rather than during it.
Filtering runs at the entrance to the infrastructure, before your server: ordinary attacks are cut off automatically and invisibly to users. For the unusual ones a person steps in and the rules are tuned to that particular attack. Nobody has absolute protection, which is why the backups and the ability to roll back are always there alongside.
We do. Monitoring usually sees the problem before you notice it. From there it is either a rollback to the previous version, a restore from a backup, or working it out on the spot. The separate advantage is that the people fixing it wrote the code: nobody has to explain to an outsider how the project is put together.
No. The project stays yours, the sources are yours, and it can be moved to another host at any point — we will help with the export. There is no minimum-term contract: you pay by the month, for as long as it makes sense to you.