Support, maintenance and takeover
Let us keep your software running.
We take over the system someone else built, the one that stalled, or the one nobody supports any more. A technical audit comes first; after that we maintain and develop it every month under a written service-level agreement (SLA).
Trusted by leading organisations across Türkiye and Europe
01Support, maintenance and takeover
Does one of these sound familiar?
- 01
The firm that built it is gone
The developers moved on or the vendor walked away. The system runs, but nobody can touch it.
- 02
The project stalled
Development stopped before the finish. We assess what is there and either complete it or tell you which part needs rewriting.
- 03
It keeps breaking
Crashes, slowness, outdated dependencies. We find the root cause and put the system on a regular maintenance schedule.
- 04
It needs new features
The system holds up, but the business has grown. Development hours included in the monthly plan let us move without a new contract each time.
02In writing, on every project
What the SLA covers
The commitments are written into the contract, not promised on a call. The maintenance agreements we run today are built on these headings.
Priority classes (P1–P4)
Every request is classed by its impact on your business, and each class has its own written response and resolution targets.
24/7 response on P1
When the system is fully down, nobody waits for office hours — we respond at night and at weekends too.
Planned maintenance and backups
Security patches, dependency upgrades and server maintenance run on a schedule; backup and restore steps are defined in the contract.
Development hours included
A set number of development hours is included each month, so small improvements do not wait for a separate quote.
Monthly report
Incoming requests, resolution times and hours spent are reported in writing every month.
ISO/IEC 20000 framework
Our support, change-management and service-level processes are certified to the ISO/IEC 20000 service-management standard.
03How we work
How a takeover works
- 01
Technical audit
A two-week audit of the architecture, security, test coverage and technical debt.
- 02
Written plan
The audit ends with a plan for gradual improvement or modernisation, with scope and price in writing.
- 03
Handover
Source code, server access and existing documentation move to our team; we fill in whatever documentation is missing.
- 04
Run under the SLA
A monthly agreement keeps the system running, and the included hours carry new work forward.
Yes. Neuros starts every takeover with a two-week technical audit covering architecture, security, test coverage and technical debt. The audit ends with a written plan for gradual improvement or modernisation, after which the system runs under a monthly SLA.
Incidents where the system is fully down are classed P1, and Neuros maintenance agreements commit to 24/7 response on P1 — nobody waits for office hours. Lower-priority requests are handled within the contracted working hours, against target times set for their class.
You do. Every line Neuros writes, together with the intellectual property and documentation, belongs to the client under the contract. When a maintenance agreement ends, the code, access and up-to-date documentation are handed in full to you or to the team you choose.
Tell us about your system; we start with an audit.
Describe what it is and where it stands today in a few sentences. Someone from the engineering team replies within one business day.