spend-cap-manager

# Spend Cap & Budget Management Expert ## Service Limits | Service | Free Tier | Spend Cap | Budget Control | |---------|-----------|-----------|----------------| | Supabase | Yes | Built-in | Dashboard | | Cloudflare | Yes | Manual | Workers/KV | | Redis | Varies | Provider | Provider | | Vercel | Yes | Built-in | Dashboard | | Netlify | Yes | Built-in | Dashboard | ## Audit Workflow ### Step 1: Check Current Usage Verify usage against free tier limits for each service. ### Step 2: Configure Spend Caps Enable built-in spend caps where available. See `cases/supabase-spend-cap.md` for Supabase configuration. ### Step 3: Implement Budget Controls For services without built-in caps, implement custom controls. See `cases/cloudflare-budget.md` for Workers/KV budget control. ### Step 4: Set Up Alerts Configure notifications before hitting limits. ## Matching Cases | Service | Case File | Control Type | |---------|-----------|--------------| | Supabase | `cases/supabase-spend-cap.md` | Built-in cap | | Cloudflare | `cases/cloudflare-budget.md` | Custom budget | ## Threshold Recommendations | Service | Warning | Critical | Action | |---------|---------|----------|--------| | Supabase DB | 70% | 90% | Enable cap | | Supabase Storage | 70% | 90% | Enable cap | | Workers requests | 70% | 90% | Rate limit | | D1 Row Reads | 70% | 90% | Query cache | | KV operations | 70% | 90% | Local cache | ## Output Format ``` ## Spend Cap Management Report ### 1. Current Status | Service | Usage | Limit | Status | Spend Cap | |---------|-------|-------|--------|-----------| | Supabase DB | X MB | 500 MB | X% | Enabled | | Workers | X K | 100 K | X% | Manual | ### 2. Recommendations 1. [Service]: Enable spend cap / Set budget limit 2. [Service]: Set alert at X% threshold ### 3. Implementation Reference: cases/<case-name>.md ```