FinOps

Continuous Cost Optimisation

Candidates found read-only, agreed with owners, applied in code, counted only once they show on the bill.

Optimisation as a loop rather than a one-off clean-up. Read-only access to every account feeds usage and billing data to the cloud's advisors and, on AWS, to a tool such as CloudFix. Candidates are agreed with the owners, applied through code, and move from potential to completed to realised once billing data confirms them. A monthly review and budgets keep the waste from coming back.

candidatesagreedrealised savingskeep itEvery account · read-only1 · Find2 · Decide with owners3 · Apply through code4 · Verify on the bill5 · Keep itThe levers, in order of paybackAWS accountproductionAWS accountdevelopment and testAmazon CloudWatchreal utilisationAWS Trusted AdvisorAWS Cost Explorerbilling and usageCloudFixAWS-vetted advisoriesSaving candidatepotentialOwner agreesperformance and riskChange in codeAWS CodePipelineor the owner's processCompletedRealisedconfirmed in billing dataMonthly reviewadvisory boardAWS Budgetsalerts on driftRightsizeRemove unusedScheduleCommitSpot capacityStorage classNewer generationsArchitecture

Point at a component to light its links; select it for what it does here and the practice that makes it right on AWS.

When to use it

  • A large estate of many accounts where nobody has time to look for savings
  • A central cloud office without write access to the workloads
  • Savings promised in an assessment that must now be proven

How NGT delivers it

Built from code, reviewed at a gate by an NGT architect, and handed over with runbooks your team can run.

FinOps