Slack
Daily digest and same-day anomaly alerts in the channel your team already watches. No dashboard to open.
StackSpend + SlackWhat does StackSpend integrate with?
StackSpend connects to AWS, GCP, Azure, Vercel, Snowflake, ClickHouse Cloud, Elastic Cloud, OpenAI, Anthropic, Hugging Face, Grok (xAI), Cursor, GitHub, and Twilio with read-only credentials. It delivers daily digests and anomaly alerts to Slack, Microsoft Teams, and email; creates and syncs tickets in Linear and Jira with status flowing both ways; and pushes anomaly and budget events to webhooks alongside a full REST API. Connect in about 5 minutes and load 90 days of history automatically.
Integrations
Connect your stack. Nothing new to adopt.
Read-only links to every provider you spend on. Cost lands where your team already works — Slack, Teams, email — and turns into tickets in Linear and Jira, or events on your webhooks.
14 providers · 5-minute setup · 90 days of history on connect
Sources
Every provider you spend on.
Connect with read-only credentials — keys, tokens, or a scoped service account. Each bill is normalised into one daily number, with up to 90 days of history loaded the moment you connect.
AI & LLM
Token-level spend across model providers and assistants.
Data & communications
Warehouse compute and messaging usage, billed daily.
Don't see your provider? Tell us what to add — new providers ship regularly.
Destinations
It lands where your team already works.
StackSpend pushes out, rather than asking anyone to log in. The daily digest and anomaly alerts arrive in Slack, Microsoft Teams, or email; the work to fix a spike becomes a ticket in Linear or Jira, assigned and synced both ways; and a critical spike can page whoever is on call through PagerDuty, incident.io or Better Stack.
- ✓Alerts routed to the right channel and the right owner.
- ✓Tickets assigned by email — they land on the owner, not a backlog.
- ✓Two-way status sync on tickets: close the ticket, the anomaly resolves.
- ✓Better Stack is two-way out of the box: acknowledge or resolve there and the anomaly follows.
- ✓incident.io can be two-way — add an API key with alert read access and resolving there closes the anomaly.
- ✓PagerDuty is outbound only: we open and close the incident, its state stays PagerDuty’s.
Delivery
Microsoft Teams
The same digest and alerts delivered to a Teams channel via the StackSpend app.
StackSpend + Microsoft TeamsA scheduled morning summary for anyone who lives in their inbox — totals, trend, and what needs attention.
Work tracking
Linear
Anomalies and monthly budget reviews become tickets — severity-labelled, assigned to the owner by email, status synced both ways.
StackSpend + Linear
Jira
Same two-way sync against your Jira project and issue types. Close the ticket and the anomaly resolves; the saving lands on the ledger.
StackSpend + JiraOn-call paging
Cost spikes can page whoever is on call, through the tool your rotation already lives in. The default is critical-only above a dollar floor, because a cost spike rarely justifies a 3am phone call. Included on the Business plan.
PagerDuty
Critical cost anomalies become PagerDuty alerts on a service you choose, de-duplicated so a multi-day spike is one incident, and resolved when someone resolves the anomaly in StackSpend. Paste an Events API v2 key.
On-call docs
incident.io
Anomalies arrive as incident.io alerts with a deduplication key and thirteen cost fields, so your existing escalation paths decide who gets paged. Add a read-scoped API key and resolving there closes the anomaly here.
On-call docs
Better Stack
StackSpend creates the incoming webhook and every parsing rule for you — no JSON mapping. Two-way from the start: acknowledge or resolve in Better Stack and the anomaly follows.
On-call docsBuild on it
Wire it into anything.
Everything the dashboard shows is available over a REST API, and every anomaly or budget event can fire a webhook. Trigger runbooks or feed your own FinOps tooling — the plumbing is yours. Paging your on-call rotation needs none of it; that is built in.
Webhooks
Anomaly and budget events pushed to your endpoint to trigger runbooks, CI jobs, or any custom workflow. Paging PagerDuty, incident.io and Better Stack is built in — no receiver to write.
Webhook docsREST API
Programmatic access to every cost figure the UI shows — pull spend, budgets, and anomalies into your own tools.
API referenceWebhook event payload
{
"event": "anomaly.created",
"provider": "aws",
"service": "NAT Gateway",
"severity": "high",
"amountUsd": 891.40,
"expectedUsd": 286.05,
"deviationPct": 212.0,
"timestamp": "2026-03-22T09:14:00Z"
}Delivered on every anomaly and budget threshold
Connect once. Cost shows up everywhere your team already is.
Read-only setup in about five minutes. Get 90 days of history and start receiving daily updates — in Slack, Teams, or email — before the next invoice lands.
14-day free trial. No credit card required. Plans from $79/month.
Read-only cost access
AES-256 encryption
Tenant isolation
GDPR compliant