What vibe coding is
With vibe coding nobody writes code line by line any more. A person describes in their own words what they need, checks the result and describes the next change. The AI does the programming. The term comes from Andrej Karpathy, a co-founder of OpenAI, in a post from 2 February 2025. Collins Dictionary named it Word of the Year 2025.
For a company this means, for example: the quality engineer builds her own complaint analysis, the cost estimator his own quoting tool, without waiting for a slot in the IT queue.
Where the risks are
- Data leaves the company. Pasting a customer list or a cost calculation into a public AI tool hands it to that tool’s provider.
- Unreviewed access. A home-made tool with credentials for the ERP can change data there that nobody should change.
- Shadow IT. Tools appear on private accounts, without versions or an owner, and nobody knows they exist.
- Personal data. Names, addresses and performance data fall under the GDPR, even in a small tool.
Banning rarely works
Ban vibe coding and you still get it, just out of sight. People use these tools because they take work off their hands. The better route is a place where building is allowed and safe: with your data, under your rules.
Rules that make vibe coding safe
- What deserves protection stays in-house. You decide which fields are protected. These values are removed before an AI works with the data. See Masking data for AI.
- Every person builds in their own space. What happens there touches nothing else.
- Every change is a version. An earlier state can be restored.
- Reading is the default. Writing to source systems happens only where your IT has set it up.
- Roles govern use. You decide who may see and use an application.
How Onagero does it
Onagero is vibe coding for companies, with these rules built in. Platform and applications run on your server. The language model runs at the model provider and gets single requests, without the values you protect. It builds not only applications but also analyses, explanations and CAD models. Details are on the security page.
How to start
With a process that runs on spreadsheets and ERP exports today and costs time every week. In a demo we show how your team builds it with Onagero themselves. The article Building internal tools without developers covers what else it takes.