A city builder for your cloud
Keep your cloud up and running. Play it like a city.
Opsburg builds and ships your apps and AI agents, from the repository to your Kubernetes. Then it turns running them into a game: every service is a building, every deploy an airship, every incident a storm. Your team keeps the city flying, and your cloud stays up.
In the workshop. Not playable yet.
Animated scene: a steampunk city floats over the clouds. A storm rolls in and lightning strikes a boiler house, which goes dark with a red lamp. A small brass automaton flies out from the clocktower, repairs it, and the lights come back on. The city keeps flying.
ScrollBuild, ship and run, in one place
Under the brass, Opsburg is a real platform for your apps and AI agents: your repositories, your pipelines, your Kubernetes. Developers use it, and so can everyone else: vibe coding for everyone, governed.
Build
Apps and AI agents from templates
Describe the service or the agent you need. Opsburg creates the repository on GitHub, GitLab or Azure DevOps, from a proven template, CI included.
Ship
One click to your Kubernetes
A tag builds the image and registers the version. One click deploys it through GitOps and Argo CD, in every environment, with rollback.
Run
Logs, health, AI that helps
Live state, logs and incidents for every service. AI agents read the logs, propose the fix and wait for your approval before touching production.
Your rules
SSO, roles, your models
Your single sign-on, your roles, your AI models, your cloud. Self-host it, or connect it to your AI client through MCP.
Keeping it up is the game
Running a cloud is a hundred small chores and a few bad nights. Opsburg turns them into a city your team wants to look after. Why a game works.
Uptime streaks
Every day the city stays in the air adds to the streak. A storm you weather fast keeps it alive.
Missions
Real chores turned into missions: patch the vaults, retire the old airships, add a reserve boiler before the season of storms.
Storm drills
Rehearse an incident on purpose and see who repairs it first. Better drills, shorter real storms.
A city that grows
Every service, environment and team adds a building. The city is the picture of your platform, for everyone to see.
Every building is the real thing
No toy simulation. Each piece of your city is backed by a piece of your stack, and each move in the game is an action on it.
Clocktower
Control plane
The heart of the city. It keeps every gear in time.
Boiler House
Compute node
Burns coal, makes steam. More boilers, more capacity.
Factory
Service
Where the actual work gets done, one assembly line per app.
Vault
Database
Thick walls, heavy doors. What goes in must come back out.
Telegraph
Message queue and logs
Messages hop from tower to tower, and every one leaves a line on the tape.
Observatory
Monitoring
Watches the sky so you see the storm before it hits.
Airship
Deploy
Carries a new version from the shipyard to every island.
Automaton
AI agent
Flies out to repair what a storm broke, and asks before it touches production.
Storms = Incidents
They roll in without warning. Weather them fast and the city keeps its streak.
Pressure = Load
Too much steam in the pipes and something bursts. Too little and the city stalls.
Coal = Cost
Every boiler burns it. A good mayor knows where every lump goes.
How a city grows
1.Found your city
Connect your Git provider, your cluster and your sign-on. Your first island rises from the clouds with a clocktower on top.
2.Build on real ground
Place a factory and Opsburg creates the service or the agent: repository, pipeline, container, all from proven templates.
3.Launch the airships
Tag a version and an airship takes off. Behind it, a real build and a real GitOps deploy through Argo CD.
4.Keep the city flying
When something breaks a storm hits the island. Read the telegraph, send your automatons, clear the sky and keep the streak.
The shipyard is open
Opsburg is in the workshop. Follow the GitHub organization to see it take shape, and tell us which storm keeps you up at night.
github.com/opsburg