SysaiQ
FA Start a project

[ SYSAIQ—SERVICE / SUPPORT-MAINTENANCE ]

Support and maintenance

What has been built must stay healthy, current and secure: monitoring, backups, bug fixes and small changes under one clear plan.

Start a project

Who this is for

  • Clients whose project was built by SysaiQ and who want to continue with peace of mind after the warranty period.
  • Businesses with a site or system whose original developer is no longer available, or whose code they own.
  • Organisations without an in-house technical team that need one clear point of contact for problems and changes.
  • Critical systems that must have regular backups and health monitoring.

Problems it solves

  • Outages nobody notices: automated monitoring checks the site and server and raises the alarm before your customers do.
  • Data loss: scheduled backups with periodic restore tests.
  • Security exposure: server, dependency and certificate updates are applied regularly.
  • Small changes that wait for weeks: requests are logged, prioritised and handled within the agreed framework.
  • Not knowing who is responsible: one point of contact, one way to log requests and a periodic status report.

Deliverables

  • Automated monitoring of site, server and HTTPS certificate availability, with alerts
  • Scheduled database and file backups with periodic restore tests
  • Security updates for the server and software dependencies
  • Bug fixes and small content and technical changes within the agreed framework
  • A request-logging channel and response times by severity, as stated in the written proposal
  • Periodic report: status, work done and recommendations

How the work runs

  1. 01

    Discovery

    We review the site or system, server, code and the current state of backups and security, and list the maintenance needs.

  2. 02

    Written proposal

    You receive the support scope, response times by severity, the monthly change allowance and cost in writing.

  3. 03

    Contract

    The contract is signed in person in Qazvin or electronically, and support periods are paid against periodic invoices.

  4. 04

    Staged build

    In the first month, monitoring, backups and overdue updates are put in place, and existing problems are prioritised and fixed.

  5. 05

    Handover and training

    You are shown the request channel and reports, and a system status document is handed over.

  6. 06

    Support

    Support continues period by period; at the end of each period you receive a status report and recommendations, and renewal is by mutual agreement.

Timeline

Support is an ongoing service, not a project with an end date. Initial setup (monitoring, backups, overdue updates) depends on the system's current state. Response time for each request depends on its severity, and the exact figures are stated in the written proposal.

How cost is calculated

Cost is calculated from:

  • The number and complexity of sites or systems under support
  • The response level: hours and severities covered
  • The monthly change allowance (hours or number of requests)
  • Monitoring and backups: number of servers and data volume
  • Whether the system was built by SysaiQ or needs an initial code review

Included: monitoring, backups, updates, bug fixes, changes within the agreed allowance and the periodic report.

Not included, agreed separately: new feature development beyond the monthly allowance, plus server, domain and external services, which are in your name.

The periodic fee is stated in the written proposal.

Read more about how cost is calculated →

Frequently asked questions

Yes, provided you own the code and credentials. We first review the code and server, and the proposal states what can be supported and what must be fixed first.

It depends on severity: a full outage is not the same as changing a page's text. Response times by severity are set in the written proposal, and we hold to them.

Yes. One-off work is done under a separate written proposal, but without contractual priority or response times. For systems in active use, a support plan is recommended.

On storage in your name, separate from the main server, so a server failure cannot harm the backup. Retention and frequency are set in the written proposal, and restores are tested periodically.

No dependency is created. Code, server, backups and every credential are in your name from the start, and at the end of the period you receive a system status document so anyone else can continue.

Let us talk about your project

Write a few lines about your business and the problem you want solved; you receive a written proposal before any commitment.

Start a project All services