Orio customer stories: The studios letting players build.

Results measured on the studio's own baseline, not ours.

RYZOM

Their game. Their engine. Their baseline.

An established community, a fixed content calendar, and a familiar slide in daily players between drops. Orio ran on their own build for a full season.

+20%

D30 retention

+35%

Daily active players

95%

Cleared automatically

Floating castle islands in a player-built game world

Week 0

Scope and baseline

We agree the metrics before anything is installed.

Week 1

SDK integration

About a day of one engineer's time, on a private build.

Weeks 2–3

Internal build

The studio team creates and reviews before players see it.

Weeks 4+

Players in

Rolled out to the community, measured against the baseline.

RYZOM

How Ryzom held daily players flat between seasons

A live title, a fixed calendar, and +35% DAU across the trough.

Desert canyon world with a platforming course

ROGUE

Reopening creation on a shelved platformer

206 player-made levels in a quarter with no new production.

Neon sci-fi arena level with a sword-wielding character

XONOTIC

Letting players build without loosening the rules

Progression and economy locked; 95% cleared verification.

Questions about pilots

How are results measured?

On each studio's own baseline, not ours. The metrics are agreed before anything is installed, and results are measured against that baseline once players are in.

How does a pilot run?

Week 0 sets the scope and baseline. In week 1 the SDK goes in — about a day of one engineer's time, on a private build. In weeks 2–3 the studio team creates and reviews before players see anything. From week 4 players are in, and results are measured against the baseline.