FinOps
Make cloud cost visible, owned and lower, and keep it that way.
At a glance
NGT helps teams see, own and lower their cloud bill. Cost per team and environment comes first; then rightsizing, schedules, commitments and storage with each owner, and guardrails that price every change before it exists.
Account structure, tags and dashboards show cost by team, project and environment, so every owner sees their bill.
Rightsizing, schedules, commitments, Spot capacity and storage classes, agreed with each workload owner.
A cost estimate on every change, approval above a threshold and budget alerts, in pipelines and the platform.
One system: tag, allocate, alert, price, optimise, review
How the pieces fit on any cloud. Select a component for what it does and the practice behind it.
- Tag and allocateAccount structure and required tags put every cost on an owner, team and environment.
- Budget and alertBudgets per account and project; threshold and anomaly alerts reach the owner, not a shared inbox.
- Price every changeA cost estimate on each Terraform plan, policy checks, and approval above a threshold.
- Optimise and reviewCandidates agreed with owners, applied in code, verified on the bill and reviewed monthly.
Point at a component to light its links; select it for what it does here and the practice that makes it right on AWS.
Problems we solve
Five cost problems customers bring us, each with the architecture we use. Select one.
Idle and oversized resources in every account
Many accounts, each with idle instances, oversized databases and old storage. The central team has no write access, and one-off clean-ups drift back.
- Read-only scans against each cloud's advisors, and CloudFix on AWS
- Owners agree each fix and apply it through code
- A saving counts only once it shows on the bill
Savings tracked from potential to completed to realised, and counted only once they show on the bill.
Point at a component to light its links; select it for what it does here and the practice that makes it right on AWS.
The FinOps loop
Not a one-off clean-up: each turn makes cost a little more visible and a little more owned.
Estimate
Price every change before it is provisioned.
Three service areas
Customers start where it hurts most; most engagements end up touching all three.
Explore FinOps
4 pages, each a few minutes to read.
Frequently asked questions
What customers ask first.
With an assessment of your bills and usage: rates and trends, account hierarchy and tagging, and how each workload uses what it pays for.
It ends with findings, quick wins and a plan: who owns what, which levers first, and which guardrails to build.
We do not quote a percentage before we have seen the data. Assessment figures are labelled as estimates; a saving counts once it shows on the bill.
The quickest wins usually come from non-production: idle resources, environments running at night, oversized machines.
No. Analysis runs on read-only access and billing data; changes are made by the workload owners or through your pipelines.
Where you prefer, write actions stay disabled centrally and account owners apply every fix themselves.
AWS, Microsoft Azure and Google Cloud, starting with each provider's own cost data: the AWS Cost and Usage Report, Azure Cost Management and the Google Cloud billing export.
Then tools chosen per customer: InfraCost for estimates in pipelines, CloudFix for continuous AWS fixes, Datadog or Grafana for dashboards.
They should not. Estimates run inside the pipeline, development deploys freely, and approval is needed only above a threshold or for higher environments.
Right-sized defaults and cost tags come with the templates, so the cheap way is also the easy way.
A language model can draft saving suggestions from current billing and configuration data and send them to the owners.
Owners and engineers decide. Nothing changes because a model suggested it.
