Your app back under control, even without documentation.
The previous vendor is gone, there is no documentation, and every change breaks something else. The first step is an audit that shows the state of the code and infrastructure. Then a plan and modernisation in stages, without stopping the business.
- Audit report stays with you, no strings attached
- 100% of code and access in your company’s name
- 2 working days to a quote after the call
The app works, but nobody wants to touch it.
- 01
The vendor is gone
The company that built the app does not answer, raised its rates or no longer exists. What is left is the code, a server and passwords scattered across e-mails.
- 02
No documentation
Nobody knows how to set the project up from scratch, where the backups are or which parts are still in use.
- 03
Outdated technology
An old framework and libraries without security patches. Every update gets postponed because nobody knows what will break.
- 04
Every change breaks something
Without tests, a small fix in one place causes a bug in another. Development slows down and costs go up.
What the takeover covers.
Audit
- Review of code, architecture and dependencies
- Security, access and backups
- Infrastructure state and cost
- A report with risks and an action plan
Takeover
- Repository, accounts and access moved to your company
- Staging environment and automated deployments
- Setup and architecture documentation
- Tests of the key paths before any change
Modernisation
- Framework and library upgrades
- A move to the cloud or a new server
- Rewriting the most troublesome parts
- New features on a clean foundation
From an audit to a stable system.
- 01 audit scope
Call and access
What works, what causes trouble and what you have access to today. The audit scope is based on that.
- 02 report
Audit
A review of the code, infrastructure and security. You get a report with risks, priorities and a cost estimate, even if you decide not to continue.
- 03 stable system
Stabilisation
Access moved to your company, backups, monitoring, tests and automated deployments. From then on every change goes through tests.
- 04 next stages
Modernisation in stages
Upgrades and rewrites of further parts in the order set by the audit, while the system keeps running.
What a takeover costs.
The first step is an audit priced on its own, because without it any modernisation price would be guesswork. After a free consultation you get a quote for the audit within 2 working days, and after the audit a plan and a quote for the next stages.
Always included
- An audit report that stays with you
- Access moved to your company
- Setup and architecture documentation
- Tests before every larger change
- Full access to the code and infrastructure
What drives the price
- Size and age of the application
- Technology and state of dependencies
- Access to code, documentation and passwords
- Scope of modernisation
- Traffic and availability requirements
Technologies that are easy to take over.
-
Python and Django
The core specialism, including old versions that need upgrading step by step, one release at a time.
-
TypeScript, React and Next.js
The front end taken over together with the back end or rewritten gradually, screen by screen, without rebuilding everything from scratch.
-
Node.js and Express
Services in JavaScript and TypeScript, upgraded or restructured.
-
Docker, Terraform and CI/CD
An environment described in code and automated deployments, so the app no longer depends on the one person who knows how to run it.
Questions about audits and modernisation.
Yours is not here? Ask during the consultation or send a message.
-
No, not every one. Python, Django, TypeScript, React, Next.js and Node.js are everyday work. For other technologies you get an honest answer at the consultation.
-
That is common. The first step is to establish what is in your hands and what to ask the previous vendor or hosting provider for.
-
Usually not. A rewrite is expensive and risky, and most applications can be fixed in stages. The audit shows which parts are worth keeping and which should go.
-
No. The report stays with you and you can take it to any vendor.
-
Yes, the work is planned so the system keeps running. Changes are made in stages and go to staging first, and larger switches happen in the quietest hours.
-
You do. The repository, cloud accounts and domains are moved to your company so the situation with the previous vendor does not repeat.
The first step is a 30-minute call.
No fees and no strings attached. Describe what you want to build or improve. Within 2 working days you get a quote and a plan, or an honest note that a simpler solution will do.