Vibe coding to production: verify, harden or rebuild
Move a vibe-coded app toward production by inspecting its actual permissions, code, connected services, release path and recovery. Preserve useful prototype feedback while testing the business rules independently. Compare bounded hardening, refactoring and replacement scopes from the evidence, then estimate the work and operating responsibilities of the intended release.

The short version
- Inspect the artifact. Deployability and generation method do not settle readiness.
- Test actual permissions. Use allowed, other-user and signed-out cases.
- Recover real effects. File rollback is different from data and external-action recovery.
- Compare bounded paths. Hardening, refactoring and replacement need evidence and estimates.
Keep the prototype evidence and inspect the implementation
Moving from vibe coding to production means establishing that the actual application can perform its intended tasks with appropriate access, verification, recovery and operating ownership. Preserve useful interface and customer evidence from the prototype, then inspect the generated code and connected services. A deployable demonstration does not establish those properties, and generation alone does not prove they are absent.
Consider an internal equipment-request app with employee and approver roles, request submission, return status and a history view. The prototype helps people discuss the workflow. Before live use, establish who may read each request, who can approve it and what happens when a status change fails. This example excludes payments, sensitive regulated records, offline work and external inventory integrations.
Stack Overflow's 2025 survey reports 84% using or planning to use AI tools in development, from 33,662 responses to that item.1 That self-selected use-or-intent measure does not identify the readiness of this app. Evaluate the artifact and the proposed exposure rather than using adoption as assurance.
- Interface evidence: retain observed task feedback, including confusing or unused screens. Treat it as input to requirements, not a complete specification.
- Data clues: inspect generated entities and relationships against real permissions and lifecycle needs.
- Recoverable code: verify repository access, export and dependencies. Lovable documents code and data export choices, while migration still requires work.8
- Unresolved questions: preserve the failures and assumptions the prototype did not test.
The same survey's multi-select frustration item reports 66% selecting almost-right output, with 31,476 responses and eligibility beyond regular AI users.1 It describes perception, not a code defect rate. For this app, an apparently correct history page may still expose another employee's record unless the actual access path is tested.
Inspect eight production concerns in the actual app
Review data access, credentials, code behavior, dependencies, verification, release, recovery and operation. Prioritize from actual exposure and consequence. A generated app may already contain useful controls, but they need evidence against the product's business rules and operating environment.
- Access: identify exposed tables, grants, policies and privileged paths. Supabase requires RLS on exposed tables and notes that policies do not revoke existing grants.5 Test allowed, other-user and signed-out requests with realistic records.
- Credentials: distinguish public identifiers from privileged secrets. Inspect the built client and deployment path, then investigate and rotate credentials that were exposed. A key's presence alone does not tell you what authority it carries.
- Code: review the behaviors that affect your task: rendering, validation, authorization and external effects. Use security findings as specific leads, not a blanket judgment about all generated code.
- Dependencies: identify deployed versions and applicable findings. Lovable's scan tools cover different checks;7 inspect scope and limitations before treating an empty result as acceptance.
- Verification: use independent task expectations and meaningful regression cases. Cursor checkpoints restore modified files around agent changes;11 they are not tests or full operational recovery.
- Release: inspect the actual path from change to production. v0 can open pull requests as well as deploy prototypes;10 configure the review and acceptance route the product requires.
- Recovery: choose recovery objectives and test data restoration, including reconciliation after a partial action. Supabase's production checklist covers recovery and infrastructure preparation.6
- Operation: assign detection, support and response. Check email delivery, administrator access and configured limits in the real environment rather than copying a historical plan threshold.
Veracode's Fall 2026 update reports 62% average security pass, with approximately 38% its rounded complement.16 Its Summer method used constrained function-completion prompts without security-specific guidance, separate compilation analysis and vendor security testing.15 Neither result measures the vulnerability prevalence of reviewed production apps or this equipment workflow.
| Period/result | Reported rate or interpretation |
|---|---|
| Summer pass | ~56% |
| Fall pass | 62% |
| Summer non-pass | ~44% |
| Fall non-pass | ~38% |
| Interpretation | Dated benchmark, not production prevalence |
Review the app's actual contexts rather than prioritizing weaknesses solely from a benchmark bar. For equipment requests, inspect record access, approver authority, stored text rendering and repeated status updates. An independent reviewer should be able to trace each important result back to a requirement and test.
Use tool features without inferring complete readiness
Inspect what the current tool and project configuration actually provide: code export, connected services, scans, file history and deployment routes. These aids cover different boundaries. A local rollback cannot recover a database write, and a security scan cannot decide whether an approver should see a particular employee's request.
| Tool | Inspect | Data path | Available aid | Verify first |
|---|---|---|---|---|
| Lovable | Inspect generated app and version | Confirm actual hosting/data path | Quick/deep scan scope varies | Test grants, policies and export |
| Bolt.new | Inspect generated languages and services | Verify actual integration | Discover history and export limits | Review server/client boundaries |
| v0 | Code and deployable prototypes | Inspect connected services | Can open a review pull request | Verify review and release controls |
| Cursor | Agent changes in a codebase | Existing project dependencies | Local file checkpoints | Test diffs and operational recovery |
Lovable documents different framework generations: new apps from May 13, 2026 use TanStack Start, while older ones use React/Vite.8 Confirm the actual generated project before planning hosting or migration. Exportable code and data still need dependency, integration and operational checks at the destination.
For a Bolt.new project, inspect the actual generated app and its configured services before committing to a migration or release plan. Inspect the actual app's languages, services, repository export and history instead of transferring another tool's behavior to it. For v0, verify that the intended review path controls the deployment. For Cursor, preserve proper version control and a recovery plan beyond file checkpoints.
Lovable says its scans complement professional review.7 Run relevant checks, investigate findings and test the business access rules. A permissive policy can be syntactically valid while violating the product's intent. Document what the scan covers and what remains with an authorized reviewer.
If the product itself uses a language model, apply the separate threats in OWASP's LLM Top 10, including injection, unsafe output handling and excessive agency.14 AI-assisted implementation and a model-based product feature create different evaluation questions; a prototype can contain either or both.
Require evidence for the hardening decision
Use a task-specific checklist with a reviewer, test and result for each relevant concern. The proposed checks cover data, credentials, code, release and operation, but their order should follow actual risk. An unresolved item needs a decision about containment or exposure, not a cosmetic completed status.
For the equipment app, seed records belonging to two employees and an approver. Test direct requests as well as visible screens. Confirm a denied read, an unauthorized approval, a repeated submission and a failed return-status update. Use the production readiness workbook to preserve release and recovery evidence.
| # | Area | Check | Done when |
|---|---|---|---|
| 1 | Data | Inventory exposed tables and actual grants | Allowed and denied roles tested |
| 2 | Data | Review RLS with grants and privileged paths | Owner, other user and signed-out cases |
| 3 | Data | Match policies to business rules | Tests use realistic restricted records |
| 4 | Secrets | Keep privileged credentials out of clients | Built bundles and deployment inspected |
| 5 | Secrets | Investigate exposed keys and rotate as needed | Old credentials and affected access checked |
| 6 | Output | Validate rendering for each context | Relevant payloads cannot execute |
| 7 | Logs | Exclude secrets and protect log structure | Sensitive values and forged entries tested |
| 8 | Server | Validate writes and abuse controls | Denied and repeated requests exercised |
| 9 | Packages | Review applicable dependency findings | Version, reachability and response recorded |
| 10 | Tests | Cover core allowed and denied tasks | Meaningful cases run in review workflow |
| 11 | Release | Require agreed review and acceptance | Actual production route follows policy |
| 12 | Environments | Separate test data and credentials | Test changes cannot alter live records |
| 13 | Recovery | Choose backup and restore objectives | Restore and reconciliation exercised |
| 14 | Access | Review admin and infrastructure controls | Current configuration and recovery tested |
| 15 | Check auth delivery and launch demand | Provider and configured limits verified | |
| 16 | Operation | Assign detection and incident response | Relevant failure reaches a capable owner |
The Supabase access and production guides support relevant configuration questions;56 the table's completion criteria still need to match this application. A clean advisor or audit cannot establish every business rule. Preserve the current versions, tested roles and meaningful exceptions beside the result.
Test recovery at the boundary where effects occur. Reverting code after an incorrect approval does not necessarily restore the previous request state or undo a notification. Determine what can be reversed, what needs reconciliation and what evidence the responder will have. Run a controlled failure exercise before assuming a restore button settles the issue.
For a mobile client, add device and distribution checks from the mobile security guide. A model-based feature also needs the source, authority and output checks in AI security guidance. Keep those tests tied to implemented capabilities.
NIST's AI RMF is voluntary trustworthiness guidance across design, use and evaluation.13 It can organize responsibilities where AI is involved, while acceptance still rests on the evidence and scope of this release. If the team lacks independent test capacity, discuss the critical cases with a QA engineer before widening exposure.
Compare hardening, refactoring and replacement
Harden when the required behavior fits and specific controls or tests are missing. Refactor when a bounded structural change addresses a demonstrated constraint. Consider replacement when evidence shows that the necessary behavior cannot reasonably be supported by the current approach. Sensitive data or unfamiliar code increases investigation needs; neither automatically proves a rebuild is the right answer.
Keep the prototype's useful findings while challenging its untested assumptions. An employee screen can remain useful evidence even if the approval path changes. The technical debt review helps compare the consequence and opportunity cost of each intervention.
| Question | Harden | Refactor | Consider rebuild |
|---|---|---|---|
| Data model | Required behavior fits | Bounded schema migration | Test alternative data boundary |
| Logic | Existing paths are understandable | Move specific authority or validation | Compare a replacement for incompatible core |
| Stack | Required capabilities demonstrated | Targeted component change | Prototype blocked requirement elsewhere |
| Understanding | Owner can explain and maintain | Investigate opaque areas | Rebuild only with evidence and migration plan |
| Exposure | Contain and test actual paths | Repair sensitive boundaries | Contain first; data type alone does not decide |
Investigate opaque code before treating uncertainty as a replacement estimate. Ask a reviewer to trace one important task, identify the responsible services and explain its failure path. Compare a narrow repair with a prototype of the blocked requirement. A rebuild still needs migration, compatibility, verification and operating ownership.
Check portability while the decision is open. Lovable's export options do not promise a frictionless hosting move.8 Inventory data, identities, files, secrets, scheduled work and external integrations. The development partner selection guide offers questions about evidence and ongoing responsibility.
Estimate a defined repair scope and its dependencies
Estimate production work after inspecting the artifact and choosing the release boundary. Compare hours, capacity, dependencies and excluded costs for alternative scopes. The following equipment-app example uses hypothetical inputs to show the calculation; it is neither a market rate range nor a promise about the duration of an unreviewed prototype.
Assume the same employee/approver workflow described above. A hardening option budgets 120 hours: 20 for discovery, 40 for access and credential work, 40 for regression/recovery checks and 20 for release preparation. For refactoring, assume the four existing views remain usable and only approval authority moves to the server. Include the full 120-hour hardening scope, two approval transitions at 32 hours each (64), server permission enforcement (32), a three-table employee/request/status migration (32), denied/repeated-action regression cases (48) and updated operator handover (16): 312 hours total.
For a replacement, assume the same four views and four operations: submission, approval, return-status change and history. Allocate 96 hours to views (four ×24), 96 to operations (four ×24), 48 to identity/permissions, 32 to source-data export/mapping, 32 to a trial and final import, 16 to reconciliation, 60 to 20 acceptance cases at three hours each, 44 to regression/recovery, 24 to release/handover and 20 to discovery: 468 hours. Both transitions assume at most 1,000 existing requests, unchanged identifiers and no attachments or external integrations. A rollback rehearsal and checks of owners, statuses and record counts are required. Replacement includes its own controls and discovery; do not add the separate 120-hour option. Credit already accepted inspection work when quoting, rather than billing the same task twice.
| Path | Hours | Capacity basis | At USD 80/h | At USD 120/h |
|---|---|---|---|---|
| Harden | 120 | 30 h/week: 4 effort weeks | USD 9,600 | USD 14,400 |
| Refactor | 312 | 40 h/week: 7.8 effort weeks | USD 24,960 | USD 37,440 |
| Rebuild | 468 | 40 h/week: 11.7 effort weeks | USD 37,440 | USD 56,160 |
Costs are hours multiplied by either chosen rate, USD 80 or USD 120 per hour. Effort weeks divide hours by the stated productive weekly capacity. They do not include external waiting, leave or review-window delays. Hosting, tools, independent specialist review, tax and ongoing operation are excluded and need separate line items.
These are alternative scopes, not stages every app must buy. If inspection finds that the existing approval path is sound, a structural refactor may be unnecessary. If recovery or data migration is broader than assumed, the relevant option needs a new estimate. The MVP estimating guide expands the method without supplying a universal duration for this repair.
- Scope growth: new payment, regulated-data, offline or integration requirements change the example boundary.
- Retained capacity: include the internal people who answer domain questions, review evidence and operate the result.
- Exposure: contain an active leak or compromised credential through the incident process before waiting for a larger architecture decision.
Resourcifi's MVP development team can discuss what to retain and what to repair. Bring repository access, hosting details, known failures, data permissions and the intended live workflow to a prototype hardening discussion so the estimate follows the actual evidence.
Prototype hardening questions
Is a vibe-coded app automatically unsafe?
Does a successful scan establish production readiness?
Can Cursor checkpoints replace a recovery plan?
When does rebuilding make sense?
What do the hardening cost examples assume?
Like this? Get more from Resourcifi in Google Search.
Sources
- Stack Overflow Developer Survey2025, AI survey: use/plans, trust and frustrations, with item response bases. Separate 2025 use/intent and frustration survey items.
- supabase.com, Row Level Security | Supabase Docs. Exposed-table RLS, grants and privileged paths.
- supabase.com, Production Checklist | Supabase Docs. Production access, recovery, infrastructure and email preparation.
- docs.lovable.dev, Security overview - Lovable Documentation. Security scans and limits of their assurance.
- docs.lovable.dev, Deployment, hosting, and ownership options with Lovable - Lovable Documentation. Code/data export and framework-generation differences.
- v0.app, What is v0? | v0 Docs. Prototype deployment and pull-request capabilities.
- cursor.com, Overview | Cursor Docs. Local file checkpoints and agent changes.
- nist.gov, AI Risk Management Framework | NIST. Voluntary AI trustworthiness guidance.
- genai.owasp.org, LLMRisks Archive - OWASP Gen AI Security Project. LLM application injection, output and authority risks.
- Veracode, GenAI Code Security Report, Summer2026 primary interactive report. Summer 2026 security benchmark and method.
- Veracode, Fall2026 GenAI Code Security Update. Fall 2026 benchmark update and rounded complement.
Web & software
Backend Frameworks Comparison
Backend frameworks compared for 2026: Node, Django, Spring, Laravel, Go and more, by performance, ecosystem and use case...
Read guide →
Web & software
Django vs Flask: choosing a Python web framework
Django vs Flask: compare the two leading Python web frameworks on structure, scalability, ORM and learning curve to see w...
Read guide →
Web & software
Engineering bottlenecks: trace the work and test one change
Find engineering bottlenecks through work-item evidence, queue analysis and a bounded experiment. Review waiting, changed...
Read guide →
Web & software
Healthcare technology trends
Healthcare technology trends that matter: AI in clinical workflows, FHIR interoperability, telehealth, wearables and IoMT...
Read guide →
Web & software
Laravel Core Concepts
What is Laravel? A PHP web framework with routing, Eloquent ORM, Blade, and queues built in. The core concepts explained...
Read guide →
Web & software
Magento to Shopify migration: data, redirects and cutover
Plan a Magento to Shopify migration with catalog and checkout checks, data mapping, redirect testing and a rehearsed cuto...
Read guide →
Mobile & apps
25 mobile app ideas worth building, with costs and revenue models
25 mobile app ideas across AI, health, fintech and commerce, with the core features, a sourced build cost range and the m...
Read guide →
Product & UX
AI in UX Design: How AI Is Changing User Experience
How AI is changing UX design: personalization, predictive flows, generative UI and faster research, with real app example...
Read guide →
Mobile & apps
App development tools
The app development tools you actually need, by category: IDEs, frameworks, backend and BaaS, testing, CI/CD, and design...
Read guide →