Skip to content
Balkan Tecnologia
AccessibilityGet in touch
Balkan Tecnologia

Understand your cloud bill and cut the waste

We break your cloud bill down by service, environment and product, find idle or oversized resources and set budget alerts so the bill holds no surprises.

A mint-green thread stretched over a brass pulley, unwinding from a wooden spool.

Who it's for

For companies whose cloud bill grows every month and nobody can explain why.

What it solves

  • The bill arrives with hundreds of lines, and nobody knows which product spends what.
  • Test environments stay on overnight and at weekends, unused.
  • Servers and databases were sized for a peak that never came.
  • Disks, snapshots and addresses from old projects are still being charged.
  • A rise in the bill is only noticed when the month closes.

What we do

Reading the bill
Spending split by service, environment and product, with the largest items at the top.
Tagging standard
Every resource labelled with owner, environment and project, a rule applied in the infrastructure code.
Idle resources
Unused machines, disks and snapshots, and test environments switched off outside working hours.
Right-sizing
Servers and databases adjusted to measured use, keeping the headroom the peak needs.
Usage commitments
Analysis of committed-use discounts; the purchase decision stays with your finance team.
Budget alerts
A warning when a product's or an environment's spending strays from the plan.

What you get

  • A report on the bill by service, environment and product
  • A tagging standard applied in the infrastructure code
  • A list of actions, each with its expected effect and risk
  • Budget alerts configured in the provider account
  • A cost dashboard to follow month by month

How we do it

  1. Read-only access

    Read-only access to the bill and the account, without changing anything.

  2. Assessment

    Where the money goes, what sits idle and what is too big.

  3. Action plan

    Each action with its expected effect, risk and decision-maker, for your team to approve.

  4. Changes

    Applied through the infrastructure code, with a way back.

  5. Follow-up

    Dashboard and alerts so spending does not creep up again unnoticed.

Technology examples

  • AWS Cost Explorer
  • Google Cloud Billing
  • Azure Cost Management
  • OpenCost
  • Infracost
  • Terraform

Related services

FAQ

How much can we save?

That can only be said after the assessment. It depends on how much sits idle, how the system was sized and what your team is willing to change.

Can cutting costs make the system slower?

It can, if done blindly. So each adjustment starts from measured use, keeps headroom for the peak and is followed by alerts and metrics after the change.

Do you negotiate with the provider or buy reservations for us?

No. Contracts, reservations and usage commitments are your company's decisions. We show the options and what each one requires; your finance team makes the purchase.

Is this a one-off job or ongoing?

It can be both. The assessment and first actions form a fixed project. After that, follow-up stays with your team, using the dashboard and alerts, or becomes part of a maintenance contract.

Write to Balkan

Talk to us about your project