Does this sound familiar?
- The software that runs your bookings, invoicing or production was built by one developer. They are leaving, or already gone.
- The system feels like a black box. If it breaks, you do not know who to call.
- The people you ask want to rebuild it from scratch. Expensive, risky, and you throw away something that works.
- You really want just one thing: for it to keep running, and someone who picks it up when something comes up.
That is exactly what we are here for. A business-critical system belongs in the hands of people who keep it alive, not hanging on one person who will soon be gone.
What we do
We take over your Java application and become your single point of contact. Spring Boot, Quarkus, Jakarta EE or older Java: we know it.
- Take it over: we map the system methodically and take it over in a controlled way.
- Keep it running: hosting, monitoring, updates and backups. If something breaks, we fix it.
- Maintain it: security updates, patches and keeping the entire runtime layer running are part of the monthly fee. Bug fixes and small changes to the application itself get a fixed price per job, agreed up front, so no surprises.
- Keep developing it: new features when you need them. One partner for hosting, maintenance and development, if you want that.
Why this is our kind of work
- Deep Java experience: we have written Java for 25 years and have run Java platforms in production daily since 2008, with a background in enterprise Java at large organisations in finance, telecom and government.
- We run a range of different systems for our clients, from an energy startup to logistics and recruitment. Taking over a system someone else built is simply our work.
- No rewrite: we keep what works and build on it carefully. A rewrite is risk and cost you do not need.
- Continuity: you always keep your code, your data and admin access. No lock-in, you can always walk away.
- Dutch infrastructure: owned hardware in Dutch datacenters, data stays in the EU. We are working toward ISO 27001 certification.
No rewrite, but an orderly handover
The biggest risk is that your developer is gone before anyone else knows the system. That is why, during handover, we work alongside your current developer for as long as they are still around. We document, we ask questions, and we take it over in a controlled way. The more overlap, the more robust and the cheaper the takeover: transferring knowledge with the developer in the room beats reconstructing it afterwards. Is your developer leaving at the end of December? Then start in September. Has your developer already left? That is still solvable: we dig into the system and take it over step by step, but count on more discovery work in the setup.
A takeover with a plan
The takeover itself is the most critical part, so we do not do it on the side. The one-time takeover setup covers discovery of the system, the handover with the departing maintainer, a runbook, and a verified restore: we actually restore your application from backup and document how. So you know recovery works before you ever have to rely on it.
The takeover setup is a one-time fee from €950. You get the exact amount after the assessment, fixed and up front, before you commit to anything. After that you pay a fixed monthly fee: a managed application stack starts at €550 per month all-in, and for P1 incidents on production we also respond outside office hours. A system like most of our clients run (application plus its own database, coverage outside office hours too): €950 one-time, then €700 per month. Seeing lower starting prices elsewhere on the site? Those apply to self-managed setups or standard workloads on our shared platform. A taken-over application gets its own managed stack. For an application without its own maintainer, this is the honest comparison.
Common concerns
Can you understand a system someone else built?
Yes, that is exactly our work. We have written Java for 25 years, have run Java platforms in production since 2008, and manage a range of different systems for our clients. During handover we work alongside your current developer for as long as they are still around.
Are you going to force me to rebuild it?
No. We keep what works and build on it carefully. A rewrite is risk and cost you do not need.
What if the software is poorly documented?
Then we read in, run it, and work out how it fits together. Thin documentation is not a showstopper, we see it often.
What if you disappear too?
That is exactly what the takeover prepares for. The runbook and the documentation mean the knowledge of your system is written down, not stored in one head. On top of that, we work with a fixed circle of partner companies who share the on-call load and can step in with that same documentation. And as the final guarantee, you always keep your code, your data and admin access.
Am I just trading one dependency for another?
No, that is exactly what the takeover setup prevents. The runbook, the documentation and the verified restore make the system independent of any one person: you trade a head full of knowledge for a system that is described and tested. And you always keep your code, your data and admin access.
Is this going to be expensive or full of surprises?
No surprises: you know the numbers before we start. The takeover itself is a one-time setup from €950. After that you pay a fixed monthly fee: a managed application stack starts at €550 per month, all-in. Anything beyond that gets a fixed price per job, agreed up front, no after-the-fact billing.
Can you keep developing the system as well?
Yes. Hosting, maintenance and development from one partner. New features are agreed up front, per job.
How it works
- Intro and assessment: you tell us what you run and where it hurts. We look at the system, under an NDA if you prefer.
- Handover: the one-time takeover with a plan, with overlap with your current developer where possible.
- Management: a fixed monthly fee for hosting, maintenance and support, from €550 per month. Fixed price, no after-the-fact billing.
- Further development: only when you need it, agreed up front, per job.
Are you the departing developer, or the shop that built the application? Read how we work with shops and developers. An introduction doesn't cost you your client.
