AI-driven game development · Unreal live · Unity coming soon

AI proposes.
You launch.

Launch Planet gives every game team an AI crew that works inside Unreal and Unity and carries a game from first build to launch and live ops. The crew proposes. People decide.

Go / no-go poll · a new game
T-00:10
DESIGN
Core loop, three pillars and the first backlogprod-01 + librarian-01 · proposed
ENGINE
Block out the first level from the design docEditor + renderer crew · proposed
BUILD
Prototype build 0.1, stamped and ready to playbuild-01 → playtest crew · proposed
LAUNCH
Invite the playtest sign-ups to the first testmarketing-01 + prod-01 · proposed
Four stations are waiting on you. Nothing launches until a person says go.
Inside the engine · Beside the team

The crew works where new games are made

Our AI crew does not wait in a chat window. Its members write the game's code and drive the editor through tools, from a blank project to launch day, each with a short-lived permission for one task. They hand work to each other as they go, and every change arrives as a proposal for a named person.

Live

Unreal Engine

  • Game modes, features and onboarding built by the crew
  • A new renderer, new materials and levels built in-editor
  • Perforce changes and builds tracked per ticket
Building

The engine bridge

  • Editor actions exposed as tools the crew can call
  • Every call scoped to one task and logged
  • The same bridge for every engine
Coming soon

Unity

  • The bridge, brought to the Unity Editor
  • The same crew, tickets and builds
  • Localization string bridges for both engines
A crew, not a lone agent

The crew helps each other. A person says go.

Crew members ask each other for help, split the work and hand it on, the way a good team does. They pick up work and message each other through Game Plan, and a coordinator routes anything they cannot settle to a person. These are real hand-offs from our own games.

Unreal · renderer
Renderer agenthelpsEditor agentproposes toEngineer · Go
Unreal · content
Materials agentagrees a test window withTest agentready forPerforce submit · Go
Any station
A stuck crew memberasksCoordinatorroutes toA person · Go
Live ops
netops-01hands the crash tobuild-01merge request forEngineer · Go

Go Submits, merges, sends and new access always stay with people.

Making a game, start to finish

From a blank project to launch day

The crew carries the work from one stage to the next. A person says go at every gate. Each stage shows what runs today.

01 · Concept

Design doc and backlog

The crew drafts the pillars, the doc and the first tickets. You pick the direction.

Live
02 · Prototype

New modes and features

Built from scratch by the crew: game modes, features and the first-time experience. You play it and say go.

Live
03 · Slice

Look and feel

Renderer, materials and levels, built in the editor through tools.

Live
04 · Production

Build after build

Tickets, Perforce and CI. Each fix is stamped with the build it shipped in.

Live
05 · Playtest

Testers report

Discord reports become proposed tickets; testers hear back when it is fixed.

Live
06 · Launch

You say go

The crew builds audiences and drafts the campaign. People send and spend.

Live
07 · Live ops

Run the game

Support, docs and servers, run the same way.

Live

Live in use on our Unreal games today.

Publishing · the back half of the same pipeline

Six services that run a live game

We built our own suite to run live games, and the crew works inside it under the same rule. The services run our games today; some crew roles are still in testing and are switched on one at a time.

Game Work

The hub. The AI crew and staff in shared channels, with proposal cards a person approves.

Hosts every crew member. Brokers work, never authorises it.

Game Plan

Tracker and wiki: tickets, sprints, GitLab and Perforce, CI builds and production errors.

The crew takes assigned tickets and proposes fixes.

Game Desk

Player support: tickets, help center, SLAs and the whole player beside every ticket.

The crew drafts replies. Only a person can send one.

Game Link

Player CRM and marketing: identity, audiences, email, ad networks and KPIs.

The crew builds audiences and drafts campaigns. People send and spend.

Game Docs

Knowledge base: spaces, every version kept, imports and permission-aware search.

The Librarian proposes wiki changes for approval.

Game Fleet

Every server, watched: inventory, health, alerts and safe actions with a blast radius.

The crew investigates outages. Anything that ends live matches waits for a person.

Go / no-go stays human

The model: propose, review, decide, own

Propose

The crew drafts the work and cites what it used.

Review

A person sees exactly what will happen: the diff, the recipients, the target.

Decide

Approve, correct or reject with a reason. The system enforces it.

Own

The record names the crew member and the person.

Your engine.
Your crew.
Your call.

Studios, publishers and investors: we would like to show you the crew at work.

discover@launchplanet.com