Jobs don't restart
Failover with checkpoints.
On most clouds a failed instance means starting over. On OpenGPU, live health checks detect a failing node and shift the job to the next best GPU, resuming from the last checkpoint without paying twice.
How it works
Every job is matched to the best available GPU in under two seconds, runs in an isolated container and is verified before payment.
The routing layer
No manual provider selection. No marketplace decisions. The router weighs signals from the network and from each workload.
What every node can do right now.
+
What each job needs to succeed.
=
The best balance of speed, reliability and cost, chosen in under two seconds.
Lifecycle of a task
01
Via Relay (card or invoice billing) or the Client App, with GPU type, VRAM, model and runtime constraints.
Client
02
The router evaluates every GPU that meets the requirements and picks the optimal path.
Network
03
The task runs in an isolated container with real-time logs and health checks.
Provider
04
Cryptographic checks before acceptance; multi-provider consensus for critical tasks.
Protocol
05
The client pays for the result, the provider is paid, and the full record is kept.
Network
OpenGPU Protocol
The OpenGPU Protocol manages every interaction between clients and providers on a decentralized network, with no central operator deciding who gets the work.
Clients publish containerized execution models, called sources, with code, dependencies and parameters. Sources are reusable definitions for future tasks.
Clients submit tasks that reference a source, with execution parameters, input data and the price for the work.
Providers register to sources that match their GPU capabilities and profitability goals, forming specialized pools per workload and GPU type.
Providers compete to deliver the first valid output. This drives fair pricing, short execution times and higher quality through computation consensus.
High-demand tasks draw more providers to the right pools.
Pricing adjusts automatically to network conditions.
Operators tune hardware to maximize returns, improving the network for everyone.
Security & reliability
Every result undergoes cryptographic checks before acceptance.
Accuracy and reliability are tracked over time and feed into routing.
Isolated, hardened execution with no persistent data storage for tasks.
For critical tasks, multiple providers execute and results are compared.
Jobs don't restart
On most clouds a failed instance means starting over. On OpenGPU, live health checks detect a failing node and shift the job to the next best GPU, resuming from the last checkpoint without paying twice.
No single point of failure
Independent providers, OpenGPU-operated datacenters and cloud overflow mean no single facility can take the network down. If one region is under pressure, new jobs simply land elsewhere.
Submit a task, or follow the network live in the Management App.