Inspiration
Orbital Cloud Simulator was inspired by the growing conversation around data centers, AI infrastructure, energy use, and the future of compute. Earth-based data centers are a major topic right now, and space-based data centers are no longer purely a science-fiction idea; they are being explored as a possible future direction for large-scale computing.
That made the concept feel like a strong foundation for a management simulation. I wanted to take the familiar satisfaction of incremental progression, resource balancing, and base-building games and place it in a more future-facing setting: what if players could build and grow their own orbital data center?
The core fantasy came from combining approachable management-game progression with a fresh sci-fi theme. I also wanted to sprinkle in recognizable real-world ideas, such as x86 and RISC server technology, so players who are familiar with compute, hardware, or networking would notice those details.
The guiding design principle became: start productive, then add constraints. UGC and mobile players often decide very quickly whether a game is worth their time, so I wanted the first moments to deliver a clear win before asking the player to understand deeper systems. More complicated mechanics have a place, but they need to arrive gradually.
What it does
Orbital Cloud Simulator is a mobile-first Simulation & Management game where players build and grow an orbital data center platform. Players place infrastructure, generate compute, earn rewards, solve resource bottlenecks, and expand their operation over time.
As the platform grows, players make light management decisions. Growth increases production, but it also creates new pressure on the systems supporting the platform. Players reinvest earnings into more capable compute equipment, supporting infrastructure, and platform expansion so their operation becomes more efficient and visually impressive.
The game is designed to work as a satisfying solo experience first, with shared-world identity layered on top. I wanted the world to feel multiplayer and alive, while also recognizing that many UGC games can have quiet or empty lobbies. The core loop does not require a full instance to be enjoyable, and shared features are designed to support the experience rather than block progress when other players are not present.
The broader goal is to make the core build-and-optimize loop fun on its own, then expand once the foundation is proven.
How I built it
For this competition, I created a full pre-production design package rather than a playable prototype. The package includes a Game Design Document, Player Journey Map, Visual Concept Package, and Production Plan.
I used generative AI tools to help brainstorm ideas, explore variations, and rapidly iterate on the design documentation. For the visual identity, I used mostly AI-generated base images with some manual editing and composition in GIMP.
The process focused on turning a broad concept into a practical game plan: define the core loop, map the first-session experience, establish a readable visual language, and separate the first playable version from longer-term expansion ideas.
I also considered the realities of mobile and UGC development while planning the design. The game needs to be readable on a small screen, satisfying in short sessions, friendly to players who may leave quickly if the opening is too complicated, and efficient enough to support growth without overloading the experience. Performance planning is part of the design, including approaches such as caching important player totals and only recalculating them when meaningful changes happen.
Challenges I ran into
The biggest design challenge was scope. The concept naturally suggests a large network of interconnected systems, progression layers, and social features. The hard part was deciding what belongs in the first playable version and what should be saved for later updates.
Making the theme readable on mobile was also important. Infrastructure, compute, and resource management can become abstract quickly, so the design needed strong visual feedback: glowing indicators, data movement, simple color coding, and clear silhouettes that players can understand at a glance.
Establishing the visual concept package was also demanding. Achieving a consistent style with AI-generated concepts required a lot of iteration, and in some cases it was better to bring the strongest generated elements into GIMP for manual cleanup, layout, and final composition.
Accomplishments that I'm proud of
I am proud that the project developed into a cohesive package where the design, first-session journey, visuals, and production plan all support the same vision. The game has a clear fantasy, a readable loop, a practical MVP direction, and room to grow after launch.
I am also proud of the “start productive, then add constraints” onboarding structure. The player gets an immediate sense of reward and progression before being asked to understand deeper management systems. That keeps the game approachable for mobile players while still leaving space for meaningful optimization later.
I am also proud that the design considers the habits of UGC players beyond the first session. Players often respond well to visible progress, frequent updates, social comparison, and ways to show off what they have built. Orbital Cloud Simulator is planned with room for ongoing updates, community goals, and future showcase features.
What I learned
This project reinforced how important it is to separate the full vision from the first playable version. A management simulation can grow in many directions, but the MVP has to prove one thing clearly: is the foundational loop fun enough to keep doing?
I also learned the value of pre-production. It is tempting to jump straight into building, but creating the design package first helped clarify the player journey, control scope, identify risks, and organize the project into a more realistic build plan.
What's next for Orbital Cloud Simulator
The next step would be building a playable vertical slice focused on the first-session experience: claiming a platform, placing the first pieces of infrastructure, earning early rewards, encountering the first management pressure, and seeing a clear reason to keep playing.
After proving that solo loop, the next phase would introduce more of the shared-world identity: community goals, simple leaderboards, lightweight social features, and ways for the station to feel active even when a lobby is not full.
Longer term, Orbital Cloud Simulator could expand with deeper progression, more advanced optimization, larger platform growth, stronger community features, and regular content updates. A planned showcase area would give players a way to show off their platforms, capture shareable moments, and potentially bring new players in through social media rather than relying only on discovery inside the platform.
The overarching goal would remain the same: build the best data center in orbit, keep it cool, sell compute, and grow your platform.
Log in or sign up for Devpost to join the conversation.