Product
Maintenance and Support for Life After Launch

Launch is when a product meets real usage, and real usage finds things testing could not. Tarfion provides application support and maintenance that keeps your product monitored, patched and improving, whether our team built it or another one did.

What Maintenance & Support Covers

[01]

Performance Monitoring

[01]
Performance Monitoring

Load times, errors and uptime are tracked continuously, so problems show up on our dashboards before users report them.

You leave with

Monitoring dashboards and alert rules.

[02]

Issue Resolution

[02]
Issue Resolution

Technical and operational problems are triaged by severity and fixed with the least possible disruption for your users.

You leave with

Resolved tickets with root-cause notes.

[03]

Feedback Integration

[03]
Feedback Integration

Support messages, reviews and usage data are sorted into clear themes and fed directly into the product backlog.

You leave with

A feedback digest linked to backlog items.

[04]

Security & Dependency Upkeep

[04]
Security & Dependency Upkeep

Libraries, frameworks and infrastructure are updated on schedule, keeping known vulnerabilities out of your production environment.

You leave with

An upkeep log and update calendar.

What Changes After Release

Usage arrives at hours nobody planned for.

Operating systems and the libraries your product depends on update, and some updates are security fixes.

Users find paths through the product that no test script imagined.

Usage arrives at hours nobody planned for. Operating systems update. A library your product depends on publishes a security fix. Users find paths through the product that no test script imagined. Each of these is normal, and each needs someone paying attention. Our support team monitors the product, responds when something breaks and schedules the updates that keep the same problem from returning.

Support and Maintenance, Side by Side

Support
Triggered by
Something has gone wrong
Aim
Restore normal service quickly
Typical work
Incident response, bug fixes, user issues
You leave with

Incident notes with the root cause

Maintenance
Triggered by
A schedule, plus what monitoring shows
Aim
Prevent the next problem
Typical work
Updates, patches, performance tuning
You leave with

An upkeep log and update calendar

From First Sketch to Shipped Screen

Alert or report

Fix and test

Alert or report

01
02
03
04
05
06

Triage by severity

Release

Backlog update

Anything that stops users completing the core task goes to the front of the queue. Every resolved issue ends with a short note on why it happened, so the cause can be removed for good.

What Every Upkeep Report Covers

[01]

Health

Goals, constraints, success measures and the assumptions everyone is currently making.

[02]

Fixes

issues resolved, their root causes and the change made to keep them from recurring.

[03]

Updates

dependencies, frameworks and infrastructure updated, plus the work scheduled next.

[04]

Feedback

recurring themes from support requests and usage data, linked to proposed backlog items.

Tell Us What the Product Runs On

Share the stack, the hosting setup and what has been going wrong lately. We'll suggest a support arrangement that fits.

Hand Over the Upkeep