Cloud infrastructure
Infrastructure is the part nobody looks at until the day it fails. Done well it never shows: it absorbs growth, it warns before it breaks, and it lets you ship a change without anyone’s blood pressure rising.
Free reviewWhen you need this
- Shipping a change is an operation done at night and with your fingers crossed.
- You could not say when the last backup ran, or whether it can be restored.
- You find out something failed because a customer calls you.
- You expect to grow and do not know whether what you have will take it.
What it includes
- Separate environments, so you can test without touching production.
- Repeatable deployment, with no manual steps only one person knows.
- Backups, and the proof that they can actually be restored.
- Monitoring and alerts when something drifts out of normal.
How we do it
Infrastructure gets decided during architecture, alongside the data and the integrations, and not at the end when there is no room left. That is what lets the operation phase be about going live rather than about putting out fires.
Five phases, each with its own acceptance criteriaQuestions about this service
Do we get locked into one cloud provider?
It depends what gets used, and it is decided with you in the room. Some services save a great deal of work in exchange for locking you in, and it is worth knowing which ones those are before choosing them, not after.
Who runs it afterwards?
Whichever you prefer. We document it so your team can take it, or we look after it under maintenance. What we do not do is leave it running with nobody knowing how.