Networks & multi-ISP failover
Routing, VLAN segmentation, switching and automatic failover across several providers, so one cut fibre is an event nobody outside IT notices.
Routing, VLAN segmentation, switching and automatic failover across several providers, so one cut fibre is an event nobody outside IT notices.
Policy design and rule-base review on enterprise firewalls, with findings written up plainly enough for management to act on.
Hypervisor clusters, guest sizing and consolidation of ageing physical servers, including the migration path off them.
Scheduled off-box backups with a retention policy, and — the part usually skipped — a restore that has actually been tested.
PostgreSQL and object storage: sizing, tuning, replication and the capacity forecast that tells you when to buy more disk.
Reverse proxy, certificate management and safe publication of internal systems to the internet, without exposing what should stay inside.
Support agreements are written against a response time and a named scope, not a vague promise of goodwill. Remote first, on site when the fault needs hands.
Service checks that tell us something has failed before your users do.
A low-level design kept current, so the next engineer is not reverse-engineering your network at 2 a.m.
Configuration backed up before every change, and rolled back automatically if the change does not validate.
That is a normal place to start. We will survey what is there and tell you what it would take to make it supportable.