# We wanted to make games. We wanted to make games, build worlds and play them with our friends. Each time something got in the way, we built the missing piece. That became Summer Engine and Summer Games. ![The Summer editor running Don’t Pray, with the game view, agent panel and scene tree.](https://www.summerengine.com/hero-loop-poster.webp) Inside Summer Engine · Don’t Pray in the editor. [Start with Summer Engine](https://www.summerengine.com/download) ## We started with an engine that agents could actually work in. AI coding agents were getting good at writing code. Making a game still meant getting that code into an engine, building scenes, finding assets and getting everything to work together. We wanted to be able to describe a game and work on it with an agent inside the same environment. We built on Godot and added the tools and engine changes that make that possible. Summer gives agents a way to work with your project, scenes, code and assets. You can use your favorite coding agent or boot Summer and use Summer AI. The point is to make room for the part you wanted to do in the first place: make a game. - [Make games with your coding agent](https://www.summerengine.com/mcp) - [Download Summer and use Summer AI](https://www.summerengine.com/download) ## Then we needed characters, worlds, sound and music. A working game needs more than code. It needs the character you want to play, the place you want to explore, the sound that makes a hit feel right and the music that changes the mood. So we built the asset studio. It brings generative tools for 3D characters, textures, images, sound effects, music and cutscenes into the game-making workflow. You can create assets, bring in work you already have and use the asset store. Your game can have its own style, whether that is a strange little 2D experiment or a detailed 3D world. - [Create assets in the studio](https://www.summerengine.com/studio) - [Explore the asset store](https://www.summerengine.com/asset-store) ## Then we wanted people to play what we made. People started asking the next obvious question: how do I share this with my friends? We wanted a place to put a game in front of players, get feedback and keep improving it without making every update feel like another launch project. That is why Summer Games exists. Summer Engine is where you make the game. Summer Games is where people discover and play it. The connection matters: you can build close to the people playing, see what they enjoy and bring them the next version. - [Share your game and play it with friends](https://www.summerengine.com/publishing) ## Playing together meant taking care of multiplayer. A game with friends should not require you to become a server-infrastructure expert. Networking code, setting up servers and maintaining them can become a project of their own before anyone has had any fun. Summer combines server infrastructure with SDK documentation that agents can follow. Your agent handles the complicated implementation with you; Summer takes care of the servers. You spend your time deciding what players can do together and making that experience good. - [Make your game multiplayer](https://www.summerengine.com/multiplayer) ## Creators needed a way to keep making their games. Letting people try a game for free can bring more people into it. Supporting that game through optional purchases usually means another layer of payment systems and operational work. We wanted small teams to have access to those capabilities, too. Sparks and the creator program connect in-game purchases with creator participation and earnings. Joining is a choice. Publishing on Summer, using Sparks and opening your game to mods are separate decisions. You own your game, and you can launch it elsewhere. - [How the creator program fits your game](https://www.summerengine.com/creator-program) - [Your game and your choices](https://www.summerengine.com/ownership) ## We grew up with mods. Of course we wanted them here. Counter-Strike, Dota, Garry’s Mod: modding is part of the gaming culture we grew up with. Players taking a game somewhere unexpected have given us entire new ways to play. Both making a mod and getting it installed have often required more technical knowledge than they should. With agents helping people build and a player destination to share through, we can rethink that whole experience. The creator still decides whether to open their game to modders. - [Why modding belongs in Summer](https://www.summerengine.com/modding) ## We admire what Steam and Roblox made possible. Steam showed what a great home for games could be. Roblox showed how much becomes possible when creation, multiplayer and community infrastructure work together. Those are real achievements, and they inspire us. Our question is what we would build with agents available from the beginning. An engine, assets, multiplayer, a place to play and ways to support creators—all connected, while leaving people free to make games with their own identity and publish elsewhere. ## Put the soul into your game. Let AI help with the infrastructure. The opportunity is bigger than generating more code. An individual or small team can attempt experiences that used to require a much larger team just to make the underlying systems work. Focus on the art, the stories, the world and the feeling of being there. Make something funny, frightening, beautiful or competitive. Make somewhere people want to spend time together. That is why we are building Summer. - [What we want games to be](https://www.summerengine.com/values) ## Make the game you have been thinking about. Start with an agent you already use, or use Summer AI inside the engine. You can begin with a small idea and build from there. [Choose your coding-agent setup](https://www.summerengine.com/mcp) ## Keep exploring - [Our values](https://www.summerengine.com/values) - [Publish a game](https://www.summerengine.com/publishing) - [Game ownership](https://www.summerengine.com/ownership) [Page map](https://www.summerengine.com/page-map) [Summer Engine — Terms of service](https://www.summerengine.com/terms) [Summer Engine — Privacy policy](https://www.summerengine.com/privacy) [Summer Engine — Refund policy](https://www.summerengine.com/refunds) [Source and licensing](https://www.summerengine.com/source-status) Canonical: https://www.summerengine.com/about Language: en [Read as Markdown](https://www.summerengine.com/about/content.md)