Capability

Cloud engineering

Infrastructure a small team can actually run.

Cloud architecture is usually sized for the organisation somebody hopes to become. That is how a team of eight ends up operating a platform built for eighty, spending its attention on infrastructure instead of the product.

Cloud engineering

What makes this hard

The reference architecture assumes a platform team you do not have.
Costs are discovered monthly, in arrears, by whoever opens the bill.
Nobody can say what would happen if the main region went down, because it has not been tried.

How we approach it

Right-sized architecture
Build for the load you have and the next order of magnitude, not for a hypothetical one after that.
Cost as a design input
Know what a feature costs to run before it ships, not when the invoice arrives.
Operable by the people who have to operate it
Deployments, alerts and runbooks aimed at your team's actual size and on-call reality.

What you should expect

A bill you can explain line by line.
Infrastructure your own engineers are willing to be paged for.