v1.0.1 · Open source · Free to run

Your AWS bill
shouldn't surprise you

StackAlert watches your AWS costs against a 7-day baseline and pings you the moment something spikes — on Telegram, Slack, Teams, or PagerDuty. Before your bill arrives.

⚠️

"Our Lambda hit $47,000 in one weekend because of a single line of code. AWS Budgets sent an email — after we'd already been billed." — r/aws

stackalert · spike alert
// 2026-03-29 02:14 UTC · spike detected
AWSLambda spike detected
+2,847% vs 7-day baseline
Service AWS Lambda
Today so far$847.32
7-day avg $0.29/day
Projected ~$1,200 today
📱 Telegram sent #alerts Slack sent 🔴 PagerDuty incident
$
scroll

The problem

AWS billing has a 24-hour blindspot

AWS Cost Explorer shows yesterday's data. Budgets alert on monthly thresholds. Cost Anomaly Detection needs 10 days to warm up per service. A single bug can run up thousands while you sleep.

Features

Alerts that actually arrive in time

Not another dashboard to check. Real-time notifications to wherever your team already lives.

Per-service spike detection

Every AWS service gets its own 7-day rolling baseline. Lambda, EC2, RDS, S3 — each tracked independently. No more "is this spike normal?" guessing.

Lambda EC2 RDS S3 + all services

Zero data egress

Runs entirely inside your AWS account. Your cost data never touches an external server. GDPR compliant by architecture.

Daily digest at 08:00

Morning summary of yesterday's spend — every service, sorted by cost. Start your day informed.

CDK construct or Terraform module

Install as part of your existing IaC stack. One import, one deploy. No separate signup, no agent to run, no YAML to write.

// AWS CDK (TypeScript)
import { StackAlert } from 'stackalert-cdk'
new StackAlert(this, 'CostAlerts', {
notifyChannels: ['telegram', 'slack'],
spikeThreshold: 1.5,
})

Multi-account support

Monitor multiple AWS accounts via IAM role assumption. One StackAlert instance, all your accounts.

Alert channels

Alerts wherever your team already is

7 notification channels. Mix and match. No lock-in.

NOTIFY_CHANNELS="telegram,slack,pagerduty" // mix and match, comma-separated

How it works

Up and running in 5 minutes

No SaaS account to create. No agent to run. Just your AWS account.

1

Install via CDK or Terraform

Add the StackAlert construct to your existing IaC stack. Configure your notification channels and thresholds.

2

StackAlert learns your baseline

The Lambda runs every 6 hours, building a 7-day rolling average per service. No warmup period — works from day one.

3

Get alerted the moment costs spike

Instant push notifications on Telegram, Slack, or wherever. Includes service name, cost, baseline, and projected daily total.

Coming soon

Dashboard: cost history,
multi-account, team view

The open-source Lambda handles alerting. The dashboard gives your team a 90-day anomaly history, multi-account overview, and notification management — without touching environment variables.

    Preview dashboard →
    app.stackalert.app
    Preview
    3
    Accounts
    $1,247
    This month
    2
    Alerts today
    Recent anomalies
    Lambda
    prod-account · 2h ago
    +847%
    $847 vs $0.29
    EC2
    staging-account · 1d ago
    +180%
    $24 vs $8.50
    🚀 Dashboard launching soon

    Get early access to the dashboard

    The open-source Lambda is live now — free forever. Join the waitlist for the hosted dashboard and shape what gets built first.

    Early access users get: free beta access, direct line to the founder, and input on the feature roadmap.

    No spam. Unsubscribe anytime. Your email is never shared.

    Common questions