Live data from Hacker News

Show HN: ProtoWall – NDA wall and reverse proxy for sharing prototypes

protowall.app

1–4 of 4 posts

Show HN: ProtoWall – NDA wall and reverse proxy for sharing prototypes

#1
I built ProtoWall to solve a problem I kept running into: needing to share a working prototype with an investor or client, but not wanting to just hand out a URL with no protection.

ProtoWall sits as a reverse proxy in front of your app. You invite reviewers by email, they click a link, read and sign a versioned NDA, and then get proxied through to your prototype. No SDK, no code changes on your end.

How it works:

- You add your prototype's origin URL and configure an NDA - Invite specific people by email; they get a one-click link - Reviewer accepts the NDA (name, timestamp, IP, user agent all recorded) - A 30-day proxy session is created; traffic flows through to your app - You can revoke access instantly; the session terminates immediately, not at the next token refresh

Every action is audit-logged. You can export a CSV of the full trail or download a per-reviewer PDF evidence package with consent records, NDA text, and SHA-256 content hashes; useful if you ever need to prove someone agreed to your terms.

Auth is magic-link only (no passwords to manage or leak). NDAs are versioned; if you update the text, existing reviewers must re-accept before they can access again.

Free tier: 1 project, 5 invites. Pro is $19/mo for 5 projects and PDF evidence export.

Happy to answer questions about the architecture or the legal side of things.

Show HN: ProtoWall – NDA wall and reverse proxy for sharing prototypes
protowall.app

Re: Show HN: ProtoWall – NDA wall and reverse proxy for sharing prototypes

#4
post #3

[flagged]

They get bumped. When you publish a new NDA version, the old document is marked superseded and existing reviewers lose proxy access on their next request. They see the new NDA text and have to re-sign before they can access the prototype again.

Each consent is tied to a specific document version (with a SHA-256 hash of the content), so you always know exactly which version someone agreed to.