The cloud bill question we couldn't answer, so we built ZopNight
Wanted to share what we've been building, and the one question that started it.
Last quarter, someone in finance asked us: of everything we spend on cloud and AI, which parts are actually creating value? We had dashboards for how much we spent. Not one of them could tell us whether it was worth it. That gap bugged us enough to build around it.
When teams run real infrastructure across AWS, GCP, and Azure, spending gets hard to control. Resources sit idle nights and weekends, ownership is unclear, and the path from "this looks wasteful" to "it's actually fixed" runs through spreadsheets and risky manual changes.
What is ZopNight?
ZopNight is a Technology Value OS for AI, Cloud, and Humans. You connect AWS, GCP, and Azure read-only, and it runs one continuous loop: find, own, fix, prove:
• Finds the waste your dashboards miss (idle resources, over-provisioned instances, orphaned storage, the cross-cloud stuff nobody checks).
• Route ownership so every resource has a name next to it, and nothing stays "nobody's problem."
• Automates the boring optimisation (schedule non-prod off, right-size, prep for spikes), with one-click fixes behind an approval gate.
• Proves which spend is actually creating value, including your AI and LLM bill, tied back to teams and outcomes.
Connect your accounts, run the audit, and see the number. Nothing moves until you say so, and ZopNight never touches your databases.
Why it exists
Every cloud already ships its own advisor (Trusted Advisor, GCP Recommender, Azure Advisor), but each one only sees its own cloud and a fixed checklist. None of them tells you who owns a resource or whether it's worth keeping. We wanted one place that spans all three, plus the AI runtime, and that we'd actually trust near production.
Who is it for?
Engineering, platform, and FinOps teams running production infrastructure on AWS, GCP, or Azure who want to cut idle spend, attribute every dollar, and optimise safely without slowing down the people shipping.
If you've ever been the person who had to explain the cloud bill, you'll recognise a lot of this. Curious how others here are tracking cloud + AI value today?
I like the shift from cost optimization to value optimization. Most dashboards can tell you where money went. The harder question—and the one leadership actually cares about—is whether that spend created enough value to justify it. That's a much more interesting problem to solve.
Where did the money go? is a solved problem; every dashboard answers it. "Was it worth it?" is the one nobody can answer, and it's the only question leadership actually asks. That's the whole reason we built toward value, not just cost. Tying spend back to a team, a tag, and an outcome is harder than flagging an idle VM, but it's the part that changes the conversation from "cut the bill" to "is this investment paying off?"
Who usually ends up owning that "was it worth it" question today?
From what I've seen, that's exactly the problem—everyone owns a piece of it, but very few organizations own the decision itself.
I've got a couple of thoughts on why that happens and how it changes product positioning, but they're easier to explain over email than in a thread.
What's the best email to reach you on?
Yes, sure! Email me at muskan.bandta@zop.dev would like to hear your thoughts.
Thanks! I've just sent it over.
Looking forward to hearing your thoughts whenever you have a chance.