Where we start
Infrastructure rarely arrives as a blank page. There is usually something running already: servers, storage, a cloud subscription, a network, a backup job of uncertain value. Our work is to understand what is there, what the organisation needs from it, and what should change.
We choose technologies to suit the client. We do not have exclusive relationships with any vendor, and we do not start from a favoured product. The same applies whether the answer is on-premises equipment, a cloud service or a mix of the two.
What we do
- Infrastructure architecture. Designing how compute, storage, networking, identity and backup fit together, with the reasons recorded where that is part of the agreed scope, so the design can be reviewed.
- On-premises infrastructure. Servers, storage and supporting services for organisations that need to run systems in their own premises.
- Cloud and hybrid environments. Designing, building and connecting cloud services, including environments that span cloud and on-premises systems.
- Infrastructure deployment. Building the agreed design, testing it and handing it over, with documentation where that is part of the agreed scope.
- Modernisation. Moving ageing infrastructure forward in stages, with as little interruption as possible to the services that depend on it.
- System integration. Connecting systems so that data and identity move between them reliably. Application-level integration is covered under systems integration.
- Technical investigations. Establishing why something fails, or fails sometimes, and writing up the cause.
- Performance troubleshooting. Finding the bottleneck in a slow application, server, storage path or network, rather than adding capacity and hoping.
- Resilience and availability. Working out what a failure would cost. We consider single points of failure and agree proportionate resilience and recovery arrangements based on the importance of each system.
- Infrastructure assessments. A review of an existing estate: what is there, what is at risk and what to change first, with a formal written assessment where that is included in the agreed scope.
In plain terms
Hybrid
An environment where some systems run in a cloud service and some on equipment the organisation owns, connected so that they behave as one estate.
Backup and recovery
A backup that has never been restored is an assumption. We set up backup so that it fits what the organisation needs to recover and how quickly, and we can test a restore as part of the work, where that is agreed, to check that the data comes back and can be used. Scheduled restore testing can form part of continuing support.
- Define what must be recovered and in what order.
- Configure backup to match, including copies held away from the system they protect.
- Restore to a different location and check that the result works.
- Keep a record of what was tested and when.
Backup for Microsoft 365 is covered on the Microsoft 365 and Azure page. Ongoing checks can form part of continuing support.
How the work is agreed
Infrastructure work is agreed as a fixed project quotation, a daily consultancy arrangement or an individually agreed investigation, depending on how well the scope is known. There are no packages and no standard price list. For larger projects we may bring in additional specialists or work alongside your own engineers. See consultancy: how we work.
Network design and wireless sit under network infrastructure. Where a problem has defeated an internal team or supplier, see Tier 3 escalation. The full range is on the services page.
Discuss your infrastructure
Tell us what you run today and what you need to change, and we will say plainly whether we can help.