u/Cute-Inevitable-2059

Been working on something called nable. It's a local MCP server that connects your billing APIs (AWS, Azure, GCP, plus Datadog, Snowflake, Stripe and a few others) to Claude or Cursor so you can ask questions about your spend in plain English.

But it's not just a connector. Here's what it actually does on top of the raw data:

Anomaly detection that compares same weekday baselines, not flat rolling averages. So it knows the difference between a Friday deploy spike and a Tuesday something-is-wrong spike.

Tag-based attribution : map your resource tags to teams in a YAML file, get spend ranked by team across every provider in one query.

Budget enforcement with a CI gate : set limits in a budget.yml, the CI step exits non-zero when you're over. No more end-of-month surprises.

Rightsizing that actually files the ticket : reads CloudWatch CPU metrics, finds the idle resources, calculates the savings, opens the Jira or Linear or GitHub issue for you.

RBAC for teams : viewer, analyst, admin roles with per key team scoping. The platform team sees platform costs. That's it.

Runs locally, credentials never leave your machine, no cloud sync, nothing to breach on our end.

Genuinely want to know:

• Is this solving a real pain or is the answer just "hire a FinOps analyst"
• What does your current workflow actually look like when someone asks why the bill went up
• What would make you never use something like this
• What would you expect to work on day one
• Anything else or things not working let me know: this is meant to be a free tool for pure visibility

Free to use, no account needed: nable.sh

Not trying to sell anyone anything, just want to know if this is useful before I build more of it.

Hey everyone. I’ve been in FinOps for a few years and one thing that never stopped bothering me is how long it takes to answer what should be a simple question. “Why did our Datadog bill spike?” becomes a whole thing. Dashboards, exports, pinging someone on the data team, waiting.

I built nable to close that gap. You connect it to your billing sources, AWS, Azure, GCP, Datadog, Snowflake, and about eight others, and you just ask questions in plain English. No SQL, no dashboards, no ticket to the data team.

Still pretty early. I’d genuinely love to hear from people here about what questions take you the longest to answer today, because that’s exactly where I want this to be useful. BTW it’s free.

Check it out if you’re curious: [nable.sh](https://nable.sh)

Hey everyone. I’ve been in FinOps for a few years and one thing that never stopped bothering me is how long it takes to answer what should be a simple question. “Why did our Datadog bill spike?” becomes a whole thing. Dashboards, exports, pinging someone on the data team, waiting.

I built nable (nable.sh) to close that gap. You connect it to your billing sources, AWS, Azure, GCP, Datadog, Snowflake, and about eight others, and you just ask questions in plain English. No SQL, no dashboards, no ticket to the data team.

Still pretty early. I’d genuinely love to hear from people here about what questions take you the longest to answer today, because that’s exactly where I want this to be useful. BTW it’s free.

Check it out if you’re curious: nable.sh