Pipeup on its own needs none of these, and sends nothing anywhere. An add-on is one extra script the page's author chooses; each asks reviewers first. In beta. Making your own? Read the guide: you can publish an add-on under your own name.
Comments reach everyone who has the page.
Sends Sealed comments, to a service you pick: a PrivateBin or your own mailbox.
Asks first Nothing is shared until the reviewer chooses to.
Try it On your own computer: the command below runs a local demo with its own sharing service, so nothing goes to a public one.
Dictate a comment instead of typing it.
Sends Nothing of its own. Your browser's speech engine does the listening.
Asks first A short note, then the browser's own microphone prompt.
See who else is on the page, and where.
Sends Presence and comments, browser to browser.
Asks first Each reviewer, before anything connects.
A small AI model on the reviewer's device reads the whole page and points to related parts of it.
Sends Nothing. The model runs on the device, and your browser may download it once.
Asks first Each reviewer, with the model, its size and what it reads, before it turns on.
A small server you run for Share, so even sealed comments stay inside your organisation.
Sends Sealed comments, to a server you run. It holds ciphertext and never sees the key.
Asks first Nothing changes for reviewers: Share still asks before anything is sent.
Needs Node 22 or newer, and an HTTPS proxy in front of it. Pipeup doesn't run a mailbox for anyone, so there is no online try: it needs a server of your own.
Write an add-on for your team or company, and host it yourself. It needs nobody's permission, and nothing goes in Pipeup's name.
Sends Whatever you decide, said in one plain sentence that reviewers are shown first.
Careful Add-ons from anyone else run with the page's full power, and Pipeup doesn't vouch for them. The guide shows how to list, pin and check what runs.
Example: not from Pipeup
The quickest way to get a review into Git: it opens GitHub's own "new file" page with the review filled in. No server, no token.
Sends Nothing from here. It opens a GitHub link; you sign in to GitHub and press its commit button yourself.
Asks first It says what it will fill in and where, and you confirm.
Example: not from Pipeup
What a company's own add-on looks like: it sends a review as Markdown to a service the company runs, which files it in Git.
Sends The open comments as one Markdown file, to the address the page names. It never holds a Git token.
Asks first It says what it will send and where, and you confirm.