How codehagen/outpulse works
Project Type and Purpose
• Outpulse is a full-stack, monorepo web platform for creating and managing AI-powered outbound calling agents.
• It consists of two primary applications:
• apps/www – a Next.js (App Router) frontend with built-in API routes and server actions.
• apps/api – a standalone Hono-based REST API service (SDK backend).
File Structure Analysis
• Top-level apps/ folder splits frontend (www) and backend (api).
• apps/www contains:
• src/app – Next.js pages & API routes (e.g., /api/calls, /api/auth)
• src/actions – server actions invoked by client components
• components, hooks, lib – UI, utilities, auth/client integrations
• prisma/schema.prisma – database schema
• apps/api is a minimal Hono service exposing REST endpoints, likely used by third-party SDKs.
• Shared tooling and config managed via pnpm workspaces and tooling/tailwind.
Key Architectural Insights from README
• Monorepo deployed on Vercel (apps/www), with build commands, environment variables, and prisma migrations.
• Uses Neon (serverless Postgres), Prisma ORM, Better Auth for authentication, Twilio for telephony, OpenAI/ElevenLabs for AI, Stripe for billing, Resend for email.