Access begins with a trusted device.
Ameeba Chat authentication connects access to your Ameeba environment, including Vault and Pseudopod, without asking you to reuse a conventional password.
How authentication worksUnderstand what Ameeba protects.
Explore how Ameeba protects your identity, conversations, files, access, AI, and shared compute.
AI changes what needs protecting.
As AI becomes part of how we communicate, work, and create, more of our conversations, files, knowledge, and computing move between people, devices, and AI.
Ameeba is designed to give people greater control over how that information moves, where AI runs, and who can access it.
Security Center
Security across Ameeba.
Start with the part of the security model you want to understand.
01
Encrypted identity
Aliases and QR based access reduce dependence on conventional account identifiers.
02
End to end encryption
Protected conversations are encrypted between participants.
03
Vault
End to end encrypted files stay protected across Ameeba Chat and Pseudopod.
04
Authentication
Ameeba Chat authentication establishes trust for new devices and your Ameeba environment.
05
Local AI
Pseudopod can keep Max inference on hardware you control.
06
Access and membership
Authorization follows the collaboration and its current membership.
07
Shared compute
Compute sharing is explicit and remote execution has a clear trust boundary.
Protection starts before the conversation.
Ameeba begins with identity and access, protects conversations and files with end to end encryption, and gives you clear boundaries around where AI and compute run.
Identity→Communication→Knowledge→AI→Devices→Compute
Encrypted identity
Identity without the usual starting point.
Aliases first.
Ameeba uses aliases and QR based access so people can connect without beginning with a phone number, email address, or password based identity.
Explore encrypted identityEnd to end encryption
Protect the conversation between participants.
Protected between intended participants.
End to end encryption protects supported conversation content between intended participants and trusted devices while access remains tied to the collaboration and its membership.
Explore encryptionVault
Encrypted files, wherever you work.
Knowledge protected end to end.
Vault uses end to end encryption for protected file storage and sharing. Access your Vault through supported mobile and Pseudopod surfaces, with access tied to Ameeba Chat authentication.
Explore VaultKeep intelligence close when you choose.
Pseudopod can run Max on local hardware, keeping local AI processing and workspace tools close to a machine you control.
Explore PseudopodAccess and membership
Access follows the collaboration.
Membership matters.
Workspace and shared compute access should be authorized against current membership rather than possession of a room identifier alone.
Sharing stays explicit.
Joining a conversation does not automatically contribute hardware. Compute sharing is something a contributor turns on.
Trust boundaries
Know where the work happens.
Local and remote execution are different security boundaries. Ameeba should make that distinction understandable.
On your device
When Max runs locally through Pseudopod, inference happens on hardware you control.
Between devices
Encryption can protect traffic while it moves between participating devices.
On another device
When another Pseudopod performs inference, that host processes the workload. Encrypted transport does not by itself make the remote execution environment confidential.