bring the workload, keep everything else
Bring a game, a container or a model. We run it near the person using it and meter the session. You keep the surface, the users and the money.
walter.gg
a game is the hardest thing to place well
This frame was rendered on a consumer GPU in the player’s own city, with a person waiting on every frame.
three kinds of work, one network
Same machines, same placement, same session. What differs is what you hand us.
01
a game
Playable on your own surface or behind your brand. The game runs a few kilometres from the player.
publishers and platforms
the publisher route02
a container
Your stack, sealed. Placed near the user, run for the session, endpoint handed to your orchestrator.
platforms and server hosts
managed capacity03
a live conversation
Your voice models in one placed, metered session. Heavy turns go to the frontier model you choose.
voice teams
live voice sessionsone price logic, not one price list
Every kind of work is billed per session, and a session runs up to one hour. Heavier work sits in a higher class. Nothing is reserved, nothing idles on your bill.
- a game session
-
one player, one machine, up to an hour
from $0.04
to $0.24 in the top class
- a container session
-
one placed container, up to an hour
from $0.04
to $0.24 in the top class
- a voice session
-
one live conversation, up to an hour
from $0.04
to $0.24 in the top class
an on-demand GPU hour in a data centre costs about ~$2.00. a session here starts at $0.04.
bring the workload
Tell us what it is, where your users are and how much of it there is. We come back with what the network serves today and what it costs.
talk to us about your workloadwho is already asking
-
games
two Japanese AAA publishers and a tier-one European carrier, on the games route
-
containers
streaming platforms with their own front end, and a low-latency server host with machines to fill
-
voice
voice teams that own their models and want them near the speaker