Simhive · pool
Your sims on everyone's machines, your machine for everyone's sims. A shared pool of computers that run World of Warcraft gear simulations for each other. Install one app, paste an invite, and your Droptimizer runs on the whole pool in seconds — while your PC sims for the others when you are not using it.
Download Simhive Get a token Sim from the browser Install & join guide All releases
Windows x64 installer, Linux AppImage / deb. macOS later. The app updates itself. Everyone is welcome: pick a name, get a token — in the app ("Get a token" in its settings) or on the join page — and use it on every machine you own.
How it works
Simhive is the same Quick Sim, Top Gear and Droptimizer you would run alone on your PC — but the work is sent to this pool, split into small batches across every machine online, and the numbers come back to your screen. Your history stays on your disk.
Your PC takes batches for other members: SimulationCraft on plain text input, one sim at a time, using the threads you allow. It pauses by itself while World of Warcraft is running, and you can pause or quit from the tray any time. Paused means nothing of anyone else's runs here — your own sims still use this machine, on one thread, so they never wait for you.
What is fair
Nobody is refused. When the pool is busy — raid night, everyone simming at once — batches go to members in proportion to what they contributed over the last 30 days, measured in simulation iterations delivered (of a five-minute fight — longer fights count proportionally). Leave a worker running off-peak and your sims jump the queue at peak. Someone who never contributes still gets served, last. The board shows who keeps the pool running.
What leaves your machine, and what runs on it
- Sent to the pool: gear, talents, spec and the fight settings of the character you sim — never the character's name or realm. That is what is on the public Armory anyway.
- Run on your PC for others: SimulationCraft, downloaded by the app from a public build channel at the exact commit this pool runs, checksum verified — never from the pool. The input is text and is checked first: anything that names a file or the network is refused before simc sees it.
- Checked both ways: every machine is probed with a known batch when it connects, and a share of its live work is quietly re-simmed on a trusted machine. Wrong numbers get a worker benched, not into your report.
Questions
Does it cost anything? No. There is nothing to buy; the currency is compute, and you bring your own.
Do I have to leave my PC on? No. It just makes your own sims faster at peak. Contributing while you play is off by default (the game is detected).
Which SimulationCraft build? The pool pins one commit for everyone, moved nightly. All machines run the same build, so a Droptimizer split across ten machines gives one consistent answer.
Can the pool operator control my PC? Only what you allow: threads, pause and the name it shows under — and only if your app's policy lets the pool do so (default: only a pool that issued your token as one of its own machines; members' machines are theirs alone). Never the pool it connects to or its token.
I have a server or a headless box. There is a Docker worker that lends cores without the interface; the invite page shows the two commands.