// services
I take over web applications that nobody fully owns anymore.
The agency moved on, the freelancer stopped answering or the in-house developer left. Credentials are scattered, nobody knows how deployment works and every incident turns into an investigation.
I take the application over in a structured way: recover and document access, audit the code, infrastructure and data, close the urgent risks and give you a stabilization roadmap — then stay on as the technical owner if you need one.
01 // fit
This service is for you if…
- the person who built or maintained the application is gone;
- you are not sure who has access to the servers, domains or third-party services;
- nobody can say with confidence how to deploy a change;
- the application handles payments, customer data or critical processes — and that worries you;
- you need someone to take responsibility, not just to fix one bug;
- you plan to grow the product and need to know what you are building on.
02 // scope
Scope of work
- scope/01
Access recovery
Repository, hosting, domains, DNS, databases and third-party accounts — collected, verified and moved under your control.
- scope/02
Infrastructure review
Servers, containers, backups, monitoring and hosting costs.
- scope/03
Deployment
How the application is built and released today, and a reproducible pipeline to replace the manual steps.
- scope/04
Code and database
Architecture, dependencies, data model, critical business processes and their weak points.
- scope/05
Security risks
Outdated packages, exposed services, secrets in the code and risky permissions — ranked by impact.
- scope/06
Stabilization roadmap
A documented plan: what to fix now, what to schedule and what can wait, with estimates.
03 // diagram
The takeover audit, item by item
Every takeover goes through the same checklist. Each item moves from unknown to documented, so at the end you know exactly what you own and what it depends on.
- unknown — not yet reviewed
- checking — under review
- verified — confirmed to work
- documented — written down for you
- 01repository accessunknowncheckingverifieddocumented
- 02infrastructureunknowncheckingverifieddocumented
- 03deploymentunknowncheckingverifieddocumented
- 04databaseunknowncheckingverifieddocumented
- 05integrationsunknowncheckingverifieddocumented
- 06security risksunknowncheckingverifieddocumented
- 07documentationunknowncheckingverifieddocumented
- 08stabilization roadmapunknowncheckingverifieddocumented
04 // pipeline.yml
How the work goes
- ~1 wkaudit:takeover
Takeover audit
Access, infrastructure, deployment, code and data reviewed and written down.
→ audit report - ~1 wkplan:roadmap
Plan
Risks ranked by business impact and a stabilization roadmap with estimates.
→ stabilization roadmap - weeksfix:stabilize
Stabilization
Urgent risks closed first: access, backups, deployment and critical bugs.
→ controlled system - per releasedeploy:release
Release
Changes released through a documented, repeatable process.
→ safe releases - ongoingsupport:ongoing
Ongoing ownership
Monitoring, updates and development as your long-term technical owner.
→ owned product
05 // outcomes
What you can expect
- All access in your hands — documented and verified.
- A clear picture of the system: architecture, infrastructure, data and dependencies.
- Urgent security and stability risks addressed first.
- A deployment process that does not depend on one person’s memory.
- A roadmap you can plan budget and features around.
06 // stack
Technology involved
Takeovers rarely come with a stack of your choice — these are the technologies I can take responsibility for.
07 // evidence
Where I have done this before
Long-term ownership is at the core of how I work: I joined a fintech platform in 2020 and have been responsible for it ever since.
- 6 years with one product client, since April 2020.
- 99.9% production uptime, kept by resolving incidents, removing recurring failure modes and hardening critical services.
- Data models with 150M+ row tables across MariaDB, MySQL and MongoDB.
- CI/CD with GitHub Actions, GitLab CI and Bitbucket Pipelines in place of manual releases.
08 // faq
Questions clients ask first
What if we no longer have some of the credentials?
That is common. Recovering access — through hosting providers, domain registrars or account owners — is the first part of the audit, and everything recovered is moved under your company’s control.
How long does the takeover audit take?
For a typical application, about a week for the audit and another week for the roadmap. Large or completely undocumented systems take longer; you will know the timeline before the work starts.
Do you need the previous developer?
No, although a short handover call helps if it is possible. The audit is designed to work from the code, infrastructure and data alone.
Will you change everything?
No. The goal is control and stability first. Changes are made where they reduce risk or unblock the business, in small steps you can review.
Can you stay on after the takeover?
Yes. Many takeovers turn into ongoing maintenance on a monthly retainer — the person who audited the system is the best placed to keep it running.
What do you need from us to start?
A contact who knows the business processes, whatever access you still have and a short list of what hurts most right now.
09 // related
Related services
- legacy.phpLegacy PHP & Vue maintenanceYour PHP or Vue application still runs the business, but nobody wants to touch it. I stabilize it, document it and get development moving again.Legacy PHP & Vue maintenance and stabilization →
- nuxt.config.tsNuxt & Vue developmentSSR, SEO, performance, API integrations and complex interfaces — Vue and Nuxt applications built to run in production, not just in a demo.Nuxt & Vue development for production products →
git push --message
Inherited an application nobody owns?
Tell me what you have — even if it is only a domain and a server login. I reply within one working day with the first questions and next steps.