Frequently asked questions.

SpendSage uses an IAM cross-account role and STS AssumeRole. The existing product documentation describes this as a scoped connection using temporary credentials, rather than asking for or storing permanent AWS passwords or long-lived keys.

No. The current product documentation states that SpendSage does not ask for or store permanent credentials. The connection uses an IAM cross-account role and temporary credentials through STS AssumeRole.

SpendSage is designed to ingest Cost & Usage Reports (CUR) along with infrastructure and configuration metadata. The documented workflow also references resource information such as EC2, EBS, RDS metadata, tags, and account structure.

The product pages describe detection of idle EC2 instances, unused EBS volumes, stale snapshots, unattached Elastic IPs, and resources that are idle, unattached, or oversized for their actual usage. It also provides rightsizing suggestions for compute, storage, and database resources.

Yes. Spike explanation is one of the documented product capabilities. SpendSage uses AI-based root cause analysis to help explain sudden changes in cloud costs.

Recommendations are ranked using estimated monthly savings, impact, and risk. The product pages describe ranking the biggest wins first and showing a risk level for every recommendation.

The product is designed around analysis and approval before automation. Approval-based automation is documented as a product capability, while Terraform and pull-request generation are currently marked as coming soon on the product page.

Yes. The current pricing page lists a Free plan at ₹0/month with 1 account, 7 days of historical data, a basic cost dashboard, basic waste detection, and top savings opportunities.

The pricing page describes the Founding 5 program as an offer for the first five companies using SpendSage. Those customers receive the Starter plan at a special founding price for the first 12 months plus direct access to the founding team.

SpendSage is positioned for engineering teams managing AWS at scale, particularly teams that need clearer cloud cost visibility, waste detection, cost-spike analysis, forecasting, and prioritized savings recommendations.