This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
The Membrane
Fail-closed authorization for AI agents in production
The Membrane is a self-hosted, fail-closed authorization gateway for AI agents with production write access. Every model and tool call needs a live, signed, time-bounded scope. Each allowed action writes a tamper-evident, hash-linked receipt. A replayed proof, a swapped model or an expired scope is refused; a broken chain severs the agent. Your keys, your models, your policy. Open source (Rust). Clone to a refused call in about five minutes, or watch a recorded replay in the browser demo.
Hey Product Hunt - I'm Zorie, and we built The Membrane.
Why: teams are handing AI agents write access to production. Agents that merge code, change infrastructure, edit tickets and touch customer data. When one does the wrong thing, what's left is scattered logs and third-party chat histories. They can't prove an action was authorized by a policy that was still in force.
The Membrane is a small Rust gateway that sits in front of your agents:
- Every model and tool call needs a live, signed, time-bounded scope. No scope, no call.
- Each allowed action writes a tamper-evident, hash-linked receipt, so any action traces back to the exact policy and issuer that authorized it.
- A replayed proof, a silent model swap or an expired scope is refused. If the receipt chain breaks, the agent is severed.
It enforces before production is touched; it doesn't just observe after the fact.
Who it's for: teams letting agents touch production systems who need proof of authorization, not just logs.
Honest state: v0.1.0, early stage, single maintainer. The gate, signing and receipt chain are real and runnable today; the hosted demo's tool effects are simulated.
What we'd most like to hear: if you run agents with production access, what would you need to see before putting a gate like this in the path?
About The Membrane on Product Hunt
βFail-closed authorization for AI agents in productionβ
The Membrane was submitted on Product Hunt and earned 3 upvotes and 1 comments, placing #96 on the daily leaderboard. The Membrane is a self-hosted, fail-closed authorization gateway for AI agents with production write access. Every model and tool call needs a live, signed, time-bounded scope. Each allowed action writes a tamper-evident, hash-linked receipt. A replayed proof, a swapped model or an expired scope is refused; a broken chain severs the agent. Your keys, your models, your policy. Open source (Rust). Clone to a refused call in about five minutes, or watch a recorded replay in the browser demo.
On the analytics side, The Membrane competes within Open Source, Developer Tools, Artificial Intelligence and GitHub β topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how The Membrane performed against the three products that launched closest to it on the same day.
Who hunted The Membrane?
The Membrane was hunted by π Rosario βZorieβ Barber. A βhunterβ on Product Hunt is the community member who submits a product to the platform β uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of The Membrane including community comment highlights and product details, visit the product overview.
Hey Product Hunt - I'm Zorie, and we built The Membrane.
Why: teams are handing AI agents write access to production. Agents that merge code, change infrastructure, edit tickets and touch customer data. When one does the wrong thing, what's left is scattered logs and third-party chat histories. They can't prove an action was authorized by a policy that was still in force.
The Membrane is a small Rust gateway that sits in front of your agents:
- Every model and tool call needs a live, signed, time-bounded scope. No scope, no call.
- Each allowed action writes a tamper-evident, hash-linked receipt, so any action traces back to the exact policy and issuer that authorized it.
- A replayed proof, a silent model swap or an expired scope is refused. If the receipt chain breaks, the agent is severed.
It enforces before production is touched; it doesn't just observe after the fact.
Try it:
- Quickstart: clone to a refused call in about five minutes. No Docker, no paid API: https://github.com/membrane-hq/the-membrane
- Browser demo: https://demo.themembrane.org - a recorded replay of the gate flow; tool effects are simulated and labeled on screen
- Site: https://themembrane.org
Who it's for: teams letting agents touch production systems who need proof of authorization, not just logs.
Honest state: v0.1.0, early stage, single maintainer. The gate, signing and receipt chain are real and runnable today; the hosted demo's tool effects are simulated.
What we'd most like to hear: if you run agents with production access, what would you need to see before putting a gate like this in the path?