Foundry

The open-source Agentic Delivery Platform for agencies and software delivery teams.

Foundry · open source · Apache-2.0

Ship software at the speed of thought.

The open-source Agentic Delivery Platform. Turn plans, conversations, and requirements into shipping software.

Get started in 15 minutes View on GitHub

git clone https://github.com/qdhenry/Foundry.git
cd Foundry
bun install
cp .env.local.example .env.local   # fill in Clerk + Convex + Anthropic keys
bun run dev:convex                  # terminal 1
bun run dev                         # terminal 2

Find what you need

Getting Started

Prerequisites, quickstart, and your first Foundry program running against AcmeCorp seed data.

Architecture & Concepts

Programs, workstreams, requirements, skills, sandboxes — and how the four-process distributed system fits together.

Deployment & Operations

Production setup on Vercel + Convex Cloud + Cloudflare, cost estimates, and rollback procedures.

Features Walkthroughs

Step-by-step tours of every user-facing surface: tasks, discovery, pipeline lab, skills, risks, gates, billing.

Sandbox Execution

Provision ephemeral Claude Code environments, watch real-time logs, and autocommit your way to a PR.

Reference

Auto-generated schema and function reference, plus hand-written CLI and environment variable deep dives.

Why Foundry

Foundry is built for teams that plan in meetings and conversations, then ship software from those plans. It structures delivery knowledge — requirements, skills, workstreams, risks — so AI agents can reason about full project context, not isolated tickets.

Delivery knowledge is the moat. Programs, workstreams, requirements, and skills form a graph the AI agents navigate, so they generate code that respects the whole system.
Engagement-type agnostic. Platform migrations, greenfield builds, system integrations, ongoing product dev — the data model applies to all of them.
Sandbox execution. Ephemeral Claude Code environments on Cloudflare containers, with real-time logs, interactive chat, and autocommit straight to a PR.
Built to be self-hosted. Bring your own Clerk, Convex, Cloudflare, and Anthropic keys. Apache-2.0. No phone-home.

Who these docs are for

Primary audience: self-hosters and operators standing up Foundry on their own accounts. Everything is written with the assumption that you will run this system in production.

Secondary audiences: contributors shaping the codebase and integrators wiring Foundry into existing delivery workflows. Inline <Aside> callouts flag anything specific to those paths — there are no separate sections for them in v1.