Key-based collaboration

Collaborative workspaces.
Built around keys and sessions.

Voryx starts with a key instead of an account. From that key, workspaces can be created with their own members, access, messages, and files.

COMING SOON Open Voryx
Read overview
System

Each workspace defines its own boundary.

Keys

A key represents access. It can be used to create or join a workspace.

Sessions

A session defines members, access, communication, and shared state.

Authorization

Access is evaluated through keys and session rules.

State

Each workspace keeps only the information required for it to operate.

Current
Encrypted messaging Exchange messages inside a workspace.
Encrypted file exchange Share files through encrypted envelopes.
Workspace management Create and manage session workspaces.
Member management Invite and remove members from a workspace.
Key-based authorization Authorize access through keys and session rules.
Questions
Why keys instead of accounts?

Keys represent access without requiring permanent user accounts.

What is a session?

A session is an isolated workspace created from a key.

Does Voryx require real identity?

No. Workspaces are independent of real-world identity.

Is this the final architecture?

No. Version 1 focuses on the core collaboration model.