We take over your codebase when your developer disappears
For business owners whose app works today but depends on someone who stopped answering. We take it over, make it safe, and keep it running.
What this feels like
You don't have the keys
The code sits in someone else's repository, the hosting is on their card and the domain is in their name. First we sort out access.
Nobody knows how it works
There is no documentation and no one to ask. The risk isn't only bugs. It's that you can't tell which ones exist.
Something is about to expire
Certificates, API keys, a framework version, a payment integration. Small things that quietly break a live app.
You can't tell good code from bad
You need an independent read on whether to keep building on it or replace it, from someone with no stake in selling you a rewrite.
What you get
- Repository, hosting, domain and third-party accounts moved into your name
- A written audit of the code, the infrastructure and the risks, in plain English
- Urgent fixes done first: backups, expiring credentials, security holes, anything about to break
- An honest recommendation to keep, repair or rebuild, and a plan for the next steps
How a takeover works
Step 1
Get access safely
We work out where everything lives and how to recover each account. Where the former developer is reachable, we ask for a clean handover. Where they aren't, we use the registrar and provider recovery routes.
Step 2
Stabilize
Set up backups, monitoring and a separate staging copy. Fix what could take the app down this month.
Step 3
Audit and report
We read the code, the dependencies and the deployment, then write up what's sound, what's risky and what it would cost to fix.
Step 4
Keep it moving
Continue with fixes and new features, or move to a monthly care plan so the app has an owner again.
Work behind this
Credit Karma
Web applications for credit monitoring and personalized recommendations, with A/B testing.
See the workTwilio
Developer tools and hackathon projects on Twilio's communication APIs.
See the workShipKit
Our own production Next.js framework: auth, payments, CMS and multi-tenant support.
See the workCommon questions
Tell us what you're working on.
A 30-minute call with the people who would do the work. If we're not the right fit, we'll say so.