Local Bridge
Share local folders with a browser-friendly URL. No uploads.
2 followers
Share local folders with a browser-friendly URL. No uploads.
2 followers
Share local folders, build outputs, and docs from your machine with a browser-friendly URL. No uploads, no deployment, one command.
RiteKit Company Logo API
@ajay_shukla5 This is a genuinely useful positioning—being clear about what Local Bridge isn't is actually more helpful than overselling it. The lifetime pricing for a tool that solves a specific friction point is refreshing. My question: how does Local Bridge handle security for sensitive folders, and what's your thinking on whether teams would want granular access controls (like password-protecting specific shares or expiring links).
@osakasaul This is exactly the area where I do not want to overclaim.
Local Bridge only exposes the folder you explicitly point it at. Files stay on your machine, public sharing uses an outbound Cloudflare tunnel instead of opening inbound ports, and sensitive shares can be run with `--password`, `.lbignore`, and `--expire`.
So my current recommendation is: treat each share as a temporary session. Use a password, ignore anything that should never be exposed, and set an expiry when the link is only needed for a short window.
On granular access controls: yes, I think teams would eventually want that. But v1 is deliberately per-share rather than full team/RBAC software. Password-protected shares and expiring sessions fit the current product. More advanced controls like per-recipient access, saved policies, or team-level permissions are interesting, but I would want to design those carefully rather than bolt them on and pretend this is already enterprise file governance.