Case studies — INTERNAL TOOL · AI PLATFORM

17 steps. Full site. Fully automated.

Internal multi-step agent platform that researches, designs, builds, and deploys full websites end-to-end.

This is the system that lets ZipLyne ship at the velocity we do. Not a generator, not a template engine, a full agentic pipeline that goes from brand brief to deployed site without a human touching code. Two pipelines: WB2 for builds, WA1 for ongoing content.

Start a project like this

Two pipelines. Build and maintain.

WB2 Pipeline Website Builder 2 to 17 Steps

Brand research → competitor analysis → sitemap generation → copy writing → design spec → component scaffolding → page implementation → SEO optimization → deployment. Each step is a structured Claude or Gemini call. Output from step N is the input to step N+1.

WA1 Pipeline Website Automator 1 to 18 Steps

The post-deploy content engine. Generates blog posts, updates landing page copy, refreshes meta descriptions, submits to search indexes. Runs on a schedule or on-trigger. 18 steps, all durable. The site stays fresh without anyone touching it.

Orchestration Trigger.dev v4, Durable by Default

Every pipeline step is a Trigger.dev v4 durable task. Step failures retry automatically without restarting the whole chain. Steps can be replayed individually during debugging. A 17-step build can be paused at step 9 and resumed, no data loss.

Model Routing Right Model, Right Step

Claude handles reasoning, copy, and implementation steps. Gemini handles structured data extraction and research tasks where it's faster and cheaper. A routing layer selects the model per step based on task type, with OpenRouter as fallback for rate limits.

From brief to deployed site.

STEP 01 Brand Research

Competitor crawl, positioning analysis, tone profile

STEP 02 Competitor Analysis

Feature matrix, gap identification, differentiation brief

STEP 03 Sitemap Generation

Pages, hierarchy, content types, structured output

STEP 04 Copy Writing

Hero, sections, CTAs, in brand voice

STEP 05 Design Spec

Color system, type scale, spacing, Claude generates tokens

STEP 06 Component Scaffold

File structure, component list, prop interfaces

STEP 07 Page Implementation

Full Astro/Next.js page code, not snippets, full files

STEP 08 SEO Optimization

Meta, OG tags, schema markup, sitemap.xml

STEP 09 QA Pass

Broken links, missing alt text, contrast ratio checks

STEP 10 Deployment

Vercel deployment API, live URL returned to the pipeline

STEPS 11–17 Analytics, Performance, Accessibility, Redirects, DNS, Monitoring, Handoff

Post-deployment hardening, GA/GTM injection, Lighthouse pass, and structured handoff brief for the client.

What it runs on.

Reasoning, copy, code Claude

Research, extraction Gemini

Fallback routing OpenRouter

Pipeline orchestration Trigger.dev v4

API layer Elysia / Bun

Platform UI Next.js

Deployment target Vercel API

On the bench.

Claude
Gemini
OpenRouter
Trigger.dev v4
Elysia / Bun
Next.js
Vercel API

Next file

1600 nits. No private APIs. →