There is a fundamental disconnect in modern collaboration. We have accepted a fractured workflow where our words live in one app, but our work—the documents, designs, and contracts—lives in another.
This separation forces you to bridge the gap with fragile external links and constant permission requests. We believe files shouldn't be second-class citizens hosted on a distant server; they should be first-class residents of the conversation itself.
In most tools, files get scattered. They are dropped into separate tabs, buried in infinite chat scrolls, or hosted on a third-party "Drive" that breaks the security model. Context is lost. Security is fragmented. You end up being a digital archaeologist, digging through history to find that one PDF.
We built files into the core architecture. Whether you attach a file to a chat, a task, or a note, it inherits the security level of that Space. Always end-to-end encrypted. Always under your control. No third-party servers.
You can attach evidence anywhere: in a chat message, a specific task, or even a note comment. The file lives where the work happens, not in a dumping ground.
For files that need a permanent home—like brand assets, contracts, or heavy documentation—every Space comes with a Vault. This is a dedicated, encrypted file manager where you can organize folders and store assets centrally. It replaces the need for an external "Drive." If you are in the Space, you have access to the Vault. Simple as that.
Every file is PGP encrypted before it ever leaves your device. Only you and the people in that specific Space possess the keys to decrypt and view it. We (the provider) see only encrypted blobs. We cannot see your blueprints, your contracts, or your photos.
Files don’t float around. If you upload a contract to a Task, it stays attached to that Task. You never lose the why—the file stays bound to the conversation that created it.
We know creators work with big files.
Files aren’t buried debris. They are active assets—encrypted, organized, and strictly bound to their context. No external drive links. No exposure. Just files where they belong.
We’re exploring secure file previews and version history. But the foundation stays solid: Files in Qaxa stay encrypted. And they stay yours.