Cloud & infrastructure consulting and management
The right cloud for you, with no lock-in and no billing surprises.
The cloud isn't an end in itself, it's a tool: the challenge is choosing the right service, sizing it correctly and keeping it under control over time. We design and manage cloud infrastructure in a provider-agnostic way, so the solution follows your needs rather than a vendor's price list. No black boxes: documented configurations, transparent costs and a single technical point of contact who owns the whole stack.
Overview
We support you across the full infrastructure lifecycle: from initial design to migration, from day-to-day management to cost optimisation. We work mainly on Google Cloud and, alternatively, on AWS and DigitalOcean; on request also Azure, Hetzner and OVH. For each workload we choose the simplest combination that genuinely holds up: a well-sized virtual machine when that's enough, load balancers and auto-scaling when traffic peaks demand it.
The goal is infrastructure that is reliable, understandable and reproducible - something you can grasp and maintain even without us. That's why every decision ends up written down: architecture diagram, rationale, expected costs and the procedure to rebuild everything from scratch. If you ever want to switch provider - or consultant - the keys stay in your hands, and whoever comes after finds order, not archaeology.
Typical problems we solve
- The cloud bill keeps climbing every month for no clear reason → cost audit, rightsizing and a report with the savings ranked by priority.
- Everything runs on a single machine that no longer handles the peaks → we redesign with a load balancer, auto-scaling and a managed database.
- Only the person who built it understands the infrastructure → we map it, document it and hand back updated access and diagrams.
- You need to migrate from on-premise or switch provider without stopping the service → inventory, dress rehearsal on a staging environment and a rollback plan.
- Backups exist but no one has ever restored them → we encrypt them, verify them with periodic restores and write the recovery procedure.
- Every service is exposed on a public IP → we segment the network with VPCs, private subnets, NAT and tuned firewall rules.
- The environment grew by hand and no one can reproduce it → where the complexity justifies it we move it to Terraform, otherwise to direct, documented configurations.
What's included
- Design: service architecture, sizing, provider selection and cost estimates before you spend a euro.
- Migration: moving from on-premise or another cloud, with an inventory, an agreed window and a rollback plan ready to go.
- Operations: updates, monitoring, security patching and on-call cover on a monthly retainer when downtime genuinely costs you.
- Cost optimisation: rightsizing, reserved resources, tiered storage, automatic shutdowns and clear spend reports.
- Infrastructure as code, when it helps: where complexity justifies it we describe everything in Terraform, versioned and reproducible; on simple environments we stay with direct, documented configurations.
- Networking and security: VPCs, subnets, security groups, secrets management, encryption and an attack surface kept to a minimum.
- Backups and high availability: encrypted backups that are genuinely tested, redundancy and restore plans we know how to run.
Stack and technologies
On Google Cloud we use the proven building blocks: Compute Engine, Cloud SQL, Cloud Storage, load balancers and auto-scaling groups; on AWS and DigitalOcean the equivalents, chosen with the same criteria. We manage machines with Debian and Ubuntu Server - on request AlmaLinux, Rocky Linux or others - and design networks with VPCs, public and private subnets, NAT and tuned firewalls. Where complexity justifies it we automate with Terraform, so every resource is versioned code; elsewhere we prefer direct configurations that anyone can read. Rounding out the picture: managed databases, object storage, queues and caches, monitoring and alerting with Prometheus and Grafana or the provider's native tooling, and repeatable deployment pipelines. If you already run containers or Kubernetes, we plug into your workflow instead of reinventing it.
A real-world example
A company running an internal management system and an e-commerce store had grown "by hand" for years: about a dozen oversized virtual machines, no documentation and a monthly bill on a steady climb. We ran the inventory, measured actual CPU, memory and disk usage over a few weeks, and redesigned the environment on Google Cloud: fewer machines but sized on real data, a managed database service, tiered storage for archives and automatic shutdown of staging environments overnight and on weekends. The migration happened in two agreed windows, with a rollback plan ready and never used. The result: monthly spend cut by roughly a quarter, a document describing every piece of the infrastructure, and backups that now get a trial restore every month.
Who it's for
- SMEs and professional firms who want a well-managed cloud without standing up an in-house IT department.
- Web agencies and software houses that need solid infrastructure behind their clients' projects.
- E-commerce and SaaS that need to scale during peaks and keep costs under control the rest of the year.
- Teams already on the cloud who are paying too much, lack documentation or want out of a lock-in.
How we work
We start from an audit of what exists or from a design on paper, define the simplest solution that carries the load, and put it into production with documented configurations - described as code where complexity justifies it. Every maintenance window is agreed in advance, every change tested before touching production. Standard coverage runs Monday to Friday, 09:00-18:00, with priorities and timeframes described on the response times page; for ongoing management there are server management plans, at a fixed price; for work needed from time to time, hour packages, which never expire. Quotes are free, with a reply within one working day: you always know what's running, what it costs and why.
Frequently asked questions
Which cloud providers do you work with?
We work mainly on Google Cloud and, alternatively, on AWS and DigitalOcean; on request also Azure, Hetzner and OVH. We pick the provider based on your real needs, budget and constraints, not sales preferences: if you already have one, we adapt to it.
Can you help us cut our cloud bill?
Yes. We review the existing infrastructure, find oversized or idle resources and propose rightsizing, reserved instances, tiered storage and automatic shutdowns. You get a readable report with the savings ranked by priority.
Do you manage infrastructure as code?
It depends on the complexity. When the infrastructure is elaborate, yes: we describe it with Terraform or similar tools, so it's versioned, reproducible and every change stays tracked. On simple environments, infrastructure as code adds an abstraction that ends up complicating exactly what it should simplify - there we prefer direct, well-documented configurations. We choose case by case, not by fashion.
Do you also handle migration from another provider or from on-premise?
Yes. We plan the migration with an initial inventory, an agreed window and a rollback plan. We test on a staging environment before moving workloads to production, so downtime stays minimal and under control.
How much does cloud consulting cost?
There is a single rate for every technology. For work needed from time to time there are hour packages from €58/hour that never expire; ongoing management is covered by the monitoring and server management plans, starting from €49/month. Quotes are always free, with a reply within one working day.
What coverage do you offer if something breaks?
We cover Monday to Friday, 09:00-18:00, with priority triage from P1 to P4: for a P1 emergency, during office hours we pick it up within one hour; out of hours within one hour with an on-call plan, otherwise within 24 hours if we already work together. Out of hours the on-call rules apply; work planned at least 20 days ahead remains possible at the out-of-hours rate.
Do you also work at night or on weekends?
Yes, for emergencies. The on-call plan extends your office hours on the days you choose: we pick up a P1 within one hour at any hour and a P2 within 4 hours during the day, and the work costs the same as in office hours. Without a plan our hours are Mon-Fri 09:00-18:00: out of hours we still pick up a P1 within 24 hours, weekends and public holidays included, at the out-of-hours rate, if we already work together; everything else is best effort. Night or holiday work planned at least 20 days ahead remains available to everyone. Plans, rates and examples are on the On-call page.
Need a hand with your infrastructure?
Tell us the problem: we reply within one working day with a clear plan and a quote.