Everything we deploy runs inside your network. This page covers the ways that can be arranged — on infrastructure you already own, on hardware we supply, or on a combination.
On your existing infrastructure
The most common arrangement. We install onto your current servers, virtual machines or container platform, sized against the workload, with minimal disruption to what is already running. Configuration is tuned to the resources available rather than assuming a reference specification.
- Bare-metal installation on physical servers
- Virtual machines on VMware, Proxmox, Hyper-V or KVM
- Containerised deployment where you already run an orchestration platform
- Air-gapped or segmented network deployment, including offline package management
Hardware we supply
Where you would rather not carve capacity out of existing infrastructure, we specify and supply it.
Servers
Specified for the actual workload — monitoring, service management or database — with redundant storage and failover where availability requires it.
Workstations
Pre-configured environments for service desk and asset management staff, connected to the intranet deployment.
Virtual machine clusters
Resource-efficient hosting for multiple platforms with isolation between them, scalable as the estate grows.
Refurbished VPS
A deliberately economical option for pilots, test environments and secondary workloads — the same open-source software and the same end-to-end control at lower cost.
Sizing
Sizing is done during assessment against your real numbers — host counts, ticket volumes, database size and growth rate, retention requirements. We would rather specify against measurements than quote a standard bundle and discover the gap in production.
Hybrid arrangements
Some organisations want core systems on-premises with non-sensitive workloads elsewhere — test environments, public status pages, documentation. We will design for that, and the useful work is in defining which data classes must never cross the boundary, then enforcing that in architecture rather than in policy alone.
The broader argument for keeping production inside your perimeter is set out on Why On-Premises, including the counter-arguments.