Service

Cloud infrastructure

The cloud does not make anything cheaper on its own. It gets cheaper when the architecture is sized for your real load and somebody reviews the bill every month.

Signs this is for you

  • Your servers are under a desk or in a room with no cooling.
  • The cloud bill climbs every month and nobody can explain why.
  • There are no backups — or there are, but a restore has never been tested.
  • If the main server dies, the operation stops and there is no plan.

What it includes

Architecture and deployment

Infrastructure designed on AWS, Azure or Google Cloud for the real load: private networks, segmentation, load balancing, scaling and managed databases. Documented in diagrams your team can actually read.

Migration from on-premise

Moving applications and databases to the cloud with a planned cutover window and a rollback plan if something goes wrong. We never migrate without a way back.

Infrastructure as code

The whole environment defined in Terraform, so it can be recreated, reviewed in version control and replicated between staging and production without surprise differences.

Backup and recovery

A backup policy by criticality, with encryption, retention and — what almost nobody does — periodic restore tests with measured recovery times.

Cost optimisation

Reviewing the bill line by line: oversized resources, orphaned disks and IP addresses, instances that can be switched off outside working hours, savings plans and reservations where they pay off.

Security and access

Least-privilege role-based permissions, two-factor authentication, secrets management, encryption at rest and in transit, and audit logging of who did what.

How we approach it

  1. Current-state audit

    An inventory of what you are running, where, what it costs and what the concrete risks are. The output is a prioritised report, not a service catalogue.

  2. Design and budget

    Target architecture with the estimated monthly cost before anything moves. If the cloud is not right for a particular workload, we say so.

  3. Staged migration

    The least critical workloads move first to validate the procedure, leaving the sensitive ones until the path is proven.

  4. Operations and handover

    Monitoring, alerting and runbooks for common incidents. With ongoing support or with training for your team, whichever you prefer.

What we use

  • AWS
  • Azure
  • Google Cloud
  • Terraform
  • Linux
  • VPC
  • S3
  • RDS
  • Entra ID

What you get

  • Architecture diagrams and infrastructure documentation
  • A Terraform repository defining the whole environment
  • A backup policy with a tested, timed restore
  • A cost dashboard and budget deviation alerts
  • Runbooks for the most likely incidents

Frequently asked questions

AWS, Azure or Google Cloud?

It depends on what you already use. If your company lives in Microsoft 365 and Entra ID, Azure integrates better and costs less in licensing. For greenfield workloads with no ties, AWS has the widest catalogue. Google Cloud tends to stand out for data and analytics, and for containers. We run the analysis on your case, not on a preference of ours.

Can I stay on my current server?

Sometimes that is the right call. A stable, predictable workload can be cheaper on a well-managed server you own. What is almost never right is having no backups and no recovery plan — and that gets fixed either way.

How much can the bill come down?

We do not quote a percentage before looking. Infrastructure that has never been reviewed usually holds oversized resources and orphaned items that can go without touching the operation. The audit gives you the real figure for your case.

Am I locked in to you?

No. The AWS, Azure or Google Cloud accounts are yours, the infrastructure is defined as code in your repository, and the documentation lets another provider take over. We would rather you stayed because you want to.

Have a project in mind?

Tell us what you need and we will tell you honestly whether we can help, how long it would take and what it would cost. No strings attached.