Project Kick Off

Building the Infrastructure Platform Red Teams Deserve

Today we’re sharing what we’ve set out to build — and, just as importantly, why, and how.

Red team operations are among the most demanding disciplines in cybersecurity. The work is high-stakes, the margins for error are thin, and the infrastructure that underpins an engagement is too often held together by manual effort, bespoke scripts, and institutional memory. We’ve lived that reality. And we’ve decided to fix it.

We’re building a platform that brings red team infrastructure and team server operations under a single roof — fully automated, from provisioning to teardown. But a tool like this is only as good as the principles behind it, so we want to start there.

It has to work

This is operational infrastructure for teams whose job is to find the gaps before adversaries do. There is no room for “mostly reliable.” Automation that fails under pressure is worse than no automation at all. From day one, our standard is that the platform performs exactly as expected, every time — because the teams relying on it don’t get second chances mid-engagement.

It has to be on premise

Red team work is sensitive by its very nature. The infrastructure, the data, and the operational detail belong to the team running the engagement — not to us, and not to a third-party cloud we control. That’s why the platform is built to run on premise, inside your environment, under your governance. We don’t want visibility into your operations, and we’ve designed the system so that we can’t have it.

It has to be protected

A platform that automates offensive infrastructure is, itself, a high-value target. We treat it that way. Security isn’t a feature we bolt on at the end; it’s a constraint we design against from the first line of code — hardening, isolation, and defence in depth throughout.

It can’t cut corners

Shortcuts in this domain become liabilities fast. We would rather build something properly than ship something quickly and hope. That means doing the unglamorous engineering work — the edge cases, the failure modes, the clean teardown — that separates a tool teams trust from one they tolerate.

Teams retain ownership of everything

This is non-negotiable. Your infrastructure, your configurations, your data, your engagements — all of it stays yours. The platform is a force multiplier for your team, not a dependency that holds your operations hostage. You own what you build on it, and you can take it with you.

The ethics underneath all of this

Offensive security tooling carries real responsibility. We build for authorised, contracted, and lawful red team work — the kind that makes organisations more secure. That purpose shapes the decisions we make: who we build for, how the platform is governed, and the care we take to keep it in the right hands. We take that seriously, and we always will.

Who we are

Our team brings deep experience across software engineering and cybersecurity, spanning both the private and public sectors. We’ve worked with dozens of teams across the industry, and we’ve seen first-hand what great red team infrastructure looks like — and what happens when it’s missing. That experience is what we’re pouring into this.

We’re based in the UK and operate globally, serving enterprise red teams, security consultancies, and government teams wherever they are.

Where we’re starting

We’re building this in deliberate stages, and our first goals are clear. To begin with, we’re focused on the redirector layer — the part of an operation that most needs to be fast, disposable, and resilient:

1. Redirector automation — fully automated deployment of operational redirectors, provisioned and configured without manual effort.

2. Rotation logic — the logic that cycles redirectors and their certificates on schedule or on demand, keeping infrastructure fresh without interrupting the operation.

3. Burn analysis and response — detecting when a redirector has been burned and triggering the corresponding rotation automatically, so a compromised node is replaced before it becomes a liability.

Getting these fundamentals right is the foundation everything else is built on. From there, we’ll expand outward across the rest of the operational backbone.

Built with our customers, not just for them

We don’t believe great products are built in isolation. Over the coming period we’ll be looking for design partners — teams willing to work closely with us, put the platform through its paces, and shape it with honest feedback. Our aim is to develop this in the open with the people who’ll actually use it, iterating on as much real-world input as we can gather.

Get in touch

If you run red team operations — in an enterprise, a consultancy, or a government team — we want to hear from you. We’re looking for design partners to build this alongside, and we’re keen to share our thinking as openly as we can and fold as much of your understanding into the platform as possible. This works best as a two-way conversation: what we know, meeting what you need.

Reach out. Let’s build it together.

Contact us!