For cloud gaming platforms

Cloud gaming's last barrier isn't bandwidth. It's a parent.

The hardware problem is solved. Any screen can run any game now. The reason a household still doesn't subscribe is that somebody has to decide whether a child should be in a lobby with strangers, and the honest answer today is a settings page. We supervise the session instead, and it works on any cloud.

GuardianGamer builds parent-side AI supervision. Live on iOS, running supervised sessions across four clouds.

Running today across Xbox Cloud Gaming GeForce Now Amazon Luna Our own cloud, for Roblox
The barrier

Every cloud is built for one adult with one account.

The moment a child is the player and a parent is the payer, the model stops describing reality.

01 · The veto

The refusal never reaches your funnel.

A parent who decides against it doesn't churn, doesn't complain, and doesn't appear in your data. The household segment looks small because the decision happens before signup.

02 · The catalogue problem

Per-title safety never finishes.

A safety feature built into one game has to be rebuilt for the next, and again for everything you licence next quarter. Breadth is your advantage and it works against you here.

03 · The compliance answer

Under-13 becomes a risk to minimise.

Age assurance, consent, data handling and duty of care are real costs. Most platforms answer by quietly not serving children, which means not serving the households they live in.

The layer

Supervision that wraps the session, not the game.

No game modifications, no SDK for studios to adopt, no change to your streaming path. That single design decision is what makes it cover an entire catalogue at once.

  1. 1
    The parent sets the terms once.One daily time budget across every game and platform, a list of approved friends, and a chat level. Set in our app, not in yours.
  2. 2
    The session runs on your cloud.Your infrastructure, your catalogue, your streaming stack. Nothing changes for the player except who can reach them.
  3. 3
    We supervise around it.Platform voice chat is disabled. Our own voice channel carries approved friends only, so the social reason to play survives. The clock is enforced our side, not on the device.
  4. 4
    The parent gets evidence.A session summary and a highlight reel rather than a log file. This is the part that converts a hesitant parent into a subscribing household.

The integration point is the session. That's the whole idea.

Because supervision sits outside the game, it doesn't care what the game is, who published it, or whether you licensed it this morning. It covers hundreds of titles on day one and every title you add afterwards.

It also means the work doesn't land on your engineering roadmap as a platform rebuild. We already run this pattern across three third-party clouds plus our own.

What changes, and what doesn't

You keep the player. We handle the parent.

The division of labour that makes this workable for a platform team.

AreaStays yoursBecomes ours
The streamRendering, latency, catalogue, storefront, the entire player experience.Nothing. We don't touch the rendering path.
The child's accountTheir progress, purchases, saves and library stay with you.Nothing moves. Families keep their own platform accounts.
The parent relationshipBilling, if you want a family tier of your own.The app, the summaries, the approvals, the support burden.
Chat and contactYour existing systems, untouched for adult accounts.Closed by default for supervised sessions, reopened only to approved friends.
Child-safety surfaceYour existing obligations as a platform.The supervision evidence: who they played with, for how long, and what was worth flagging.

Every provider is competing on catalogue, latency and price. Nobody is competing for the parent.

Those first three are expensive to win and quickly matched. Parent trust is neither: it's slow to build, hard to copy, and it decides whether the household subscribes at all. It's the open flank in this market.

How we'd start

A cohort, not a launch.

Bounded, measurable, and reversible. No brand exposure until you want it.

Phase 1

A defined group of households.

Supervision enabled for a cohort of family accounts on your service. No public announcement, no commitment beyond the pilot.

Phase 2

Measure the parent, not the player.

Trial conversion, household retention, and whether a supervised account holds a subscription longer than an unsupervised one.

Phase 3

Decide on evidence.

If it holds, it becomes a family tier. If it doesn't, you've spent a quarter and learned something concrete about a segment you aren't currently serving.

Worth an hour?

We'll bring what we've learned running supervised sessions across four clouds, including the parts that were harder than we expected.