Changelog
ShipFoundry is live
ShipFoundry is now publicly available, helping you take advantage of accelerating improvements in your product stack.
ShipFoundry is now live and publicly available for agentic builders.
The frameworks, runtimes, APIs, models, databases, platforms, and services underneath a product keep shipping faster. Most of those changes will not matter to a specific project. Some can remove a dependency, reduce cost, improve performance, simplify code, strengthen reliability, or unlock a new product capability.
ShipFoundry exists to find the difference.
From Stack Update to Product Decision
Each ShipFoundry project has a Watchlist that defines the tools and services it should monitor.
When a meaningful update lands, ShipFoundry:
- matches the update against the project and its watched stack;
- checks the selected GitHub repository read-only for applicable package, version, configuration, route, import, call-site, and implementation evidence;
- separates theoretical potential from verified project fit;
- identifies any genuinely customer-owned fact that the repository cannot answer;
- produces a clear recommendation and next action;
- packages useful opportunities into the brief the available evidence supports.
Repository evidence can strengthen a recommendation, narrow it, or close it as not relevant.
Available Today
The public launch includes:
- automatic project context from a selected read-only GitHub repository;
- project Watchlists that control which stack updates can enter the recommendation workflow;
- daily matching against relevant framework, platform, API, model, runtime, database, and developer-tool updates;
- evidence-led recommendations with clear Status, Potential, Project Fit, Proof, and Action;
- bounded repository investigation across packages, versions, files, routes, configuration, imports, SDK usage, and implementation surfaces;
- focused customer questions only when the repository cannot establish a genuinely team-owned fact;
- Research Brief, Engineering Spike, and implementation-ready handoff paths;
- copyable Markdown delivery;
- remote MCP access for Codex, Claude Code, Cursor, OpenCode, and other compatible agent workflows;
- optional Linear issue delivery;
- durable outcomes for useful, shipped, dismissed, and irrelevant opportunities;
- a public Signals feed for honest judgment on meaningful stack changes.
Built to Say No
ShipFoundry is not designed to turn every release into work.
It does not automatically modify repositories, create commits, or open pull requests. The GitHub integration is read-only.
The purpose is to give builders and their agents better work to begin with—and to make it just as useful to reject an irrelevant update as it is to discover a valuable one.
Plans
The Dev plan is $19 per month and includes:
- one watched project;
- 10 tracked stack items;
- the complete ShipFoundry workflow.
The Pro plan is $59 per month and includes:
- up to three watched projects;
- 60 tracked stack items shared across the account;
- the complete ShipFoundry workflow.
Both plans begin with a seven-day trial. A card is required, and the trial can be canceled before billing.
For the public launch, promotion code SHIPFOUNDRY gives 30% off the first two paid months.
What Comes Next
The immediate focus is external product truth:
- how ShipFoundry performs against unfamiliar repositories;
- which recommendations save meaningful attention;
- which stack coverage is still missing;
- and whether the evidence-backed handoff gives coding agents better work to start with.
A lightweight local CLI or bridge is a likely next integration. The dashboard and remote MCP workflow are available today.
The stack is accelerating. Your product should benefit.