Install it, and the first machine is already a pool. Add a second with a join code — a Mac serves models and seals storage, and a Windows PC joins for jobs. Linux serving has not been measured. No account, no server to run, nothing rented.

Ask your pool. The answer comes from a model running on a machine you own, and the line under it says which model and why the pool chose it. Nothing leaves your machines to be answered.

One command registers the pool as a tool server for Claude Code or any Model Context Protocol client. The agent gets the pool’s models, machines and storage behind that machine’s own credential — no login, no token to paste. Consent is one switch; off refuses the very next call in plain words.

Existing code ports with a change of base URL. On your own network the pool answers directly; away from it, the hosted gateway at api.poolpartyai.com answers behind a key you mint, with rate limits and budgets on every key.

Any LLM command-line tool can point at the pool and choose a model per request from a list that tells the truth: what is actually available, a posted price or an honest blank, and a fit label marked as advice. Nothing downloads, warms or spends outside a consent that already said yes.

Work that needs a graphics card is placed on a machine that has one and runs as an owner-installed program pinned to its digest, in a private working directory. Its consent is separate from Contribute, because the sandbox is weaker and says so.

Encrypted on your device, split, and scattered across your machines. 2-of-3 recovery, device-to-device key approval, recovery codes shown once, automatic healing. The machines holding the pieces can read none of it; the hub never holds a key.

Machines find each other beside consumer and enterprise VPN clients instead of breaking against them. If every direct path fails, the hub carries sealed data it cannot open — time-limited, budgeted, never a place your data rests.

A signed and notarized macOS build. Windows and Linux builds that are unsigned for now and say so plainly. Every release ships its SHA-256 digests, signed update metadata and a software bill of materials — check it yourself, or point your AI at the trust page and let it check.

The app tells you an update exists and you choose; opt into automatic if you like. Every update is verified before it applies and can be rolled back. No silent updates, ever.

Only while idle, only plugged in, inside thermal limits that no preset can waive, and it stops the instant you touch the keyboard. Opt-in per machine, a kill switch always visible, every refusal shown in plain language.

Credits measure compute used in your own pool. The Public Pool is not open yet; public-network credit use will be described when that service opens.

One machine can belong to your own pool and friends’ pools at the same time. The Public Pool is not open yet; support for it will be described when that service opens.

Invite a friend with a one-time code shown on screen; approve their machine with a tap. Their idle time helps your pool, yours helps theirs, and only your own machines answer their prompts unless you decide otherwise. Leave or revoke at any time.

Threads between your machines travel device-to-device, encrypted with keys only they hold; when one is offline the hub carries ciphertext it cannot read. Text and images ride the same sealed plane as your files.

Claude Code on your laptop can message the agent on your desktop through the pool — behind three locks, all off by default: the sending agent’s permission, the receiving machine’s rail, and the receiving agent’s own consent. Every thread is readable by the humans who own the machines. Messages are speech; actions stay behind consented tool doors.

A bot is a name, a brain and a budget. It is a contact on every device in your pool, it answers on your own hardware with the same routing line as any chat, and a budget of zero refuses every ask by name until you raise it — so a bot can never spend what you did not post.

The app opens to one screen — ask your pool, see your machines swimming, flip Contribute, stop everything — and a gear that dives to Depth, where every rail, door, ledger and receipt lives. Night is a tint, not a redesign.

Machines attest to the hub continuously and a node that stops answering is quarantined until it proves itself again. The live rung is a software key today, stated as such; the hardware rung joins when the platform allows it.

Off by default. When you turn it on, the report is built from an allowlisted set of technical fields, shown to you in full before anything leaves, and contains no file contents, prompts or secrets.

More than 140 architecture decision records, fail-closed verification gates, three-OS continuous integration, and an evidence record for every arc. When a check cannot be satisfied the system refuses, in plain words, rather than proceeding hopefully.

Git Pool is being developed to bring code, reviews, files and collaborators into one Projects view, with repositories hosted on your pool machines. In development and off by default. Repository hosting, file access, collaboration and synchronization are not available yet.

A Windows PC already joins a pool and takes jobs. The daemon's control channel, the LAN storage plane and the sealed-storage verbs on Windows are being built, so a PC serves models and holds sealed shards the way a Mac or a Linux box does.

A separate, signed-in workspace is being developed for managing approved computers, models, agents, storage and compute from a browser. Access will require approval from an installed device; the public website remains a static product guide.

Connect supported model providers through an owner-approved setup flow, alongside models running on your own computers. Provider credentials and billing remain separate from PoolParty credits.

The planned orchestration flow will let an approved lead agent assign work to worker agents, show each role and result, and connect supported harnesses with explicit permissions. Code presence alone does not make this available in the beta.

Coming after the beta: connect your own computers to your pool across networks, directly where possible or through a relay you control. Serving remains on your hardware.

Coming after the beta: approve a phone or laptop as a consume-only device so it can request work from your pool. These devices cannot add hardware, read sealed files, or contribute.

The Public Pool is not open yet. It is planned to run small, sealed, sandboxed batch jobs using idle capacity, without exposing private prompts or files. Its aggregate counter will be published when the service opens.

Point the pool at a folder or a database and get answers with citations. Training only ever reads data in the clear on machines you name.

Machines and apps offer actions the pool’s agents may invoke, with per-tool, per-caller consent granted on the tool’s home machine, and receipts on both ends.

A domain-locked, consume-only key and one script tag, so a site you run gets your pool behind it.

A persistent workspace for your agents that lives on the pool instead of on the machine in your hand, so they keep working with the laptop closed.

The same product run as a company: the hub on your network, the machines you already bought, operator roles, directory sign-in, escrow keyring, policy that can only narrow. Packaged today; offered with a company release and a real price, not before.

This planned serving approach would divide one model across multiple computers. Cross-machine performance and compatibility still need qualification; current model selection does not combine VRAM or pool the memory of separate GPUs.

Sampled verification and no-plaintext serving — the gates that must be green before a stranger’s prompt ever touches a stranger’s machine. Both are public, including what each one unlocks.

Pools open to contributors beyond people you already trust, behind the verification ladder.

Credits are real today; money is not. Fiat belongs to a later, deliberately gated phase.

An agent with a wallet buys pool compute per request, fractions of a cent at a time, with no account — behind the ladder, the credits terms and the entity decision.

Spending credits earned on your machine against other sites’ premium features.

The third-party program that lets a site’s visitors contribute to the pool behind it.