Keep
Fix and secure
The application runs but has open defects, outdated dependencies or security issues. We stabilise, update and add monitoring.
Maintenance and modernisation.
We take over existing applications, bring them into a secure state and replace legacy systems without throwing away the knowledge inside them.
Three ways to make an existing application viable again.
A rebuild is rarely the first answer. Usually there is a cheaper route that preserves the domain knowledge inside the application.
Renew
Modernise step by step
Functions are renewed one after another while the application stays in production. Users notice improvements, not migrations.
Replace
Swap components
Individual parts are replaced, for example the interface or the database, while the rest stays. For a measurement technology client we replaced a database application with a web interface this way.
What a handover covers.
Before we take responsibility, we give you and ourselves a complete picture.
- Source code, dependencies and how current they are, including known security issues
- Operating environment: where the application runs, who has access, how it is backed up
- Active contracts, licences and certificates with their expiry dates
- Existing documentation and the gaps in it
- An assessment: keep, renew or replace, with reasoning and effort
The result is a condition report that is useful even if you continue with someone else.
Proactive instead of reactive.
Monitoring
Systems and applications are watched. Anomalies reach us, not you.
Health checks
Regular review of dependencies, certificates, backups and capacity.
Roadmap
Upcoming updates and larger changes are planned instead of arriving as a surprise.
A named contact
One person who knows your application, with a team behind them for cover.
You are not sure what condition your software is in.
That is the most common reason for this conversation. A survey creates clarity before something fails.
Frequently asked questions
Do you take over software built by someone else?
Yes, that is a regular case. We start with a survey: source code, dependencies, operations, known security issues and documentation. Afterwards you know the condition of the application and what a handover means, before you commit.
Our developer is no longer reachable. What now?
Then you first need access and an overview: where the application runs, who holds the credentials, where the source code sits, when certificates and contracts expire. That survey is the first step and it is useful regardless of whether we continue afterwards.
Modernise or rebuild?
It depends on how much domain knowledge sits inside the old application and how stable it runs. A working application with a dated interface is rarely a case for a rebuild. An application without tests, without documentation and with discontinued dependencies often is. We tell you what we consider right, even when the rebuild would be the larger project for us.
What does proactive maintenance mean?
That we get in touch before you notice anything. We monitor systems and progress, run regular health checks and plan updates instead of waiting for incidents. Our principle is to find causes and prevent outages rather than earn money from them.
How fast do you react to an incident?
That depends on the agreed scope. We offer support as a monthly flat rate or per case, and we put response times in writing before the case occurs.
What about documentation?
We document continuously, not at the end: concept, technologies used, operations and a quick-start guide for new developers. That is why a handover inside our team works, and it protects you from dependency.
Michael Lanik
Head of Sales, Associate Partner
Tell us in 30 minutes what this is about. Afterwards you know whether and how we can help.