We audit and redesign AWS environments layer by layer: compute, data, network and foundation. Every change carries a number, euros per month or milliseconds of latency, and lands in your repository as infrastructure as code.
We always start with the assessment. Then we act where the impact per euro invested is highest.
Rightsizing, Savings Plans, Graviton, Spot and tiered storage. A FinOps approach: every team sees what it spends and why.
Bottleneck diagnosis across compute, database and network. Autoscaling that responds to real demand and observability that explains every spike.
Multi-account landing zone, migration from a data centre or another cloud, and modernising monoliths towards containers or serverless when it pays off.
Infrastructure as code, deployment pipelines and shared on-call. Your team keeps the knowledge and the repository.
Typical savings per lever in accounts that have not been through a FinOps review. The assessment confirms which ones apply to you and in what order.
| Lever | Typical savings | Effort | Risk to production |
|---|---|---|---|
| Savings Plans and Reserved Instances on steady usage | 20 to 40 % of compute | Low | None |
| Rightsizing of EC2, RDS and EKS nodes | 15 to 30 % | Medium | Low, with load tests |
| Migration to Graviton | 10 to 20 % per instance | Medium | Low if the software is compatible |
| Spot for interruption-tolerant workloads | 50 to 70 % on those workloads | Medium | Medium, needs design |
| S3 Intelligent-Tiering and lifecycle rules | 30 to 60 % of storage | Low | None |
| Orphaned resources, snapshots, IPs and NAT | 3 to 8 % of the bill | Low | None |
| Data transfer and VPC endpoints | Variable, up to 15 % | Medium | Low |
Indicative ranges based on typical projects. The figures for your account are calculated in the assessment from your Cost and Usage Reports.
Closed phases with concrete deliverables. You can stop at any of them and keep the report.
Account inventory, cost per layer, Well-Architected review and prioritised performance bottlenecks.
Roadmap with estimated savings, effort and dependencies. Every action carries a number: euros per month or milliseconds.
Changes in Terraform or CDK, reviewed by your team and deployed environment by environment within agreed windows.
Monthly cost and performance review, shared on-call and training so your team can run it on its own.
Figures are illustrative examples from typical projects. They will be replaced with real cases with client authorisation.
Our own platform: three web applications, each with a frontend, an API and a MySQL database, running in production on AWS. The whole thing costs less than a single managed database instance, with no trick we would not recommend to a client.
| Line item | What it covers | USD / month |
|---|---|---|
| EC2 t4g.small, one-year Compute Savings Plan | MySQL 8, three backend containers and Caddy, 730 hours. No upfront payment; 13.4 USD on demand | 8.5 |
| EBS gp3, 20 GB | Operating system, images, database volume and certificates | 1.8 |
| Route 53 | One hosted zone and DNS queries for all subdomains | 0.6 |
| EBS snapshots | Daily incremental backup of the volume, three days retained | 0.4 |
| S3 and CloudFront | Three static frontends and one distribution per app, also in front of the APIs; TLS certificates from ACM | < 0.1 |
| Public IPv4 address | None. The instance is IPv6-only and CloudFront reaches it over IPv6. Would be 3.7 USD | 0 |
| Data transfer out | CloudFront covered by its free tier; first 100 GB a month from EC2 free | 0 |
| Total | One-year commitment on the instance only | ≈ 11.5 |
A single Docker Compose stack for shared infrastructure: MySQL with a 128 MB buffer pool, phpMyAdmin reachable only from the instance, and Caddy as reverse proxy. Each app adds its own compose file with a 512 MB backend container on the shared network. CloudFront sits in front of everything, terminates TLS and talks to the origin over IPv6, so the instance needs no public IPv4. Administration goes through Session Manager, which is free.
No high availability: one instance in one zone, so a maintenance event means minutes of downtime. Restore is from the daily snapshot. It fits internal tools, early-stage products and demos. When one app needs more, move only that one to Fargate or RDS and keep the rest where it is. We stop here on purpose: a t4g.micro or a three-year reservation would shave a few more dollars at the expense of headroom or flexibility.
Prices for eu-west-1 (Ireland) in September 2026, excluding VAT. The same stack on demand, with a public IPv4 and seven days of snapshots, comes to about 20.5 USD a month.
Per closed project, at a fixed price after the assessment. We do not take a percentage of the savings, so we have no incentive to recommend commitments that do not suit you.
Not for the assessment. A read-only role with access to Cost Explorer and the CUR is enough. For execution, changes go through your pipeline with your team's review.
Yes, and that is what we aim for. We pair with your engineers and document every decision so operations stay in-house.
We work on AWS, Google Cloud, Azure and Oracle Cloud: the infrastructure viewer, the security report and the cost estimate cover all four clouds (entire organisations on Google Cloud; full subscriptions or management groups on Azure; whole tenancies on Oracle Cloud). If you have a hybrid or multi-cloud environment, we assess it case by case.
The ten-day assessment tells you, with the plan to reduce it.
Tell us what your environment looks like and what worries you. Within 48 hours we will tell you whether we can help and what the first step would be.