Vibe coding, governed
Vibe coding for everyone. Governed.
Anyone in the company can describe an app or an agent and watch it get built. Opsburg makes sure it starts from your templates, passes your checks, waits for the right approval and runs on your cloud, not on someone's laptop.
Animated scene: on a small island fenced in brass, a brass automaton builds an app floor by floor on a glowing blueprint. An airship lifts it and carries it through three brass gates labelled Tests, Security and Approval. At the last gate it waits until the lamp turns from amber to green, then it lands in the city, labelled Your cloud, and the new building's windows light up.
The new shadow IT builds itself
Saying no doesn't work: people build anyway, because now they can. Opsburg says yes, inside the walls.
An app in an afternoon
With AI, a marketer or an analyst can build a working tool in an afternoon. Great, until it holds customer data.
Running where?
On a laptop, a personal cloud account, a free hosting plan. Nobody knows it exists until it breaks or leaks.
Secrets in the code
Keys pasted into a prompt end up in the repository, and in its history for good.
Nobody owns it
No updates, no logs, no one on call. The person who built it moves on, the app stays.
From an idea to your cloud, through the gates
The same road for everyone, whether they write code for a living or have never opened a terminal.
1.Start from an approved template
The platform team owns the templates: stack, sign-on, logging, database. Nobody starts from a blank page or a random tutorial.
2.Describe it, the agents build it
Say what you need. AI agents, on the models your company chose, write the code in a real repository on GitHub, GitLab or Azure DevOps, CI included.
3.Checks on every change
Tests, security scans and your policies run before anything moves. A failed gate stops the airship, not the person: the agent reads the error and fixes it.
4.A person approves production
Builders try things freely in their own environment. What reaches production waits for someone with the right role.
5.Shipped through GitOps
Approved versions are deployed by Argo CD to your Kubernetes, behind your single sign-on, with rollback one click away.
6.It joins the city
The new app gets a building, an owner, logs and alerts. When it needs care, its owner gets a mission, not a surprise.
Freedom to build, and a platform that stays in charge
For the builder
- Build what you need without waiting months in a backlog
- No servers, keys or YAML to learn
- A live link to share as soon as it is approved
- Automatons that help when something breaks
For the platform team
- Every app starts from a template you own
- Every change passes your checks
- Production only after the right approval
- One map of what runs, who owns it and what it costs
The walls, one by one
The platform team draws them once. Everyone builds inside them.
Single sign-on and roles
Who can build, who can approve, who can see. Your identity provider decides.
Your AI models
Agents use only the providers and models you allow, with your keys.
Secrets out of the code
Keys are set on the platform by the people allowed to, never pasted into a prompt.
Coal budgets
Each workshop has a cost limit, so a weekend experiment doesn't burn the month's budget.
Everything on the tape
Every build, check, approval and deploy is recorded, with who did it and when.
On your cloud
Self-hosted on your Kubernetes. The apps your people build never leave it.
Let everyone build. Keep the city safe.
Opsburg is in the workshop, not playable yet. Follow the build on GitHub, and tell us what your people are already building on their own.