Managed server operations and research software deployment
Both sit with the same team, because they are the same job: get a system installed, get it running, and keep it usable.
Linux server operations
- Deployment and initial configuration
- Monitoring and alerting
- Backups, and restore drills — a backup nobody has restored is not a backup
- Security updates and version upgrades
- Incident response
We operate systems we built, and we take over systems somebody else built and nobody currently maintains. The second case starts with an audit of what is actually running; you get those findings before any commitment to take it on.
Research software deployment
Configuration of research computing environments and specialist scientific software.
The difficulty with this software is rarely using it — it is getting it installed. Dependency chains nest several layers deep, documentation trails the code, compiler flags can change numerical results, and licensing arrangements differ from package to package. The hours researchers lose to this are hours not spent on research.
What we deliver is a working environment, a record of the versions and build flags used, and reproduction instructions clear enough that the same environment can be rebuilt on another machine.
Ongoing support
Service hours, response times, and escalation are agreed per project and written into the contract. A development box and a production environment do not need the same level of cover, and one number quoted for both is wrong for at least one of them.
We do not advertise "24/7". What you get is specific terms in a contract.
Get in touch
Tell us what it runs on now, how many machines, and who currently looks after it.