Frequently asked questions

A platform that builds and ships your apps and AI agents, from the repository to your Kubernetes, with a game on top: your stack is a flying city, and keeping it up and running is how you play.

It creates repositories from templates on GitHub, GitLab or Azure DevOps with CI included, registers every version you build, deploys it through GitOps and Argo CD to your environments, and shows live state, logs and incidents. AI agents help read logs and propose fixes.

Because keeping a cloud up is a lot of small chores and a few bad nights. Streaks, missions and storm drills make the chores visible and the team faster when a real storm comes.

Not here. The streak belongs to the team, nobody is ranked or blamed, and the city grows with outcomes like uptime and patched services, not with commits. More on the Why a game page.

Yes, that is the idea: describe the app and AI agents build it from a template your platform team approved, through tests, security checks and a human approval before production. More on the Vibe coding page.

No. When you place a factory, a real service is created. When an airship takes off, a real version is built and deployed. The game is the interface, the infrastructure is yours.

AI agents that work for your city. They read logs, propose fixes and repair damage after a storm, on the AI models you choose. Anything that touches production waits for your approval.

Yes, that is the plan: one container, or a Helm chart on your Kubernetes, with your single sign-on.

Not yet. Opsburg is in the workshop. Follow the GitHub organization to see it take shape.