Three deployment roles, one network
Chat only through the browser with no installation; peer and chat together through the desktop client; or peer only as a background service under systemd, launchd or a Windows service. The peer agent is a single Go binary and ships with a Helm chart for cluster deployment.
Hardware profiling and live earnings
First launch profiles the GPU, reports which models it can serve within acceptable latency and estimates the hourly credit rate. A tray counter shows served requests and accumulated credits without opening the application.
A ledger that runs both directions
Purchased, earned, spent and cashed-out credits are separate entries against one account. Operators who both serve and consume see a net position, while earned and purchased balances remain separable for tax treatment and future eligibility criteria.
Encryption as the architecture
Channel messages use XChaCha20-Poly1305 under a per-channel symmetric key, sealed with libsodium sealed_box to each member's X25519 public key, which is itself derived from the account password through Argon2id. The server holds ciphertext and sealed blobs only; keys never leave the operator's devices.
Identity separation before inference
The relay removes the user identifier, IP address and conversation identifier before a request reaches a peer. Repeated requests are distributed across peers wherever capacity allows, so no single peer can reconstruct a usage profile.
Any Ollama-compatible model
The network-wide catalogue is curated centrally, but a self-operated peer decides what it serves. A privately registered model is visible only to the registering account unless it is explicitly advertised to the network.
Settlement without a token
70% of every token is retained by the peer, 25% funds the platform and 5% goes to a refund and risk pool. Payouts run through Wise once the KYC threshold is met — no exchange listing, no wallet and no token price to track.