CorpConnect

AI-Powered B2B Collaboration & Networking Graph Platform

CorpConnect is a next-generation multi-tenant platform designed to help organizations discover, connect, and collaborate through structured relationship graphs, pre-event matchmaking, real-time messaging, and AI-assisted operational workflows.

---

🚀 The Vision: Beyond Simple Events

Unlike transactional event portals that focus strictly on ticket sales and static guest lists, CorpConnect treats events as catalysts for strategic connections.

The platform is architected around an Organization-First Networking Graph:

• Relationship-driven: Businesses build persistent organization profiles detailing services, technologies, hiring statuses, and partnership interests.
• Intelligent Matchmaking: Vector search similarity analyses identify complementary organizations and propose connections.
• Pre-Event Coordination: Attendees can request private 1-on-1 business meetings prior to events starting.
• Interactive Live Collaboration: Virtual panels feature real-time WebRTC streams with interactive hand-raising queues, chats, and sentiment polling.
• B2B Discovery: A rich organization directory allowing businesses to browse and filter by industry, size, location, and tags.

---

🏗️ System Topology & Hybrid Architecture

CorpConnect runs a hybrid, multi-tenant monorepo architecture, distributing concerns across specialized runtimes:

graph TD
    Client["Client / Web App (Next.js Frontend)"]
    
    subgraph CorpConnectCore ["CorpConnect Next.js Application Core"]
        NextServer["Next.js App Router (SSR/ISR/Server Actions)"]
        DomainLayer["Domain Layer (/domain)<br/>(Queries, Actions, Validation)"]
        NextAuth["Next-Auth Session Layer"]
    end
    
    subgraph Microservices ["Microservices Layer"]
        WSService["ws-service (Node/Socket.io)<br/>[Real-time Direct & Group Chat]"]
        LVService["lv-service (Node/Express/LiveKit)<br/>[Virtual Rooms management]"]
        AIService["ai-service (Python/FastAPI)<br/>[Recommendations, Brainstorming, pgvector]"]
    end
    
    subgraph DataStorage ["Data & Cache Layer"]
        DB[(PostgreSQL Database<br/>+ pgvector)]
        Redis[(Redis Cache & Adapters)]
    end
    
    subgraph External ["External Integrations"]
        Stripe["Stripe / Razorpay SDKs<br/>(Payments & Webhooks)"]
        Cloudinary["Cloudinary<br/>(Image/Logo Uploads)"]
        LiveKitCloud["LiveKit Server<br/>(Real-time WebRTC Live Streaming)"]
        ResendSMTP["Resend / SMTP<br/>(System Mailer)"]
    end

    Client -->|HTTPS / Next.js Pages| NextServer
    Client -->|WebSocket Connection| WSService
    Client -->|WebRTC Audio/Video| LiveKitCloud
    
    NextServer --> DomainLayer
    DomainLayer --> DB
    WSService --> DB
    AIService --> DB
    LVService --> DB
    
    WSService <-->|Pub/Sub Adapter| Redis
    NextServer -->|Embedding & Brainstorm Jobs| AIService
    NextServer -->|Payment Processing| Stripe
    NextServer -->|Logo Assets| Cloudinary
    LVService -->|Mint Tokens & Admin Rooms| LiveKitCloud

Loading

Services Breakdown

1. Next.js Core Web App: Main web portal handling server-side rendering (SSR), incremental static regeneration (ISR) for public directories, form validation (Zod), and secure mutations (Server Actions) decoupled into a Domain-Driven /domain structure.
2. WebSocket Service (ws-service): A stateful Node.js + Socket.io service handling real-time direct messaging, group chat, typing indicators, read receipts, and in-event interactivity (emojis, raise-hand queues). Scales horizontally using a Redis pub/sub adapter.
3. LiveKit Proxy Service (lv-service): Node.js Express service wrapping the LiveKit Server SDK. Generates JWT video room tokens, enforces event attendance permissions, and tracks active meeting durations.
4. AI Microservice (ai-service): Python/FastAPI service embedding data utilizing all-MiniLM-L6-v2 and performing vector calculations (pgvector) to recommend events, suggest matching partners, search semantically, generate event brainstorming briefs, and perform feedback sentiment analyses.

---

💎 Features & Subscription Tier Matrix

CorpConnect enforces multi-layered tier gates across database queries, APIs, and real-time sockets:

Platform Feature	Free	Pro	Enterprise
Workspace Profile & Switcher	✅	✅	✅
B2B Filtered Discovery	✅	✅	✅
Standard Event Registration	✅ (max 50 attendees)	✅ (Unlimited)	✅ (Unlimited)
Paid Event Gateways (Stripe/Razorpay)	❌	✅	✅
Direct Messaging (DMs)	❌	✅	✅
Pre-Event 1-on-1 Matchmaking	❌	✅	✅
Organization Connections	❌	✅	✅
AI Partner & Event Recommendations	❌	✅	✅
External API Key Credentials	❌	✅	✅
Real-time WebRTC Virtual Rooms	❌	✅	✅
WhatsApp-style Group Chats	❌	❌	✅ (Invitation-only)
AI Brainstorming & Event Pitching	❌	❌	✅ (Chat + Brief Flow)
Post-Event Sentiment & Reports	❌	❌	✅ (Aggregated & AI Summary)
Semantic Search (pgvector)	❌	❌	✅
Organization Webhook Delivery	❌	❌	✅ (With HMAC Signature)

---

🔒 Governance & Constraints

To keep organizational workspaces compliant, the platform enforces strict business rules at the domain layer:

• Role Governance: Organizations are restricted to exactly 1 Owner and a maximum of 5 Admins to maintain operational security.
• Ownership Transfer: Promotions to OWNER must run through the transactional transferOrganizationOwnershipAction to demote the current owner to ADMIN and promote the target atomically.
• Abuse Prevention: Free tier organizations are blocked from publishing paid event checkouts, and a 2% (Pro) or 1% (Enterprise) platform commission fee is applied at payment checkouts.

---

📁 Monorepo Directory Structure

/
├── actions/             # Legacy and shared server actions
├── ai-service/          # Python FastAPI microservice (embeddings, recommendation engine, chat briefs)
├── app/                 # Next.js App Router (pages, middleware, and API routes)
├── components/          # React components structured by domain (shared, billing, messaging, virtual)
├── constants/           # Platform constants, menu links, metadata
├── data/                # Data Access Layer (DAL) - database reads with permission isolation
├── docs/                # Feature specs, implementation plans, and architecture walkthroughs
├── domain/              # DDD / Vertical Slice Layer (Actions, Queries, Validation, Types)
│   ├── events/          # Event lifecycle queries & actions
│   ├── messaging/       # Direct & Group messaging operations
│   ├── notifications/   # Laravel-style notification dispatcher with multi-adapter system
│   ├── organizations/   # Org profile, onboarding, and connection workflows
│   ├── pitches/         # Event pitching lifecycle schemas & actions
│   └── tags/            # Unified tag system queries & actions
├── hooks/               # Client-side hooks (Socket.io subscriptions, intersection observers)
├── lib/                 # Infrastructure clients (Prisma, payment gateways, mailer, job queues)
├── lv-service/          # LiveKit WebRTC rooms management gateway microservice
└── ws-service/          # Socket.io real-time chat service

---

🛠️ Local Development Setup

1. Prerequisites

• Node.js 20+ (with pnpm)
• Python 3.11+ (with venv)
• PostgreSQL (with the pgvector extension installed/enabled)
• Redis (for WebSocket scaling and AI cache)

2. Database Initialization

From the project root:

# 1. Install the pgvector extension. Must run before the schema sync, because the
#    embedding columns are declared as Unsupported("vector(384)").
npx tsx scripts/enable-pgvector.ts --extension-only

# 2. Apply the Prisma schema and generate the client
npx prisma db push

# 3. Create the embedding columns and IVFFlat indexes.
#    Additive — existing embeddings are preserved on re-runs.
npx tsx scripts/enable-pgvector.ts

# 4. Seed the reference tables (industries, event categories).
#    Onboarding and event creation both require these; idempotent.
pnpm db:seed

The Docker entrypoint (entrypoint.sh) runs all four steps automatically on container start, in every environment.

2a. Create the First Platform Admin

User.isAppAdmin defaults to false and nothing in the UI can set it, so a fresh deployment has no way to reach /admin — and therefore no way to approve the KYB submissions that gate organization verification. Bootstrap it once:

# Register through the normal sign-up flow first, then promote that account:
pnpm grant-admin you@company.com

# Inside Docker:
docker compose exec server npx tsx scripts/grant-admin.ts you@company.com

# To revoke:
pnpm grant-admin you@company.com --revoke

Sign out and back in afterwards so the session picks up the new claim.

3. Next.js Web Application

# Install dependencies
pnpm install

# Run the dev server
pnpm dev

4. WebSocket Service (ws-service)

cd ws-service
pnpm install
# Compile typescript and start
pnpm dev

5. LiveKit Gateway (lv-service)

cd lv-service
pnpm install
pnpm dev

6. AI Microservice (ai-service)

cd ai-service
python -m venv .venv
source .venv/bin/activate  # Or .venv\Scripts\activate on Windows
pip install -r requirements.txt

# Run the Uvicorn FastAPI server
uvicorn main:app --reload --port 8000

Note: The first startup of the AI service downloads the all-MiniLM-L6-v2 model (~90MB) and stores it locally.

---

📧 Notification System

CorpConnect implements a Factory + Adapter notification pattern. Job handlers enqueue events (like SEND_EVENT_REMINDER or VIRTUAL_ROOM_OPENED) which resolve active notification adapters concurrently:

• Email Adapter: Relies on Nodemailer/SMTP and logs results in the EmailLog table for auditing and tracking.
• In-App Adapter: Writes directly to the Notification table.
• Slack / Google Chat / SMS Adapters: Hook into outgoing chat webhook formats.

Add channels by creating an adapter under domain/notifications/adapters/ and listing it in registry.ts.

---

⚙️ Environment Variables

Copy the .env.example templates in the root, ws-service, lv-service, and ai-service folders. Key environment variables include:

• Next.js Core:
  • DATABASE_URL: PostgreSQL connection string.
  • AUTH_SECRET: NextAuth session encryption secret.
  • BASE_URL: Public app URL (e.g. http://localhost:3000).
  • NEXT_PUBLIC_WS_URL: WebSocket URL (e.g. http://localhost:4000).
  • AI_SERVICE_URL & AI_SERVICE_MASTER_KEY: AI service endpoint and authorization token.
  • STRIPE_SECRET_KEY & STRIPE_PUBLISHABLE_KEY: Payment integration with Stripe.
  • RAZORPAY_KEY_ID & RAZORPAY_KEY_SECRET: Payment integration with Razorpay.
  • NEXT_PUBLIC_LIVEKIT_URL: Real-time video/audio room provider.
  • SMTP_SERVER_HOST, SMTP_SERVER_USERNAME, SMTP_SERVER_PASSWORD: Outgoing email configuration.
• AI Service:
  • DATABASE_URL: Async-compatible PostgreSQL scheme (e.g. postgresql+asyncpg://...).
  • MASTER_KEY: API authentication key.
• ws-service:
  • DATABASE_URL: PostgreSQL connection string.
  • REDIS_URL: Redis backend URL.
  • AUTH_SECRET: SHA token matching the Next.js core session secret.
• lv-service:
  • DATABASE_URL: PostgreSQL connection string.
  • LIVEKIT_URL, LIVEKIT_API_KEY, LIVEKIT_API_SECRET: LiveKit server authorization.

---

🛡️ License

This project is proprietary and private software. All rights reserved. Unauthorized redistribution or duplication is strictly prohibited.