Maintenance and Support

An SLA contract, daily backups and round-the-clock monitoring for your site.

Launching a website is not the finish line. Security patches ship every month, SSL certificates expire, databases grow, and vulnerabilities get published in libraries that had been stable for years. CodeOrigins has been maintaining websites and applications since 2022, under contracts with response times written down rather than promised verbally.

Our support is proactive rather than reactive. We do not wait for your phone call: monitoring usually tells us about a problem before your customers notice anything is wrong, and often before it becomes visible at all.

What the SLA actually covers

An SLA is a document with real numbers in it, not a promise to help. Critical issues — the site is down, payments are failing — are picked up within one hour. Important but non-blocking issues are handled the same working day. Routine requests and changes take one to three working days. The plan also includes a fixed monthly allowance of hours for content and functional changes, so that every small request does not turn into a separate quote and a separate negotiation.

Backups and restore testing

A backup is only worth something if the restore has been tested. We configure automated daily backups of both database and files, stored in a separate location rather than on the same server as the site itself. Retention is typically 30 days, with daily copies for recent days and weekly copies for older periods. We periodically run restore drills into an isolated environment, so that a real incident is not the moment you discover the archives were corrupt.

Security patching and hardening

Most sites are not broken into by a targeted attacker but by automated scanners that find one unpatched library or plugin. We track security advisories for the framework and every dependency, apply updates first to a staging environment and only then to production. We configure automatic SSL renewal, admin area protection, brute-force login limits and correct file permissions. Suspicious activity triggers an alert, and we respond the same day rather than at the next scheduled review.

Monitoring and incident response

Uptime is checked every minute from several locations. Beyond availability we track page response times, server disk and memory usage, slow database queries and the application error stream. When an incident happens we follow a defined runbook: isolate the problem, apply a temporary fix to restore service, then eliminate the root cause. After every serious incident you receive a written report explaining what happened and what changed so it does not repeat.

Version upgrades: Laravel, PHP, Flutter, mobile SDKs

Every project under maintenance is moved to new framework and language versions instead of staying frozen on the version it launched with. When a new major Laravel release ships (for example Laravel 14), every Laravel site we maintain is upgraded to it; the same applies to PHP, Node.js, Vue/Nuxt, Flutter, the iOS and Android SDKs and the databases. The upgrade first runs on a staging copy with automated and manual checks, then goes to production with a backup taken beforehand. The result is a site or app that still receives security updates years later and keeps meeting the current App Store and Google Play requirements.

How we work

01

Technical audit

We review the code, server, backups and security posture, and produce a written list of the risks we found.

02

Plan selection

We agree the support level — response times and monthly hours — and record it in the SLA contract.

03

Infrastructure setup

We enable monitoring, automated backups, log collection and the alerting channels your team will actually read.

04

Monthly work and reporting

We apply updates and changes, and send a report of the work done at the end of each month.

Technology

  • Laravel
  • Nginx
  • MySQL
  • Redis
  • Docker
  • Git
  • Uptime monitoring

Selected work

The lecturer speaks their language, the student hears theirs: real-time AI translation — Maintenance and Support
The lecturer speaks their language, the student hears theirs: real-time AI translation
A timetable that builds itself: an AI system for a school — Maintenance and Support
A timetable that builds itself: an AI system for a school
AI Telegram bot for a real estate agency: instant answers instead of 24 hours — Maintenance and Support
AI Telegram bot for a real estate agency: instant answers instead of 24 hours

ALL PROJECTS

Our guarantees

How we work and what you get

Transparent terms from the first call to launch: you see and check the finished product before the final payment.

  1. You pay after you check

    We hand over a fully working project. You test it, make sure everything meets your requirements, and only then pay. You choose how: the full amount after acceptance, in stages, or a partial prepayment with the rest after acceptance.

  2. Technologies written into the contract

    The programming languages, frameworks and versions for your website or app are stated in the contract before work starts, so you know exactly what you are getting.

  3. Launched and ready to use

    We install the project on your server, configure it to run securely and fast, connect your domain, and publish mobile apps on the App Store and Google Play.

  4. Technical documentation

    At handover you receive a document listing the languages, versions and technical specifications of your project, so you can verify the quality of the work.

  5. Video guide to your admin panel

    A video walkthrough of your admin panel in the language you prefer, so your team can easily manage the website or the app.

  6. Quality and free support after launch

    We follow international development standards, guarantee the quality and speed of the result, and support every project free of charge after launch, for the period set in the contract.

Frequently Asked Questions

Do you upgrade the site when a new Laravel version comes out?

Yes, as part of the maintenance contract. Once Laravel 14 is released, every Laravel site we maintain will be moved to it, just as we did with previous versions. The same applies to PHP, Flutter and the mobile SDKs. The upgrade is done on staging first, so your site keeps running without interruption.

Can you maintain a site built by another company?

Yes, that is a large share of our support clients. We start with a three to five day technical audit, then tell you honestly what condition the code is in and whether it can be supported without remedial work first.

What happens if the site gets hacked?

We treat it as a critical SLA incident: contain the damage, restore from a clean backup, close the vulnerability that allowed entry, and rotate every credential. Afterwards you receive a written report explaining how the compromise happened.

How often do you back up?

Daily and automatically, covering both database and files, stored away from the site server itself. For busy online stores we back the database up more frequently. Restore drills are run regularly, not improvised during an actual emergency.

Does support include new features?

The plan includes a monthly hour allowance that covers content changes and small improvements. Larger functional blocks are quoted separately as small projects, but they are built by the same engineers who already know your system.

What if we do not use the monthly hours?

A portion of unused hours rolls into the following month, within the limits set in the contract. The base fee still covers monitoring, backups and readiness to respond, all of which run continuously whether or not you raise a request.

Can we cancel at any time?

Yes, with one month of notice. On exit we hand over all server credentials, backup archives and configuration documentation, so your next team can continue without a gap in coverage or a period of guesswork.

This service by region

Other services

Request a quote

codeorigins.info@gmail.com  |  +374 94 14 90 60

Request a quote