The Foundry Manual
Project Registry
Track production URLs, GitHub repos, owners, rate limits, local setup notes, and fleet guidance — behind one API.
Open the registry →Symphony Tasks
Durable tasks with comments, blockers, PR status, deploy state, and agent handoff history. Promote feedback into work.
See the workflow →Feedback & Voting
Public or private boards. Upvotes, status, and notify-on-ship. Promote real signal into the task queue.
Wire it up →Changelog
Auto-drafted from completed tasks. Embeddable widget, in-app unread badge, version tags and categories.
Read the recipe →Waitlist
Drop-in waitlist for any new product. Forms, embeds, exports, and analytics out of the box.
Collect signups →fnd CLI & SDK
Every surface available via REST, fnd api, or the TypeScript SDK. Agents and humans use the same contract.
- Operator
- Sarthak Agrawal — sarthakagrawal927
- Runtime
- Cloudflare Workers · D1 · KV · R2
- Interfaces
- REST ·
fndCLI · TypeScript SDK · Embeddable widgets - Auth
- better-auth (Google OAuth) · opaque session tokens · CLI prefix
sm_ - Primitives
- registry · feedback · changelog · tasks · audits · waitlist · widgets
- Origin
- MMXXIV →
- License
- MIT — open source on GitHub
If you’ve never opened Foundry before, the Quickstart gets a project registered and your first feedback item created in about three minutes. If you want the bigger picture before touching anything, read The Standard — the opinionated shape every fleet project should keep.
For day-to-day work, the Foundry CLI is the primary interface: every route is validated against the API reference, so anything you can do in the Cockpit you can also do from the terminal or from an agent.