Service · Automation & DevOps

Automate the work that keeps breaking by hand.

Infrastructure as code, pipelines and workflow automation for firms that want repeatable operations rather than heroics.

Talk about automation

What's included

GitLab CI (continuous integration) pipelines with secret scanning.
Ansible and AWX for server configuration.
kolla-ansible for the OpenStack platform.
n8n for cross-system workflows (alerts to tickets, reports, prospect research).
PowerShell and Python tooling for Microsoft 365 and Windows estates.
Self-hosted AI tooling (vLLM) for internal drafting and summarisation, kept off client data unless agreed.

What you can expect

Response targets

These are the response targets in our standard agreement. They are targets, not a signed service-level agreement (SLA): the terms that apply to you are the ones in your contract. Business hours are Monday to Friday, 09:00–18:00.

Response targets by priority, from our standard agreement
Priority	Definition	Response	Resolution target
P1 Critical	Business operations halted (email down, ransomware in progress, directory outage)	1 business hour	4 business hours
P2 High	One significant function affected (a server down, one team cannot work)	4 business hours	1 business day
P3 Normal	Single user or non-critical issue	1 business day	3 business days
P4 Low	Information or change requests	2 business days	5 business days

Critical incidents out of hours are covered by agreement in your contract.

Service levels: how we classify priority →

Tools we run

GitLab Ansible AWX n8n kolla-ansible PowerShell Python vLLM

Tell us what isn't working.

A 30-minute call, no slides. We ask about your estate, your auditor if you have one, and what you would like to stop worrying about.

Talk about automation