308

Named after a redirect.
On purpose.

Australian-owned, founder-held, small by design. Two co-founders, one job – protective and defensive technology for the organisations responsible for critical systems.

Origin

It started a long way from a codebase.

I came to this from disaster relief in global conflict zones. Places where the systems around you are broken by definition, and the only measure that matters is whether help arrives.

I spent years watching organisations with overlapping mandates duplicate effort, undermine each other for funding, and perform for stakeholders instead of delivering for the people they claimed to serve. What worked, when anything worked, was small teams, properly scoped risk, and no interest in credit. That carved the path for everything since, and it is why my co-founder came on board.

We named the company after an HTTP status code. 308. Permanent Redirect. The old path doesn’t work. We’re the new one.

BA, 308 co-founder

BA / Co-founder

Why now

The gap got wide enough to walk through.

Product development and partnership in this country are fragmented and hard to see into. Work gets won by people who will not build it, resold by people who did not make it, and sold on certainty nobody has earned. Meanwhile the people who can build have nowhere to do it together. 308 exists to be that place, and it runs one way – a rigorous method, our own hands on the work, and nothing white-labelled.

It is also built so it cannot drift into the thing we watched. There is no layer of people whose job is talking about the work, and no growth for its own sake. We are paid by delivery, accountable for what we ship, and small enough that everyone’s name is on something real. We grow at the pace the work sets, and we own the company outright.

A long shared workbench under industrial windows at midday, several part-built things spaced along it.
Founders

Two founders. One standard.

BA, 308 co-founder

BA

Co-founder / Leads 308 Research

The call on what 308 builds, and what it walks away from.

The field came first and the study after – international relations and security, then cyber and product capability built deliberately in the years since. Strategy, security and product development sit together in one head, because deciding what 308 builds and why takes all three.

NM, 308 co-founder

NM

Co-founder / Leads 308 Continuity

The call on when something is ready to deploy.

A background in mechatronics, then a career in agentic systems and RPA across high-assurance sectors, finance and insurance among them. That experience runs through the pipelines, the baselines, and the definition of done that survives production.

The team

Most of us you won’t meet on a website.

Our people and partners work where a name on a website carries real exposure, so the absence of a team page is duty of care. Partners choose their own visibility, project by project. They are named on the work they have chosen and unnamed everywhere else, at no cost to how the upside is shared. Client names stay off for the same reason. Under NDA we will walk you through the work itself, deliberately de-identified, including the architecture, the method, what held and what we changed.

Figures at work behind reeded glass, present and unresolvable.
What we do

One posture, three modes.

Continuity

Defined work, delivered and handed over. Transformation, AI adoption and workforce uplift, and infrastructure that comes out harder than we found it.

Research

Where the things the critical sectors can’t buy get made. Hardware and software, built through five gates and funded by delivery. Salus started here.

Impact

Protective work for the people and places that can’t pay. Our own projects, and pro bono work for aid organisations operating in conflict and disaster zones. Coming soon.

Method

Five gates, whoever the work is for.

  1. Need

    The same need keeps surfacing, and the workaround is costing someone.

  2. Definition

    The problem is written down precisely.

  3. Review

    Accountable people in the room. Plenty stops here. That is the system working.

  4. Build

    Security discipline from the first commit.

  5. Validation

    Judged by people who did not build it. It advances when it passes.

Where

Led from Australia. Built where it serves.

Australian-built.
Home
Sydney, Australia.
Reach
Australia and allied nations. We go where the work is, and every engagement is still led from here.
The rule
Australian-based contributors in Australia, without exception. Who builds a system is part of its supply chain.
The point
We don’t mark up offshore work and sell it back at a premium. Onshore is the whole idea.
Sectors
  • Defence, government, health, and the services that care for vulnerable people, including childcare, aged care and disability support.
  • Critical infrastructure across energy, water, communications, data, transport and food.
  • Mining and resources, financial services and markets, and advanced manufacturing.
The list is not closed – we work in any sector where a failure carries real consequence, and when one of these systems fails a person feels it before a dashboard does.
Where this is going

A home for builders, and the companies that come out of it.

Ten years out, we want a portfolio of companies that came out of Research. Clients and partners who have been with us long enough to stop checking our work. Contracts with organisations large and small, on terms nobody has to be nervous about. And a place where a builder can bring an idea without fear of it being taken, get support with no strings attached, and move on when their interests move on. People change, and so does what they are good at. A structure worth building makes room for that. Too much talent walks away because someone senior said no without thinking. Not here.

A long row of roller doors on an industrial shed, one of them standing open on darkness.

Tell us what’s at stake.

Message on Signal