How it works
From account to launched game in six steps
StudioHQ is designed so a first-time developer can follow a guided path, while an experienced studio can shape every part of the workflow.
- 1
Create a studio or a solo workspace
Start as an independent developer or set up a studio with members, roles and permissions. You can belong to as many studios as you need.
- 2
Select a development template
Pick your genre, then choose a blank project, a guided project, or a published studio template. Guided projects come with phases, checklists, milestones and a starter design document.
- 3
Customise the game development plan
Remove, reorder or add checklist items and phases. Your plan becomes real records in the database, not suggested text, and you can change it whenever your production method changes.
- 4
Invite collaborators
Invite programmers, artists, animators and testers with the exact access level they need. Contractors see only what you assign them.
- 5
Assign tasks and track milestones
Turn checklist items and storyboard scenes into tasks, assign owners and due dates, review submitted work and watch phase progress update itself.
- 6
Launch and manage the game
Complete the launch readiness checklist, record sign-offs, publish a release with notes, then track your game with update planning, community work and recorded analytics.
Guided for beginners
Genre templates, recommended checklists and helpful empty states tell you what to do next without overwhelming you.
Granular for studios
Custom roles, per-project module toggles, published templates and permission checks enforced on the server, not just hidden in the UI.
Everything links up
A bug can link to a task, a task can link to a storyboard scene, and a scene can link back to its document section.