Start with a project
Game Assembling
An Assembler prototype workflow that assembles a game project from modular, pre-built templates.
The main product of Starward Platform
Starward Assembler.
Bring your game together.
A game-development workspace built around existing coding agents. Bring your idea, implementation, tests, and play feedback into one reviewable workflow, with people guiding what the game becomes.
In development. Initial new-game pilots are invitation-only.
Recorded Assembler demos
See Assembler at work.
Explore prototype workflows for assembling a game, adding a feature, generating tests, reviewing play sessions, and inspecting AI usage.
These recordings show prototype workflows. Assembler is in development; access is invitation-only.
AI Game Feature Generation
An AI agent adds a game feature—random enemy bullets—from a natural-language request.
AI Generate Test
A QA-agent workflow for generating and running game test scripts in the engine.
Recording & Replay
A walkthrough of recorded play sessions and native replay for reviewing game behavior.
LLM Usage Audit
A dashboard walkthrough showing AI interactions and token usage for a generated session.
A loop, not a single prompt
From an idea to the next better version.
Start with a small, clear scope. Use agents for implementation and tests, then review the results before a build reaches invited players.
- 01
Idea & rules
Define the game, its rules, and what a good result should do.
- 02
Build
Turn an agreed scope into a working change with AI agents.
- 03
Verify
Check behavior and review the evidence before moving on.
- 04
Play
Put a reviewed build in the hands of invited players.
- 05
Observe
Connect player experiences to what actually happened in the game.
- 06
Improve
Use what you learn to choose and verify the next change.
Our first milestone: a verified build for invited players. People review the work and decide when to release.
The pieces behind the work
Shared context. Visible results.
A place for decisions
Assembler connects goals, changes, results, and review. Existing coding agents do the implementation work; the workbench helps people follow it.
Foundations for the game
Starward Game Services and its Client SDK provide reusable backend and client foundations. Game code and contracts retain their own responsibilities.
A way to check behavior
Game Control, Registry, and QA tools make intended behavior and verification evidence inspectable. Coverage, executed results, and release decisions each tell a different part of the story.
Runtime tracking connects a player's experience to what happened in the running game. That evidence can inform investigation, a new test, or the next fix. We're still learning which parts reduce uncertainty without adding unnecessary work.
Hengstar's own SGS development and Panda integration provide a practical test setting. A general creator workflow still needs validation with new projects. Semantic game commands also do not exercise every screen, input path, or player journey.
Where this is going
Start with a build. Grow toward the whole lifecycle.
Our long-term goal is to automate development, verification, release, and operations within goals, budgets, and permissions you approve. Expert agents would help along the way, with exceptions and major decisions returned to people. We're building toward that future one reviewable step at a time.
Start a new game with us
Have a game in mind?
Join the Starward waitlist for updates and early access. We're starting with invitation-only pilots for creators making a new game. Joining the list does not grant immediate platform access.
- Early access
- Join the waitlist. Initial pilots are invitation-only.
- First milestone
- A verified build for invited-player testing.
- Support
- Initial invited trial is free. Extra human support is scoped and quoted separately.
- Your team
- Bring your ideas and judgment. A technical partner is optional.
A few practical questions
Before you join.
What is Assembler?
Assembler is the main product of the Starward Platform: a game-development workspace built around existing coding agents. It connects a game's intended behavior, implementation changes, verification results, and human review.
What does an initial pilot aim to deliver?
An initial pilot starts with a small, agreed scope for a new game and aims for a verified build suitable for invited-player testing. People review the work and decide when to release. Joining the waitlist does not grant immediate platform access.
Do I need a technical partner?
No. The early audience is creators with strong game ideas and limited technical resources. A technical partner can help, but is optional. Initial invited trials are free; additional human support is scoped and quoted separately.
Which game engines are in scope?
Unity is the current reference path. Broader Godot adoption is part of the direction and still needs real-project validation. There is no promise of universal engine support.