Production recovery

Stuck with AI another vendor could not ship?

About a third of our AI engagements start exactly there.

Recover the build →
Case studies Book a 30-minute discovery call

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.

Kanika Mathur
By Kanika Mathur, Service Delivery Lead
Reviewed by Resourcifi engineeringPublished Sep 23, 2026Updated Nov 16, 202611 min read
Engineering
A desk by a window with a laptop showing a blurred mobile app prototype of coloured blocks, a second screen with a dark terminal, a printed checklist with empty tick boxes, blank sticky notes on the wall, a small plant and a desk lamp, no people
Key takeaways

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.

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.

38%
Approximately 38% non-pass in the dated Fall vendor security benchmark, not production vulnerability prevalence.
Veracode Fall 2026 update
Review
Verify the actual grants, row policies and privileged-key paths in this app.
Access-control review
66%
Selected almost-right output as a frustration in a multi-select survey item with 31,476 responses.
Stack Overflow 2025; self-selected respondents
  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. Recovery: choose recovery objectives and test data restoration, including reconciliation after a partial action. Supabase's production checklist covers recovery and infrastructure preparation.6
  8. 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.

Two dated vendor benchmark updates
Reported average security pass rates and approximate complements. Summer and Fall are the same vendor study series, not independent replications or production defect measurements.
Dated security benchmark results and rounded complements The pass and non-pass values within each period are complementary. Methods and evaluated model snapshots matter; these are not production vulnerability rates. 0%25%50%75%100% 50% reference 56%62%44%38% Summerpass Fallpass Summernon-pass Fallnon-pass
Reported averages and arithmetic complements
Period/resultReported rate or interpretation
Summer pass~56%
Fall pass62%
Summer non-pass~44%
Fall non-pass~38%
InterpretationDated benchmark, not production prevalence
Sources: Veracode Summer 2026 report and Fall 2026 update.1516 Summer used constrained function-completion prompts and vendor security analysis; noncompiling outputs were not security-analyzed. The Fall update does not state the same task count.

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.

Documented capabilities and project-specific discovery questions
ToolInspectData pathAvailable aidVerify first
LovableInspect generated app and versionConfirm actual hosting/data pathQuick/deep scan scope variesTest grants, policies and export
Bolt.newInspect generated languages and servicesVerify actual integrationDiscover history and export limitsReview server/client boundaries
v0Code and deployable prototypesInspect connected servicesCan open a review pull requestVerify review and release controls
CursorAgent changes in a codebaseExisting project dependenciesLocal file checkpointsTest 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.

Proposed hardening evidence; tailor priority to actual exposure
#AreaCheckDone when
1DataInventory exposed tables and actual grantsAllowed and denied roles tested
2DataReview RLS with grants and privileged pathsOwner, other user and signed-out cases
3DataMatch policies to business rulesTests use realistic restricted records
4SecretsKeep privileged credentials out of clientsBuilt bundles and deployment inspected
5SecretsInvestigate exposed keys and rotate as neededOld credentials and affected access checked
6OutputValidate rendering for each contextRelevant payloads cannot execute
7LogsExclude secrets and protect log structureSensitive values and forged entries tested
8ServerValidate writes and abuse controlsDenied and repeated requests exercised
9PackagesReview applicable dependency findingsVersion, reachability and response recorded
10TestsCover core allowed and denied tasksMeaningful cases run in review workflow
11ReleaseRequire agreed review and acceptanceActual production route follows policy
12EnvironmentsSeparate test data and credentialsTest changes cannot alter live records
13RecoveryChoose backup and restore objectivesRestore and reconciliation exercised
14AccessReview admin and infrastructure controlsCurrent configuration and recovery tested
15EmailCheck auth delivery and launch demandProvider and configured limits verified
16OperationAssign detection and incident responseRelevant 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.

Conditional choices, not automatic triggers for replacement
QuestionHardenRefactorConsider rebuild
Data modelRequired behavior fitsBounded schema migrationTest alternative data boundary
LogicExisting paths are understandableMove specific authority or validationCompare a replacement for incompatible core
StackRequired capabilities demonstratedTargeted component changePrototype blocked requirement elsewhere
UnderstandingOwner can explain and maintainInvestigate opaque areasRebuild only with evidence and migration plan
ExposureContain and test actual pathsRepair sensitive boundariesContain 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.

Alternative hypothetical scopes for one equipment-request prototype
PathHoursCapacity basisAt USD 80/hAt USD 120/h
Harden12030 h/week: 4 effort weeksUSD 9,600USD 14,400
Refactor31240 h/week: 7.8 effort weeksUSD 24,960USD 37,440
Rebuild46840 h/week: 11.7 effort weeksUSD 37,440USD 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.

Frequently asked

Prototype hardening questions

Is a vibe-coded app automatically unsafe?
Inspect its implemented behavior and intended exposure. Generation alone does not prove that controls are absent, just as a deployable demonstration does not establish they work. Test permissions, credentials, code paths, dependencies, recovery and operation against the actual business rules. Keep useful prototype evidence while recording unresolved risks and the decision about what can safely be exposed.
Does a successful scan establish production readiness?
Read the scan’s scope and limitations, investigate findings and test the application’s actual business rules. Lovable says its scans complement professional review. A syntactically valid row policy can still give the wrong person access, and a clean dependency result cannot establish correct approval behavior. Preserve the tested roles, versions, direct-request cases and unresolved exceptions with release evidence.
Can Cursor checkpoints replace a recovery plan?
Cursor checkpoints capture modified files around significant agent changes. They do not restore database state, infrastructure or external effects. For a failed approval, determine whether code rollback leaves a changed record or sent notification behind. Test the actual restore and reconciliation process with an authorized responder, usable access and relevant evidence before relying on it for a live release.
When does rebuilding make sense?
Compare replacement when evidence shows the required behavior cannot reasonably be supported by the current approach. Investigate unknown code and prototype a blocked requirement before making that commitment. A replacement still needs data migration, compatibility, verification and operating ownership. Sensitive data, a framework preference or sunk effort alone should not determine the decision; compare a bounded repair against the same release needs.
What do the hardening cost examples assume?
The internal equipment-request example has four views and employee/approver roles, excluding payments, regulated records, offline work and external integrations. Hardening is 120 allocated hours. Refactor is 312 hours including that hardening plus server approvals and a three-table migration. Replacement is 468 allocated hours including its own controls, acceptance and transition of up to 1,000 requests. Hypothetical 80/120-dollar rates and productive capacity give conditional labor/effort weeks; waiting, tools, specialist review and operation are separate.
Kanika Mathur

Kanika Mathur

Author · Service Delivery Lead, Resourcifi

Kanika Mathur is Service Delivery Lead at Resourcifi. She leads the engineering pods that scope, build and run client software, from mobile apps to AI systems, and she reviews the process and figures in our engineering guides for accuracy.

Resourcifi on LinkedIn →

Like this? Get more from Resourcifi in Google Search.

Sources

  1. Stack Overflow Developer Survey2025, AI survey: use/plans, trust and frustrations, with item response bases. Separate 2025 use/intent and frustration survey items.
  2. supabase.com, Row Level Security | Supabase Docs. Exposed-table RLS, grants and privileged paths.
  3. supabase.com, Production Checklist | Supabase Docs. Production access, recovery, infrastructure and email preparation.
  4. docs.lovable.dev, Security overview - Lovable Documentation. Security scans and limits of their assurance.
  5. docs.lovable.dev, Deployment, hosting, and ownership options with Lovable - Lovable Documentation. Code/data export and framework-generation differences.
  6. v0.app, What is v0? | v0 Docs. Prototype deployment and pull-request capabilities.
  7. cursor.com, Overview | Cursor Docs. Local file checkpoints and agent changes.
  8. nist.gov, AI Risk Management Framework | NIST. Voluntary AI trustworthiness guidance.
  9. genai.owasp.org, LLMRisks Archive - OWASP Gen AI Security Project. LLM application injection, output and authority risks.
  10. Veracode, GenAI Code Security Report, Summer2026 primary interactive report. Summer 2026 security benchmark and method.
  11. Veracode, Fall2026 GenAI Code Security Update. Fall 2026 benchmark update and rounded complement.
Keep reading
Related guides worth your time
All Engineering insights →
Backend Frameworks Comparison 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 → Django vs Flask: choosing a Python web framework 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 → Engineering bottlenecks: trace the work and test one change 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 → Healthcare technology trends Web & software Healthcare technology trends Healthcare technology trends that matter: AI in clinical workflows, FHIR interoperability, telehealth, wearables and IoMT... Read guide → Laravel Core Concepts 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 → Magento to Shopify migration: data, redirects and cutover 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 → 25 mobile app ideas worth building, with costs and revenue models 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 → AI in UX Design: How AI Is Changing User Experience 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 → App development tools 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 →
Bring the repository, data rules and known failures

What can you retain, verify and operate?