Software you already run, fixed and developed further.
When the original developer has moved on, or the team can no longer keep up, we take over the code and the servers. We fix what is broken, add the features on your list, and keep the system updated, backed up, and monitored.
- Code and infrastructure review
- Bug fixing
- New features
- Performance fixes
- Security updates
- Dependency upgrades
- Hosting and servers
- Backups and restores
- Monitoring and alerts
- Automated releases (CI/CD)
- Documentation
- White-label support for agencies
What we take over.
Most takeovers start with software that works but that nobody can change safely any more: the original developer has moved on, bugs come back after each fix, and releases are deployed by hand.
We read the code, write down what we find, and make the system safe to change before we add to it.
- Access in your nameRepositories, servers, domains, and accounts are moved to your ownership, and the credentials are documented.
- A written reviewThe code, the data, and the infrastructure: what is at risk, what to fix first, and what to leave alone.
- Safe to changeBackups tested, error reports and monitoring on, releases automated, and the urgent bugs fixed.
- Development continuesNew features and fixes in planned releases, with a written update every week.
Bug fixes
Each bug is reproduced in a test, fixed at its cause, and stays fixed. Errors in production reach us before your users write in.
New features
Features are added in small releases you review, in the codebase's existing style, with the documentation updated alongside.
Infrastructure and support
Servers, databases, and dependencies kept updated, backups restored in tests, and alerts on, with engineers to call when something breaks.
Example of what we deliver.
An ERP for liquid cargo operations: inventory, ownership transfers, blending, and transport documents in one system, with roles, an audit entry behind every change, and printable documents. A web application and a desktop application share one Rust core, and the desktop app keeps working when a terminal loses connectivity.
- 96%of operations recorded on the day they happen, from a little over half
- 79%faster to close the month (from two weeks to three days)
How we work.
01Read before we change
We read the code and the infrastructure first, and write down what we find before we fix anything.
02Safe to change first
Backups, error reports, and automated releases come before new features.
03Respect the existing code
We follow the codebase's structure and style, and rewrite a part only when a fix cannot hold otherwise.
04No overengineering
The simplest change that solves the problem. Fewer moving parts, fewer surprises.
05Every fix tested
A bug is reproduced in a test before it is fixed, so it does not come back.
06Direct communication
You talk to the engineers writing the code, and you get a written status update every week.
07Yours to keep
Repositories, servers, and accounts stay in your name, and the documentation is updated with every release.
08Fair price, no surprises
A monthly plan for continued development, or a fixed quote for a single piece of work, agreed before we start.
Questions about this service
What do you need to take over our software?
Access to the code repository, the servers or hosting accounts, and whatever documentation exists. Where something is missing, we reconstruct it and tell you what could not be recovered.
The previous developer is not available. Can you still take over?
Yes. Most takeovers start that way. We work from the code and the running system, and the written review lists what is still unclear.
Will you rewrite everything?
No. We keep what works and change what blocks fixes or features. A rewrite is proposed only with its reasons and cost, as a separate decision.
Which technologies do you take over?
Most web, desktop, and backend stacks: TypeScript and JavaScript, Java, C#, Python, Rust, C++, and SQL databases. For a stack we know less well, we say so after the review.
Can you support software for our clients under our brand?
Yes. Agencies bring us projects for their clients. We work in your repository, follow your process, and the work goes out under your name.