for people who build client sites

A hosting planfor every client? You're losing money.

Every site you park on a monthly hosting plan is margin you leave to someone else. With your own server and a ready codebase, your clients' sites all live in the same place — and hosting turns from a cost into income.

Twenty clients,
twenty plans.

Twenty control panels, twenty due dates, twenty renewals to chase. And on each one a margin that depends on someone else's price list.

Twenty clients,
one server.

A single machine, yours, set up once. Every site runs in its own space, and they're all updated, protected and backed up the same way.

The difference
stays with you.

Your clients keep paying you for hosting as they do today. You pay for one server: what's left is margin, every month.

Do the maths
with your numbers.

Move the sliders: how many sites you host, what you pay today for each, what you charge for it, what a server costs. The starting values are an example: put in yours.

Margin today €2,400
With your own server €4,440
Extra, every year €2,040 and it grows with every client you add

A rough calculation on the values you choose. It doesn't count the time you spend running things: that's what the codebase is there to cut.

What's in
the codebase.

Any Linux server, and on top of it everything you need to host clients' sites without becoming a full-time sysadmin.

How do you work?
the page adapts
  1. Watch

    If a site goes down, you know before your client does.

    Uptime checks per domain, alerts by email or Telegram, logs in one place.

  2. Backups

    Automatic copies of sites and databases, kept off the server.

    Encrypted nightly backups to external storage, with a tested restore procedure.

  3. Publishing

    Put a new site, or an update, online with one command.

    Deploys from Git, builds in containers, roll back to the previous version with one command.

  4. Domains and HTTPS

    Add a domain and the certificate sorts itself out. And renews itself.

    Caddy reverse proxy, automatic Let's Encrypt certificates, redirects and security headers.

  5. A space per site

    Every site lives in its own space: if one has a problem, the others don't notice.

    Docker Compose, one service per site, resource limits per container.

  6. The server

    A VPS from a European provider, in your name: you choose it, you change it whenever you like.

    Ubuntu LTS, key-only SSH, firewall and automatic security updates.

Choose how much
you do on your own.

The codebase is always there. What changes is how far we walk with you: from the code alone to someone setting it up with you.

  1. the best fit for you

    With the method

    Course + codebase

    Every piece, understood.

    For people who want to know what each piece does before trusting it with clients.

    • Everything in Codebase
    • The video course: from an empty server to the first client online
    • Exercises on a practice server
    • Moving a site you already have, step by step
    I'll take the course →
  2. the best fit for you

    With us beside you

    1:1 training

    Someone at your side.

    For people who want to move fast, on their own real projects.

    • Everything in Course + codebase
    • One-to-one sessions with the people who built the codebase
    • Your server set up together, live
    • Your sites moved over with you
    I'll take the 1:1 →

Prices on request: they depend on the path and on how many sites you bring.

The questions
we get asked.

  1. I'm not a sysadmin.

    You don't need to be: the sysadmin decisions are already made in the codebase, and the commands you need are few and documented. If you've never opened a terminal, the course starts right there.

  2. What if the server goes down?

    You know straight away, because the watch alerts you. Backups live off the server, and bringing everything back up on a new machine is a written procedure, step by step.

  3. Does it work with WordPress?

    Yes: WordPress runs in its own space with its own database, next to static, Astro, Next.js or Node sites.

  4. What about the clients' email?

    Mailboxes are best left to a dedicated service: the codebase hosts sites, not mail. We show you how to connect the domains to an email provider cleanly.

  5. Can I move the sites I already have?

    Yes. In the course and in 1:1 training we move an existing site together; with the codebase alone you get the written procedure.

  6. How much is it?

    It depends on the path you choose. Tell us how many sites you run and how you work today: we'll reply with a proposal for your case.

Let's talk.

Tell us how many sites you run and where you're starting from: we'll reply with the right path, in person.

You're more of a
The path you're interested in