Understack
Let’s talk about a project

Managed hosting

You hand it to the client. The server stops being your problem.

Managed hosting for agencies, on a stack tuned for WordPress: dedicated servers, configured and maintained by the people who build the sites. Updates, backups and monitoring handled, not sold as an add-on.

Request a quote
A layered hosting infrastructure — HTTPS, nginx, PHP, database, with cache, monitoring and backups — becomes the nginx configuration file, and then the client's site online with its numbers: response time, HTTP/2, HTTPS grade and uptime. infrastructure — client.com Let’s Encrypt · HTTPS nginx · HTTP/2 PHP-FPM 8.2 MariaDB 11 Cache FASTCGI Monitoring EVERY MINUTE Backup EVERY NIGHT client.com RIGHT NOW RESPONSE 118 ms PROTOCOL HTTP/2 HTTPS A+ UPTIME 99.98% RESPONSE TIMES · 24 HOURS client.conf 1 2 3 4 5 6 7 8 9 10 11 12 13 server { listen 443 ssl http2; server_name client.com; ssl_certificate /etc/letsencrypt/live/client.com/fullchain.pem; root /var/www/client.com/public; location / { try_files $uri $uri/ /index.php?$args; } location ~ \.php$ { fastcgi_pass unix:/run/php/php8.2-fpm.sock; fastcgi_cache WORDPRESS; } }

Half the performance is decided before the code reaches the browser.

You can write the cleanest markup in the world: if the server answers in eight hundred milliseconds, the score stays red anyway. Time to first byte, compression, cache, PHP version, database memory are infrastructure choices, and they are half of what your client sees. On shared hosting someone else already made them, identically, for thousands of sites unlike yours.

This site runs on a machine configured that way. The numbers on the home page were taken from it.

What managed hosting for agencies includes

Not a control panel to learn: a service that does what you would do yourself, if you had the time.

  • 01

    A stack tuned for WordPress

    Not a generic server with WordPress installed on top. PHP, object cache, page cache and database are configured for how WordPress actually works: the difference between hosting that stores and hosting that accelerates.

  • 02

    Dedicated server

    One machine for your agency or for a single project, sized on real traffic. No neighbours you have never heard of and cannot control.

  • 03

    A panel for your agency

    The area where your team manages every site it has handed us: status, backups, access. It is for you, not for your clients — you keep talking to them yourself, as before.

  • 04

    Updates, security and certificates

    Operating system, PHP, WordPress, plugins and HTTPS updated and renewed by us, with a check after every change. You do not get a notification: you get the work done.

  • 05

    Daily backups, actually restored

    One full copy a day and, above all, restores tested for real. A backup nobody has ever brought back is not a backup: it is a hope.

  • 06

    Monitoring and automatic restart

    We watch that the site answers. If a service goes down it restarts on its own; if the problem persists, we know before your client does.

What we guarantee

Few promises, all verifiable. If one were not true, we would rather not write it.

  1. Response time 24 hours

    We answer every report within twenty-four hours. That is not resolution time: it is the time within which you know the problem is in someone’s hands.

  2. Backups daily

    A full copy every day, with restores tested periodically. At worst you lose a day of changes, not a week of them.

  3. Automatic service restart active

    Every service comes back on its own if it falls. That is the difference between a thirty-second outage and one that lasts until somebody notices.

  4. Measured before and after always

    Every migration closes with the same measurements taken before and after, on the same scale. If it did not improve, we are the ones telling you.

How you move

Migration is the scary part. It takes four steps, and the domain moves only once the new site has already been tested.

  1. Analysis

    We look at the site as it is: weight, queries, plugins, dependencies. We tell you what will improve and what will not, before moving anything.

  2. Copy and test

    The site is replicated on the new machine and tested there, with the domain still where it is. No surprises in production.

  3. Switch

    DNS moves in a window agreed with you. The old hosting stays up until we are sure.

  4. Verification

    Measurements before and after, same scale, same tool. We send you the report, we do not describe it.

Frequently asked questions

  1. Will my client know the server is yours?
    No. The infrastructure is ours, the relationship stays yours. You invoice, you talk, and your agency is the name that appears.
  2. Can I bring sites you did not build?
    Yes. During analysis we tell you what we can guarantee and what we cannot: on a site full of plugins we do not control, some promises are not ours to make, and we would rather say so first.
  3. What happens if the site goes down at night?
    Services restart on their own. If the problem runs deeper, monitoring flags it and we step in within the agreed times, which are written down rather than implied.
  4. What if one day I want to leave?
    You get full access, the backups and the configuration. No closed format, no proprietary panel to escape from: it is WordPress on a server, and it stays yours.
  5. How much does it cost?
    It depends on traffic and how many machines are needed. Tell us how many sites you have and what kind: we answer with a proposal, not a generic price list.