DevOps, cloud and industrialised deployments
Cloud migration, Terraform, Kubernetes, CI/CD, FinOps and observability. We leave behind an infrastructure described in code that your teams can rebuild identically.
- Model
- Fixed price or embedded
- Duration
- 4 to 16 weeks
- Expected outcomes
- A deployment that becomes a non-event, runnable in the middle of the day
- Expected outcomes
- A cloud bill understood line by line and tied to actual usage
Who it is for
- IT departments migrating to AWS, GCP or Azure without a cloud team
- Teams that deploy by hand on Friday evenings
- Companies whose cloud bill grows without explanation
- Organisations with no monitoring beyond a ping
Who it is not for
- Standalone 24/7 first-line managed services
- Mandated migrations with no possible architectural arbitration
- Environments where administrator access will never be granted
Deliverables
- Documented target architecture with flow diagram and security zones
- Infrastructure described in Terraform, in your repository, with locked remote state
- CI/CD chains with isolated environments and reproducible deployment
- Observability: metrics, centralised logs, traces, alerts wired to runbooks
- Backup policy and an actually executed restore test
- FinOps review: sizing, reservations, orphaned resources
- Incident runbooks and on-call procedure
How it runs
01
Current-state review
Inventory of what exists, fragility points, undocumented dependencies, and above all: what happens today when the key person is on holiday.
02
Target architecture and path
Target diagram, but above all the path: which building blocks move first, where the point of no return is, how to roll back at each step.
03
Industrialisation
Terraform, CI/CD, observability. Every environment must be destroyable and rebuildable identically. Until that is true, it is not finished.
04
Handover and on-call
Written runbooks, an incident exercise played with your teams, a real restore test. Then internal takeover or managed service, your call.
Stack
- AWS
- Google Cloud
- Azure
- Terraform
- Kubernetes
- Docker
- GitLab CI
- GitHub Actions
- Ansible
- Prometheus
- Grafana
- Datadog
How the assignment is structured
Three ways to engage this service. The figure is set at the end of framing, once the scope is written: it is the only way to commit firmly without pricing in a risk you would end up paying for.
Cloud & FinOps audit
fixed price, 2 weeks
Drifting bill, architecture never reviewed
- Architecture and security review
- Detailed billing analysis
- Priced, prioritised savings plan
- Industrialisation roadmap
Industrialisation project
fixed price, frozen scope
Migration or CI/CD and IaC rollout
- Infrastructure in Terraform
- Complete CI/CD chains
- Observability and alerting
- Real restore test
- Runbooks and handover
Embedded DevOps engineer
time and materials, 3-month minimum
Continuous reinforcement on platform and on-call
- AWS, GCP or Azure certified
- On-call participation where contracted
- Fluent French and English
- Replacement within 10 business days on mismatch
Frequently asked questions
Do your teams access our production?
Only if you grant it, by named individual, through your bastion and identity provider, with MFA and full logging. Access is time-bound and revoked at the end of the assignment. The named access list is part of the monthly reporting.
What cloud savings can we realistically expect?
Entirely dependent on your starting point, and be wary of anyone quoting a percentage before seeing the bill. The most common gains come from instance sizing, orphaned resources, non-production environments left running overnight, and log retention policies. The audit prices each item separately.
Do we have to move to Kubernetes?
No, and it is often a bad idea. Kubernetes earns its keep above a certain number of services and with a team able to operate it. Below that, a managed application service costs less and breaks less. We regularly recommend against it.
Other services
Twenty minutes is enough to know whether we are useful
No sales deck. You describe the need, we say whether it is in scope, at what price and on what timeline. If it is not for us, we say so during the call.