--- title: "Why PoolParty" description: "Connect your computers, agents, and models in one private network. Cross-network access is coming after beta." canonical: "https://poolpartyai.com/why/" site: "PoolParty" generated_from: html --- *Why PoolParty* # Use your own computers for AI and compute PoolParty connects computers you own into one private network for shared models, compute, and encrypted storage. You choose what each computer contributes and who can access it. Access across networks is planned for after beta. *Problem 01* You want AI to run on hardware you control. ## Run AI models on your own computers. PoolParty routes a prompt to a model running on a computer in your pool. The response identifies the model and explains the routing choice. On your own network, apps connect directly to the pool. For remote access, the hosted gateway forwards requests to your pool behind a key you create. The AI computation still runs on your hardware. [See it: /how-it-works](https://poolpartyai.com/how-it-works) *Problem 02* Your computers have useful hardware to pool. ## Join computers to one private pool. Install PoolParty on your computers and join them with a code. Each device contributes the services its hardware and platform support. The pool places work on a computer that can run it. Cross-network access is planned for after beta. It is not available in the current beta. Connecting computers creates a shared pool of services. Splitting one AI model across several computers is a separate feature in development. [See it: /start](https://poolpartyai.com/start) *Problem 03* Your agents need shared models, tools, storage, and messaging. ## Connect agents to your pool and to each other. Connect an MCP client such as Claude Code to use the pool’s models, computers, and storage. Existing OpenAI-compatible apps can use the chat endpoint. Access is controlled by the computer owner. Agents can exchange encrypted messages through the pool when their owners enable messaging. Tool actions require separate permission. Persistent agent workspaces that continue while a laptop is closed are planned next. [See it: /agents](https://poolpartyai.com/agents) *Problem 04* You need to verify the software before installing it. ## Check installer signatures and release records. The macOS installer is signed and notarized. Windows and Linux installers are unsigned for now, and the download page explains the resulting warnings. Every release publishes checksums, signed update metadata, and a software bill of materials. You can check these yourself or ask an AI to help. Updates require your approval and are verified before installation. [See it: /trust](https://poolpartyai.com/trust) *Problem 05* Your company needs AI and compute on its own network. ## Pool company computers with administrator controls. Company mode puts the hub on your network and uses computers your company owns. Administrators control admission and set policies that can restrict what a device contributes. Planned company deployment includes directory sign-in, key recovery under company control, and reports showing compute use by team. These features will be offered with the company release; pricing is not published yet. [See it: /company](https://poolpartyai.com/company) *Problem 06* You want unused compute to contribute useful work. ## The Public Pool is planned, but not open yet. The Public Pool is not open yet. It is planned for optional sandboxed jobs using idle computer capacity, without private prompts or files. If the Public Pool opens, contributions are planned to earn credits for pool compute. Credits are not money; public-network use and any contributor priority will be described when that service opens. [See it: /credits](https://poolpartyai.com/credits) *Problem 07* You want to share compute while keeping control of your computers. ## Share resources through pools you control. Each pool runs on computers its members control. Group pools let trusted people share resources, and each owner chooses what their computers contribute. The Public Pool is not open yet. A marketplace for strangers to serve private requests remains gated on security verification and an external audit. [See it: /public-pool](https://poolpartyai.com/public-pool) *Build verification* ## Verify how PoolParty is built Review installer signatures, security checks, architecture records, and tests across supported operating systems. ### Signed and notarized [In the beta] The macOS installer is signed and notarized under a real Apple Developer ID. Your operating system can verify who built it before it runs. Windows and Linux builds are unsigned for now and say so. ### Stop work when security checks fail [In the beta] When a check cannot be satisfied, the system refuses rather than proceeding hopefully. Refusals are surfaced in plain language — never hidden, never quietly retried around. ### More than 140 architecture decision records [In the beta] Every significant design choice is written down with its reasoning, including the ones that turned out to be wrong and were amended, and every arc of the build carries an evidence record. ### Automated tests on macOS, Windows, and Linux [In the beta] The test suite runs across macOS, Windows, and Linux. A defect found on one platform is treated as a defect everywhere until proven otherwise. **Held to the same standard here.** This site publishes no benchmark it did not measure. It labels planned features clearly and publishes SHA-256 digests for the files you download. ## Connect the computers you already own Free, and nothing about you is collected to do it. [Download PoolParty](https://poolpartyai.com/download) [Built for agents](https://poolpartyai.com/agents)