earn with your PCbring a workload
workloads · containers

your stack, near your users, for the session

You keep your orchestrator, your protocol and your product. When it needs a GPU near a person, it asks ours. We place your container in range and meter the session.

bring your container how a session runs

a rental sells you a machine. this sells you the session.

a GPU rental

  • you reserve capacity in advance and estimate your peaks
  • the region you booked, and the user is wherever they are
  • the hour is billed whether anybody used it

this network

  • capacity on demand, shared across every project on the network
  • the machine is chosen for the person, by region or by their address
  • a session is billed when it ends, and nothing idles on your bill
  • your own servers can join the pool and earn when they are idle

your orchestrator asks ours

One interface, two ways in. A platform with its own orchestrator calls us when it lacks capacity. A platform without one hands us the distribution and gets the same four steps.

  1. ask Your orchestrator, or your launcher, asks ours for capacity: which container, and where the person using it is, as a region or as their address.
  2. place We pick a compatible node in range of that person and start your container on it. Nothing is opened, nothing is injected unless you ask for our streamer.
  3. run The session runs on that machine for up to an hour. Your endpoint, your protocol, your users. A longer use becomes a new session.
  4. settle The session is metered and settled when it ends. The operator whose machine served it is paid from the same fee. No reservation, no idle hours.

what runs, and where

what runs
your container, sealed, on a dedicated node for the session; nothing of yours is opened
where
chosen for the person, by region or by their address, so sovereignty is a placement rule and not a data-centre contract
how long
a session runs up to one hour and a longer use rolls into a new one; you pay for sessions, never for idle hours
access
no shell into the host for you, and no other workload beside yours for the session
your machines
your own servers join the pool under our orchestration, keep their sovereignty claim, and earn from other sessions when idle
overshoot
when a launch overshoots, commercial cloud stands behind the mesh so nobody is turned away; it can be written into the agreement

per session, like everything else here

A container session follows the same compute classes as a game session. Tell us what it needs from a GPU and where your users are, and we quote it in a day.

a container session

from $0.04

per session, up to one hour, to $0.24 in the top compute class

orchestration only

quoted with your fleet

when your own machines join the pool

how every session here is priced

bring the container

Tell us what it runs, what it needs from a GPU, and where your users are. We come back with where the network can place it today and what a session costs.

talk to us about capacity

who is already asking

  • a streaming platform

    runs its own front end on commercial cloud today and wants a GPU nearer its players

  • a platform with its own orchestrator

    wants this network as one vendor beside the hyperscalers it already uses

  • a low-latency server host

    has machines and wants the orchestration in front of them