01
Own the boring parts
Patching, backups, documentation, and access reviews are where outages are actually prevented. We do them on a schedule, not on a reminder.
Operating focus
The operating interests sit in technology services for small and mid-sized organisations, with room for adjacent businesses as they are established.
Operations
Day-to-day operation of the systems a business runs on: endpoints, identity, network, backup, and the monitoring that catches problems before anyone files a ticket.
Partnership
Working alongside an existing internal team rather than replacing it. The in-house staff keep ownership; we take the load they do not have capacity to carry.
Resilience
Mail authentication, patch discipline, least-privilege access, tested restores. The unglamorous work that decides whether an incident is an afternoon or a quarter.
Build
Practical build work: internal tooling, integrations, and fast, maintainable websites that a business can actually keep current.
How we work
01
Patching, backups, documentation, and access reviews are where outages are actually prevented. We do them on a schedule, not on a reminder.
02
Every environment we run is written down well enough that someone else could take it over. That is the test, and it is not optional.
03
Deterministic scripts and boring, well-understood tools outlast novel ones. We choose what will still be maintainable in five years.
04
Plain assessments about what is working, what is at risk, and what a fix will cost. No inflated urgency, no invented findings.
Structure
The group is being formed in Oregon. Operating companies and their contact details will be published here as each is established.