EEveon Minutes Documentation

Subscription-based meeting intelligence product with API-first ingestion, summarization workflows, and plan-managed access.

Meeting Ingestion
Subscription Billing
Provider Webhooks

Stack

  • Backend: FastAPI
  • Database: Postgres + Alembic
  • Billing: RevenueCat
  • Web app: JS client with RevenueCat SDK
  • Deployment: Cloudflare Pages (`eeveon-frontend`) + Worker gateway

Plans

Minutes uses entitlement-based subscription access with configured package IDs.

Plan Plan ID Billing Model
Monthly monthly Recurring monthly subscription
Yearly yearly Recurring annual subscription
Lifetime lifetime One-time purchase entitlement

Entitlement name: EEveon Pro. Offering key: default.

Auth + Organization

  • POST /auth/register
  • POST /auth/login
  • POST /orgs
  • GET /orgs/me
  • POST /orgs/{org_id}/api-keys

Meetings

  • POST /webhooks/{provider}/meeting-ended
  • GET /jobs/{job_id}
  • GET /meetings
  • GET /meetings/{meeting_id}
  • GET /standups
  • GET /standups/schedules
  • POST /standups/schedules

Billing

  • POST /billing/revenuecat/link
  • GET /billing/me
  • POST /billing/webhook/revenuecat

Meeting ingestion and notes endpoints are gated by active/trial billing state.

Webhooks

# RevenueCat webhook auth (optional)
Authorization: Bearer <token>
# or
X-RevenueCat-Webhook-Auth: <token>

Deployment

# Worker gateway (minutes backend repo)
cd /Users/adarsh/Desktop/Files/eeveon/eeveon-minutes/infra/worker
npx wrangler deploy

# Minutes frontend (inside eeveon-frontend)
cd /Users/adarsh/Desktop/Files/eeveon/eeveon-frontend
npm install
npm run build
npx wrangler pages deploy dist --project-name frontend

The Minutes app is published under /minutes-app in the main EEveon frontend project.

Implementation Notes

  • Use SSL-ready pooled Postgres URL in DB_URL.
  • Set BACKEND_ORIGIN secret on worker for API forwarding.
  • Maintain plan IDs in RevenueCat and keep entitlement mapping stable.