Case studies

A few projects from recent years, without client names. For each one, we describe where we started, what we did and what the result was.

Infrastructure and operations

Migrating an end-of-life cluster to AlmaLinux

Starting point
Unsupported CentOS 6 servers in a clustered environment.
Solution
A step-by-step migration to AlmaLinux 8, with the services running throughout.
Result
A supported system that receives updates.

Cloud and DevOps

Moving a Laravel application into containers

Starting point
A PHP application on a traditional server, released by hand.
Solution
A Docker-based environment, a separate infrastructure repository and a GitLab pipeline.
Result
An automatic release after every git push.

Related post: Moving a PHP application into containers with a GitOps approach

Cloud and DevOps

Moving a legacy application to AWS ECS

Starting point
An ageing application that was hard to deploy.
Solution
Dockerfiles, ECS services and load balancing.
Result
Reproducible deployments and scalable hosting.

Infrastructure and operations

Atlassian cloud migration

Starting point
Self-hosted Jira, Confluence and Bitbucket.
Solution
Migration of the data and users to Atlassian Cloud.
Result
No more server maintenance or version upgrades.

Infrastructure and operations

Spam filtering in front of the existing email system

Starting point
A lot of spam, and the email system was to stay as it was.
Solution
Proxmox Mail Gateway in front of the mail servers.
Result
Filtered incoming mail, with the mailboxes unchanged.

Related post: Proxmox Mail Gateway spam filter

What every project has in common

The projects above come from different areas, but they share the same approach: a change should not be a risky leap but a series of well-prepared, reversible steps. That is why every job starts with an assessment, and we only touch the production system once we know exactly what is going to happen.

As far as possible, we treat configuration as code: in a version-controlled repository, reviewable and repeatable. So at the end of a project, we don’t hand over a system that only we understand, but a documented environment that someone else can also take forward.

If you are facing a similar task – legacy servers, manual releases, a move to or from the cloud – describe the situation briefly and we’ll tell you where it makes sense to start.

How a project runs

  1. Assessment

    We look at the existing system, its dependencies and the risks, and agree on what the goal is.

  2. Plan

    We write down the target state, the steps and the schedule, and also how to roll back if something doesn’t go to plan.

  3. Step-by-step implementation

    We move forward in small, verifiable steps, and schedule critical cutovers for the lowest-traffic period.

  4. Handover

    We hand over documentation, version-controlled configuration and, if needed, operations support.

Let’s talk about your project

Tell us briefly how we can help, and we will get back to you as soon as we can.

Get in touch