Pulseguard
Under Attack?The work the platform cannot do for you.
PulseGuard tells you what is wrong across your estate. These are the engagements where our engineers go and fix it: build the servers, redesign the network, move the workload, and stay on afterwards if you want us to.
Pick the one that matches the problem in front of you.
Linux Infrastructure
Provisioning, hardening, and ongoing administration
Servers built to a written baseline, hardened against it, and kept there. You get the audit report, the diff, and the ability to run both yourself.
Windows Infrastructure
Active Directory, IIS, and Windows Server support
Directory design and remediation with tiering that holds: privileged credentials usable from a handful of machines and nowhere else.
Cloud Engineering
AWS, Azure, and GCP architecture and migration
Architecture reviews, migrations, and landing zones delivered as Terraform in your repository, with a plan you can run without us.
Networking
VPNs, load balancers, and network segmentation
Segmentation designed as zones rather than as a rule list, so one stolen credential reaches one zone instead of the entire estate.
Web Infrastructure
Web servers, CDNs, and application stacks
The stack under the site measured request by request, then tuned where the milliseconds actually are, on your traffic rather than a lab score.
Bounty
Report a vulnerability, get rewarded
Published reward bands, response targets a person is accountable for, and safe harbour for research that stays inside the rules.
Three shapes, and the same rules in all of them.
An audit
A defined piece of work with a written report at the end: a hardening review, an architecture review, a segmentation design.
A migration or build
A move, a rebuild, or a remediation programme, run to a plan with a date and a handover you can operate afterwards.
Ongoing administration
We hold the estate: patching, changes, capacity, and the on-call rota, with the platform reporting on it in the background.
Nothing hidden
Access is named and time-bound, every change lands as a reviewed diff, and the runbooks stay in your repository, not ours.
Tell us what is breaking.
A short call is usually enough to work out whether this is an audit, a project, or something you should keep in house.