BLOG 6 min read

On your premises or in a data centre? How to decide the hosting question

One of the decisions from the first two weeks of the sprint sounds technical but is a business decision: where should the software run? On your own servers – or with us, in a data centre we operate? Both are possible, neither is right in principle. Here is how to decide.

The two options

In your infrastructure. That can be a server in your building, the environment your systems house operates for you, or a cloud account in your name. What they have in common: the environment belongs to you, and someone on your side looks after it.

With us in the data centre. Here Cloudwerks is the hosting provider itself: our own hardware in a European, ISO 27001-certified data centre – the same environment we run our own products in. We provide the servers, manage and service them fully, and deliver your software there. The hosting contract is with us: one monthly fee paid to Cloudwerks, not to the data centre, and no other providers you have to settle with.

The software is the same in both cases

This is the most important point up front: the decision does not change what is built. It changes where it runs and who looks after it. So you can make it without it making the project larger or more expensive – and you can change it later if your business changes.

Five questions that carry the decision

1. Who looks after it when something goes wrong?

Servers need updates, backups and someone to check when they stop responding. Do you have an IT department or a systems house that already runs your servers today? Then your infrastructure is the natural choice, and we work with those people. Do you have nobody for it? Then hosting with us is usually the more honest answer – there, we look after the hardware and the foundation.

2. Where does your ERP run?

If the new software works closely with an ERP that runs on a server in your building, there is a good case for running it nearby. If your ERP offers an interface over the internet, or runs in the cloud itself, the location hardly matters.

3. Who needs access?

Only the office staff? Then the software can run purely internally. Field staff on smartphones, customers, suppliers? Then it has to be reachable from the internet anyway – and a data centre is built for that, whereas a server in the office first has to be secured for it.

4. Which rules apply to your data?

GDPR compliance can be achieved in both cases; the data centre where our hardware stands is in Europe. Some industries and some customers have additional rules of their own, for instance that data may not leave company premises. If you have rules like that, the question is answered.

5. What does it really cost you?

Your own hardware looks cheap because it is already there. Add the time someone spends on updates, backups and outages. Hosting with us costs one monthly fee paid to Cloudwerks, with everything included: hardware, data centre, network, backups and the care of the foundation. No second invoice from another provider – one contract, one price, one point of contact.

What applies in both cases

  • Running costs are not included in the fixed price. Hosting with us is a separate monthly contract with Cloudwerks that covers all hosting costs. Only app store fees and the like are paid by you directly to the respective provider.
  • Ongoing operation of the software is a separate agreement. The sprint delivers the software up and running. Who monitors it afterwards and stands by in case of outages is agreed separately and in writing – wherever it runs. With hosting by us, the hardware is covered; looking after the software itself is agreed on top.
  • Software and data belong to you. You receive all access credentials to your system and the documentation – with hosting by us too. Moving to your own infrastructure remains possible at any time.

Our recommendation, honestly

For most mid-sized companies without their own IT staff, hosting with us is the better choice: less for someone to look after, and reachable from the internet from day one. Those who have a systems house or an IT department that already runs servers reliably do well with their own infrastructure – we then work with those people.

We give the recommendation in the first two weeks, with reasoning and the trade-offs behind it. The decision is yours.

For the first conversation

Two details are enough: is there someone who looks after your servers today – and where does your ERP run? With that we can already say in the architecture call which way it is heading.

All posts

The next step is always the same.

A 30-minute architecture call. You describe the bottleneck, you get an assessment of whether and how it can be solved – whether or not you hire us.

30 minutes · free · directly with the architect who builds