Introduction
What Subsweep is, what ships in the package, how a charge becomes a flagged subscription, and where to start reading.
3 min readUpdated Oct 17, 2026Applies to Subsweep 0.1.0
On this page
Subsweep finds the software subscriptions a small business pays for, flags the ones that waste money, and reminds the owner before the next renewal. Everything points at one number: estimated monthly savings.
You can run it for one business, or sell it to many businesses as a hosted service with the included Free, Pro and Accountant plans and Stripe billing.
Tip
Want to see it first? The live demo at subsweep.app has a one-click demo shop (Northwind Studio) on its sign-in page. It is a shared sample workspace: other visitors may be using it at the same time, and it is reset when it is empty or more than a day old.
What is in the package
| Area | What you get |
|---|---|
| Sources | Manual add, a 48-tool quick-add checklist, a UPI Autopay mandate form, statement upload (CSV, XLSX, text-layer PDF), bank feeds through Plaid, and Gmail and Outlook receipt scans |
| Detection | A rules-based engine that groups charges, finds weekly, monthly, quarterly, yearly and custom cycles, scores confidence and raises waste flags |
| Day to day | Subscription list with Keep / Unsure / Cancel tags, detail panel, renewal calendar, actions queue, savings tracker, offboarding checklist, overview dashboard |
| Alerts | Renewal reminders, manual charge checks, email alerts and a monthly or weekly digest, all driven by one hourly job |
| Teams | Owner, Editor and Viewer roles with email invites, plus accountant accounts that hold several client workspaces |
| Selling it | Free, Pro and Accountant plans, a 14-day Pro trial, Stripe Checkout, customer portal and webhook |
| Extras | CSV export, a printable report, an expiring share link, a browser extension, light and dark themes, an installable web app |
| Source and tooling | Full TypeScript source, a bootstrap SQL schema, a Stripe price setup script, vercel.json with an hourly cron, a docker-compose.yml for a local Postgres, and unit tests for detection, statement parsing, sign-up, billing and bank return rules |
It is built with Next.js 16 (App Router), React 19, TypeScript, Drizzle ORM on Postgres (with embedded PGlite for local development), Better Auth and Tailwind CSS 4.
Note
Subsweep does not use any AI model. Detection is plain rules: merchant patterns from a catalogue of 534 vendors in 25 categories, interval checks and a confidence score. Nothing is sent to an AI provider.
How a charge becomes a flag
- A source brings in charges. A bank feed, a scanned receipt or an uploaded statement becomes rows in a transactions table. Manual entries skip this step and become subscriptions directly.
- Detection groups and scores them. Charges are matched to a known vendor (or kept as an unknown online merchant), grouped, checked for a regular interval and scored. High-confidence groups become subscriptions; medium-confidence groups become subscriptions marked Needs review; low-confidence groups are ignored.
- Flags explain the waste. Overlapping tools in the same category, price changes and trials that turned into paid plans are flagged with a one-sentence explanation and an estimated monthly saving.
- The owner acts. Tag a subscription Cancel, copy the pre-written cancellation email, then mark it cancelled to add the saving to the tracker.
- The hourly job keeps it current. It syncs bank feeds, re-runs detection, schedules reminders and sends alerts and digests.
Adding and detecting subscriptions covers each step in detail.
What you need to run it
The short version, detailed on Requirements:
- Node.js 20.9 or newer (22 recommended) and a PostgreSQL 13 or newer database.
- A host for a Next.js app: Vercel (the package is set up for it) or your own server behind HTTPS.
- Something that calls the job endpoint once an hour.
- Outbound email (any SMTP account or Resend) for sign-in links, verification, invites and alerts.
- Optional keys for Stripe, Plaid, Google, Microsoft and the other integrations.
Third-party usage (hosting, database, email, payments, bank data) is billed to you by those providers and is not included in the purchase.
Where to go next
- Evaluating? Read Requirements, then Known limitations and the FAQ.
- Trying it locally? Quick start runs it on your laptop with no database server and no keys.
- Going to production? Follow Installation and deployment, then Configuration.
- Selling it to businesses? Read Plans, billing and selling it as SaaS, including the licensing note.