Pure Deterrence builds protective and defensive technology for critical sectors, and often for the civilians those sectors serve. We find the gaps nobody is selling an answer to, then define, build and test an answer through five gates. What passes can seed a new company, with 308 and its partners holding equity alongside each other. Salus, built with Vox Novus, was the first, and its own company is being formed now.
Deterrence usually rests on the threat of a response. Ours comes from protection, and that’s what makes it pure. We build technology that makes critical systems, and the people who rely on them, harder to disrupt, harder to breach and quicker to recover, so an attack costs more than it could ever return. Some of it serves a sector directly, a hospital, a grid or a port. Some of it reaches civilians just as much, in homes, clinics and on the road. The test is the same either way. Does it make the harm less likely?
A gap in how a critical sector protects itself, or the people it serves, keeps surfacing, and the workaround is costing someone. One observation is an anecdote. The gate opens on a pattern with a cost we can measure.
The problem is written down precisely, before anyone is allowed to fall for an answer. It covers who is exposed, what they need protecting from, what success looks like and what conditions it must survive. How it will be built is deliberately left out.
A formal review with the accountable people in the room, and many ideas stop here. The decision is recorded against their names, including a decision to stop.
Many ideas stop hereBuilt from a hardened baseline, with who can see what settled before the first feature. Partners bring in capability where the product needs it.
Judged against the need as it was first written down, by people who didn’t build it. Passing this gate opens the conversation about forming the company under PartnershipDNA.
Company formed under PartnershipDNA
Every build follows a DevSecOps method. The threat model is written before the architecture, each product starts from a hardened baseline we maintain, and we attack it ourselves before anyone else can.
We classify the data before we model it and decide who can see what before the schema is drawn. How long data is kept and how it’s destroyed are decided on day one.
Automated evaluation runs for the whole build, covering the cases that matter and everything that has failed before. The evidence is kept so it can be produced when someone asks for it.
Hardware gets the same controls as software, from the parts list to the last unit shipped. Components are sourced as a supply chain and board revisions are versioned like code.
We build with founders and small companies. Bring your own idea or build on one of ours. Either way it goes through the same five gates, under PartnershipDNA, the framework we wrote so partners can trust each other with IP before anything is proven.
“As they say on my own Cape Cod, a rising tide lifts all the boats. And a partnership, by definition, serves both partners, without domination or unfair advantage.” John F. Kennedy, Frankfurt, 1963
What you bring in stays yours. It’s identified and ringfenced in writing before any work starts, and if you exit it leaves with you, along with what you need to keep running on your own.
Anything created inside the project is held in trust for the future company from the moment it’s made, and moves into that company when it’s formed. Until then, licences between partners are mutual and bounded to the project’s defined field.
Every contribution is logged as it’s made, so the record is ready when the time comes. When a company is formed, partners hold shares directly alongside 308, set by the risk each one took and what they contributed.
308 stands up and runs a high-assurance environment for each project, open to inspection by every partner. A risk and compliance firm independent of 308 audits it and sends its findings to all partners at the same time.
Each product is funded for what it needs to reach the market, and the mix is set by its timeline, its strategy and what it costs to build. 308 itself stays with its founders.
Timeline
How soon the product has to reach the market.
Strategy
Who it has to reach, and who should have a stake in it.
Cost to build
What it takes to get there, hardware included.
The mix
308
When the build fits what 308 can carry itself.
The partners
When they bring capability or capital to the product they’ll co-own.
Grants
When the work fits what a grant program is set up to fund.
Outside investors
When the timeline or cost goes beyond the others, venture capital included.
Salus drafts care plans for Australian home care and Support at Home providers. It reads the assessments, notes and records a provider already holds, pulls them into one picture of the client, and produces a draft plan that a care manager reviews, edits and approves.
Everything we build here is meant to make a critical sector, and the people who depend on it, hard enough to harm that harm isn’t worth trying. That’s deterrence through protection, not through threat.
No. Defence is one critical sector among several, alongside health and care, energy, transport and the systems behind them. Much of what we build is used by civilians as much as by the sector itself. Salus, the first product, is used in Australian home care.
No. Pure Deterrence builds products from needs we’ve found ourselves or that a partner brings to us. Nothing we see inside a Continuity client becomes a Pure Deterrence product.
Yes. If a large firm has a problem its own setup can’t carry, we’ll build the answer with them under PartnershipDNA.
We’ll look at what you’ve built. If we don’t have the capacity or aren’t the right fit, we’ll introduce you to people who might be, once we’ve done our own checks.
Anything built in a project is held in trust for the company it can become, and moves into that company when it forms, with 308 and the partners holding equity alongside each other. Background IP stays with whoever brought it, and that’s agreed in writing before any work starts.