This post originally appeared on the Makko AI blog.
Most game development tools are built by engineers for engineers. The assumption baked into their design is that the person using them already knows how to code, already understands engine architecture, and just needs better tooling to move faster. Makko was built on a different assumption: that the person with the best game idea in the room is not always the person who can ship it.
That belief shapes everything about how Makko works, what it prioritizes, and who built it. This week, GeekWire featured Makko in its Startup Radar series, spotlighting the founding team and the platform's early traction. More than 3,000 people joined the beta before it wrapped, and the number has since grown to nearly 4,000.
The founders and where they come from
Makko was founded in 2025 by three people who each bring a different piece of what the platform needed to exist.
Jeremy Bird is CEO and co-founder. He spent more than a decade at Amazon across gaming and Prime Video, which means he has seen at scale what it takes to build, ship, and sustain interactive entertainment products. That background informs the decisions Makko makes about workflow design, not just technical capability.
Tony Valcarcel is co-founder and previously led marketing at Shrapnel, a Seattle-based gaming startup, and served as digital marketing director at Convoy. The marketing lead being a co-founder matters because it means the question of how creators discover, understand, and commit to a tool is not an afterthought. It is part of how the platform was designed from the start.
Mike Fehlauer Hayes is co-founder and helped create the Penny Arcade Expo, better known as PAX. PAX is one of the largest gaming conventions in the world, and building it required a deep understanding of gaming culture, creator communities, and what makes people genuinely excited about games rather than just interested in them.
The risk they are deliberately avoiding
GeekWire included a quote from a venture capitalist reviewing Makko that is worth sitting with:
"The risk is you become a grab bag of features when studios really want one tool they can rely on every day. Build a couple opinionated, end-to-end workflows that output production-ready assets in a consistent style, then showcase creators who shipped and will publicly say you sped them up."
This is a sharp and honest framing of the failure mode for platforms like Makko. The AI game development space is filling up with tools that do a lot of things adequately. The risk is becoming one of them: broad, shallow, and forgettable.
The counter to that risk is not more features. It is opinionated workflows. Deciding that Makko will do certain things exceptionally well rather than most things acceptably. The character animation pipeline, the agentic game logic layer, and the reasoning modes that separate fast iteration from deep structural builds are all examples of choices made in that direction.
What the platform is actually for
Makko is an AI Game Development Studio. That phrase has a specific meaning in how the platform is designed. It is not a generator you prompt and walk away from. It is an environment where you describe what you want, the AI plans and assembles the logic, assets, and systems, and you stay in the loop as the creative director rather than the implementer.
The people it is built for are creators who have game ideas but hit a wall when it comes to execution. Writers who want to build visual novels. Artists who want to ship a platformer. Designers who can describe exactly how a game should feel but cannot write the code to make it happen.
Nearly 4,000 people signed up for the beta. The question Makko is answering is not whether AI can make games. It is whether AI can make the right part of game creation invisible so that the people with the best ideas can do the work that actually matters.
Read the full post and explore the Makko blog at blog.makko.ai
Built with Makko AI — AI-native game creation, no coding required.
Top comments (0)