Vibe Coding 2.0 is here...

Summary

Wes Roth demonstrates how an AI-built app can move beyond a working prototype to an application suitable for use across a company. The example is a customer-support CRM for handling a damaged-headphones refund. It brings customer details, orders, support tickets, return requests, and event history together.

Building the CRM

• Roth uses Superblocks’ AI assistant, Clark, first in planning mode and then to build the app.
• Clark creates a PostgreSQL database and can draw on a company knowledge base, including its design system.
• The workflow is designed around two roles: support agents can submit refund requests, while managers review and decide them.
• The agent and manager views present different information and actions. The demo follows a fictional $249 refund from the initial ticket through approval.

Access and authorization

The video distinguishes between platform access and business rules inside the app:

• Organization and application permissions determine who can open, edit, or deploy an app.
• Application logic must enforce who can approve a particular refund. Hiding an approval button is not sufficient; the operation that changes the refund’s status should verify the logged-in user’s role.
• Roth says Superblocks apps have SSO by default, so the app can identify the user and their group. He stresses that real deployments should be tested with the kinds of accounts employees will actually use, with IT involved in configuring access and reviewing sensitive actions.

Security checks and records

• Superblocks is shown running security checks during building, publishing, and in production.
• The initial scan flags two issues in the refund request: trusting identity data supplied by the browser and not comparing the refund amount with the original order.
• After Roth selects “fix all” and rescans, a low-criticality warning remains. He notes that the demo’s approval process still runs in the browser and that a real deployment also needs server-side authorization.
• The video separates business history—the request, amount, reason, and decision—from platform oversight. Audit logs track changes to the app, while the security center gives administrators visibility into company apps, their creators, and vulnerabilities. Roth argues that organizations need both.

Deployment and enterprise use

• The video presents CloudPrem as a deployment option in which the Superblocks system runs inside the company’s AWS account. Roth says the app, data, and AI processing through Amazon Bedrock remain in that environment.
• The broader argument is that enterprise “vibe coding” needs more than an AI-generated interface: organizations also need controls over access, sensitive operations, audits, security, and deployment.
• Superblocks is presented as an alternative to either blocking AI app development or letting employees release apps without oversight. Lovable is briefly mentioned as a tool for quickly creating an initial version.

Video details

• Type: Sponsored product demonstration and enterprise-readiness walkthrough, rather than an independent product review.
• Main speaker/source: Wes Roth, presenting a Superblocks demo. Superblocks is identified as the video’s sponsor.