Frequently Asked Questions

Yes. To properly administer a system — kernel, services, firewall or handling a live incident — root access is necessary; without it you can only do half the job. I always manage it with security in mind: SSH keys instead of passwords, individual and traceable access, and least privilege. While I am responsible for the system I hold root access to maintain change control, and everything I touch is documented.

Yes, I sign NDAs, no problem. Your data and your clients’ data are yours: they are not shared with third parties, not used for anything beyond the agreed work, and are handled in accordance with GDPR. Being trusted with access to someone else’s infrastructure is something I take seriously.

However you prefer. I can work completely in the background — your client never knows I exist and you introduce me as part of your team — or visibly if you prefer. I adapt to what the agency needs. What I never do is go around the agency to keep their client.

I have my own tools and procedures, but I adapt to how you work: Slack, your ticketing system, Git repositories, whatever channel you use. The idea is to fit into your workflow, not force you to change it.

No minimum, no lock-in. You can call on me only when something one-off comes up or build an ongoing relationship. The hourly rate is agreed based on volume and level of commitment: the more continuity, the better the terms.

I work on your existing infrastructure, whether it is a VPS, dedicated server or cloud (AWS, Hetzner, etc.). I do not force you to migrate anywhere. That said, if I see your setup is holding you back, I will tell you and advise the best option — the final decision is always yours.

I handle the system: the server, performance, security, and backups. Your store’s code is your development team’s territory. But I act as a bridge: when something looks like an application bug but is actually coming from the system — or the other way round — I help developers see it and point it out. That clear boundary avoids the classic “it’s not the code, it’s the server / it’s not the server, it’s the code”.

Yes, with nuance. DNS and SSL certificates, no problem. For email I almost always recommend outsourcing to a specialist provider — running your own mail server today is asking for deliverability and security headaches — and I will help you do it properly. Everything in its best place.

Each migration is assessed case by case. I do not promise “zero downtime” because that would be a lie, but I do plan the lowest-impact window — usually outside trading hours — so the cut is minimal and, for a store, does not translate into lost orders.

No. I specialise in Linux and BSD; Windows Server is not my territory and I would rather tell you straight than do a mediocre job outside my speciality.

You have my direct number. My first goal is for everything to be set up so well that you never need to call me, but if you do, I am here. The response commitment level — including out of hours — is adjusted to the collaboration model: a retainer includes coverage that a one-off engagement does not guarantee. Details are in the services section.

Yes. Even if we have never worked together, if your site is down or you suspect an intrusion, get in touch and we will agree a rapid intervention. In an emergency the priority is to contain and restore the service; the root cause analysis comes after.

It is tailored to each case — I do not have off-the-shelf rates. Depending on what you need we work on a fixed-price project, hourly packages or a monthly retainer, and the hourly rate depends on volume and commitment. Before we start I always provide a clear proposal with objectives, timelines and deliverables.

Yes. Listening to your problem and reviewing your environment at a high level to define the scope is free and without obligation. I only quote once I know exactly what is needed.

You are not locked in. Everything I do is documented so your team can continue without depending on my memory. If we stop working together I hand over full root access and carry out a proper handover. And for extended absences, such as holidays, I have trusted colleagues who provide cover.