Skip to content

Docodex - websites, applications and digital systems for business.



Continuity and technical responsibility

Technical maintenance for stable and updated digital products

We monitor, update and remediate active digital products with clear limits, priorities and reporting.

From149 €+ VAT / month

Pricing depends on technology, risk, infrastructure, monitoring, support schedule and time reserved. Standard monitoring does not mean 24/7 intervention.

  • Monitoring
  • Backup
  • Updates
  • Incidents
  • Priorities P1–P4
  • Reporting
Monitoring and technical maintenance for Docodex digital products

Important clarification

Post-release stabilization does not replace technical maintenance

Stabilization

Corrects delivered functionality to specifications

  • Period defined in the project contract
  • Reproducible delivery errors
  • It does not include new requirements or integrations
Maintenance

Protects product performance over time

  • Checks, monitoring and updates
  • Recurring incidents and activities
  • Agreed limits and support schedule

What does it include?

Recurring activities defined by offer and contract

An incident is not automatically converted to development, and new functionality is not submitted to maintenance.

01

Monitoring

  • Uptime, SSL, processes and resources
  • Forms, checkout and critical integrations
  • Alerts at set intervals
02

Backup and restore

  • Frequency, retention and location defined
  • Generation verification
  • Restoration tests where included
03

Controlled Updates

  • Framework, Libraries and Systems
  • Testing, deployment and rollback
  • Major updates are estimated separately
04

Incidents and support

  • Analysis, debugging and remediation
  • P1–P4 prioritization
  • Report and recommendations
Problems solved

Small risks become costly incidents when not tracked

We build a clear process for verification, intervention, escalation and reporting.

01

Unavailability and Expirations

Stopped processes, expired SSL, out of space or faulty configurations.

02

Faulty critical functions

Forms, checkout, payments, emails or billing affected.

03

Unverified backup

Children generated without clear retention, restoration test or accountability.

04

Blocked integrations and tasks

Changed webhooks, queues, syncs, and external services.

Covered products

We evaluate the technology before confirming support

01

Websites and e-commerce

Forms, tracking, checkout, payments, billing and server.

02

Web Applications and SaaS

Users, roles, modules, databases and asynchronous processes.

03

Mobile applications

Builds, notifications, crashes, compatibility and backend.

04

APIs and infrastructure

Endpoints, webhooks, Linux, Nginx, processes and logs.

Support level

The response confirms the takeover. The resolution depends on the incident.

Response time

We confirm, evaluate and communicate the first steps

The range depends on the package, priority and support program.

Time to solve

Depends on severity, access and dependencies

Replication, deployment, and third-party vendors can influence duration.

Automatic monitoring does not mean permanent intervention. The schedule, channels and conditions for urgent situations are contractually defined.

Priorities

Incidents are classified by impact

P1 / Criticism

Service unavailable

Checkout blocked, active data loss or major incident.

P2 / Raised

Important function affected

Major impact, with partial or alternative operation.

P3 / Normal

Limited error

Bug without full crash or scheduled activity.

P4 / Reduced

Improvement

Optimization without immediate operational impact.

External project

The takeover begins with a technical audit

We analyze the repository, local runtime, infrastructure, access, dependencies, backup, logs and technical debt.

The audit identifies risks and options, but does not guarantee acceptance of the project for maintenance.

  • Takeover in current form
  • Remediation before takeover
  • Refactoring or migration
  • Rebuilding some components
Request project audit

Evidence and reporting

See activities, time and technical decisions

01 / Report

Checks and incidents

Completed activities, time spent, blockages and recommendations.

02 / History

Documented changes

Commits, reviews, deployments and important decisions in the agreed tools.

03 / The next step

Technical plan

The risks and priorities for the next period remain visible.

Packages

Technical maintenance levels

The package is confirmed after evaluating the product, risk, infrastructure and support program.

Maintenance Start

From €149+ VAT / month

For low-risk websites and products that need recurring checks and a technical point of contact.

May include:
  • Basic automatic monitoring
  • Monthly check
  • Backup according to the offer
  • Up to 1 hour of intervention
  • Monthly report
  • Answer in the agreed schedule
Maintenance Plus

From €299+ VAT / month

For stores, apps and active integrations that require recurring checks and interventions.

May include:
  • Monitoring critical functions
  • Backup and checks included
  • Controlled Updates
  • Up to 4 hours of intervention
  • P1–P4 prioritization
  • Report and recommendations
Business maintenance

From €599+ VAT / month

For operationally important products with multiple components and the need for extensive technical responsibility.

May include:
  • Extensive monitoring
  • Planned technical checks
  • Approved backup and restore tests
  • Up to 8 hours of intervention
  • Staging and rollback where available
  • Monthly technical plan

Hosting, licenses, external services, 24/7 support and advanced audits are not included by default.

Quick comparison

Compare packages

The choice depends on the product, risk, objectives and actual capacity required.

AppearancePackageMaintenance StartFrom €149 + VAT / monthRecommendedMaintenance PlusFrom €299 + VAT / monthPackageBusiness maintenanceFrom €599 + VAT / month
PositioningMaintenance StartRecommendedBusiness maintenance
PriceFrom €149 + VAT / monthFrom €299 + VAT / monthFrom €599 + VAT / month
What does it include?Basic automatic monitoring, Monthly check, Backup according to the offer, Up to 1 hour of interventionMonitoring of critical functions, Backup and checks included, Controlled updates, Up to 4 hours of interventionExtended monitoring, Planned technical checks, Backup and restore tests agreed, Up to 8 hours of intervention
Suitable forFor low-risk websites and products that need recurring checks and a technical point of contact.For stores, apps and active integrations that require recurring checks and interventions.For operationally important products with multiple components and the need for extensive technical responsibility.

Process

From auditing to operating and reporting

  1. DiscussionProduct and risk.
  2. AuditCode and infrastructure.
  3. OfferCoverage and limits.
  4. AccessSafe channels.
  5. OnboardingBackup and alerts.
  6. OperationChecks and incidents.
  7. ReportActivities and risk.
  8. PlanNext steps.

Technology

We only work with stacks that we can support responsibly

Projects in other technologies are evaluated individually before collaboration is confirmed.

Maintenance assessment

Do you have a product that needs to be protected and maintained?

Do not submit passwords, keys, code archives or sensitive data through the form.

FAQ

Questions
frequent

Docodex Technical Maintenance Consultancy

Not sure which maintenance level is right for you?

Schedule a callSchedule a call

Activities may include monitoring, checks, backups, updates, incident investigation, deployment and reporting, within the limits of the package and offer.

It does not automatically include new functionality, redesign, major refactoring, migration, 24/7 support, advanced security auditing, or unlimited development.

Packages start from €149 + VAT per month. The cost depends on the technology, risk, infrastructure, monitoring, support schedule and time reserved.

Not by default. Hosting, VPS, storage, licenses and external services are separate costs unless the offer states otherwise.

May be included as per package and infrastructure. The offer defines frequency, retention, location and responsibilities.

Restore tests are only performed if they are included and a safe environment exists. A generated backup is not automatically a verified backup.

No. The monitoring can run automatically, but the intervention takes place in the contractually established schedule and conditions.

Only if there is a separate agreement for interventions outside the program. The standard service does not promise permanent availability.

It is the interval in which we confirm the takeover, assess the situation and communicate the first steps. It is not the same as resolution time.

It depends on severity, replication, access, complexity, deployment and external providers. Duration cannot be guaranteed prior to investigation.

The incident is classified and prioritized according to the package. Limiting the impact and protecting data take precedence over definitive remediation.

Not automatically. The carryover only exists if it is explicitly stated in the offer or contract.

Analysis, debugging, manual interventions, updates, testing, deployment, meetings and documentation can consume the included time.

Yes, after an audit of code, infrastructure, accesses, dependencies and risks.

No. The audit may recommend taking over, fixing, migrating, refactoring or rebuilding some components.

Technical maintenance

Need post-launch technical accountability?

We evaluate the product, risks and support program before recommending the package.