Scenarios Coming soon
Review the signed-out visitor, the admin and the empty account as separate states of one version.
Forge Cloud closed beta
Review AI-builtprototypes like realproduct work.
Publish a frozen version. Stakeholders open a link, type six digits and pin comments to the real screens. Every comment comes back to your repo.
How a review works
From your terminal to their comments, and back again.
01 forge publish
Publish a frozen version
Freeze exactly what you built, then publish it. Forge Cloud hosts that version and prints a short link and a six-digit PIN. The version never changes under anyone’s comments.
02 PIN gate
Send the link and the PIN
Stakeholders open it in any browser and type six digits. No account, no install, no seat to buy. The page speaks English or Portuguese.
03 Review room
They comment on the real screens
The prototype runs as built, with one small bar at the bottom. Stakeholders pin a comment to the exact element, switch between desktop, tablet and phone widths, and can see when the feedback window closes.
04 forge comments triage
Triage in your repo, then tell them
New comments come into your repository, where your agent helps you turn each one into a task, a decision or a question. When a later version ships the fix, the stakeholder’s link shows where their comment landed.
Cloud inbox coming soon
Your Cloud dashboard
Every prototype, version and open feedback window, in one place.
See what needs you first: new comments, open questions from stakeholders and feedback windows about to close.
Stakeholders Coming soon
Invite people to a prototype once, then see who has commented on each version.
Feedback windows
Each feedback window closes at a date and time you set. After that the version stays readable and stops taking comments.
The Forge record free, local, yours
The repo stays home. The review goes out.
Forge Cloud is the part that needs other people. Everything else is files in your repository: the brief, every decision with its reasons, the tasks, each frozen version. The forge CLI and the coding agent you already use keep that record, and it works without Cloud. Cloud displays what you publish; the record stays the source of truth.
Stays on your machine
- Source code and Git history
- Your coding agent and its keys
- Decisions, tasks and the brief
- Every freeze, tagged in Git
Runs in Forge Cloud
- Hosted review links and PINs
- Pinned comments and threads
- Feedback windows and their deadlines
- The trail back to each stakeholder
forge freeze v6Froze v6 at 3f2a91c handoff pack: handoff/v6/forge publish v6Publishing v6… frozen.design/s/8KQ2M7PD 42 file(s) hosted · 3 freeze(s) published on this plan PIN 418027 Send it with the link. It is not saved in this repo.forge comments triage v6Staged 3 comment(s) at .forge/triage/v6/. Disposition them with the forge-triage skill in your agent session.
Pricing
Free where it is yours. Paid where it is hosted.
Forge record
Free
On your machine, without an account.
- The forge CLI: freeze, check, review, triage
- The Design Record format
- Skills for Claude Code and Codex
- Feedback imported from Figma or GitHub issues
Forge Cloud · free plan
Free
Enough to run one real review.
- 1 hosted prototype
- 5 hosted freezes, for the life of the account
- Comments from 1 stakeholder
- Review links, PINs and the resolution trail
Forge Cloud · paid Coming soon
Price at launch
For a designer with more than one thing in review.
- Lifts the prototype, freeze and stakeholder limits
- Scenario switching for stakeholders
- Stakeholders and developers never need a seat
- Cancel and your repository stays exactly as it is
Hit a limit and only the publish is refused: freezing and everything else keep working locally.