Launching today
Hollr.to
Your personal inbox link. Encrypted on arrival.
4 followers
Your personal inbox link. Encrypted on arrival.
4 followers
Your personal contact link: hollr.to/you. Messages are encrypted in the sender's browser with your public key. A focused way to receive a first hello. MIT code.
Free
Launch Team / Built With
CloudflareYour next app belongs on Cloudflare Workers. Deploy for free
Promoted
1/4 · A contact link should fit on one line: hollr.to/you. Whoever opens it shouldn't need a tour before saying hello.
First, a clarification. What I announced as the Weekathon (7 launches in 7 days, 10-16 November) has become the Product Hunt Marathon: 11 free, open-source products launched on Product Hunt, one a day, 10-20 November. After Megamesh come AI Credit Checker, xnftables, Timescreen and Mars.
The full line-up: Junk, ASE, Mang, Hollr, Clippy, Mercury, Megamesh, AI Credit Checker, xnftables, Timescreen, Mars.
Today is Day 4 of 11, and that's Hollr. Claim a handle, share your link, and receive messages encrypted in the sender's browser with your public key. It's a small, focused inbox for a first hello, with MIT-licensed code you can inspect and adapt. A short personal link is easy to put in a bio or an email signature, and gives people somewhere simple to send a first message without handing over a full address.
I like using AI to help build software without putting AI into every interaction. Sometimes the best result is a smaller tool that does its job and stays out of the way of the conversation.
Privacy deserves precise language. Browser-side encryption doesn't make devices invulnerable, remove metadata or settle how keys are handled, so I've explained those boundaries in a separate comment rather than hiding them behind a slogan.
Would someone you sent this link to know exactly what to do next? Tomorrow, Day 5: Clippy.
2/4 · What the encryption does and doesn't mean
The open-web spirit is not a demand that everyone expose everything. I want a tool whose implementation can be questioned while the people using it retain a private space. Openness and personal privacy solve different problems.
Claim a handle, share a link such as hollr.to/you, and receive a message encrypted in the sender's browser with PGP.
The short link is the easy part to show. The privacy boundary is the part I want to explain carefully. Browser-side encryption does not remove questions about key management, device security or metadata, and this is not a blanket promise of anonymity.
Use Hollr: https://hollr.to
Inspect the project: https://github.com/paulfxyz/hollr
All 11 launches of the Product Hunt Marathon: https://ph.paulfleury.com/
3/4 · A useful flow, not AI in every interaction
For Day 4 of 11 of the Product Hunt Marathon (11 free open-source launches, one a day, 10-20 November), I'm especially interested in where a sender or recipient becomes uncertain. Is the next action clear? Does the interface imply protection it hasn't explained? Could a short piece of guidance prevent a wrong assumption?
Here is the argument behind Hollr: AI-assisted building does not require AI in every runtime interaction. Your organisation may need a better contact or intake flow, not a model reading each message. A CHO can coordinate design, engineering and security to build and maintain that flow, rather than leave every team buying another tool. Test whether ownership improves the work and the full cost. This is a design principle, not a new privacy guarantee; keys, devices and metadata still matter.
The CHO (Chief Hacking Officer) title is playful; the role is serious. I'm open to a CHO brief of up to 30h/week with a great company or startup, a worthwhile product, trust and a modest budget: paulfleury.com/contact.
4/4 · Feedback and contributions
The MIT repository is available to inspect, extend or commercialise with the required notices. If you use Astra or another AI to improve it, choose a concrete part of the flow, set a budget and have it connect each proposed claim to the implementation. Test and review before sending a PR.
I'll put reproducible problems and meaningful small fixes ahead of decorative additions, and assess what it takes to fund the next iteration. Please keep confidential material out of public reports.
Would this be understandable to someone you shared the link with, without an explanation from you?
Web Summit in Lisbon is over, and thank you to everyone I met there. I live in Lisbon and I'm happy to meet around the city if you'd like to talk about Hollr or anything else: X or LinkedIn (@paulfxyz), or paulfleury.com/contact.
Separately from the marathon, a few things I'm working on. Openline (openline.com) is my main venture and startup: it aims to reshape the eSIM market, with a deep pipeline of ideas ready to execute, and I'm raising, so VCs, angels and investors are welcome to get in touch.
Iris (iris.online) and Digital Spot (digital.spot) are spin-offs of tools built for Openline, and I'm looking for investors and early customers for both.
Enki (enki.ngo) is rather a thought experiment: a non-profit, local-first AI public good, too big for me alone, and I'd like to hear from philanthropists, donors and helpers.
Cup of News (cupof.news) is a Sunday-afternoon hobby that is turning into an app, and I'm looking for contributors and users. Tomorrow, Day 5: Clippy.