Skip to content

How it works

How the OpenGPU Network 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

Every job, matched to the best GPU at that moment.

No manual provider selection. No marketplace decisions. The router weighs signals from the network and from each workload.

Network signals

What every node can do right now.

  • GPU class
  • VRAM
  • latency
  • utilization
  • health
  • reputation

+

Workload signals

What each job needs to succeed.

  • model type
  • memory
  • duration
  • budget
  • priority

=

Optimal placement

The best balance of speed, reliability and cost, chosen in under two seconds.

  • <2s routing
  • auto failover

Lifecycle of a task

Submit. Route. Execute. Verify. Settle.

  1. 01

    Submit

    Via Relay (card or invoice billing) or the Client App, with GPU type, VRAM, model and runtime constraints.

    Client

  2. 02

    Route

    The router evaluates every GPU that meets the requirements and picks the optimal path.

    Network

  3. 03

    Execute

    The task runs in an isolated container with real-time logs and health checks.

    Provider

  4. 04

    Verify

    Cryptographic checks before acceptance; multi-provider consensus for critical tasks.

    Protocol

  5. 05

    Settle

    The client pays for the result, the provider is paid, and the full record is kept.

    Network

OpenGPU Protocol

A self-regulating marketplace for compute.

The OpenGPU Protocol manages every interaction between clients and providers on a decentralized network, with no central operator deciding who gets the work.

  1. 01

    Source publication

    Clients publish containerized execution models, called sources, with code, dependencies and parameters. Sources are reusable definitions for future tasks.

  2. 02

    Task submission

    Clients submit tasks that reference a source, with execution parameters, input data and the price for the work.

  3. 03

    Provider registration

    Providers register to sources that match their GPU capabilities and profitability goals, forming specialized pools per workload and GPU type.

  4. 04

    Competitive execution

    Providers compete to deliver the first valid output. This drives fair pricing, short execution times and higher quality through computation consensus.

  • Demand attracts supply

    High-demand tasks draw more providers to the right pools.

  • Prices find their level

    Pricing adjusts automatically to network conditions.

  • Providers optimize

    Operators tune hardware to maximize returns, improving the network for everyone.

Security & reliability

Trust the math, not the vendor.

  • Task verification

    Every result undergoes cryptographic checks before acceptance.

  • Provider reputation

    Accuracy and reliability are tracked over time and feed into routing.

  • Secure containers

    Isolated, hardened execution with no persistent data storage for tasks.

  • Computation consensus

    For critical tasks, multiple providers execute and results are compared.

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.

No single point of failure

No single region can take it down.

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.

See it run on real workloads.

Submit a task, or follow the network live in the Management App.

What do you want to do?