services / 08

Maintenance and security

Maintenance plans, updates, security audits, monitoring, backup and recovery — for projects we built and for projects taken over from other teams.

maintenance-security.md

# in short

  • Maintenance plans
  • Security updates
  • Security audits
  • Monitoring and alerts
  • Backup and recovery
  • Post-launch support

01/ what

What we do

01

Maintenance plans

We agree on what is included: updates, periodic checks, a volume of changes and how you report a problem.

02

Security updates

Operating system, dependencies and application components, applied in a controlled way and tested before production.

03

Security audits

Access, permissions, exposed data, server configuration and vulnerable dependencies. You get the findings, ordered by risk.

04

Monitoring and alerts

Site availability, certificates, disk space and application errors, with an alert when something breaks.

05

Backup and recovery

Automatic copies kept away from the server, and restore procedures checked periodically.

06

Post-launch support

Fixes, small changes and new features, planned on the same codebase.

02/ preluare

Taking over a project built by others

It happens often: the team that built the application is no longer available. We take it over in clear steps.

  • Audit

    What runs, where, with what access, what is exposed and what has no backup.

  • Documentation

    We write down what is missing: how to install it, configure it and deploy it.

  • Stabilisation

    Security and stability problems first, before any new features.

  • Plan

    We propose what to keep, what to refactor and what to replace, with the reasons for each decision.

03/ ai + people

Where AI helps and where it doesn’t

AI helps with analysis and documentation. Access and production changes stay with people.

Where we use AI
  • log analysis and error grouping
  • automated checks for vulnerable dependencies
  • a first draft of documentation for a taken-over project
  • suggested fixes, as a starting point
What stays with people
  • access to servers and data
  • security priorities
  • any change in production
  • testing restores from backup

04/ deliverables

What you get

  • the audit report, with findings and priorities
  • a written maintenance plan: what is included and what is not
  • a log of interventions
  • a tested restore procedure
  • up-to-date project documentation

05/ questions

Frequently asked questions

Can you take over a project built by another team?

Yes. We start with an audit and only then propose a plan. You get the findings before any change.

What happens if the site has a problem outside working hours?

It depends on what we agree in the maintenance plan: what is monitored, who gets the alerts and how we respond. We do not promise a response time before we agree on it together.

How much does maintenance cost?

It depends on what is running and what the plan includes. The quote starts from an audit; we have no standard packages.

contact

Request a quote: maintenance and security

Tell us briefly what you want to build. Pricing is set per project, once we understand what needs to be done — we do not sell standard packages.

  1. 01A person on the team reads your message.
  2. 02We get back with questions or suggest a call.
  3. 03You get a quote split into stages, with what each one includes.

Or directly: office@magdalagroup.ro