This morning, I sat at a coffee shop with a buddy who's building an indie game. He sighed, "Man, I spent six months on a reward system, still don't know who to reward." I showed him the Stacked article, pointed to "SDK integration under one day." He went quiet. "One day? For real?"
March 27, 2026, Pixels opened Stacked's SDK to third‑party studios. No beta or whitepaper. Just real infrastructure that had processed 200 million rewards and driven over $25 million in revenue. Four whole years to reach that moment.
It runs simply: a studio plugs in a REST API, defines rewardable events, funds a pool, and watches a dashboard showing live spend vs revenue. The AI economist analyzes cohorts, spots churn patterns, proposes reward experiments on its own. No data scientist or custom anti‑fraud system needed. Everything ships inside the SDK. One reactivation campaign targeting players inactive over 30 days delivered 131% ROI. Not a forecast, internal production numbers.
I call it Pivot from Token to Tool. No longer "buy Pixels because the game will grow," but "use Stacked because it solves retention for any game." Value no longer ties to a single title.
But I see a clear weak spot. Once the SDK opens, Pixels risks becoming an ad network for lousy games. A studio hops in, integrates, grabs emission, farms, exits. The ecosystem gets diluted by games never meant to last. Stacked filters bots, not bad studios.
My suggestion: apply the same RORS benchmark to partner studios. Any studio using the SDK must hit minimum RORS within six months or lose emission access. Use the proven mechanism to protect the ecosystem from exploiters.
Stacked isn't Pixels' new product. Game is just the first use case. But when the SDK door opens to everyone, will Pixels keep its quality, or become a bazaar any game can walk into?