Scheduled Maintenance Agreement
On-site checks, updates and a status report at agreed intervals. Response time is committed in the contract.
When your server stops, production stops with it. We manage that risk through scheduled maintenance, continuous monitoring and a response time written into the contract.

After the initial conversation we narrow or widen the scope to match what you need. Quote lines are written against the headings below.
On-site checks, updates and a status report at agreed intervals. Response time is committed in the contract.
On-site intervention across Ankara and the surrounding provinces, with first-level diagnosis handled remotely.
A backup policy designed for your systems, with regular restore drills and a retention plan that is actually followed.
Critical systems identified, outage scenarios written out and recovery time objectives agreed.
Continuous monitoring of server, disk and service health, with alerts on threshold breaches and preventive action.
We map the current infrastructure and report the risks, single points of failure and components past their service life.
Which system is covered, how often and with what response time, all written down before work starts.
Planned maintenance, continuous monitoring and periodic reporting.
Scope reassessed as the infrastructure grows and priorities change.
If your question is not here, ask directly and we will settle it in the meeting.
Which systems are in scope, how often they are checked, the committed response time, whether spare parts are included and how out-of-scope work is priced. Anything left vague at signing becomes a dispute during an outage.
The response time is agreed per contract and depends on how critical the system is. It is the single number worth negotiating hardest, because it defines how long production can stop.
Yes, and this is the step most often skipped. A backup that has never been restored is an assumption. Restore drills are part of the agreement and the result is reported.