ServicesCloud

Server management where you keep root.

We patch, monitor and back up your Linux servers as code: on our own platform, at another hosting provider or within the automation you built yourself. You keep access, you keep your configuration, and you can always leave.

Managed does not have to mean handing over the keys.

At most hosting providers "managed" means they run a control panel and you can no longer reach your own server. Docker or your own tooling often does not fit, and the application is explicitly your problem. With us, the levels only differ in who manages which layer. Root stays with you in all three.

We manage as code: your servers' configuration lives in a repository, changes can be traced and a deviation shows up instead of silently staying. If you already have Ansible, Terraform or an automation model of your own, we work within it instead of moving you onto our tooling.

Three levels

Who manages which layer.

Unmanaged

For teams that manage their servers themselves.

  • A VM on our own network in the Netherlands
  • We monitor hardware, hypervisor and network
  • You manage the operating system and everything above it
  • An engineer on the line when you get stuck; work billed by the hour
Managed

For those who want to hand over the operating system and the stack.

  • Hardening and configuration as code
  • Critical security updates within 7 days at the latest, high within 30; faster in practice
  • Monitoring with Prometheus and Alertmanager, with HTTP and protocol checks
  • Off-site, encrypted backups
  • Your application stays yours
Managed+

For teams that want management and application with the same people.

  • Everything in Managed
  • We work in your repo and on your automation model
  • Your application's metrics in our monitoring, and we act on them
  • We debug and develop your application with you, within a fixed block of hours

In all three: root with you, your configuration and backups go with you when you leave, and engineers you know by name.

How we manage

What we really do.

Management as code
Your servers' configuration lives in a repository: ours, or yours. Every change can be traced, and we report a deviation rather than leave it in place.
Patching by severity
Critical vulnerabilities within 7 days at the latest, high within 30, reboot included. That is a ceiling; in practice we are faster. Where possible, first on one server and then on the rest.
Monitoring that measures something
Prometheus and Alertmanager, with checks on HTTP and the protocols your service uses. With Managed+ also the metrics of your own application.
Backups off-site
Off-site and encrypted, at a different location from your servers. When you leave, your backups go with you.
In practice

A fleet on the customer's model.

For a SaaS company we manage a fleet of 31 servers in four roles: database, application, control and big data. Not on our standard package, but on the automation model the team built themselves. Our engineers also contribute to the application and debug it when something goes wrong. That is Managed+: the people who manage the servers also know the code.

  • 31 servers
  • 4 roles
  • The customer's own automation model
How we work

A conversation first, a server second.

  1. Conversation
    What runs, where is it, who manages what today and what automation is already there? The level follows from that, not the other way round.
  2. Advice
    A proposal for level and infrastructure. It may turn out cheaper or more expensive than you expected; the advice is not binding, but we make sure you take what fits.
  3. Onboarding
    We bring your servers into the configuration as code, or connect to yours, and record what we manage.
  4. Management
    Patching, monitoring and backups, with an engineer you can call. Response times are agreed in your contract.
Why Xyphen IT

Less clicking, more conversation.

  • Root with you, even with management
  • Your own automation and tooling stay in place
  • Engineers who know both the servers and the code
  • Our own network and Dutch data centres beneath your servers, if you want them with us

You can also keep servers at another hosting provider; with us, management and hosting are separate choices.

FAQ

Frequently asked questions about managed servers

Do I keep root when you manage my servers?

Yes, in all three levels. Changes you make outside the code are reported as a deviation, so they end up in the configuration. Only if you choose software we developed ourselves can access be limited. Even then we help you leave.

What do I take with me when I leave?

The configuration as code, the monitoring rules, the agreements and documentation about your environment, and your backups. We help with the move, even if you do not stay with us.

Do you also manage servers that are not hosted with you?

Yes. Management and hosting are separate choices. If your servers are at another hosting provider, we manage them there, without you having to move first.

We already have Ansible or Terraform. Does that have to go?

No. With Managed+ we work in your repository and on your automation model. We propose changes the way a colleague would, and the tooling stays yours.

How quickly do you patch?

Critical vulnerabilities within 7 days at the latest, high within 30, including the reboot it takes. That is the ceiling we guarantee; in practice we patch faster.

What is not covered by management?

With Managed your application stays yours: we manage the operating system and the stack beneath it. If you want us to look into the application, debug it and develop with you, that is Managed+.

What does it cost?

Managed starts at €125 per server per month, excluding VAT and excluding the server itself. Managed+ is put together after a conversation, because it depends on your fleet and how much we develop with you. Our advice may turn out cheaper or more expensive than you expect and is not binding; we make sure you take what fits you, not the biggest package.

Let's talk first.

Tell us what runs and how it is managed today, and we will advise a level.