For anything your AI writes
Your assistant writes a report, a plan or a dashboard. PeerForge turns it into a link. Whoever you send it to highlights the sentence they disagree with and types. Those notes come back to your assistant, attached to the words they were about.
Free, and no account needed · or start from a ready-made example
Migration runs behind a flag for two weeks. We ship the billing rewrite in October. Support gets the runbook a week before.
Dual-write means two sources of truth for a fortnight. We accept that, and we reconcile nightly.
Comments
Select any sentence to start a thread.
Works with every agent
If it can make a web request, it can publish here. Nothing to install, no library to adopt, and two assistants from different companies can work on the same document.
What gets published
Ask your assistant for any of these and it hands you a file. Published here, your colleagues open the real thing — charts that draw, tables that sort, prototypes they can click — instead of a screenshot or a PDF. HTML stays HTML and Markdown is turned into a page. A link is all they need, and each one keeps every version and takes comments line by line.
The part everyone gets wrong
A comment here is attached to particular words. Your assistant rewrites those words all the time — that is its job — and every rewrite risks leaving somebody's note pointing at nothing. Most tools let that happen quietly. The reviewer assumes they were heard. They were not.
Every time a new version is published we check every comment against the new text, before anyone opens it, and the answer comes straight back. Not a count — the actual comments, by name, so your assistant can fix what it just broke in the same sitting.
Still attached
The same words, in the same place. Nothing to do.
Moved
The words survived but are somewhere else now. Re-attached for you.
Now ambiguous
That sentence appears more than once, so we will not guess.
Came loose
The words it was written about are gone from this version.
Two comments came loose and it is told which two. No other tool will tell it that.
After you send it
Who opened it, what they said, and which comments your last rewrite broke — for every document, in one place. This is the half that a publish button on its own does not give you.
Documents
12
in this workspace
Versions
41
every one kept
Open comments
5
1 came loose
Reads
74
last 30 days
| Name | Access | Reads | Comments | Updated |
|---|---|---|---|---|
| Q3 plan — billing rewriteHTMLbT19LHOu · v2 | Link | 48 | 31 loose | 12min ago |
| Support macros auditHTMLTSS9jcJu · v1 | Domain | 17 | 2 | 3hr ago |
| Onboarding email sequenceMDvaqRaDAb · v4 | Named | 9 | — | yesterday |
Activity
peerforge.app
where you are signed in
prfg.link
where the documents live
A published page cannot read who you are, act as you, or reach any other document. The browser stops it, not us.
For anyone who wants the specifics: the document is put in a sandboxed frame with no same-origin privilege, so the browser gives it no identity at all.
<iframe sandbox="allow-scripts"
allow-same-origin ← never
inside the document: self.origin === null
which is the browser saying “this page is nobody”
Why it is safe to open these
An HTML file can contain code, and nobody reviews what an assistant writes before a colleague clicks the link. So we do not run it anywhere near your account. Documents are served from a second website that holds no login of any kind, in a locked box the browser itself enforces.
In practice: a document cannot read who you are, cannot act as you, and cannot see any other document — not even the last one you opened. That is the browser's own rule, not a promise we are making.
A test in our suite opens a published document and checks that the page around it cannot read a single line inside it. But the guarantee is the browser’s, not ours: it comes from the sandbox attribute and the content policy the document is served under, and it would hold even if we stopped looking.
Nothing to lock you in
Do it yourself in a browser, or let your assistant send it. Two assistants from two different companies can work on the same document without treading on each other — if one saves over the other's work, it is told rather than allowed.
Drag the file in and get a link. No terminal, no key, nothing to install.
q3-plan.html → a link you can sendGive it a key and it publishes for you — then reads the replies back.
curl --json @plan.json peerforge.app/api/publishSix ready-made documents. Publish one in a click and see how it works.
a dashboard · a spec · a board update · …The usual ways
Your assistant writes something good and it goes straight into a tool built for something else. The page stops working, the feedback lands somewhere your assistant cannot see, and somebody spends an evening copying comments across by hand.
| PDF by email | Pasted into chat | Shared drive doc | PeerForge | |
|---|---|---|---|---|
| The document still runs — charts, tables, prototypes | — | — | — | |
| Comments land on the sentence, not in a thread | — | — | ||
| Your assistant can read the feedback back | — | — | — | |
| You are told when a new version breaks a comment | — | — | — | |
| Every version kept, and each comment remembers which one it was left on | — | — | Partly | |
| A colleague opens it without installing anything | Needs the account | |||
| You can close it again — an expiry date, named people, one company | — | — | ||
| It runs where it cannot touch your account | Cannot run at all | Cannot run at all | Cannot run at all |
Pricing
Reading is always free, on every plan and with no limit. If a document is public or shared by link, whoever you send it to just clicks and reads — no account. The private settings ask them to sign in, because that is the only way to know it is really them. What you pay for is publishing, and it is flat per workspace rather than per person, so nobody has to argue about who deserves a seat.
For one person, and anything you are happy to hand out a link to.
€0
Free, and staying that way
One price for everyone at your company. Readers stay free.
€12/month
Flat, whatever the size of the team. Plus VAT.
For companies that need sign-in restricted to their own directory.
€35/month
Flat, whatever the size of the team. Plus VAT.
Publishing without an account needs no card and no plan. Paid plans are billed by Paddle, who are the seller of record and add VAT at whatever rate applies where you are. Tell us what you need if none of these is the shape of it.
Drop in a file your assistant made, or start from one of ours. You will have a link to send before you have decided whether you like this. No account, no card.