Where to start
| You want to | Read |
|---|---|
| See your own waste in ten minutes, free, with nothing hosted | Quickstart: free MCP server |
| Give Spendsaw scoped access to an account | Connect an AWS account |
| Understand a finding and where its dollar figure comes from | Findings and cost sources |
| Know what can run, and who has to approve it | Risk tiers and approvals |
| Fix Terraform-managed resources at the source | Terraform pull requests |
| Get the weekly digest and approve from Slack | Slack app |
| Pull costs, findings and savings into your own tools | API |
What runs today
Spendsaw is pre-launch. These three labels are used across the site, and each page says which one applies to it.
- Design partnersThe hosted service runs scheduled scans and a read API:
GET /v1/findings,GET /v1/findings/{id}andGET /v1/savings. Findings carry list prices. There is no sign-up and no web console; we create each tenant by hand, by invitation. Write to hello@spendsaw.com. - Built, not hostedSlack approve and snooze, spike alerts, Terraform pull requests, the model's explanations, billed cost and verified savings from the Cost and Usage Report, the white-label monthly report and billing. These run in the self-hosted application and are tested against mocked AWS. The hosted service does not have them yet, and remediation has never run against a live AWS account. The hosted weekly Slack digest is deployed and has not posted, because it needs the Slack app.
- Not yet publishedThe
spendsaw-mcppackage is not on PyPI, the source repository is not public, and there is no public Slack app or GitHub App. Until the repository is public, the self-hosted instructions in these docs describe how the code works, not something you can install.
How far each part has been proven is under status on the trust page.
How the pieces fit
- A read-only role scans your accounts for more than 25 resource types.
- Each result becomes a typed finding with a monthly cost and the source of that number.
- Ownership detection decides the route: Terraform-owned resources get a pull request, click-ops resources get a reviewed CLI command, and anything unknown stays a recommendation.
- A named person approves. Low and medium risk actions can then run under a separate write role. High risk never runs.
- Each cut is recorded in a savings ledger and compared with the bill in later months.
Names you will see: the roles and some settings still use the internal name, CostAgent.