Existing software, maintained and developed further.
When the original developers are no longer available, or an in-house team needs more capacity, we take over the codebase and the infrastructure. We fix defects, deliver new features, 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.
A takeover usually starts with software that is in production but has become difficult to change: the knowledge left with the original developers, fixes cause regressions, and deployment is manual.
We review the code, document what we find, and make the system safe to change before extending it.
- Repositories, servers, domains, and accounts are moved to your ownership, and the credentials are documented.
- The code, the data, and the infrastructure: what is at risk, what to fix first, and what to leave alone.
- Backups verified, error tracking and monitoring in place, releases automated (CI/CD), and critical bugs fixed.
- New features and fixes in planned releases, with daily updates during active development.
Bug fixes
Each bug is reproduced in a regression test and fixed at its root cause. Error tracking reports failures in production to us as they happen.
New features
Features ship in small releases you review, follow the conventions of the existing codebase, and come with updated documentation.
Infrastructure and support
Servers, databases, and dependencies are kept up to date, backups are verified by test restores, and alerts reach an engineer who knows the system.
Example of what we deliver.
An ERP for liquid cargo operations: inventory, ownership transfers, blending, and transport documents in one system, with role-based access and a full audit trail. The web and desktop applications share one Rust core, and the desktop application works offline and syncs when the connection returns.
- 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 review the code and the infrastructure first, and document what we find before changing anything.
02Safe to change first
Backups, error tracking, 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, without a new dependency or service unless the fix requires one.
05Regression tests
Each bug is reproduced in a test before it is fixed, which guards against regressions.
06Direct communication
You talk directly to the engineers writing the code, so questions are answered by the people who know the system.
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.