What is Cheesemaker?

An AI-native game engine designed for production. Not a plugin. Not a layer. A complete system — from editor to deployment.

Games are built on engines. Engines are built on assumptions — about platforms, about teams, about what gets automated and what stays in human hands. The assumptions that produced the last generation of engines no longer match how software is made.

Cheesemaker is an AI-native game engine. Not a plugin. Not a layer over someone else's runtime. A complete system — editor, engine, backend, build pipeline, deployment — designed from the first line of code around the reality that developers now work alongside models.

We did not start this to make game creation faster in the way that phrase usually implies. We started it because the gap between what a small team can imagine and what they can ship has stopped being a talent problem and become a tooling problem. The talent is there. The tools have not caught up.

Existing AI game tools prototype.

Cheesemaker ships.

AI should remove friction, not ownership.

The promise of AI in creative tools is not that the machine makes the thing for you. It is that the machine removes the small, accumulative frictions that sit between having an idea and being able to act on it — the boilerplate, the lookup, the conversion, the setup, the part of the work that is effort without being craft.

What AI must never remove is ownership. Ownership is the relationship between a maker and the thing they have made: the ability to understand it, to change it, to be surprised by it, to take responsibility for it. A tool that removes friction while preserving ownership is an amplifier. A tool that removes friction by removing ownership is a replacement — and the people who use it are no longer makers, but operators of someone else's machine.

Cheesemaker is built on the amplifier side of that line. The AI inside the engine writes code you can read, generates assets you can edit, and proposes changes you can refuse. It does not produce opaque artifacts. It does not make decisions you cannot inspect. It does not own any part of your project that you cannot take back by hand.

This is the only honest way to put AI inside a tool that professionals use. Anything else eventually asks the developer to give up the thing that makes them a developer — the right to be the final authority on their own work.

We build the engine.
You build the game.

Four constraints we will not trade away.

Developer First

The developer is the operator of the system, not a passenger in it. Every AI capability in Cheesemaker can be inspected, refused, undone, or rewritten. Nothing happens to your project that you did not invite and cannot trace. The engine exists to extend the reach of a single developer or a small team — not to replace them, and never to act without their consent.

AI Without Lock-In

AI is a capability inside the engine, not a service the engine depends on. Models can be swapped, endpoints can be changed, and any AI-assisted artifact can be edited by hand afterwards. You are never required to use the AI, never required to use a specific model, and never bound to a vendor. What the AI produces is yours; what it runs on is your choice.

One Engine, Every Platform

Cheesemaker is not a frontend over a frontend. There is one engine, one runtime, one editing model. The same project that runs in a browser tab compiles to a native desktop binary, ships to mobile, and targets consoles — without re-authoring scenes, rewriting logic, or maintaining parallel codebases. Build once. Deploy everywhere.

Production Ready

This is not a prototype of an engine. It is an engine. Cheesemaker is being built for projects that ship to real players on real platforms under real deadlines. The editor is a tool you can spend ten hours a day inside. The backend is something you can launch a game on. The build pipeline is something you can trust on release day. Nothing here is a demo of what might exist later.

WHAT YOU CAN BUILD

Everything a game needs. Nothing it doesn't.

Every feature below exists because someone needed it to ship a real game. Nothing here was added to fill a grid or test well in a survey. If it's on this list, it's in the engine.

A Real Engine

Not a framework. Not a wrapper around someone else's runtime. A complete game engine — rendering, physics, audio, scripting — built from scratch for the AI era. You get the source. You own the output.

Multi-Agent Systems

Deploy coordinated fleets of AI agents that perceive, decide, and act. NPCs that don't follow scripts — they follow intent. Enemies that adapt. Allies that improvise. Worlds that feel awake.

Asset Marketplace

A living ecosystem of models, textures, sounds, and prefabs — engine-native and ready to drop in. Find what you need. Publish what you build. Every transaction stays inside the engine.

Cross-Platform Shipping

One project. Every platform. Compile to browser, desktop, mobile, and console from a single source tree — no per-target re-authoring, no parallel codebases, no compromises on fidelity.

Instant Sharing

Ship a playable link in seconds. No app stores, no installs, no gatekeepers. Your game reaches players the moment you decide it's ready — and they play it in the browser, immediately.

Remix Culture

Fork any public game and make it yours. Swap assets, rewrite mechanics, build on someone else's foundation. Great games should be starting points, not endpoints. Creation is cumulative.

Native Multiplayer

Multiplayer is not an afterthought bolted on with third-party SDKs. State synchronization, lobby management, and netcode are engine primitives — as native as rendering a sprite.

Game Jams

Built-in jam infrastructure. Create events, set deadlines, collect submissions, run community voting — all inside the platform. No external tools. No spreadsheets. Just make games together.

More to come