InkHive Docs

Architecture

How the app components and services interact.

Architecture

InkHive uses a client-first UI with serverless orchestration and realtime data updates.

Primary services

  • UI: Next.js app router pages and dashboard.
  • Realtime data: Convex collections and functions.
  • Orchestration: Inngest workflows for generation and publishing.
  • AI: Google Generative AI for text generation.

Event flow

  1. The client creates a project via Convex mutation.
  2. A Next.js API route triggers Inngest with project input.
  3. Inngest runs generation steps and writes outputs to Convex.
  4. The UI subscribes to Convex updates for live status.
  5. Publishing triggers a separate Inngest flow with per-platform updates.

On this page