GetNotes.ai — AI Meeting Notes SaaS

Plan limits live in one file, lib/plans.ts, read by the process route, the usage endpoint and the UI. Free is one meeting ever (a lifetime quota window, not monthly), 30 minutes, with a 60 MB upload backstop. Pro is unlimited meetings, 3 hours per recording, a 400 MB backstop and a 25-hour monthly audio cap. One source of truth is why the client can pre-check limits and still be honest: the server enforces the identical numbers. The fair-use cap is a duration cap, not a meeting cap, because meetings vary wildly in length and a meeting count says nothing about cost. The route sums duration_seconds across the user's non-error meetings since the start of the calendar month and rejects with a 402 and a machine-readable monthly_audio_exceeded before it calls ElevenLabs or Claude.

The meeting row is inserted as status processing before any audio is downloaded. That row holds the quota slot, so two parallel requests from the same user cannot both pass a count check that neither has yet incremented. It also gives the UI something to poll and gives failures somewhere to record an error_message instead of vanishing. Duration is then measured server-side with music-metadata against the downloaded buffer, because browser-recorded WebM often ships without usable metadata, and over-limit audio is marked errored and deleted from storage rather than left in a bucket I pay for.

Transcription uses ElevenLabs Scribe with diarize set to true, and I post-process the word-level response myself rather than taking the flat text. Words are grouped into lines when the speaker changes or after a silence gap of more than 8 seconds, and each line is stamped as [MM:SS] Speaker N. That structure is what makes the minutes attributable, and it is what Claude sees.

Notes generation is deliberately non-fatal. A transcription failure returns a 502 and stops the pipeline, but if Claude errors or returns stop_reason refusal, the transcript is still saved and the response carries a notesGenerated flag plus a human-readable notesError. Input and output token counts are stored per meeting so cost per meeting is measurable rather than guessed. Because the prompt asks Claude to wrap critical phrases in mark tags, model output reaches the DOM, so the markdown converter escapes all HTML first and then re-enables only that one tag.

The browser recorder mixes the microphone with optional tab audio captured through getDisplayMedia, joined in an AudioContext destination stream, so an online meeting can be captured without a bot joining the call. iOS Safari cannot record audio/webm, so the recorder falls back to audio/mp4 when the type is unsupported.

Subscription state is written only by the Stripe webhook, through the service-role client, keyed on stripe_customer_id with fallbacks to client_reference_id and customer metadata. The endpoint subscribes to exactly the three events the handler implements. Row-level security on profiles allows reads of your own row and no user writes at all, so a user cannot promote themselves to Pro.

Mobile reuses the web API instead of duplicating it. The route-handler Supabase client accepts either scheme: session cookies for web, or an Authorization bearer token for the Expo app. Because quotas, plan gating and processing all key off the authenticated user rather than the client type, that one fallback was the only backend change the app needed.