What is a serverless messenger?

Most messengers, even encrypted ones, run servers that see connection metadata and can be compelled to change behavior. A serverless messenger removes that single point of failure entirely.

PrivaMesh is serverless in the literal sense: messages are encrypted blobs in Solana transaction memos, and the only network dependency is a swappable, self-hostable Solana RPC. There is nothing central to attack.

The word needs care because the cloud industry uses it to mean the opposite. In cloud engineering, serverless means the servers are managed by someone else and hidden from you - they exist, they process your data, you simply do not administer them. For a messenger, that is not a privacy property at all.

The literal sense is a much stronger claim, and it can be tested. A genuinely serverless messenger has to answer four questions without a backend: where accounts live, how keys are distributed, how messages are routed, and what holds a message while the recipient is offline. Any app that answers one of them with a company machine is not serverless.

PrivaMesh answers all four without one: accounts are locally generated seed phrases, keys are wallet-signed prekey bundles published on-chain, routing is a zero-value Solana transaction, and the chain itself holds ciphertext until a device fetches it. The trade is a small per-message fee and no server-side features - no cloud sync, no history restore, no account recovery.