Simhive

this 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.

0machines online right now
~0iterations per second on real sims
0members
0iterations shared in 30 days
Get it

Download Simhive All releases

Windows x64 installer, Linux AppImage / deb. macOS later. The app updates itself. To use this pool you need an invite link from whoever runs it — it opens a page that gives you a token to paste into the app.

How it works

When you sim

Simhive runs Localbots on your PC — the same Quick Sim, Top Gear and Droptimizer you would run alone — 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.

When you don't

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.

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. Leave a worker running off-peak and your sims jump the queue at peak. Someone who never contributes still gets served, last.

What leaves your machine, and what runs on it

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.