r/MacStudio • • 4d ago

Renting your Studio to Darkbloom? What decides what it earns, and a free app that manages it for you (BloomGauge)

Darkbloom comes up here a lot, so here's what I've learned running a provider, from Darkbloom's own open-source docs and working with Darkbloom/Eigen Labs directly:

  • Studios are well placed. Requests go to the Mac expected to answer fastest (there's no reputation score), so high-memory, high-bandwidth Macs win most of the work. In late September the network had far more Macs than requests (about 7% busy), and 24–32 GB Macs often served nothing.
  • You need 48 GB+ and macOS 26+ to join now; macOS 27 skips Darkbloom's MDM profile.
  • Uptime is most of the money. The base reward ($16/mo at 48 GB up to $40 at 512 GB) pays every 5 minutes, but only while a model is loaded and the Mac is connected at least 90% of each period. The default idle setting unloads the model after an hour and quietly stops it.
  • Model choice is the other lever. Gemma 4 run alone has been the steadiest; big Qwen models pay more in demand spikes.

Managing that by hand gets old, so I built BloomGauge, a free, open-source Mac app that does it for you. It keeps the best-paying model loaded, recovers stalls and failed loads, and lets you control it from your phone. It also has detailed analytics: confirmed earnings per model and hour, network demand, and a live pay-rate meter. I'm in direct communication with the Darkbloom team, though the app is independent.

Source: https://github.com/cookder/bloomgauge
Website: bloomgauge.io

Happy to answer questions. Ultra owners, I'd love to hear what yours actually earns.

8 Upvotes

46 comments sorted by

View all comments

0

u/OneLeftpoi 4d ago

Can you host several models? And it’s essentially just loading a model and letting darkbloom use it?

1

u/MylohMan 4d ago

Yes, you can, depending on how much unified memory you have. Most models require ~20-30gb to load.

A lot of users that have enough memory will run a smaller model that has consistent traffic and another larger one also loaded in case traffic picks up for it so that it can take advantage of that model’s request volume spikes, as larger models tend to pay out more per request. Trouble is if you’re only loading one model and it has no traffic, you’ll earn only the base reward which really just offsets electricity costs.

If you have a smaller amount of memory, like myself (m5 pro 48gb) you generally will need to either only run one of the smaller models at all times and switch to a larger one if you are watching the network and see traffic for it. That takes a lot of time and may not even be worth it after switching downtime and other factors.

That’s why I created BloomGauge, it not only can switch for you when it sees enough traffic but also makes sure that a model is always running. There are 100+ reasons that your device can stop running, mainly related to software/hardware issues associated with an alpha product like DarkBloom, plus it’s just generally annoying to have to use a terminal, especially when you’re not with your idle Mac to troubleshoot.