Launching today

nable

Launching today

Cut your cloud and AI bill from inside your editor

13 followers

Cut your cloud and AI bill from inside your editor

13 followers

Visit website

Issue tracking software

•

Command line tools

•

Cloud Computing Platforms

Every cloud cost tool stops at the dashboard. nable doesn't. It's an agent that lives in Claude and Cursor: it finds the waste across your cloud and AI spend, drafts the fix as a Terraform PR or ticket you approve, then watches your next bill to see if the saving actually showed up. Local-first, propose-only, your own key. It never invents a number. Built to handle seven-figure bills spread across 14 providers.

Launch tags:SaaS•Artificial Intelligence•Tech

Launch Team / Built With

Viktor.comThe AI employee that does the work, in Slack & Teams

Promoted

Maker

📌

Every cloud cost tool I've ever bought ended the same way: a gorgeous dashboard that slowly became a tab I stopped opening. I've spent my whole career in this space, long enough to watch a dozen vendors get born, get acquired, then quietly disappear. The pattern never changed. Someone sells you a dashboard. They price it as a percentage of your cloud bill, so they earn more as your spend grows and less when they actually save you money. Then they hand you a list of recommendations you still have to act on yourself. The dashboard looks great. Your bill keeps climbing. I built nable because the shape was always wrong. What changed is that software can finally do the work instead of just charting it. A dashboard waits for you to open it. An agent doesn't. nable lives inside Claude and Cursor. You ask your whole cloud and AI bill anything in plain English, and it answers like an analyst who already knows your stack: it finds the waste, drafts the fix as a Terraform PR or a ticket you approve, then watches the exact line item it targeted on your next bill and tells you if the saving didn't show up. Read-only and propose-only. It never touches prod. And it gets sharper on your stack every time. Three things I wouldn't compromise on, because I've been burned by the alternatives: It runs locally on your own LLM key. Your bills never get pooled into someone else's multi-tenant warehouse. It never fakes a number. Exact dollars when it measured the line item, an honest range when it didn't. No tool should dress a guess up as precision. We don't take a cut of your cloud spend, and we don't mark up your AI. We charge for the tool, not for your bill being big. It's built for the reality I keep seeing: a million dollars a year and up, spread across 14 providers, with AI now climbing to the top of the bill faster than anything I've watched before. Today it's local and in your editor. For the people who own the bill but don't live in a terminal, a single-tenant hosted version is coming, your own isolated instance, never pooled with anyone else's. It's free. Run uvx nable, point it at your real bill, and tell me where it's wrong. That feedback is worth more to me than any upvote. Chandan

Report

1d ago

This is a strong take on cloud cost tooling. I like that nable does not stop at recommendations and actually drafts the fix for review.

How do you handle confidence when suggesting Terraform changes across different providers and billing structures?

Report

14h ago

Maker

@prashant_patil14
Thanks Prashant, good question to poke at. Two things stay separate: the savings number and the change itself.
The Terraform change itself is always propose-only. nable drafts the diff as a PR you approve, it never applies it, so a wrong call dies in review, not in prod. After you merge, it watches the exact line item the change targeted on your next bill and flags if the saving doesn't show up. That after-the-fact check is what keeps the confidence honest, and it tunes the next suggestion for your stack.

TLDR: precise when it measured, a labeled range when it inferred, human-approved either way, and verified on the bill afterward.

Report

8h ago