/estimate-temps-savings

name: estimate-temps-savings
description: |
  Audit a project's infrastructure and SaaS stack, then produce a cost report showing what the user currently pays and what they would save by consolidating onto Temps (self-hosted or Temps Cloud). Detects hosting platforms (Vercel, Netlify, Railway, Render, Heroku, Fly.io), analytics (PostHog, Plausible, Mixpanel, Amplitude, Fathom), error tracking (Sentry, Bugsnag, Rollbar, Honeybadger), session replay (LogRocket, FullStory, Hotjar, Highlight), uptime monitoring (Pingdom, UptimeRobot, Better Stack, Checkly), managed databases (Supabase, Neon, PlanetScale, MongoDB Atlas, Upstash, RDS), and transactional email (SendGrid, Postmark, Resend, Mailgun) from dependencies, config files, and env var names. Use when the user wants to: (1) Know how much they would save by switching to Temps, (2) Audit their SaaS/infrastructure spend, (3) Compare their current stack's cost against self-hosting, (4) Decide whether Temps is worth it, (5) Build a business case for consolidating tools. Triggers: "how much would I save", "temps savings", "cost comparison", "audit my stack", "am I overpaying", "saas spend", "calculate savings", "is temps cheaper".

Estimate Temps Savings

Scan the current project, detect every paid SaaS tool it depends on, estimate the monthly bill, and show the delta against running Temps instead. The output is a savings report the user can act on (or show their team).

Temps is a self-hosted PaaS that replaces the deployment platform, web analytics, session replay, error tracking, uptime monitoring, managed databases, and transactional email relay with a single binary. Self-hosting is free (you pay only for the server); Temps Cloud is a managed server at cost + 30% (from ~$6/mo).

Ground Rules

1. **Never read or print secret values.** Detection uses dependency names, config file presence, env var **key names**, and the **hostname** of connection strings only. If you must open a `.env*` file, extract key names (`cut -d= -f1`) — never echo values into the report or your reasoning. 2. **No vanity math.** Only count tools you actually detected. If a tool has a free tier the user likely fits in (e.g. Google Analytics, small Sentry dev plan), say so and count $0 or a range starting at $0. An inflated savings number destroys trust; an honest one converts. 3. **Ranges, not fake precision.** You don't know the user's plan. Report low/typical estimates and label them as list-price estimates. If exact numbers matter, tell the user which invoices to check. 4. **Be honest about what Temps does NOT replace** (see the "Not replaced" section below). Always include it in the report.

Step 1 — Detect the Stack

Run these checks from the project root. Check dependency manifests (`package.json`, `requirements.txt`, `pyproject.toml`, `Gemfile`, `go.mod`, `Cargo.toml`), config files, CI workflows (`.github/workflows/`), and env var key names in `.env*`, `.env.example`, `docker-compose*.yml`, and IaC files.

| Category | Signal → Tool | |---|---| | **Hosting** | `vercel.json` or `.vercel/` → Vercel · `netlify.toml` → Netlify · `railway.json`/`railway.toml` → Railway · `render.yaml` → Render · `fly.toml` → Fly.io · `Procfile` + no Dockerfile → Heroku · `amplify.yml` → AWS Amplify | | **Analytics** | `posthog-js`/`posthog-node` → PostHog · `plausible-tracker` or plausible.io script tag → Plausible · `mixpanel-browser` → Mixpanel · `@amplitude/*` → Amplitude · `fathom-client` → Fathom · `@segment/analytics-*` → Segment · `@vercel/analytics` → Vercel Analytics | | **Error tracking** | `@sentry/*`, `sentry.properties`, `sentry-sdk` → Sentry · `@bugsnag/*` → Bugsnag · `rollbar` → Rollbar · `@honeybadger-io/*` → Honeybadger | | **Session replay** | `logrocket` → LogRocket · `@fullstory/browser` → FullStory · Hotjar script tag / `HOTJAR_ID` → Hotjar · `@highlight-run/*` → Highlight · PostHog with `session_recording` config → PostHog Replay | | **Uptime / status** | `checkly.config.ts` → Checkly · env keys or CI mentioning Pingdom / UptimeRobot / Better Stack (BetterUptime) / Statuspage | | **Managed DB / cache** | `@supabase/supabase-js` or `supabase.co` host → Supabase · `@neondatabase/serverless` or `neon.tech` host → Neon · `@planetscale/database` or `psdb.cloud` host → PlanetScale · `mongodb+srv://` or `mongodb.net` host → MongoDB Atlas · `@upstash/redis` or `upstash.io` host → Upstash · `rds.amazonaws.com` host → AWS RDS · `redns.redis-cloud.com` host → Redis Cloud | | **Transactional email** | `@sendgrid/mail` / `SENDGRID_API_KEY` → SendGrid · `postmark` / `POSTMARK_SERVER_TOKEN` → Postmark · `resend` / `RESEND_API_KEY` → Resend · `mailgun.js` / `MAILGUN_API_KEY` → Mailgun · `email-smtp.*.amazonaws.com` → AWS SES (already cheap — flag, don't count) | | **Observability (partial)** | `DD_API_KEY`/`datadog` → Datadog · `NEW_RELIC_LICENSE_KEY` → New Relic (Temps covers logs/metrics/traces basics — count partially, note the caveat) |

Env key names worth grepping for: `SENTRY_DSN`, `NEXT_PUBLIC_POSTHOG_KEY`, `MIXPANEL_TOKEN`, `AMPLITUDE_API_KEY`, `SEGMENT_WRITE_KEY`, `LOGROCKET_APP_ID`, `DATABASE_URL`, `REDIS_URL`, `MONGODB_URI`, `UPSTASH_REDIS_REST_URL`, `VERCEL_TOKEN`, `NETLIFY_AUTH_TOKEN`, `RAILWAY_TOKEN`, `FLY_API_TOKEN`.

Multi-repo note: if the user says this is one of several apps, ask how many apps/environments share these tools — per-seat and per-project pricing multiplies.

Step 2 — Ask for Usage (only what's needed)

Ask ONLY about categories you detected, in one batch. Every question needs a default so the user can answer "don't know":

• Team seats with dashboard access (drives Vercel/Netlify per-seat) — default 2
• Monthly pageviews or analytics events — default 100k pageviews
• Errors/month sent to error tracking — default within Sentry Team tier
• Session recordings/month — default 5k
• Emails sent/month — default 20k
• Number of uptime monitors — default 10
• Databases/branches in use — default 1 production DB

If the user answers "jus