Software maintenance and application support
We maintain web applications, APIs and AI agents with security updates, fixes and monitoring. Support hours and response times are agreed in writing.
One fictional month of maintenance: what happens, when, and who is told.
- 1
- 2
- 3Update
- 4
- 5
- 6
- 7
- 8
- 9Backup
- 10
- 11
- 12
- 13
- 14AlertFix
- 15
- 16
- 17
- 18
- 19
- 20
- 21Upgrade
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30Report
Update
Day 3: Security update
A library update, tested and released through the usual path.
Backup
Day 9: Backup restored
Last night's backup restored on a test environment. It works.
Alert
Day 14: An alert, 08:05
Payment webhook failing after a provider change. The alert reaches the engineer on duty.
Fix
Day 14: Fixed, 10:40
The fix ships with a test that reproduces the failure.
Upgrade
Day 21: Framework upgrade
One supported step, deployed and verified.
Report
Day 30: Monthly note
What was done, what was found, what is next.
- 4 changes released, 0 rolled back
- Backup restore: passed
- 1 incident: payment webhook, fixed in 2 h 35 min
- Next: image storage clean-up
- Day 3: Security update A library update, tested and released through the usual path.
- Day 9: Backup restored Last night's backup restored on a test environment. It works.
- Day 14: An alert, 08:05 Payment webhook failing after a provider change. The alert reaches the engineer on duty.
- Day 14: Fixed, 10:40 The fix ships with a test that reproduces the failure.
- Day 21: Framework upgrade One supported step, deployed and verified.
- Day 30: Monthly note What was done, what was found, what is next.
What changes
TodayUpdates wait until something breaks.
With AL+Security updates and upgrades on a schedule.
TodayBackups nobody has restored.
With AL+Backups restored and checked.
TodayAlerts that reach no one.
With AL+Monitoring that reaches a person, and a note each month.
What software maintenance includes
Running
Security updates, certificates, restored backups and incident response.
Correct
Bugs fixed, and integrations brought back in line when the other side changes.
Changeable
Unused code removed, tests and deployments improved.
How maintenance works
Start with a review
If someone else built the system, we start with a takeover review.
Agree it in writing
Days per month, support hours and how incidents are handled.
A monthly note
What was done, what was found, what comes next.
Products built by AL+
We maintain our own products every month: PostDeploy Analytics, KeySend, Milkglass and Food & Fit.
Who this is for
A good fit
Software that matters to a business and needs a responsible owner for years.
Look elsewhere if
You want a ticket desk with nobody owning the system, or contractual 24/7 on-call.
Questions
Do you offer 24/7 support?
Support hours, response times and incident handling are agreed in writing. Automated monitoring does not mean round-the-clock human cover.
Are hosting and services included?
No. Providers bill them to your company's accounts. Maintenance covers our work on the system.
Can you guarantee the software is secure?
Nobody honestly can. We keep dependencies supported, review access and test backups. When a system needs a penetration test or an audit, we say so.
Further reading
Software maintenance cost: what your budget should cover
Estimate maintenance for an existing web app or SaaS: separate takeover, upkeep, support and feature work, then compare what each quote includes.
Software needs an owner
Software becomes expensive when nobody clearly owns it. Ownership is a role, not a repository permission, and most struggling systems are missing it.
Maintenance is product work
Most of a product's life happens after launch. Treating maintenance as a cost to minimize is how software quietly degrades and how the best improvements never get made.
Discuss application maintenance
Tell us which application you use and what support you need. We establish what needs reviewing before maintenance starts.
Or copy the address: paul@alplustech.com