We're already at work.
Here's the map so far.
Not two products — a roadmap. Every opportunity we've heard, rated for viability, with the first build already named. The rest of the board fills in as we sit with more teams.
The starting point.
AI at Riot won't live in one room. It starts where the pain is clearest — with Broadcast — and expands from there as the vision proves itself.
Already live on this site — a working intelligence engine built from the Sao Paulo event's first scrape across Reddit, YouTube, Twitch, VLR and Kick. Preliminary findings, real data.
In the Broadcast conversations, we surfaced the need for a single morning read that tells Broadcast what content performed, where, and why — so the team stops chasing dashboards and starts the day aligned. It lands inside God's Eye.
In the same conversations, we mapped a faster path from rushes to audience-ready cuts: auto-tagging at ingest, then an assembly engine that turns tagged moments into trailers and social cuts.
Staging, load-in and resource forecasting. Heard second-hand — we haven't seen how planning actually happens.
Creator and summit content. One gathering, hundreds of local moments — but we haven't met the team that owns it.
The internal automations nobody demos. Your engineers would rank these better than we can.
Every opportunity, rated for viability.
Value against effort, dot size for confidence. Click any dot to see the discovery notes — what we already have, what we'd have to build, and the unknowns the next session would settle.
A working ingestion and narrative engine with live preliminary findings, plus Broadcast's requirements captured first-hand: real-time event mode, creator and co-streamer chat pairing, regional language views.
An eight-week launch: scale the source set, real-time event mode, co-streamer chat pairing, editorial controls, and a live event pilot tuned with the Broadcast team.
The final source list, which co-streamers make the first roster, and how findings slot into the morning-of routine. The event pilot settles this.
Two rows carry scores because those are the conversations we've actually had. The rest of the map stays unscored on purpose — sitting with those teams is what turns this from our ranking into Riot's.
You told us what matters.
Six things came up again and again with Broadcast leadership. Each now has a named home — not a promise, a plan.
A live pulse the production team can act on mid-event, while it still changes the show.
What everyone is talking about, where it came from, and the top creator posts from the last twelve to sixteen hours.
What a streamer says, paired with how chat reacts — calibrated on one co-streamer first.
Broadcast runs in over a dozen languages; regional teams see the heat in their own region.
Separate competitive narrative from general game talk — and package the game-side findings for the game team.
“We posted a player feature that day” sitting next to the spike it created.
One build now.
We can build this — in fact, it's already running. The engine is live on real data today, naming the week's biggest Valorant stories with traceable sources. The launch turns it into Riot's system: more sources, real-time event mode, co-streamer chat pairing, editorial controls, and a pilot inside a real event. Every other opportunity on this map stands on the data layer it creates.
- — A working system today, not a mockup
- — Scoped and priced from live evidence
- — The data layer the rest of the roadmap stands on
One engagement, one output: a working God's Eye system in your hands. You decide what happens next with it.
Where we're confident, and where we're not.
God's Eye is already running on real data, and it's the build we're naming first. Its findings are a first read — the event pilot is what hardens them. Trailer Studio is mapped and rated, but priced only from evidence we gather during the God's Eye build.
Physical production, community & events, engineering ops. We've heard they matter; we haven't sat with those teams, so we're not going to pretend a number.
Discovery meetings put real divisions on the board. Each session turns a placeholder into a scored row — our ranking becomes Riot's.