Roadmap
A practical view of where ZipPigeon is headed: stronger team controls for organizations, clearer deployment ownership, and safer expansion of the constrained anonymous sharing path.
ZipPigeon should stay narrow and understandable. The product is for private file handoffs, not broad cloud storage. Every roadmap item should make the sender, recipient, access window, encryption boundary, and remaining metadata easier to explain.
Future enterprise plans include custom logo and theme support, branded recipient pages, organization policy controls, default expiration rules, allowed recipient patterns, download-limit policies, and clearer administrative reporting. These controls should help teams make private delivery feel like their own trusted process without weakening the encryption model.
The planned enterprise deployment model should support customer-owned encrypted object storage and a customer-owned PostgreSQL-compatible database. That direction gives organizations more control over residency, backup, retention, and infrastructure review while keeping file contents protected in the browser before storage.
A constrained anonymous path is live for short-lived handoffs without creating an account. It uses browser encryption, a one-time share link, short expiration, low limits, blocked high-risk file types, and human verification where configured. It does not keep the transfer in a sender history or provide account-level audit records.
Anonymous sharing should not grow into an open upload pipe. Before increasing size or traffic limits, the roadmap calls for stronger human checks, edge rate limits, short retention, one-time download grants, file-type controls, browser-side file validation, monitoring, and abuse-response paths.
Enterprise SSO enforcement, formal compliance reports, customer-managed keys, public key transparency, hardware-backed server controls, and deeper privacy-preserving malware analysis remain future work. Public pages should keep naming these as planned or under evaluation until the controls are shipped and documented.
This page describes future direction. Current public pages should not imply that custom branding, bring-your-own infrastructure, SSO enforcement, or formal compliance controls are already complete unless release notes say so.
No. The intended boundary remains browser encryption before upload. Bring-your-own storage changes infrastructure ownership, not the normal file-content privacy model.
Some people only need a short-lived encrypted handoff and should not have to create an account. The live flow stays deliberately limited so it does not replace account-bound delivery when records and identity matter.
Use ZipPigeon when a file needs to reach the right person without becoming another attachment or shared folder to clean up later.
Open signed-in sender