PoolParty downloads and beta access
Free, for machines you already own. Every release publishes its digests, its signed metadata and its full dependency list — so you can check what you have before you run it, and so can an AI you trust.
Public beta. PoolParty is free, unfinished software. It may have bugs, lose data or stop working, and it will change. Download and use it at your own risk, and keep your own backups. Read the End User Licence Agreement before you install.
After installation: Your Pool, the browser workspace for managing devices, models, agents, storage and compute, is in development. It will require sign-in and approval from an installed computer. Preview the planned workspace
Downloads for macOS, Windows, and Linux
The same application. Two of them ship unsigned for now, and that is said here rather than discovered by you. The card for the machine you are reading this on is marked — detected in your browser, nothing sent, nothing stored.
This machine
macOS
SignedSigned and notarized by Apple. It will open the way any other app does.
PoolParty_0.1.49_macos_arm64_signed-notarized.pkg · 101.2 MB · SHA-256 76563ab94adc3b5cf189d36f0dd3390e98aef867761608751439cbb3068954a5
This machine
Windows
UnsignedNot code-signed. Windows will show a blue SmartScreen warning — see below for why, and what to check instead.
PoolParty_0.1.49_windows_x64_unsigned-beta.msi · 86.0 MB · SHA-256 6f1df56ddcdba8fe6433c94852600cd2ad0ac4cfd8d57a42b907774476533eb0
This machine
Linux
UnsignedDebian packages and tarballs. Linux model serving has not been measured. Verify each file with its published digest.
poolparty_0.1.49_arm64.deb · 80.2 MB · SHA-256 3f5bb0588f6156c008d1fd17e550178eaeb069d4c4703c693535f87a92cba67d
atlas-agent_0.1.49_linux_aarch64.tar.gz · 13.1 MB · SHA-256 332383ab89a5078c1e18dfc262d25c896bc3eb836b93e32496dca804931c3699
poolparty_0.1.49_amd64.deb · 82.4 MB · SHA-256 baae9492ebeb49ca95db2b9c591e06e0cf4fb5d34847dded28f75706cc8a276d
atlas-agent_0.1.49_linux_x86_64.tar.gz · 14.1 MB · SHA-256 443e79b8df185f1d8640be6dd7373daf01cd20f37e079481c958067c3764cdba
Why Windows will warn you
The Windows build is not code-signed. When you run it, Windows will show a blue “Windows protected your PC” screen, and you will have to click More info and then Run anyway to continue. That warning is Windows telling you the truth: it does not know who made this file.
A code-signing certificate makes that message disappear. It does not make the software safer — it makes it attributable, and it costs money and identity paperwork we have not done yet. We would rather ship unsigned and explain it than delay, and rather explain it here than let you meet it alone.
So check the digest instead. It is the stronger check anyway: a signature tells you who published something, and a digest tells you that the bytes you have are exactly the bytes that were published. Signing this build is a decision we expect to take later, and this page will say so when it changes.
Verify download signatures and checksums
Every release publishes machine-readable provenance. Point something you trust at it.
- Choose your platform
- Get the published file
- Compare its SHA-256 digest
- Review signed metadata and the SBOM
Release files and verification records
- SHA-256 digests for every file.
- Signed release metadata, so the digest list itself cannot be swapped.
- An SBOM — the full list of what is inside the build.
- trust.json — all of the above in one machine-readable manifest.
Ask your AI to verify a download
Hand your assistant the manifest and the file you downloaded and ask it to confirm the digest matches, the metadata signature is valid, and the dependency list holds nothing it does not recognise. It takes seconds and you do not have to take our word for any of it.
The root digest, published here as a second channel — compare it with the one the
download origin serves before you pin it. Root version 1:
fcc10945e120d19d2745b6fb2c9dff8e18811cf11ef2f8ec1602417fbe526f85
Root version 1 is the first one, and it has never been rotated. The ceremony that rotates it is scheduled inside the beta’s first thirty days, and this page will carry the new digest beside the old when it happens.
The honest limit, because the framing above invites you to over-trust it. Integrity and provenance are verifiable: this file is byte-for-byte what was published, by us, on that date, containing those dependencies. Absence of malice is not certifiable from a binary — not by an AI, not by a scanner, not by anyone. What would go further is a source audit and open-sourcing the code. Those are real decisions we have not taken, and we are not going to let an agent-scan story stand in for them.
Software terms and privacy
The plain-words version. The licence is the operative document.
PoolParty runs work on your hardware. We have built it to be careful with your machine: it is designed to work only while the machine is idle and plugged in, unless you change that. It will not push past its thermal limit, and it stops the moment you touch the keyboard. Those limits are not preferences you have to find — the thermal one cannot be switched off at all.
We still cannot promise your hardware will never fail. Software that keeps a machine busy cannot guarantee the machine, and anyone who tells you otherwise is selling something. The software is provided as it is, and you run it at your own risk. The limits of our liability are set out in the licence, which is the document that actually governs this — this paragraph is here so you know what it says before you agree to it.
If something does go wrong, tell us: hello@poolpartyai.com. We would rather hear it than not.
Get started with your pool
Install PoolParty for local, account-free use. Your Pool browser controls are in development and will require account sign-in and device approval.