Getting Started
Introduction
The V03 platform model, trust boundaries, and operator map.
AI Workflow Center V03 is a self-hosted directory platform with an agent execution layer. A buyer receives and runs an isolated deployment. One deployment may contain several branded Sites, but it never mixes different buyers in a shared SaaS database.
The platform has four surfaces:
- The public site renders only reviewed, published, available facts.
- The operations console manages Site-scoped Links, Dimensions, content, datasources, tasks, reviews, credentials, orders, and recipes.
- The worker and scheduler execute nine versioned tasks through a durable Postgres queue.
- Public agents receive six read-only WebMCP tools; authenticated REST endpoints remain the only external write surface.
Data model
Link is the stable fact record for a URL. Optional Tool and Resource extensions carry type-specific fields. Dimension holds categories, occupations, tasks, workflows, audiences, and topics. Relations are Site-scoped and enforced by composite foreign keys plus forced row-level security.
Generated output never publishes directly. Model-driven tasks create reviewable candidates, record provenance and cost, then suspend for an eligible reviewer. Publication follows the forward-only DRAFT → REVIEW → PUBLISHED → ARCHIVED lifecycle.
Bundled assets
The normalized import includes 490 tool records, O*NET 30.3 with 1,016 occupations, 200 completed occupation resource packs, and 20,000 associations. Imported facts remain in review or noindex states until reachability, rights, evidence, and human-review gates pass.
Runtime requirements
- Node.js 24.15 or newer.
- pnpm 11.9.
- Postgres 17-compatible storage.
- A browser worker for screenshots and dynamic-page collection.
- Cloudflare R2 for production media and release delivery.
- Polar for source-template checkout and fulfillment.
The supported production path uses a Linux VPS with PostgreSQL 17, five PM2 roles, and host Caddy. Migration and seed/import are one-shot release jobs; web, MCP, worker, scheduler, and browser-worker processes remain isolated and independently health-checked. Docker Compose and Serverless adapters are not part of the V03 release promise.
Start with Getting started, then read Deployment and Environment variables.