The Origin
This was built over a weekend - not as a portfolio piece, but to solve a problem discovered in practice.
Google Meet attendance records, transcripts, and recordings are gated behind Google Workspace Enterprise plans. For anyone on a personal account or a lower-tier Workspace plan, that data is either inaccessible or deleted after a short retention window. Founders, coaches, recruiters, and freelancers - people who run high volumes of meetings but aren't on Enterprise plans - have no way to retrieve what happened in a meeting last month.
The fix shouldn't require an Enterprise upgrade.
The Solution
Meeting Analyzer lets any user sign in via Google OAuth and access up to one month of past meeting data - for free - regardless of their Workspace plan tier. A MongoDB-backed permanent archive then retains all synced meeting data indefinitely, beyond whatever the platform's own retention limits are.
The result: a unified dashboard for searching, streaming, and downloading attendees, transcripts, and recordings - from meetings that Google itself may have already deleted.
Key Features
| Feature | Detail |
|---|---|
| 1-Click OAuth Login | Google OAuth - no admin approval, no Workspace Enterprise required |
| Past Meeting Access | Up to 1 month of historical meeting data surfaced immediately on sign-in |
| Permanent Archive | MongoDB-backed storage retains meeting data beyond platform retention limits - forever |
| Unified Search | Search across attendees, transcripts, and recordings from a single dashboard |
| Attendee Insights | Who attended, how long they stayed, engagement trends over time |
Technical Architecture
Stack: Node.js · Express.js · Next.js 16 · React 19 · MongoDB · AWS · Redis · Google OAuth
Key Design Decisions
OAuth Without Enterprise Dependency
The core insight: Google's Meet API does surface historical meeting data for non-Enterprise accounts via OAuth - the data exists, it's just not exposed in the UI. By implementing Google OAuth 2.0 and calling the Meet API directly, the platform unlocks that data for any signed-in user without any special plan.
MongoDB for Permanent Archival
Meeting data - attendees, transcripts, metadata - is stored in MongoDB immediately after sync. Once archived, it's independent of Google's retention policies. Even if Google deletes the source data, the archive persists.
Redis for Session & Cache Layer
Redis handles session management and caches frequently accessed meeting metadata, keeping dashboard load times fast as archived data grows.
Dual Platform Support
The integration layer abstracts over both Google Meet APIs, normalizing its different response shapes into a unified meeting data model - enabling the single-dashboard experience across both ecosystems.
Development Process
Built in a focused weekend sprint - the kind of velocity possible only when the problem is well-understood before the first line of code:
- OAuth & API integration - Implemented Google OAuth flow and Meet API calls; validated historical data was accessible for non-Enterprise accounts
- Permanent archive - Built MongoDB storage with meeting metadata indexing for fast search
- Dashboard - Built the Next.js frontend with search, transcript viewer, and attendee breakdown
- Redis layer - Added caching for session management and dashboard performance at scale
Impact & Takeaway
Meeting Analyzer closes a real access gap - not a missing feature, but data that exists and is arbitrarily withheld by a paywall - using a clean OAuth integration and a permanent archive.
The weekend origin is itself a signal: clear problem definition, known toolset, focused execution. That's the most reliable path from idea to working software.
Google locks meeting data behind Enterprise plans. A weekend OAuth integration unlocks it for everyone.
Tags: SaaS · Meeting Management · Google Meet archive · meeting transcript analysis · Node.js · Next.js · MongoDB · Redis · Google OAuth · AWS · CodeScapes