Software takeover · fixed-price assessment · EU contract
We take over business-critical custom software that nobody on your side fully understands anymore: assess it in 10 working days, make it stable, and keep it running under a monthly agreement.
Access under your NDA. No commitment beyond the assessment. You keep the report whatever you decide.
When companies call us
60-second stack check
Tick what you run. Dates are the end of official security support from each vendor.
no security patches ends within 12 months supported
Your stack check
Tick what your system runs on.
Software past its end of life gets no more security fixes. An unpatched framework is an open door, not a theoretical risk.
Good news. Keep a monthly patch routine and an SBOM for what you ship.
How a takeover works
Each step has its own price and its own deliverable. Nothing is bundled, nothing is hidden in the monthly fee.
Rules we work by
Takeover assessment10 working days · €5–10k
We read the code, infrastructure and data, talk to whoever still knows anything, and write down what the system does, where it will break next and what it costs to keep alive.
Stabilisation4–12 weeks · €20–80k
The fixes from the assessment, in order of risk: backups and restore, deployment from a clean machine, monitoring, critical bugs, security patches, documentation.
Ongoing engineeringmonthly · €3–8k
A named lead engineer, agreed hours for changes and a response time for incidents: one business day as standard, faster or 24/7 by agreement.
The assessment
System map
Components, integrations, data flows, external services and who pays for them.
Risk register
What will break next, how likely, how bad, and what it costs to prevent.
Operational check
Can it be deployed from scratch? Are backups restorable? Who holds the credentials?
Code and dependency review
Outdated libraries, known vulnerabilities, parts nobody should touch without tests.
Plan and price
A stabilisation plan in order of risk, a fixed price for step 2 and a monthly figure for step 3.
PHPJavaNode.jsPythonGoReact / AngularAWS / KubernetesWooCommerce / Magento
Proof, not promises
FAQ
No. Each step has its own price and deliverable. You can stop after the assessment and keep the report — it is written so that any competent team can act on it.
PHP, Java, Node.js, Python, Go, React and Angular front ends, AWS and Kubernetes infrastructure, WooCommerce and Magento shops. If it is something rarer, we tell you on the first call whether we have the people.
Read access to the repository, servers and any documentation (after we sign your NDA), one or two hours with the people who use the system daily, whatever is left from the previous developer, and a decision-maker for a 60-minute readout.
Yes, step by step: an API layer in front of the old code, the most fragile parts replaced first, data migrated with checks. Big-bang rewrites are rarely the cheapest path.
Security patches and dependency updates are part of stabilisation. If you need an outside view first, start with our external security assessment.
Related
Next step
Describe it in a few sentences on a 30-minute call. No access needed yet. If it fits, you get a fixed price for the assessment.
You will talk to
Gleb Zamyslovsky
Executive Officer · Warsaw
One reply within a business day: questions, a fixed price, or an honest “not worth it”. No account managers in between.
