Web application repair and modernization
We identify the causes of errors and slowdowns, then prioritize repairs by business impact. Application modernization follows in stages, with checks at each release.
Assessment, repairs and modernization
Assessment
Code, key journeys and dependencies, tested as a visitor and as a signed-in user.
Repair and stabilization
Broken journeys, exposed data and slow pages, then tests, backups and monitoring.
Modernization
Runtime, framework and database upgraded step by step.
What changes
TodayEvery fix breaks something else.
With AL+Tests around the risky parts before anything changes.
TodayYou don't know what is wrong or what it costs.
With AL+A written report, ranked by cost to the business.
TodayThe platform is out of support.
With AL+Upgrades in steps that each ship on their own.
What we often find
Common in apps made by any team, including those built with AI app builders such as Lovable, Bolt, Replit, v0 or Cursor.
Anyone can read the database
Access rules are off or too broad. On Supabase these are Row Level Security rules.
Secret keys in the browser
Payment or email keys shipped in front-end code.
Login that only looks secure
Permissions checked in the browser, not on the server.
An unsupported platform
The framework, runtime or database no longer gets security fixes.
From diagnosis to repairs
Fixed-price assessment
What we examine, the access you can give and the report you get.
Ranked findings
What to fix first, with a separate offer for the repairs.
Repair, then modernize
Each step tested and shown to you; you can stop after any of them.
Products built by AL+
We built PostDeploy to keep production errors, their logs and the release that was live in one place, so a fix starts from evidence.
Who this is for
A good fit
Web applications, SaaS products and APIs with real users that must keep running during the repair.
Look elsewhere if
A mainframe, an ERP, or a rewrite with a fixed launch date and no plan for the years after.
Questions
Can you fix my app without rebuilding it?
Usually. We keep what works and repair the rest. We recommend a rebuild only if the assessment shows repair would cost more.
How is it priced?
The assessment has one fixed price. Each repair and modernization step is priced in writing before it starts.
Can our developers keep working on it?
Yes. Changes go into a repository your company owns, with tests and notes.
Further reading
Vibe coding cleanup: how to hire help for your app
Need help with an AI-built app? Define the failure, agree a repair scope, and ask for evidence on permissions, recovery, deployments and tests.
Production-readiness checklist for AI-generated applications
Thirty concrete checks that separate a working AI-generated (vibe-coded) prototype from production software: security, data, failure handling, operations, coherence, dependencies, and ownership.
Repair or rewrite?
A rewrite is a conclusion you reach after understanding a system, not a starting point. Most systems proposed for rewrite need an owner, a plan, and a few months of repair.
AI-built software still needs an engineer
AI changes how code is produced. It does not remove technical responsibility. Software generated quickly still needs someone who understands it and answers for it in production.
What is failing in your application?
Describe the problem and its effect on users. We establish the access needed and what the assessment will cover.
Or copy the address: paul@alplustech.com