Guides for when an app is broken, a launch has stalled or the original developer is gone: how to triage it, what to secure first, and how RAITHub takes over and stabilises a codebase without rewriting everything.
What connecting a Lovable project to GitHub actually gives you, and the ten steps after it: company-owned accounts, a local build, a branch strategy that keeps Lovable and developers out of each other's way, a secrets audit, CI, first tests, the database, hosting choices and a clean handover to a developer.
Read articleA 30-day, week-by-week plan for turning a prototype built with Lovable, Bolt, Cursor or another AI tool into software you can put customers on: a two-day freeze, then security, tests and CI, observability and backups, and load, cost and a launch gate, with the SQL, CI and config samples for each step.
Read articleA practical guide to getting your code back from a freelancer or agency who is still reachable: what a complete handover includes, how repository and hosting transfers actually work, how to prove the code is complete, whether you own what you paid for, the contract clauses that protect you, and when source code escrow is worth it.
Read articleA 25-item checklist for accepting a software handover from a developer or agency, grouped into accounts, repositories, infrastructure, secrets, documentation, tests, data and licences. Each item says how to verify it yourself, which items must be done before the final payment, and what to do when a developer will not hand something over.
Read articleA day-by-day plan for the first week after a freelancer hands over a codebase: a recorded walkthrough and access on day one, a clean build on day two, production parity on day three, secrets and dependencies on day four, and a first small change shipped and rolled back on day five, ending with a one-page takeover note.
Read articleThe rewrite-or-refactor argument is usually settled by whoever argues loudest. It should be settled by a short paid audit that measures the codebase. What the audit should check, a decision table that maps evidence to a verdict, and how a live system is upgraded incrementally without a rewrite.
Read articleWhat you should get from a code rescue or project takeover service, what moves the price, published 2026 market ranges from other agencies, typical timelines, and an honest comparison of freelancers, agencies and RAITHub, including when RAITHub is the wrong choice.
Read articleWhat a single bug fix should include, why two bugs that look alike can differ tenfold in cost, 2026 market rates for freelancers and agencies, hourly versus fixed price, and how RAITHub handles "fix a specific issue" jobs, including when to hire someone else.
Read articleWhat to do when a freelancer ghosts you or an agency stops responding: a nine-account access inventory, the order to lock things down, how to recover accounts held in someone else's name, the contract and IP questions to ask a lawyer, and how to judge the code you get back.
Read articleWhy an app built with Lovable, Bolt or Cursor works in the preview and breaks in production, the 10 gaps to check (secrets, authorization, validation, tests, logging, config drift, dependencies, rate limits, migrations and cost), a 10-minute test for each, and the fix.
Read articleA step-by-step playbook for taking over an abandoned or inherited codebase: secure access in the first 48 hours, run a 2-week diagnostic, stabilise checkout, auth, payments and data, decide what to keep or replace, and hand back with runbooks. Includes worked diagnostic examples and an honest section on when a rewrite is the right call.
Read article