What we shipped.
What comes next.
We publish the roadmap because you deserve to know whether PlayServ is a real platform or a fundraising deck. This is the real shape of what we've built in the last year and what we're building in the next.
The essentials are running in production.
Foundations through to the first AI surface. Each item is live, documented, and used by studios today.
Changelog from my journey
Q2 2025
Q2 2025
Realtime Config & Feature Flags
Remote config, game-native segmentation, A/B tests. Push a value to every client in <50 ms. See Pulse →
Extensible data constructor
Typed schemas you can extend without migrations. Base of the dynamic admin UI that ships in Q1 2026. See Forge →
Q3 2025
Q3 2025
Cloud Functions — Unity magic mode
Write server code in your Unity project, annotated with [Server]. SDK splits, compiles, deploys. Zero DevOps. See Lambda →
Authentication
Multi-provider auth: Steam, PSN, Xbox, Google, Apple, email, guest. JWT, rate limits, account linking. Cross-save layer follows in 2026.
Inter-module message bus
The reactive spine. Every module emits, every module subscribes. Inter-client messaging rides on the same bus.
Q4 2025
Q4 2025
Declarative multiplayer for Unity
[Sync] on a field — authoritative server, RUDP, matchmaking handled. No netcode engineer required. See Sync →
Unreal slice on Lambda runtime
Authoritative Unreal server compiled to a ~30 MB cloud function, not a 2 GB container. Multi-region scale without DevOps. See the highlight above.
Observability foundations
Per-project environments, deploy history, structured logs. The boring layer that makes the flashy layer debuggable.
Q1 2026
Q1 2026
First AI surface — read and write
Claude and other MCP clients read Pulse configs, Lens dashboards, Seasons timelines — and can already create and populate typed data models through Forge schemas. Push a flag, draft an event, scaffold a leaderboard from chat.
With PlayServ you can build practically any game.
Realtime config. Authoritative server logic. Multiplayer on Unity andUnreal — the Unreal server as a 30 MB slice on our execution engine, not a 2 GB container. Extensible typed data model. Auth for every major platform. A reactive message bus wiring it all together. And MCP read + write — AI clients already scaffold data models, push configs, and draft events on your project.
The essentials are shipped and running in production. What's next is polish of the flagship Canvas and LiveOps surfaces, then the modules that unlock monetisation, hosting, and MMO-scale.
Flagship polish — and the first AI surface.
Beta with early studios. Each item ships to GA as the rough edges come off.
Changelog from my journey
Q2 2026
Q2 2026
Visual Backend — flagship
Core loop works. Closed beta with early studios — polishing UX, node inspector, versioning. See Canvas →
LiveOps timeline
Drag-and-drop event planner. Cascades into Pulse, Lambda, Lens. In beta — GA once template library stabilises. See Seasons →
Browser multiplayer
Same [Sync] API, WebRTC transport when UDP is blocked. Transport path works — still stabilising NAT traversal across providers.
Dynamic admin UI
Auto-generated CRUD for every typed schema. Add a field → admin grows a column, a filter, a form. Stabilising this quarter.
Basic analytics
Event ingestion, retention cohorts, revenue cards, export to Amplitude / BigQuery. See Lens →
Payments, hosting, MMO worlds, consoles.
The next four quarters. Dates are targets, not promises — see Q2 2026 for what's actively shipping.
Changelog from my journey
Q2 — Q3 2026
Q2 — Q3 2026
Hathora migration sprint
Docker-compatible migration path, dedicated support team. Hathora closed May 5, 2026 — we're moving studios in days, not months. Migration →
Cross-module correlations
Which config → which retention. Which event → which revenue. The dashboards Amplitude can't compute.
Q3 2026
Q3 2026
Payments & IAP
Server-side receipt validation for Apple, Google, Steam. Fraud filters, refund panel, one API for three stores. See Vault →
Unreal magic mode
Annotate Unreal C++ with UCLASS(Server). SDK extracts, compiles, ships the slice. Unity magic, Unreal edition.
Bare metal + matchmaking
Dedicated hosting, cloud burst at peaks, skill-/party-aware matchmaker. Two initial regions at launch, two more by year-end. See Edge →
Q4 2026
Q4 2026
Economy engine
Store, inventory, currencies, gacha, auctions. Server-authoritative, Vault-integrated, schedulable from Seasons. See Market →
Anti-cheat — server + ML
Free-by-architecture server authority plus ML deviation detection. EAC / BattlEye verdicts land on EE as events. See Shield →
Cross-save + cross-platform glue
Progress that follows the player. Conflict resolution a player can actually read. PS5 ↔ Xbox ↔ Mobile. See Passport →
Q1 2027
Q1 2027
Marketplace soft launch
Free templates for every module, curated by us. Premium publishing opens once 50+ free templates exist. See Marketplace →
Seamless world stitching
For MMO / open-world games. Zone ownership, distributed entities at boundaries, PlayServ stitches what Unreal / Unity renders.
AI draws pipelines
"Build me a battle royale with 60 players and a season pass." AI composes a Canvas from Marketplace templates and your Forge schemas.
Replay audit + client AC fusion
Deterministic server-side replays. Review why a player was flagged, frame by frame.
Q2 2027
Q2 2027
PS5, Xbox, Switch certification
First-party SDKs, cert pipelines, platform-specific Passport providers wired up. Bring your game to all three.
Godot first-class
Godot as a third engine alongside Unity and Unreal. Same Sync, Lambda, Forge story.
Private cloud deployments
Dedicated infra, dedicated TAM, SLA tier above 99.9%. For the studios that need compliance, not just uptime.
Want visibility on something specific?
If a module in Ahead is a blocker for your project, tell us. Prioritisation moves when real teams raise real hands.