u/OfficeOk8949

While everyone is mining for gold in cloud (saving costs, scaling apps)

I’m building the shovel

Tools that detect hidden AWS/Azure waste before the bill arrives

What I mean is while other big companies like Microsoft azure and Amazon web services earn big money from cloud services I decided not to do same coz obviously I can’t stand a chance to compete against them they are like a multi billion dollar company

So I came up with this idea why not simplify what they do I mean make it more understandable for beginners to understand cloud bills and help them save money and create a tool on it

And I did that darted with manual audits and I’ve eleven doing great now Im happy to say Im launching my tool to help ppl save money on cloud fully automated with ai agents

Now if you guys want my services feel free to reach out

Im now in the process of creating a tool that helps ppl understand their cloud bills in simple terms and also help individuals save money on cloud

Im proud to say that it’s been a long journey but this month i managed to help out a small Saas team save $4927 on azure from $9800 they were paying

Thats wasn’t my first rodeo I mean I also did the same for some students in Austria who had problems understanding their azure bills

I would have posted as a case study source but they preferred me to explain rather than posting their details in replit

But feel free to reach out for free manual audits on your cloud bills and everything

Where ppl mess up in azure is that they get a VM azure assigns them an IP

You delete the VM and assume the IP is also delete but it’s still running your bill still is reading going up nickname it (silent killer )

In short

In azure networking resources live on their own

And can keep billing once compute is off

From the basics l learnt from cloud Im happy to say Im building a tool which does this 👇👇

1. Compute checker (VMs running)

What the code does

• lists VMs / EC2 instances

• checks state = running

• flags them

How it saves money

• catches machines left on after use

• stops 24/7 billing

2. Stopped vs deallocated (implicit in compute check)

What the code does

• surfaces VMs still consuming compute

• forces you to verify real state

How it saves money

• prevents “I stopped it but still paying” mistake

3. Unattached disk checker

What the code does

• lists disks / volumes

• checks if they have no VM attached

• flags them

How it saves money

• finds storage that keeps billing after VM deletion

4. Logs / monitoring checker (basic)

What the code does

•flags high log usage or growth

Logs don’t just stop coz tje app is idle they quietly grow on your azure bills everyday

How ppl loose money

You run a VM /app

Logs start collecting

You forget logs never stop

Reality -every request ,error,event is stored and billed

Why is it dangerous

It runs on background

It’s invisible

No warning feeling

Ppl think logs are just info

Azure thinks logs are stored data

So to prevent you from loosing money on this

Limit logs and delete old data

Disable unecessary logs

Reduce retention

Big misunderstanding ppl think I deleted VM everything is gone NOPE 👎 storage is independent

What actually stops is manually deleting disk

In azure every vn has a disk when you delete a VM the disk isn’t deleted

How ppl get big bills

Situation create VM

Use it

Delete it

You think everything is gone

Reality disk is still seated there

Billing continues

You make azure richer ..

now how to avoid this ask do I have disks with no vm attached 🤔

In portal look for unattached disks

And always remember storage is independent

Ppl think azure is stealing from them coz you stopped a VM but it’s not ..!!

Stopping a VM doesn’t mean billing stops only deallocation stops billing

In azure if you stop a virtual machine there are two states

1.stopped (allocated)

2.stopped (deallocated)

The first one you still pay to compute as azure has reserved the machine for you CPU is stained but the resource is still allocated

To avoid being billed after you thought you’ve stopped the VM you need to click the stop (deallocated) to avoid having surprise bills at tje end of the month

Let’s say in Virtual machines you are billed based on computing hours

Now this is how ppl get high bills…

You deploy your virtual machine

You test something and leave

You think 🤔 Im done

Reality vn keeps running 24/7

Example vm costs $0.06 per hour

One day 1.20

A week $8-10

That’s how random bills gives you shock

You think

Im not using it

Azure thinks

It’s ON -You pay

To avoid this don’t just leave the tab or the app you must click stop (deallocate)

Keep your heads up students on Azure to avoid this unexpected bills