Skip to main content

Application Maintenance & Support

Hosting, Maintenance & Technical Support

Keep your business systems running with hosting, scheduled maintenance, and optional technical support. Choose coverage around your system and the responsibilities you need us to handle.

Sample scope in English

Agree who responds, approves and operates the system

You need bounded help with an application that has a named owner, known access and a clear support scope.

Use a modernization project for a significant replacement or migration. A support allowance is not an unlimited feature-development subscription.Compare the options

What you receive

  • Application/access inventory and a responsibility record.
  • Request classification, diagnosis and approval before chargeable changes.
  • Agreed work/time record, checked release outcome and remaining risks.

What to prepare

  • Application/version, repository rights, host owner and dependency inventory.
  • Backup/recovery evidence, known incidents and critical operating hours.
  • Authorized requesters, approver and update recipient.

Agreed separately

  • An initial response acknowledges or starts diagnosis. It is not a guaranteed resolution time.
  • Out-of-hours coverage and severity commitments require explicit agreement.
  • New features, vendor outages and work beyond the approved allowance follow their own approval decision.
See a sample

Illustrative request record: reported issue → priority and coverage check → diagnosis → estimate/approval → implement/check/deploy → time used and outcome. Classify a warranty defect, a maintenance task, a new feature and a vendor incident separately.

Acceptance example. The approver sees the scope and any charge before extra work. The final record states what changed, what was checked, approved time used and unresolved risks. The operating owner retains responsibility for vendor accounts and bills unless agreed otherwise.

Read the sample scope, acceptance and handover records

Are backups and hosting included?

Only the accepted plan defines hosting, backup frequency, recovery checks and ownership. A technical allowance does not imply universal operating coverage.

What if the allowance is exhausted?

Agree the next priority and approve additional work before it starts. Response, diagnosis, implementation and vendor recovery are different steps.

Four different kinds of post-launch help
Project care concepts to confirm in the accepted agreement
ConceptPurposeExample and boundary
First-year basic maintenanceThe basic-care tasks and term listed in the accepted project scope.An agreed maintenance task is different from adding another approval screen. Hosting, backups and renewals need named owners.
Annual consultation allowance4 hours of first-year consultation where those project terms apply.Discussing a workflow change does not include implementing it. Confirm the term, availability and work classification.
Scoped defect warranty90-day warranty under the applicable accepted project terms.A failure against an agreed acceptance rule differs from a new requirement or vendor outage. Coverage depends on the warranty terms.
Optional monthly technical allowance4 approved technical hours per month under that plan.Agreed fixes or changes consume recorded time. Extra work needs approval. Unused hours do not imply unlimited work or rollover.

These project-care concepts do not replace the separate product rules for Luma or ResumeForU. Confirm plan applicability, initial response coverage, renewal, exclusions and request authorization in writing. A response begins communication or diagnosis, not a promise of immediate resolution.

Care, editing and operating responsibilities
Responsibility checklist to complete with the accepted plan
TaskBuyer responsibilityScope to confirm
Hosting and vendor billsName the account and payment owner.First-year term, renewal owner and any annual hosting/basic-maintenance coverage.
Backups and recoveryApprove recovery needs and access.Backup owner, retention, restore checks and recovery work explicitly covered.
Patches and monitoringIdentify critical operating constraints.Systems covered, update approval and monitoring/incident contact.
Content editsSupply approved copy/images and nominate an editor.Staff editing versus agreed care tasks or separately approved work.
Defects and new featuresDescribe expected behavior and approve changes.Warranty classification versus technical allowance or an additional quote.
Reporting and exitKeep authorized contacts and account ownership current.Work/time record, remaining risks, access, exports, licences and cancellation/renewal terms.

First-year care, annual basic maintenance and a monthly technical allowance are different scopes. This checklist does not add coverage to a plan. Record included work and extra-work approval in writing.

Our Support Services

Choose the monitoring, maintenance, and technical help your system needs.

Proactive Monitoring

Automated checks help identify availability issues. Monitoring does not imply staffed 24/7 incident response.

Security Patching

Keep covered applications and hosting components updated. Your plan defines the security maintenance included, the systems we handle, and any exclusions.

Performance Optimization

We agree the scope and engineering hours for performance diagnosis and tuning. Ongoing optimization is not automatically included in basic maintenance.

Process

Onboarding Process

We review the system, agree any stabilization work, and define ongoing responsibilities.

01

System Audit

Review access to source code and data, dependencies, and operational responsibilities. We agree the assessment scope separately before taking over support.

  • Audit Report
02

Stabilization

We estimate stabilization work and get your approval before implementation. This work is not automatically included in hosting or ongoing support.

  • Stability Baseline
03

Ongoing Management

We carry out the monitoring, scheduled maintenance, and reporting included in your support plan.

  • Agreed maintenance records and reports
Coverage & Costs

Support Plans

Choose hosting care, a monthly technical allowance, or separately quoted work. Each plan defines coverage and third-party costs.

Infrastructure

Annual Hosting & Basic Maintenance

Best for: Businesses needing hosting and basic maintenance

Custom quoteper yearCoverage: Coverage and scheduling agreed before activation

Purchase hosting and basic maintenance as a standalone service. We quote for the server, backup, monitoring, and security maintenance your system needs.

The Nodesify Edge

Clear responsibilities, exclusions, and additional costs

  • Backup frequency, retention, location, and recovery checks agreed
  • Hosting and maintenance responsibilities recorded
  • Not an engineering-hour subscription
Discuss Your Support Scope
Optional

Monthly Technical Support

Best for: Businesses needing a monthly technical allowance

NZD 300per monthCoverage: Coverage and scheduling agreed before activation

Includes up to 4 hours per month. Server charges are separate. Communication, consultation, diagnosis, implementation, checks, and deployment count toward these hours. Unused hours expire each month.

The Nodesify Edge

Clear responsibilities, exclusions, and additional costs

  • Written estimates and change approval
  • Support coverage and escalation agreed
  • Covered warranty fixes do not use paid support hours
Discuss Your Support Scope
Approval First

Additional Technical Work

Best for: Defined projects or small tasks with uncertain scope

NZD 70per hour for small uncertain tasksCoverage: Coverage and scheduling agreed before activation

Get a fixed quote for clearly defined work. For small tasks with uncertain scope, we provide an estimate and obtain written approval before charging the published hourly rate. This service is billed by approved work, without a prepaid hours package.

The Nodesify Edge

Clear responsibilities, exclusions, and additional costs

  • Agreed estimate and scheduling
  • No unapproved extra work
  • Third-party costs disclosed
Discuss Your Support Scope
Custom

Special Coverage

Best for: Out-of-hours or specialized operational needs

Custom quoteseparately agreedCoverage: Coverage and scheduling agreed before activation

We agree out-of-hours coverage and special operational responsibilities separately. Staffing and availability must be confirmed before coverage begins.

The Nodesify Edge

Clear responsibilities, exclusions, and additional costs

  • Named coverage and escalation responsibilities
  • Recovery targets confirmed against supporting evidence
  • No standard 24/7 or uptime commitment
Discuss Your Support Scope

Beyond Basic Support

Plan improvements and future capacity with separately scoped advice and engineering.

Continuous Improvement

Regular recommendations for system enhancements.

Scalability Planning

Preparing your infrastructure for future growth.

FAQ