Skip to content
coralmesh
all products
AI infrastructure · beta

CoralMesh Desktop

Distributed LLM inference. Run the client to use the network, enable peer mode to serve it, or run the agent headless and only earn.

Overview

A distributed inference network with one application and two roles. The desktop client profiles the hardware on first launch, reports which models it can serve at acceptable latency and the approximate credit rate, then places a live counter in the system tray. Credits move in both directions on a single ledger — purchased, earned, spent and cashed out are kept as separate line items, so a machine that both serves and consumes settles against one balance while the two sources stay distinguishable. Inference covers quantised 3B to 14B models; training is out of scope for this generation. Unlike the token-based networks in the same space, settlement is a credit ledger rather than a cryptocurrency, which keeps the regulatory surface small and the accounting ordinary.

Specifications

Audience
AI infrastructure
Platforms
macOS · Windows · Linux
Status
beta
Built with
Go peer agent · Tauri

Capabilities

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.

Signal-grade privacy, by default

The encryption is not bolted on to a chat product — it is the product. Three concrete promises, and three things it would be lying about if it claimed more.

#1

We can't read your messages

Channel messages are encrypted with XChaCha20-Poly1305 under a per-channel symmetric key. That key never reaches the server in plaintext: it is sealed with libsodium's sealed_box to each member's X25519 public key, which is itself derived from your password via Argon2id. The server holds ciphertext and sealed blobs. The keys live on your devices.

#2

We don't store your messages

Channels have zero server-side persistence — messages pass through the signalling bus as ciphertext and are never written to disk. Direct messages are the one exception: an opaque queue holds them for up to seven days so an offline recipient does not lose the thread, then it is deleted automatically.

#3

Peers don't learn who you are

When a prompt goes to a peer's GPU, the relay strips your user id, IP and conversation id first. The peer sees the prompt — it has to, to answer — but cannot link it back to you. Repeated requests rotate across peers where possible, to make profile reconstruction harder.

What it would be lying about if it promised more

The server knows the membership graph
Routing a private channel message requires knowing who is in it. That metadata is real even though the contents are not readable.
Forward secrecy is on the v2 roadmap
Today's design uses static per-channel keys, so a future compromise of someone's master key could decrypt their past messages held on disk. Signal's double ratchet prevents this; it ships here once channels stabilise.
Lose your password and you lose your history
It cannot be reset, because the master key was never held on the server. Write it down.

How it differs from the rooms you already use

CoralMeshDiscord / SlackTelegramSignal
Server can read messagesNoYesYesNo
Messages stored long-termNo — DMs 7d, channels 0ForeverForeverNo
AI bot inside channelsBuilt in3rd-party only3rd-party only
GPU earnings for usersYes

What a peer could earn

An estimate, not a promise. Throughput is averaged per GPU class on a ~7B-class model, and the electricity comes straight back off the top.

≈40 tok/s · ≈200 W while serving

Hours the machine is on and you are not using it.

Your rate. Drag it to what you actually pay.

Gross
$9.68
Electricity / kWh
$7.20
Net
$2.48

per month, after electricity

Real earnings depend on demand for the models you serve. 1 credit = $0.01. Peers keep 70%, the platform takes 25%, and 5% goes to a refund and risk pool. Cashouts above the KYC threshold require ID verification.

For data centres and GPU farms

Spare H100 or RTX racks during off-peak hours? Mark 5–20% of the fleet as available and CoralMesh routes inference into it, in 30-second slots, with no sales motion and no customer onboarding of your own. Data-centre-grade peers rank first in the scheduler and earn a 1.2× quality multiplier. The agent is a single Go binary with a Helm chart; resource caps and thermal hooks are built in, so it will not fight your existing scheduler. Fleets of 50+ GPUs can negotiate committed minimums, custom SLAs and a dedicated routing pool.

enterprise@coralmesh.io

Questions

Which models can I run?

Any Ollama-compatible model. The network-blessed catalog is curated, but if you run your own peer you decide what it serves.

Do I need a GPU to chat?

No. Chats are routed to peers. You only need a GPU if you want to earn credits by serving the network.

What does running a peer cost in electricity?

It depends on the card. A modern 200 W GPU running 8 hours a day at $0.15/kWh costs about $7 a month — the calculator above subtracts exactly that.

Is it legal where I live?

Sharing idle compute is legal in the EU, US, UK and Türkiye. Some jurisdictions tax peer earnings as income, so check locally. Cashouts above the KYC threshold require ID verification.

What happens if my peer drops mid-answer?

The gateway retries transparently on another peer running the same model. The user sees a brief stall, never a half-finished response.

Can I run a private model?

Yes. Register it on your peer and only your account sees it in the menu, unless you choose to advertise it to the network.

What is the cashout flow?

Earn credits, reach the $500 KYC threshold, submit ID, and operations processes a Wise transfer to your registered email within 14 days during the beta.

Engineered independently. Priced transparently.

No per-seat licensing, no vendor lock-in, no unpredictable invoicing. Our teams are available to scope an evaluation for any product in the portfolio.