StackPrism
AI apps

Tech stack for an AI meeting notes app (2026)

AI meeting notes, designed by StackPrism from one sentence: 13 components, a reason for each, and the live checks that watch them.

The stack

  • Next.js
  • Node.js
  • Clerk
  • Inngest
  • Supabase
  • Slack
  • Zoom
  • Notion
  • OpenAI
  • Sentry
AIBackground jobsIntegrationsUpdated
The idea someone typed
“An AI meeting notes app that joins Zoom and Google Meet calls, records and transcribes them, writes a summary with action items, and sends the notes to Slack and Notion.”

Make it yours. Open this stack in the editor to check its health, harden it and hand it to your coding agent. No sign-up, nothing to generate.

Start from this stack
goes down

Select a component to see what it does and what it connects to, or pick one above to see what breaks if it goes down. Pinch or use the buttons to zoom.

Why this stack

A meeting ingestion service joins Zoom and Google Meet calls, records them and uploads the audio to Supabase Storage. An Inngest worker takes it from there in the background: it uses OpenAI to turn the recording into a summary with action items, saves the results in Supabase PostgreSQL and sends the notes to Slack and Notion. People sign in with Clerk and review past meetings in a Next.js app backed by a Node.js API. Sentry reports failed joins and jobs.

Why each piece

All 13 components on the diagram: what each one does, what it talks to, and what stops if it goes down.

  1. Next.js Web App

    User dashboard. Calls Node.js API, Clerk (auth) and Sentry (errors).

    Nothing else on the diagram depends on it.

  2. Node.js API

    Core API. Calls Supabase PostgreSQL (reads), Supabase Storage (uploads), Meeting Ingestion Service (triggers) and Sentry (errors). Called by Next.js Web App.

    If it goes down, 1 of 12 components stops working.

  3. Clerk

    User auth. Called by Next.js Web App (auth).

    If it goes down, 1 of 12 components stops working.

  4. Meeting Ingestion Service

    In Backend Services

    Join and record. Calls Supabase Storage (uploads), Zoom (joins) and Google Meet (joins). Called by Node.js API (triggers).

    If it goes down, 2 of 12 components stop working.

  5. Inngest Worker

    In Backend Services

    Async job processor. Calls Supabase PostgreSQL (stores), Sentry (errors), OpenAI (summarizes), Slack (posts) and Notion (updates).

    Nothing else on the diagram depends on it.

  6. Supabase Storage

    In Data & Storage

    Audio and artifacts. Called by Node.js API (uploads) and Meeting Ingestion Service (uploads).

    If it goes down, 2 of 12 components degrade.

  7. Supabase PostgreSQL

    In Data & Storage

    App database. Called by Node.js API (reads) and Inngest Worker (stores).

    If it goes down, 3 of 12 components stop working.

  8. Slack

    In External Services

    Notes delivery. Called by Inngest Worker (posts).

    If it goes down, 1 of 12 components degrades.

  9. Zoom

    In External Services

    Meeting platform. Called by Meeting Ingestion Service (joins).

    If it goes down, 1 of 12 components degrades.

  10. Google Meet

    In External Services

    Meeting platform. Called by Meeting Ingestion Service (joins).

    If it goes down, 1 of 12 components degrades.

  11. Notion

    In External Services

    Notes pages. Called by Inngest Worker (updates).

    If it goes down, 1 of 12 components degrades.

  12. OpenAI

    In External Services

    AI summarization. Called by Inngest Worker (summarizes).

    If it goes down, 1 of 12 components degrades.

  13. Sentry

    Error tracking. Called by Inngest Worker (errors), Next.js Web App (errors) and Node.js API (errors).

    If it goes down, 3 of 12 components degrade.

When this stack fits

  • The work happens after the meeting, so transcribing and summarising can run in the background.
  • Notes need to land where people already work, such as Slack and Notion.

When to pick something else

  • You need live captions during the call: this stack processes recordings after the meeting ends.
  • Calls fall under strict consent or industry rules: recording people and sending audio to OpenAI needs consent flows and agreements this diagram doesn’t show.

What you need to build this

13 components across 7 areas of the stack.

Build it with your AI agent

Hand the stack to Claude Code, Codex, Cursor or any coding agent as a brief: how it connects, install steps and a build plan.

Frontend1

  • Next.js Web App

    User dashboard

    npm install next

    Docs

Backend & APIs7

  • Meeting Ingestion Service

    Join and record

  • Inngest Worker

    Async job processor

  • Zoom

    Meeting platform

  • Google Meet

    Meeting platform

  • Slack

    Notes delivery

  • Notion

    Notes pages

  • Node.js API

    Core API

    Docs

Data1

  • Supabase PostgreSQL

    App database

    npm install @supabase/supabase-js

    Docs

Auth1

  • Clerk

    User auth

    npm install @clerk/nextjs

    Docs

AI1

  • OpenAI

    AI summarization

    npm install openai

    Docs

Storage & CDN1

  • Supabase Storage

    Audio and artifacts

    npm install @supabase/supabase-js

    Docs

Observability1

  • Sentry

    Error tracking

    npm install @sentry/nextjs

    Docs

Install

npm install next @supabase/supabase-js @clerk/nextjs openai @sentry/nextjs

SDKs only. Pick your own database driver or ORM.

See all 30 example stacks