Suprascribe is an open-source, self-hostable platform that scans your inbox to automatically discover subscriptions across services that produce recurring billing, and it is aimed at individuals and small operators who want one dashboard showing what they pay for and when it renews.

What it is

Suprascribe is a web application built with Next.js 15 (App Router) and TypeScript, backed by Supabase (PostgreSQL with Row-Level Security) and authenticated through Supabase Auth with Google, Microsoft, and Apple OAuth. AI-driven discovery runs through the Vercel AI SDK with multi-provider support, so a deployment can point at OpenAI, Anthropic, or Groq, and Stripe handles a one-time Checkout Session for the paid tier. The code is licensed AGPL-3.0 and published at github.com/akomis/suprascribe, with a hosted instance at suprascribe.com.

The concrete problem is that recurring charges hide inside email receipts and renewal notices, so people lose track of what they signed up for and when it bills again. The free tier covers what a person already knows about, through manual subscription creation with no limit and multi-currency support, while the PRO tier removes that manual entry by reading Gmail, Outlook, iCloud, or any IMAP mailbox and extracting the subscriptions found there. Discovery is the difference between a tracker you must feed and a system that fills itself.

Key capabilities

• Automatic subscription discovery from Gmail, Outlook, iCloud, or any IMAP provider, built on OAuth credentials configured in Google Cloud Console and Azure Portal.
• Manual subscription creation with no limit, plus multi-currency support, on the free tier.
• Bring Your Own Key (BYOK): users supply their own AI API keys from dashboard settings for unlimited discovery, or the operator sets MODEL_API_KEY against OpenRouter as the default model.
• Subscription management dashboard with insights, complete history, and search, sort, and grouping of discovered subscriptions.
• Quick unsubscribe, renewal email reminders sent through Resend, and a calendar view of upcoming charges.
• Supabase Row-Level Security over PostgreSQL, with BYOK keys encrypted under an ENCRYPTION_SECRET generated by openssl rand -base64 32.
• One-time PRO upgrade through a Stripe Checkout Session, testable locally with stripe listen --forward-to localhost:3000/api/stripe/webhook.

Who uses it and how

• Individuals who want one dashboard of recurring charges discovered from their own mailbox instead of tracking signups by hand.
• Self-hosters comfortable running a Next.js 15 application with Supabase as the database and auth layer, since the stack assumes both.
• Privacy-conscious users who connect Google or Microsoft accounts through OAuth and prefer BYOK AI keys over an operator's model budget.
• Operators running a private instance, applying schema from supabase/migrations/ and exercising payment webhooks with the Stripe CLI.
• People evaluating before committing, through the hosted demo at suprascribe.com/demo.

Getting started

Clone https://github.com/akomis/suprascribe, run yarn under Node.js 20+ with Yarn v4, create a Supabase project, apply the files in supabase/migrations/ or run npx supabase db push, then copy .env.example to .env.local and fill in the Supabase, OAuth, and model variables. A hosted version and demo at suprascribe.com mean no installation is required to try it.

How it compares

No paid products that Suprascribe replaces are listed in the facts provided, and no similar subscription-tracking tools are named there either. On the available record it stands alone in this registry.

When to use it — and when not to

A self-hoster must operate a Supabase project for PostgreSQL and auth, register OAuth applications for Google and Microsoft, and optionally configure Stripe, Resend, and Brandfetch for payments, reminder emails, and service logos. The project is small and its documentation thin: 11 stars, 1 fork, a single open issue, no repository topics, and a README that stops mid-table at .env.exa, so anyone needing a settled API or an active community should look elsewhere. The AGPL-3.0 licence is also a real constraint, because modifying it and offering it as a network service carries source-disclosure obligations.

git clone https://github.com/akomis/suprascribe.git
cd suprascribe
yarn

npx supabase link --project-ref <your-project-ref>
npx supabase db push

stripe listen --forward-to localhost:3000/api/stripe/webhook

cp .env.example .env.local

openssl rand -base64 32
# paste output into ENCRYPTION_SECRET

yarn dev

yarn dev          # Development server (Turbopack)
yarn build        # Production build
yarn lint         # Lint and auto-fix
yarn format       # Format with Prettier

yarn lint    # must pass
yarn build   # must pass