# Marcus Tilden, Senior Cloud Infrastructure Engineer at Cartridge Health — read of Cloud Price Alert, June 18 2026

> 9 years in infrastructure, currently the one-man cloud team at a 180-person Series B health-tech company. We run about $40k/month across AWS and a sliver of GCP. I coach U8 soccer on Saturday mornings and I miss half of them because of Slack fires.

## How I got here

Googled "aws price change notification" sometime around 10pm after our April bill came in $6k over forecast and I couldn't immediately explain why. Third result was a Reddit thread that mentioned something like this. Clicked a link from there that bounced me to this page. I had low expectations.

## What I clicked first

The mock alert in the hero stopped me. The specificity of it: `aws:us-east-1:ec2:m5.large ALERT Price jumped 18% in 2h Old: $0.096/hr → New: $0.113/hr`. That is the right format. That is the thing I actually want to see in Slack. Not a dashboard, not a weekly digest. That exact message at that level of granularity. I scrolled down.

## Where I paused

The "Poll AWS, GCP, Azure, and DigitalOcean pricing APIs every 15 minutes" line. I stopped here for a while. Because here is the thing: AWS on-demand list prices do not change every 15 minutes. They barely change once a quarter. What changes constantly is Spot pricing. But the page is marketing against the scenario where "your cloud provider just raised prices" like it's a surprise event that snuck up on you. That is not how AWS pricing works. They announce changes. The real problem I have is not that AWS secretly raised m5.large by 18% overnight. The real problem is that I had 14 Reserved Instances expire and didn't catch it, or a new workload got launched in the wrong region. That's a cost anomaly, not a price spike. I'm not sure this page understands its own problem.

## What I distrusted

Two things.

One: "Honest disclosure: we don't have live customers on this idea yet. We shipped the strategy package; you ship the customer conversations." I respect the transparency, I genuinely do. But that sentence, combined with "Adopt the build $99 - $199" and "Dossier plus the working code starter," tells me I am on a product idea marketplace, not a product page. The alert mock-up I liked so much is a design mock. There is no live polling of any pricing API happening right now.

Two: The yearly impact math. "Est. yearly impact: $149k" from an m5.large going up $0.017/hr. That math implies you're running roughly 1,000 of those instances continuously. If you have 1,000 m5.larges in one region, you have a FinOps team and you are not finding this on a Google search at 10pm. The scenario and the customer don't match.

## What would convince me

Show me a screenshot of an actual Slack message that fired from a real AWS account. Not the mock. Show me the raw pricing API response you polled and the logic that decided it crossed a threshold. I want to see what happens when AWS does one of their actual list price changes, like the time they changed EBS pricing in 2023. Did the tool catch it? What did the alert look like? What did the migration roadmap suggest?

And honestly, if this is really about Spot price volatility rather than list price changes, say that. That is a real problem and I would pay for a good solution to it. The repositioning to Spot monitoring would make more technical sense and the hero would still basically work.

## What I'd ask in an email reply

1. When you say "poll pricing APIs every 15 minutes," are you hitting the public pricing endpoints like `pricing.us-east-1.amazonaws.com` or are you pulling from Cost Explorer or billing exports? Because those are very different latencies and very different data.

2. The alert mock shows an 18% change in 2 hours on an on-demand instance type. Can you give me one real example from AWS, GCP, or Azure where a list price moved that fast on a standard instance? I'm asking because I don't think that happens, and I want to understand what your tool is actually detecting.

3. The $199/mo Professional tier is reasonable if this works. But you said there are no live customers. Is there a beta or a proof-of-concept I can point at a read-only billing role for 30 days before any money changes hands?

## Verdict: on-the-fence

The visual mock hit the right nerve and the pain is real, but the technical premise has a hole in it that the page never addresses. If the founder can answer question two honestly, I'm probably booking a call.

---
*Memo by skeptic persona, generated 2026-06-18. Studio breaks own self-grading loop.*