Verto AI

RoleFounder Engineer — Full-Stack & AI Systems
CategoryAI SaaS · Productivity
TimelineApr 2025 – Apr 2026 (12 Months)
Status
Production Deployed (Active R&D)

PROJECT
OVERVIEW

Verto AI is a full-stack creative workspace built on Next.js 16 that combines three distinct subsystems: an 8-agent LangGraph pipeline for presentation generation, an Inngest-powered mobile design generator, and a hosted MCP server that exposes presentation workflows to external AI clients. The architecture deliberately separates these subsystems while sharing a common AI runtime router and Prisma data layer.

Verto AI is an interconnected platform using LangGraph, Inngest, and MCP to programmatically generate layout-aware presentations — serving both human users through a visual editor and AI agents through a protocol-standard MCP endpoint.

Layout-first generation guarantees agents are structurally aware of target formats before writing a single word — content fits the visual container, not the reverse.
ADR-005: Layout-First Generation
Key Details
01

Why 8 Agents, Not 1 Prompt

Decomposing generation into 8 specialized agents (initializer → outline → layout → writer → image query → image fetch → JSON compile → persist) means each agent has focused instructions, independent LLM settings, and isolated failure domains.

02

Why Layout-First Generation

Layout selection happens before content writing (ADR-005). This ensures the content writer produces copy that fits the target visual structure — preventing the common AI problem where generated text overflows or underflows its container.

03

Why Hosted MCP Server

Verto serves both humans in the browser AND AI agents via protocol. The hosted MCP endpoint exposes 11 tools and 4 resources over Streamable HTTP, letting Claude Desktop and Cursor create and edit presentations programmatically.

04

Why BYOK Runtime

Users store their own provider keys (Google, OpenAI, Groq), choose preferred models, and the AI runtime router resolves the correct provider based on business rules. Free-tier users get hosted defaults; premium users bring their own keys.

SYSTEM
ARCHITECTURE

Engineered for production durability, type safety, and scalable domain isolation. Every module operates with strict boundaries and predictable failure handling.

MODULAR DOMAIN ISOLATION — BUILT FOR ZERO-DOWNTIME DEPLOYMENTS, TYPE-SAFE CONTRACTS, AND FAIL-SAFE EXCEPTION BOUNDARIES.

SYSTEM BLUEPRINTOpen Vector View
Verto AI Architecture Diagram
Architectural Modules
01

3 Distinct Subsystems

Presentation pipeline (LangGraph), mobile design generator (Inngest), and MCP server — each with different execution strategies but sharing the AI runtime router and Prisma data layer.

02

8-Agent LangGraph Pipeline

State machine with 8 sequential agents: projectInitializer → outlineGenerator → layoutSelector → contentWriter → imageQueryGenerator → imageFetcher (conditional loop) → jsonCompiler → databasePersister.

03

Recursive Content Tree

Slides are stored as recursive JSON trees (ADR-006). The same tree renders identically across 4 modes: editor, preview, shared public view, and PDF export. Zustand manages the editor state with undo/redo.

04

BYOK Runtime Router

Every generation request passes through a business rule check: free-tier → hosted default; BYOK-eligible → resolve user's preferred provider (Google, OpenAI, Groq) and model; fallback → safe default runtime.

05

Event-Driven Mobile Design

Mobile design generation runs as Inngest background jobs because it produces raw HTML frames and can take longer than normal request lifecycles. Per-frame regeneration is also handled via Inngest.

PROJECT
IMPACT

Production performance measured under live traffic load, latency stress profiles, and automated system profiling.

ALL OUTCOMES ARE EMPIRICALLY VERIFIED IN PRODUCTION ENVIRONMENTS — MEASURED UNDER HIGH CONCURRENCY, PEAK LATENCY PROFILES, AND AUTOMATED SYSTEM HEALTH AUDITS.

01
11

MCP Tools

02
8

LangGraph Agents

03
8

Architecture Decision Records

04
3

AI Providers (BYOK)

KEY
CAPABILITIES

Core capabilities engineered for high-scale reliability, intuitive operator workflows, and real-time production execution.

PRODUCTION-TESTED SYSTEM FEATURES — ARCHITECTED FOR LOW-LATENCY INTERACTION, DETERMINISTIC STATE HANDLING, AND COMPREHENSIVE TELEMETRY.

MODULE / 01
LangGraphState MachineZod Validation

8-Agent LangGraph State Machine

A sequential pipeline of 8 specialized agents: projectInitializer creates the DB record, outlineGenerator produces slide outlines, layoutSelector assigns layout types per slide, contentWriter generates structure-aware copy, imageQueryGenerator creates search terms, imageFetcher loops until all slides have images, jsonCompiler assembles the final Slide[] JSON, and databasePersister saves everything. Recursion limit: 150.

8Specialized Agents
SequentialPipeline
MODULE / 02
ADR-005Layout IntelligenceStructure-Aware

Layout-First Content Generation (ADR-005)

Layout selection happens as step 3, before content writing at step 4. The content writer receives the chosen layout type and generates copy that fits the target visual structure. This prevents the common AI problem where generated text overflows or underflows slide containers.

LayoutBefore Content
StructureAware Output
MODULE / 03
MCPStreamable HTTPBearer Authstdio

Hosted MCP Server (11 Tools, 4 Resources)

Exposes presentation lifecycle operations to external AI clients over Streamable HTTP (protocol version 2025-03-26). Supports both remote Bearer-token auth for hosted use and local stdio transport for development. Session-based — clients must initialize before sending tool calls.

11Tools
4Resources
MODULE / 04
Multi-ProviderBusiness RulesKey Validation

BYOK Multi-Provider Runtime

Users store API keys for Google, OpenAI, and Groq with validation metadata. Every generation request passes through a business-rule router: free tier → hosted default, BYOK eligible → resolve preferred provider and model, fallback → safe default. The same resolver is used by web generation, streamable API, MCP tools, and mobile design jobs.

3AI Providers
UnifiedRuntime Router
MODULE / 05
Recursive JSON TreeZustandhtml2canvas + jsPDF

Recursive Slide Editor (ADR-006)

Slides are stored as recursive JSON content trees. The same tree structure renders identically across the editor, preview, public share view, and PDF export. Zustand manages the editor state with theme switching, content editing, and the recursive rendering engine.

4Render Modes
RecursiveContent Tree

DEVELOPMENT
PROCESS

A rigorous, phased engineering lifecycle designed to transform architectural requirements into scalable, production-ready systems.

DISCIPLINED SYSTEM METHODOLOGY — ARCHITECTED FOR END-TO-END OBSERVABILITY, DETERMINISTIC REVIEWS, AND ZERO-REGRESSION RELEASE CYCLES.

Connected Lifecycle Grid
PHASE / 013 Subsystems

Architecture

Designed three distinct subsystems (LangGraph pipeline, Inngest mobile generator, MCP server) sharing a common AI runtime router and Prisma data layer. Each subsystem has different execution strategies suited to its workload.

System DesignSubsystem Decomposition
PHASE / 028-Agent Design

LangGraph Pipeline

Implemented the 8-stage state machine with independent LLM settings per agent, Zod validation on all outputs, and a conditional loop in the image fetcher. Layout selection before content writing was a deliberate decision (ADR-005).

AI PipelineADR-005
PHASE / 03Recursive Tree

Editor & Rendering

Built the recursive React rendering engine that traverses the JSON content tree. Same renderer used across editor, preview, share, and export modes. Zustand stores manage theme, content state, and undo history.

ReactADR-006Zustand
PHASE / 04Protocol + SaaS

MCP & Billing

Exposed the generation engine to Claude Desktop and Cursor via hosted MCP. Integrated Lemon Squeezy billing with usage gating and BYOK activation rules for premium users.

MCPSaaSBilling
ARCHITECTURE STACK // COMPONENT MATRIX

TECHNOLOGY
STACK

An engineered architectural map outlining foundational nodes, runtime environments, and type-safe deployment frameworks.

DETERMINISTIC ARCHITECTURE STACK — PROFILED FOR PRODUCTION LATENCY, STRICT TYPE SAFETY, AND HIGH-CONCURRENCY SCALABILITY.

Total Nodes
25+
Architectural Components
Type Safety
Strict%
System Expansion Slot
Layer 1

frontend

Next.js 16
React 19
Tailwind CSS 4
Zustand 5
Radix UI + shadcn/ui
Layer 2

backend

Prisma 6
Clerk
Inngest
Lemon Squeezy
MCP Server
Layer 3

ai

LangGraph
Gemini 2.5 Flash
Vercel AI SDK
@ai-sdk/google
@ai-sdk/openai & @ai-sdk/groq