Why we're building this
Game engines are extraordinary, and they're also a wall. Between the idea in your head and a thing you can actually play sits a long climb: scene trees, scripting languages, build pipelines, export settings. Plenty of people with great game ideas never get over that wall.
Geek Engine exists to lower it. You describe the game you want — the world, the mechanics, the feel — and an AI does the engine work: editing a structured game model, generating the art and sound, and compiling a real build you can play in your browser. The learning curve stops being the price of admission.
What we actually are
We're a small studio in Costa Rica, not a large company with a marketing department. We'd rather be honest about that than invent a roster of fake executives. The product is real and being built carefully; the team behind it is small and focused.
We care more about your game working than about which technology ships it. Your game compiles to a real build that runs instantly in the browser and travels as a link — and every change behind it is structured, recorded, and inspectable, because we don't believe creators should be locked into a black box.
Under the hood, compiled games run on our own runtime built from the open-source Cocos engine (Apache 2.0) — chosen so your builds stay lightweight, portable, and free of per-seat tooling. You never have to think about that; it simply ships your game.
How we think about the work
AI-assisted doesn't mean AI-magic. Every change the system makes is structured, recorded as a snapshot, and inspectable, so you can always see what happened and roll it back. We'd rather the tool be honest and legible than impressively opaque.
We're pre-launch. That means we're choosing to ship something we trust rather than something we rushed. If you want to follow along, the launch newsletter is where the real updates land.