Identity without ordinary account exposure.
Ameeba uses aliases and QR based access so people can connect without beginning with a phone number, email address, or password based identity.
Authentication and sync →Explore the security layers behind your identity, access, conversations, AI, and shared computing power.
Each layer protects a different part of the system. Open the deeper guides for the parts you want to understand in detail.
Ameeba uses aliases and QR based access so people can connect without beginning with a phone number, email address, or password based identity.
Authentication and sync →QR based authentication connects access to the device and session rather than asking you to reuse a conventional password.
How authentication works →End to end encryption protects conversation content between participants while access remains tied to the collaboration and its membership.
Explore encryption →Pseudopod can run Max on local hardware, keeping local AI processing and workspace tools close to a machine you control.
Explore Pseudopod →Workspace and shared compute access should be authorized against current membership rather than possession of a room identifier alone.
Joining a conversation does not automatically contribute hardware. Compute sharing is something a contributor turns on.
When Max runs locally, inference happens on hardware you control.
Remote PseudopodWhen another device performs inference, that host processes the workload.
Encrypted transportEncryption can protect traffic between devices. It does not by itself make a remote execution environment confidential.
Open Compute Center →See how Ameeba connects access across devices.
Open guide →Understand how protected conversations move between participants.
Open guide →Understand local and remote inference and the trust boundary between them.
Open Compute Center →