What is in production needs somebody awake
Building a system and operating it are different crafts. We do both, and it shows in how we build.
We operate ADN Vortex every day of the year. We know what it is like to get an alert at three in the morning and what it costs not to have set up the right monitoring six months earlier.
That knowledge is what we apply when we take over a client's infrastructure: we do not design for the demo, we design for the day something breaks.
What it includes
- Infrastructure design and implementation on AWS, Azure or GCP
- Infrastructure as code, versioned and reproducible
- Continuous integration and delivery pipelines
- Observability: metrics, traces, logs and alerts that matter
- Backups with periodic restore testing
- Cloud cost optimisation with measurement before and after
- On-call and incident response under a service level agreement
How we do it
Alerts somebody answers
An alert that demands no action is noise that trains the team to ignore the dashboard. We configure few alerts, each with an associated procedure.
Everything reproducible
No hand-configured servers nobody dares to touch. If it is not in code it does not exist: it is the only way to recover quickly.
Blameless postmortems
After each incident, a written analysis of what happened and what changes. The goal is that it does not repeat, not finding who is responsible.
When it makes sense
- Deployment is manual and nobody dares do it on a Friday
- Nobody knows why the cloud bill went up
- There are recurring incidents with no root cause analysis
- The development team spends too much time operating
- Coverage outside business hours is needed
Other practices
Consulting and transformation
Most projects that fail do not fail because of the code: they fail because nobody agreed which problem was being solved.
View →Data and artificial intelligence
Most data initiatives die in the pilot. Usually not because of the model, but because nobody settled where the data comes from or who maintains the result.
View →Engineering and custom development
We build systems that other people will maintain. That changes how they get written.
View →Tell us what you need to build
Initial assessment at no cost. We answer with a concrete scope, with cost and date.
