Skip to main content
Get Template — $89

Search AI Workflow Center

Search tools, categories, stacks, and pages

The template

Everything you're looking at, running for you by tomorrow

This site is not a demo of the template — it is the template. The 293-tool directory, occupation-task-workflow graph, operations console, durable task runtime, and public agent interfaces share one policy-enforced codebase. Deploy it, configure Sites and Recipes, and retain control of data, credentials, review, and release delivery.

Read the docs first

One-time purchase · instant source download · optional private GitHub repo for updates · deploy on any VPS you own

293tools verified on a rolling schedule
9versioned tasks with durable execution
63workflow guides written against real data
Forcedrow-level security on every Site-owned table

Automation

A site that runs itself

Repetitive work is automated, but publication authority stays explicit. Six parts of the nine-task system:

Evidence-bound discovery

Approved ranking sources create provenance-bound candidates. Nothing becomes public merely because a source or model mentioned it.

Isolated crawl and change detection

A separate browser worker validates every destination and redirect, records content-addressed snapshots, and turns structured differences into reviewable change evidence.

Bounded model generation

Structured retries, versioned prompts and schemas, deterministic quality scores, usage accounting, and human review keep model output from publishing itself.

Deterministic release audit

The audit task evaluates Site, Link, Dimension, TaskRun, and release invariants and emits blocking findings rather than silently repairing ambiguous data.

Occupation, task, and workflow graph

O*NET-backed occupations connect to contextual task and workflow Dimensions without duplicating shared nodes or losing Site-scoped provenance.

Durable operations

Postgres outbox and inbox records, leases, checkpoints, bounded retries, dead letters, and kill switches keep long-running work outside web requests.

What's inside

Three products in one deploy

The public site

  • Verified Link and tool directory with categories and rankings
  • Head-to-head comparisons and alternatives pages
  • Occupation, task, and workflow pages
  • Daily matchups with privacy-preserving vote retention
  • Pricing facts and change history folded into each tool page
  • Recipe Gallery, PWA, JSON-LD, sitemaps, AGENTS.md, and llms.txt

The operations console

  • Site-scoped Links, Dimensions, content, datasources, tasks, and orders
  • DNS-verified multi-Site identity and versioned Recipes
  • Credential references without browser or database secret values
  • Human output review, cost records, dead letters, and release evidence
  • Five Site roles with a transactional append-only action ledger

The agent layer

  • Scoped API keys: read / content / publish / admin
  • Complete OpenAPI 3.1 reference, live at /api/docs
  • Six-tool, published-only WebMCP surface with no write capability
  • Install and rebrand Skills in the repo: your coding agent does the setup

Agent-native delivery

Your coding agent does the installing

No forty-step tutorial with screenshots that were outdated last month. The template ships with agent Skills: open the repo in Claude Code or Cursor, and your agent deploys the stack, seeds the content, wires your domain, and rebrands the whole site to your identity — while the text-first docs give humans the same path in plain language.

  • Setup Skill — from clean server to running site
  • Rebrand Skill — your name, brand, and content everywhere
  • Read-only WebMCP — safe public agent discovery
Launch price
$89one-time
  • Full template source + seed content
  • Polar entitlement and signed release delivery
  • Setup & rebrand agent Skills
  • Docs, migration tests, SBOM and AIBOM
  • Deploy unlimited sites you own

Instant source download the moment you pay. Code you deploy is yours forever.

Frequently asked questions

What exactly do I get?

The signed V03 source release behind AI Workflow Center: public site, operations console, nine task definitions, worker topology, migrations, normalized assets, read-only WebMCP, scoped REST, Polar fulfillment, tests, Docker deployment, SBOM, and AIBOM.

How is it delivered?

Instantly. The moment payment clears, the full source code downloads straight from your Polar receipt page — the complete, buildable repo with docs and agent Skills inside. Want updates the git way? Send us your GitHub username and we add you to the private repo, so future releases are one git pull away. Every new release also drops into your Polar library automatically.

Is this a subscription?

No. One payment, and the code you ship is yours forever. Template updates are delivered through the repository — pull them in with plain git whenever you like.

Do I need to be a developer?

It helps, but the template is built agent-first: the included Skills let a coding agent handle deployment and rebranding, and day-to-day operations happen in the admin console, not in code. If you can run a guided setup and use a dashboard, you can run the site.

How do I make money with it?

V03 does not sell editorial priority or ranking. You can add affiliate attribution, sponsorship inventory, subscriptions, or your own products while keeping acceptance, ratings, votes, and directory placement independent from payment.

What does it cost to run?

Run cost depends on traffic, retained data, browser workload, model usage, R2, email or Push volume, and backup policy. The supported production topology is a Linux VPS with PostgreSQL 17, five PM2 roles, and host Caddy; measure your own workload before choosing host size.

Can I resell the code or launch it for clients?

You can deploy unlimited sites you own. Reselling or redistributing the source — including as another template or an open-source repo — is not allowed, and a client project needs the client's own license. The full terms ship with the code.

Does it have to be an AI tools directory?

No. A Site Recipe defines branding, Dimension types, page templates, datasource rights, package hashes, and compatibility. Vertical fields live in versioned Link attributes instead of hardcoded Tool columns.

Want to see what buyers build with it? Visit the showcase — or compare plans on pricing.