Vibe coding typically needs to be double-checked to make sure that it does what it's actually supposed to because LLMs are notoriously prone to hallucinations. This ad suggests that their AI is better and you don't need to double check it.

But what's probably more likely is that they're just trying to break searches for "ai bubble."

Before current AI/LLM shenanigans, there were a lot of "low code/no code" visual programming solutions aimed at allowing novices to write software using little to no code. Visual programming software like Microsoft Power Automate, which provides users with a list of predefined commands which they can drag-and-drop onto a flowchart. When a user clicks the play button, the commands in the flowchart execute in order.

This sort of system is great for novices, allowing people who do not have experience programming (people like you, apparently) to create simple programs that do useful things. But as a project grows in complexity, so does the need to get into the code itself and tinker around to fix the nitty gritty details. A more experienced developer is going to want to get into the lower functions of the program and find a solution to the problem. But these visual programming solutions do not offer the ability to fix the nitty gritty. You are stuck only refining the high-level details, which is often not enough to solve your problem.

"Traditional" vibe coding with languages like JavaScript, C++, etc. can potentially work because an LLM spits out actual programming code that ostensibly does something. And if a developer needs to tweak that code to work a little differently, they hypothetically can. Sure, a pure vibe coder will not know what they are doing as they turn the proverbial knobs in an attempt to fix the system. But at least the knobs are there to turn, and turning them in the right way can potentially eventually solve the problem.

"Vibe code without the code" probably means to speak to an LLM and have it spit out one of those minorly-editable flowcharts. You get the benefits of vibe coding and the detriments of visual programming. You don't know what to do to fix it, and you can't fix it anyway because the tools don't let you.

It's probably some app engine that lets product teams enter prompts without even giving the option to view the code.