Research labs
Research software maintenance that keeps your systems working.
Research software needs upkeep. Libraries change, servers need patches, and researchers ask for new fields after launch. Research software maintenance keeps your systems running and secure without a full software team.
Research software maintenance
Research software needs upkeep. Libraries change, servers need patches, and researchers ask for new fields after launch. Research software maintenance keeps your systems running and secure without a full software team.
We agree a written support plan with response times, a change process and a monthly review. Work is tracked, so you can see what was done and why.
What we build
What a support plan covers.
Updates and patches
Security and library updates, tested before release.
Bug fixes
Issues reported by your team are logged, prioritized and fixed in agreed windows.
Small changes
New fields, reports and workflow adjustments, handled through a simple request process.
Monitoring and backups
Health checks, backup checks and alerts, reviewed with your team.
Documentation
Runbooks and change notes kept current, so a new engineer can take over.
Who it is for
| Team | Typical problem | What we deliver |
|---|---|---|
| Research lab with a legacy tool | The original developer has left | A team that can support the code |
| Institute IT team | Too few people for many research systems | Regular maintenance under a written plan |
| Grant-funded project | Software must keep running after the grant ends | A handover and an optional support plan |
How the work runs
01
Review: we audit the current code, hosting and open issues.
02
Agree: we write the support plan, response times and change process.
03
Maintain: we apply updates, fix issues and report each month.
04
Hand over: if you want, we transfer the runbooks and train your team.
Services that build on it
How do I maintain research software after the original developer leaves?
Start with a review of the code, hosting and open issues. Then agree a written support plan covering updates, bug fixes and response times, and document the system so a new engineer can take over.
What does research software maintenance include?
Security and library updates, bug fixes, small changes, monitoring and backup checks, and documentation kept current, all under a written plan.
How much does software maintenance cost for a research lab?
We don't publish prices on this page. Support is agreed in writing, based on the systems covered, the response times you need and the expected number of changes.
Can an engineering partner take over software built by someone else?
Yes, after a review of the code, hosting and open issues. We agree the scope before we start.
Do we need a full software team to keep research applications running?
No. A written support plan covers updates, fixes and monitoring. Your team keeps ownership of the system and sets the priorities.
Tell us how your research team works
Book a free review. We confirm the problem, the right approach and the next step.