Services Consulting & support
Maintenance
Scheduled updates, backups and fixes, so the systems you rely on stay current, recoverable and working.
At a glance
- Includes
- Patching and dependency updates, backups with tested restores, bug fixes and small changes
- Works with
- Your applications, servers, cloud accounts and ticketing tools
- Delivered as
- A recurring schedule and a request queue, agreed in writing
- Starts with
- A review of what you run and what is overdue
Fit
Is this right for you?
Usually the right call when one of these sounds familiar.
Updates keep slipping
Nobody has time to patch, and the list of overdue items grows.
Backups no one has tested
They run, but you have never tried a restore.
Small fixes pile up
Minor bugs wait behind bigger projects.
Knowledge in one person's head
Only one engineer knows how to look after the system.
Not the right service? Need alerts watched around the clock: 24/7 monitoring. Need extra people to build new features: Team augmentation.
Scope
Scope and what you get
Agreed with you in writing before work starts. Each piece of work has a matching thing you receive.
- What we do
Patching and dependency updates
Operating system, framework and package updates applied on a schedule.
What you receiveA system that stays current
Updates applied, tested and recorded, so fewer old versions linger.
- What we do
Backups and restore tests
Backups checked, and restores tried rather than assumed.
What you receiveProof that recovery works
A written record of each restore test and what it showed.
- What we do
Bug fixes and small changes
Requests are handled through a queue that you can see and prioritise.
What you receiveA request queue
Each request is logged, ranked with you and closed with a short note.
- What we do
Documentation and records
We record what was changed, when and why, in your own tools.
What you receiveRecords you can read
A change history your own team can follow without us.
Use cases
Relevant use cases
Practical situations where this service is put to work. Open a card to see how it applies.
Keeping an application current
Regular updates to the application and the packages it depends on, tested before they reach production.
- Updates scheduled with you
- Changes tested before release
- A note of each change
Proving that backups restore
Backups checked by restoring them, so recovery is something you have seen work.
- Restores tried on a schedule
- Results written down
- Gaps raised with you and fixed
Handling small requests without a project
A queue for fixes and minor changes, so small work is done without being planned as a project.
- Requests logged and prioritised with you
- Fixes reviewed before release
- Status visible in your ticketing tool
Sample use cases, drafted as placeholders. The Plethora team confirms the final list.
Process
How it works
Four stops, agreed with you as we go. Each shows what we do and what we need from you.
Assess
We doWe review what you run, which versions it is on, and how backups and releases are done today.
You doYou give us access to systems and repositories and tell us what must not break.
Plan
We doWe agree the schedule, what is covered and how requests are raised and ranked.
You doYou confirm maintenance windows and who approves changes.
Support
We doWe apply updates, test restores and work through requests, recording each change.
You doYou raise requests, approve changes and tell us about anything new.
Review
We doWe report what was done and what is outstanding, and recommend what should come next.
You doYou decide priorities for the next period.
Quality
Quality and handover
How the work is checked, accepted and passed to you.
Tested before release
Updates are checked in a test environment before production where one exists.
A way back
Each change has a rollback step written down before it is applied.
Changes recorded
What changed, when and why is kept in your tools.
A defined handover
Schedules, scripts and notes stay with you if you take it over.
Tools
Tools and technology
Tools we use in delivery. We choose them to suit your team, and the list does not imply any partnership. Logos belong to their owners.
- GitHub Actions
- GitLab
- Docker
- Sentry
- Jira Service Management
- Confluence
Engagement
Engagement and cost factors
Ways to work with us
Ongoing support
A recurring schedule and request queue, agreed in writing.
A scoped project
A one-off clean-up of overdue updates, backups and records.
A team alongside yours
Our engineers share the upkeep with yours.
What shapes scope, timing and cost
- How many systems and environments are covered
- How out of date things are today
- How often you want updates and restore tests
- How many requests you expect
- Your approval and release process
Scope and cost are confirmed with you in writing before work starts.
FAQ
Frequently asked questions
Yes. Bug fixes and small changes are handled through a request queue. Larger changes are scoped separately.
We restore it. Each test is written down so you can see what was tried and the result.
We plan updates around the maintenance windows you set, and agree any expected disruption with you beforehand.
Often, yes. We begin by reviewing what exists and confirm what we can look after.
Keep what you run current and recoverable. Start with a conversation.
Tell us what you need and we will come back with next steps.
Talk to usRelated