How Hachiflow actually works, written by the people who run it. Keys, invites, exports: the mechanisms, and the days they were tested.
Requests through CDNs and proxies have body ceilings, and a customer export is one archive. Multipart upload is the boring, correct fix, and we did not call it done until a 260 MB archive came out the far side, byte for byte.
An invite link is a signed code on a 30 day clock, not a row in a database. It expires, it dies instantly when the workspace's signing identity rotates, and the durable fix for both is a stable URL you control.
A Buzz identity is a keypair made on your device, not an account in our database. Join a second workspace and you are already you. What we mint for a workspace, and what stays yours alone, are different keys on purpose.