Project Aether
Narrative Strategy
Explore a decaying cosmos through tile-based puzzles. Your choices rewrite planetary histories.
Where Play Meets Vision
We are Brandaxo, an independent studio crafting tactile, memorable game experiences from Berlin. We explore the edges of interaction, narrative, and form—transforming constraints into unique creative signatures.
Scroll
Our Games
A Spectrum of Play
Our portfolio spans from intimate narrative experiments to expansive action worlds. Each project is a unique laboratory for a specific creative question.
Cel-Shaded
Lumina
Pixel Art
8-Bit Journey
Low-Poly
Assembly
Deep Dive
Anatomy of a Game Concept
Core Loop Visualization
Developer's Note
"We wanted to explore the tension between automation and creativity, a theme that resonates in our own tool-building process. The game asks: does optimization kill discovery?"
Core Pillars
Core Loop
Collect → Combine → Evolve
A satisfying arc of incremental power and visual transformation.
Art Direction
Retro-futuristic Synthwave
High contrast, neon lines, and synthetic pastels.
Target Audience
Casual Strategy Enthusiasts
Players who enjoy systems over reflexes.
Decision Lens: Concept Viability
This framework helped us validate "Project Aether" against our studio's non-negotiables.
✓
Does it reward mastery over time?
Yes. Unlock paths and visual styles scale with player expertise.
✓
Is the core loop understandable in 60 seconds?
Yes. A single tutorial piece demonstrates the full cycle.
⚠
Does it require complex hardware?
No. It's optimized for integrated graphics, but sacrifices high-resolution textures.
Development Pitfall
Early prototypes felt too punishing. We introduced a "grace undo" mechanic to preserve player momentum and reduce frustration.
Signature: The Setup Vignette
A
Custom Macro Configuration
The Last 10%
It's 9 PM. The tournament starts in 12 hours. My core routine is flawless, but a single skill has an awkward default key bind. In most games, I'd compromise. In Project Aether, I open the menu.
The interface is dense but logical. I don't search for "settings." I remap my thumb keyboard in under 45 seconds. No hunting. No restart required. The UI *anticipates* the need for precision under pressure.
— Alex, Competitive Strategy Player & UX Engineer
Process
From Spark to Launch
Concept
The "Constraint" Prototype
Q2 2024
Initial paper-and-pencil tests. Defined the 1-bit palette rule to force strong silhouettes.
Pre-Production
First Playable
Q3 2024
Core loop functional. Major pivot: from open world to contained levels to improve pacing.
Pivot Point
Narrative Re-write
Q1 2025
Playtest revealed the puzzle was engaging but lacked emotional stakes. Story was expanded to give context to the "what" and "why".
Production
Vertical Slice
Q3 2025
3 fully polished levels demonstrating the complete experience, art style, and UI philosophy.
Polish & Beta
Wider Playtest
Q4 2025
Focus on onboarding flow and accessibility. Iteration on controller mapping based on player feedback.
Manifesto
The Brandaxo Philosophy
Constraints as Catalysts
We often start with a monochromatic palette. This constraint forces us to communicate mood and gameplay through shape and motion alone, leading to stronger, more iconic art direction.
Trade-off Frame
Benefit
Iconic, readable visuals.
Cost
Less traditional visual fidelity.
Juice as Feedback Loop
"Juice" isn't just screen shake. It's the tactile, satisfying feedback loop that makes a click feel consequential. We script this at the engine level, not as a post-effect.
Systems, Not Scripts
We build robust underlying systems (input, audio, VFX) that are configurable by designers. This allows for rapid iteration without code changes and empowers the team to create emergent experiences.
In Practice
Where Theory Meets Reality
QA
Scenario: Pre-Release Bug Triage
Berlin, Q4 2025
A tester flags a rare crash when combining specific items. The modular system lets us isolate the issue to the VFX script, fix it in an hour, and run a full regression test—all before lunch. The constraint (working within a small team's timeline) is mitigated by the architecture.
Operating Constraints
- • Team: Core team of 5. Remote-first, async communication.
- • Engine: Custom-built in C# for full ownership of the stack.
- • Timeline: 18-month cycles. No "crunch" mandate. Sustainable pacing.
- • Target Platform: PC-first, console exploration in final phase.
Interested in Collaboration?
Whether you're an indie publisher, a platform looking for unique content, or a developer seeking a technical partner, we're open to conversation.