AurelacStudio

Studio Console · Early access · Godot 4

The production console we built to ship our own Godot game.

Writers, translators, artists and producers do their work in a browser. Changes to game content come back to your developer as reviewable git commits — nothing merges without them.

Board view: sprint columns with tasks, type and priority chips (illustrative)

01The problem

Game data lives in Godot-native formats that only open in the editor.

So every content change waits on someone who knows Godot.

02How it works

  1. 01

    Staff edit in the browser.

    Writers, translators, artists and producers.

  2. 02

    Changes stay off the main game until submitted.

    Work in progress never lands on main. Scene work and code stay in the Godot editor, where they belong.

  3. 03

    Your developer reviews and merges.

    Submit for review hands the change over as a pull request in your repo. Plain diffs, your call.

03What it does today

Plan the production

Board

Kanban with epics › tasks › sub-tasks.

  • Sprints, phases, timeline (Gantt)
  • Velocity report, per-person workload
  • Studio working-day calendar

Access

One sign-in for everything.

  • Five roles, viewer to admin
  • Per-discipline grants

Write the game

Write the game (illustrative)

Bible

Nested wiki for the game's design bible.

  • Version history, per-line status chips
  • Glossary with auto-underlined terms
  • Decision log, print to PDF

Dialogue

Branching-conversation graph.

  • Edit lines and responses without opening Godot

Translation

Line table.

  • Per-line confirm
  • Staleness tracking

References

Documents, node-graph flowcharts, Miro boards and links in one rail.

  • Flowcharts embed inside documents

Make and check the content

Make and check the content (illustrative)

Assets

Production tracker with deliver-for-review.

  • Multi-stage approval chains
  • Layered room preview with blend modes
  • Clip Studio .clip upload
  • One-click placeholder room scaffold

Story

Whole-game reachability map.

  • Unreachable endings
  • Orphaned flags
  • Dead jumps

Puzzle

Drag to reposition puzzle nodes.

  • Positions reach the game without a scene edit

Ask and move around

Ask and move around (illustrative)

Assistant

Telegram bot and in-app chat drawer.

  • Ask about tasks in plain language
  • Create and edit tasks with a preview-then-confirm step
  • Daily digests, voice notes

Everyday

⌘K command bar across every view.

  • Activity feed for studio leads
  • Recoverable delete
  • Several colour skins, phone layout
Bible: page tree, line status chips, decision log (illustrative)
Story reachability map flagging an unreachable ending, an orphaned flag and a dead jump (illustrative)

04Who it's for

Small Godot teams, about 6–12 people, with non-engineer staff.

Writers, translators, artists and producers — plus one dev who runs builds.

  • Godot 4 only.No Unity or Unreal support.
  • Not a Godot replacement.Scenes and code still happen in the editor.
  • Your own private instance.One Console per studio. Your data is never mixed with another team's.
  • Early access.Now opening to other Godot studios.

Built for and used on Those Returning.

See the game

05Early access

Join the early-access waitlist.