Eight Mile · Infrastructure · London
Cloud and infrastructure engineering in London.
AWS, GCP and Azure platforms, delivery pipelines, Terraform, containers and the databases under them: designed, built and run from London by AWS Professional certified engineers. We run what we build: monitoring, backups and the midnight page are part of the job.
Scope
The platform under the product.
Six things every business system needs and few have written down. We describe them in code wherever code can hold them, so the setup is reviewable, reproducible and yours.
Cloud platforms
Accounts, networks, identity and cost on AWS, GCP and Azure: landing zones for a new estate, or order brought to one that grew by clicking. UK and EU regions by default.
Terraform and pipelines
Every server, VLAN, firewall rule and DNS record in HCL, planned and applied through a pipeline. Where a provider does not exist for the platform you are on, we have written them.
Containers and hosting
Docker Swarm and Kubernetes where they earn their keep, plain hosts where they do not, and the ingress, certificates and secrets handling around them. Nothing published that should not be.
Databases and continuity
Highly available PostgreSQL with automatic failover behind one stable address, backups that are restored on a schedule to prove they work, and a written recovery plan for the day it matters.
Monitoring and on-call
Dashboards that show what the system is doing, alerts that fire on what customers would notice rather than on every blip, and a person who answers the page at midnight, because we run what we build.
Cost and compliance
The cloud bill read line by line, resources nobody remembers switched off, instances sized for today rather than launch day, access reviewed, and data kept in UK and EU regions unless you decide otherwise.
How an engagement runs
01
Survey
02
Deliver
03
Support
Who it's for
From one server to a whole estate.
Some customers have an estate and a platform team; some have one cloud account and a worry. Both get the same written plan and the same engineers.
Enterprises
Order brought to an estate that grew by clicking.
Landing zones, identity, networking and cost across accounts, imported into Terraform so it can be reviewed. We work beside your platform or security team, in your pipelines and change process, and hand it back documented.
Small and medium businesses
Make what you have defensible.
The cloud account a contractor set up, the server under a desk, the backups nobody has tested. We make it safe, make it cheaper, and run it for you on a monthly arrangement if you would rather not think about it.
Product teams
The platform under your SaaS.
Delivery pipelines, staging that matches production, a database that fails over on its own and hosting that scales when the launch goes well. You ship features; the platform stays out of the way.
Practice
How we build and run it.
Everything that can be written down as code is, so a change is a reviewed pull request rather than a click nobody remembers.
Clouds
AWS first
GCP and Azure
Smaller European providers
Hardware you control
In code
Terraform for everything
Providers we have published
Plans reviewed before applying
Pipelines for every change
Runtime
Docker Swarm or Kubernetes
Plain hosts where they suit
Certificates and secrets managed
PostgreSQL with failover
Operations
Monitoring and alerting
Backups restored on a schedule
A written recovery plan
Twelve months of cover
What you get
Your estate, in code, with someone watching it.
Whether we built it or inherited it, you finish holding the same three things.
01
The estate in Terraform
Every account, network, server and DNS record described in code in your repository, read back to you so you can see the whole estate in one place, perhaps for the first time.
02
A written plan, worst risks first
What is exposed, what is fragile and what is costing money for nothing, in the order worth fixing, each with the effort it takes. Some fixes are an afternoon; the plan says which.
03
Monitoring, backups and cover
Alerts wired to a person, backups proved by a restore, and twelve months of cover on everything we delivered, with monitoring, patching and on-call available as a monthly arrangement.
Proof
Work that shows how we do it.
Each of these is told in full on the case studies page: the challenge, the approach, the outcome, and the figures the project's own repository states.
Straight answers
The questions people ask first.
Next step
Tell us what is running, and what worries you about it.
A cloud account, a server under a desk, a database that has never failed over: describe it in a few sentences and you will get a straight answer about what it would take to make it defensible.