Trust and runtime

New indie games need clear runtime boundaries.

RetiPie Zone serves uploaded games inside an isolated play surface. The platform injects its bridge, enforces security headers, and keeps external tracking integrations out of creator bundles.

Creators, players, and technical reviewers

Zone, RetiPie’s game runtime, serves every HTML5 game inside an isolated surface with strict security headers and signed access.

The upload pipeline scans HTML and JavaScript for external tracking scripts so creator bundles stay focused on gameplay.

Isolation cuts both ways: games cannot reach into player data, and nothing outside the sandbox can interfere with a running game.

The RetiPie SDK communicates platform events through a controlled bridge rather than asking each creator to wire external runtime code.

Players get one consistent promise across the feed: every game, from every creator, starts inside the same boundaries with the same rules.

That trust works for creators too — players open unknown games without hesitation, which is exactly what a new release needs.

Keep learning

Move through the practical RetiPie Learn path without jumping straight into API reference.

SDK bridge

Understand the public runtime surface exposed to creators.

Runtime capture

Learn why first-screen rendering matters for mobile presentation.

Instant play

See how sandboxing supports no-download game discovery.

Technical docs

When you are ready to implement, move from the Learn narrative into the exact RetiPie docs.

Game requirements

Review file limits, accepted assets, sandbox rules, and runtime constraints.

Uploading games

Package HTML or ZIP releases with the structure RetiPie expects.