Our own title: a dark-fantasy dungeon crawler built end to end in-house — art direction, UI language, meta systems and client build. That pipeline then runs on client work, with no handover friction because there is no handover.
Astel Games — internal title2025Unity
Client
Astel Games — internal title
Engine
Unity
Platforms
iOS, Android
Year
2025
Duration
In production
Team size
Internal team
Disciplines
Game design, 2D art & UI, Client engineering, Live-ops tooling
Category
Full-cycle
Original IP — Dungeon Crawler — cover artwork
Artwork from our archive. High-resolution originals are available on request under NDA.
Production stills
The goal
What we set out to build.
Running an original title alongside client work means the internal project sets the bar instead of following one — and it has to stay staffable while paid work comes and goes. The art direction had to be something a small team could sustain across hundreds of assets.
How we ran it
Locked a limited palette and a single lighting model first, so every later asset could be checked against one reference.
Built the UI as a component library, so new screens are assembled rather than redrawn.
Kept one source project for the game and client submissions: same folder conventions, same review process.
Funnel-tested screens as key art before committing to full illustration, cutting rework on login and store art.
Instrumented the build from the first playable, so balance changes were measured rather than argued about.
Result
A complete original title in production, owned outright — no licensed IP, no platform-holder art approvals.
The internal component library and palette now reused on client casual titles.
Login, world-map and store screens produced in-house without external illustrators.
The studio’s proof that we can originate a product, not only execute a brief.
