Your machine helps when it's free — never when you need it.
When you connect a machine to OmnibusCloud, you decide how, when and how much it participates. Contributing idle power should never get in the way of your own work, gaming, studying or creating.
Control isn't a bonus feature here — it's the core of the model. Crowdcomputing only works if contributors can stop, limit and schedule participation as easily as they start it.
Works only when your machine is idle
OmnibusCloud is idle-first by design. Your machine helps when it's available, not when you're using it — turning unused capacity into useful computation without slowing down anything you're doing. The moment you sit down to work or play, contribution steps aside.
On your schedule
You decide when your machine is allowed to participate. Keep it to evenings, weekends or overnight; limit it to certain hours; or let it help whenever it's idle. Your machine, your hours.
Choose which machines help
Participation is per machine, not just per user. One machine, and it's simple. Several, and you choose exactly which ones contribute, and to what:
- your gaming PC supports a rendering project;
- your workstation helps a private group;
- your laptop stays out entirely;
- any machine can be paused without removing it from your account.
Pause or leave anytime
Pause a machine whenever you want your full power back, and leave a project at any time. Crowdcomputing is built on consent: if participation were hard to stop, the model would fail. A machine its owner can't control has no place in a trust-based network.
The conditions you set
Depending on your settings and the project, participation can be shaped by:
- idle state — only when the machine isn't in use;
- schedule — only during the hours you allow;
- machine selection — only the devices you choose;
- project membership — only the projects you've joined;
- pause status — off whenever you say so;
- power and performance — within limits that suit your setup, including power draw;
- workload requirements — work matched to what your machine can handle.
The exact controls may grow during the public beta, but the principle won't change: OmnibusCloud respects the owner of the machine first.
What if I need my machine?
It's always yours. Because participation is idle-aware, scheduled and pausable, your machine helps only when it can — and the moment you need it back, it's yours. You never have to choose between contributing and using your own computer.
On your terms
This page is about when and how your machine participates. For what runs on it — reviewed workloads, self-contained execution and open code — see Trust & safety →.
Contribute on your terms, and pause the moment you want to.
Let's build the ultracomputer together!