Terrafix
Third-person building game on a dead planet. Every machine is a plant, and the whole factory exists to bring the planet back.
Wega Studios product · grown out of the 2025 game jam prototype
Early access planned for Q4 2027
Built for production, not for the pitch.
Backend systems, mobile apps and Unreal Engine games. Built by one engineer who owns the architecture.
In developmentKey art created with AIBuild a factory. Get a planet back.
See the gameReal projects. Concrete context.
Shapes – Puzzle Escape
A puzzle game for Android and iOS, co-developed by Wega Studios and MayStudios.
Co-development · Wega Studios × MayStudios
Tiles – Logic Puzzle
A logic game for Android and iOS, built jointly by Wega Studios and MayStudios.
Co-development · Wega Studios × MayStudios
AI assists. The engineer remains responsible.
AI does not write code that ships unchecked. It speeds up research and variants — what survives is decided by a review.
Clarify intent and boundaries
Acceptance criteria, data and critical risks are settled before implementation.
Shape the architecture deliberately
Separate components so changes stay traceable and testable.
Use assistance selectively
AI gets only the context it needs and bounded tasks. Generated material stays visible.
Test, harden and approve
Tests, builds and project-specific gates decide what ships.
The work I take on.
Backend & platforms
Domain logic, APIs and data flows that are still changeable years later.
Full-stack products
Applications that carry one hand from the data model to the interface — and hand over cleanly.
Mobile apps
Android and iOS from one codebase, with resilient state and a release path that holds no surprises.
Unreal & game development
Gameplay systems in Unreal Engine 5 — from the mechanic on paper to a build someone can play.
AI-native engineering
Agent harnesses, skills and plugins that make AI systems predictable. With evaluations, gates and measurable behaviour instead of gut feeling.
JavaSpring BootPostgreSQLREST & API designDockerTypeScriptReactNode.js
FlutterDartFirebaseUnreal Engine 5C++BlueprintsAgent harnessesEval gatesMCPGit & Perforce
No account manager in between.
You talk to the person who writes the code and owns the architecture.
Currently continuing his studies
Reporting directly to the development lead, responsible for the architecture and APIs of the mobile and web clients — from cutting the endpoints to implementing them.
Name roles honestly
Team work remains team work; project context and individual contribution are not blurred.
Keep technology explainable
Architecture and risk are documented so decisions remain reviewable.
Match quality to risk
Tests and gates are shaped by the real cost of possible failure.
Large initiatives become concrete before they become large.
Substance comes from clear scope, visible risk and reviewable increments — not blanket guarantees.
Clarify
Define the problem, users, constraints and success criteria together.
Target state · Risks · Acceptance criteriaShape
Reduce architecture, interfaces and delivery slices to a reviewable plan.
Scope · Architecture · BacklogBuild
Implement visible increments, review them and test them against the criteria.
Demos · Tests · DecisionsHarden & hand over
Secure failure paths, accessibility, operations and handoff for the usage context.
Release gates · Documentation · Handoff
What matters before the first conversation.
Straight answers on scope, collaboration and the use of AI.
Can Wega Studios take on larger software initiatives?
Yes, when the target, risks and delivery increments are shaped clearly. Larger scopes begin with a bounded discovery and architecture stage; any additional roles required are named transparently.
How is AI used in development?
Selectively for bounded tasks such as research, variants, boilerplate or test ideas. Architecture, security and product decisions, diff review and approval stay with the engineer; outputs must pass the same tests and gates as other code.
Does Wega Studios work with existing teams?
Yes. Interfaces, responsibilities, review paths and the definition of done are aligned at the start so the work can integrate without creating knowledge silos.
Does Wega Studios still build websites?
Yes, when they are part of a product or a clear digital objective. The focus is software engineering; visual design is a supporting capability.
When can I expect a credible effort estimate?
Once the scope is clear enough. Uncertainty is shown explicitly; where technical risk is open, a small prototype is often a more honest basis than early false precision.
Let’s clarify the problem first.
Briefly describe what should be built or improved, which systems are involved and where the largest risk sits today.
Direct contact
You do not need a finished specification. An honest outline of the goal, context and open questions is enough to begin.
Write an email