Infrastructure and Maintenance

Infrastructure that fits the job.

Many small deployments can start on a modest VPS. Others need more storage, more performance or hardware on your own premises.

We help you choose, set it up, and look after it if you want us to.

# What decides the setup
users        25
services     mail, nextcloud
storage      300 GB, growing
backups      daily, off-site copy
→ suggestion  larger VPS + off-site backup
An illustration of how requirements lead to a setup.
Options

Three ways to run it.

Small VPS

Starting point

A virtual server rented from a hosting provider. A good start for small teams and light workloads, such as a messaging server, a few mailboxes or a small Nextcloud.

  • Low monthly cost, often a few euros
  • Limited memory and storage
  • The provider's network and policies apply
  • Backups need to be planned separately

Larger VPS or dedicated

Growing needs

More CPU, memory and storage, or a physical server in a data centre that you don't share with others.

  • Room for more users and data
  • Steadier performance
  • Higher monthly cost
  • Still a provider's network and policies

Your own hardware

On your premises

A suitable machine you own, in your office or placed in a data centre. The data stays physically with you.

  • Full physical control
  • Uses hardware you may already have
  • You provide power and connectivity
  • Failed parts must be replaced by you
Choosing

What decides the setup.

We look at these together with you. None of them alone decides, and the answer is often simpler than expected.

Users

How many people, how actively, and from where.

Storage

How much data today, how fast it grows, and how fast it must be.

Performance

Memory and CPU for the services, especially Nextcloud and spam filtering.

Connectivity

Bandwidth, a fixed IP address, and reverse DNS for mail.

Backups

How often, where the copies live, and how a restore is done.

Availability

How long an outage you can live with, and what that costs to avoid.

Security

Access, encryption, updates and who may administer the system.

Maintenance

Who keeps it running: your team, us, or both.

Installation and maintenance

Two different things.

Setting a system up is a project. Keeping it healthy is an ongoing task. We keep the two apart, so you know what you are agreeing to.

Initial installation

A one-off project with a defined result.

  • Requirements and architecture
  • Server setup, DNS and certificates
  • Configuration, migration and testing
  • Documentation and handover

Ongoing maintenance

Optional, agreed separately.

  • Updates and security patches
  • Backup checks and restore tests
  • Certificate, DNS and configuration changes
  • Monitoring and troubleshooting

The scope, response times and costs of maintenance are agreed for each project. Nothing on this page is a service-level agreement.

Contact

Not sure which setup fits?

Describe what you want to run and for how many people. We'll suggest a setup and explain why.