Firevault, offline secure storage, physically disconnected from the internet
Pricing

Firebreak®Supplied by Firevault within Control

Cut the path, not the business.

Firebreak® is Layer 1 hardware that physically opens and closes network paths on command, zone by zone. The command arrives out of band, so the unit never depends on the network it is there to cut.

Four models, copper and fibre, rack and desktop.

Firebreak R1200-12E unit, front view
Firebreak® R1200-12E. One 1U unit, twelve port pairs, each its own physical switch.

What happens when

One compromised account. Every connected zone in reach.

Most networks are built to stay connected. When something goes wrong, the paths an attacker needs are already there.

  1. A supplier account is used.

    Remote access for a vendor, a reused password or a compromised laptop. Nothing looks wrong yet.

  2. The paths are all open.

    Plant, finance systems and backups sit on routes that exist all the time, whether anyone needs them or not.

  3. Someone has to pull cables.

    Without a physical control, separating a zone means rule changes on reachable devices, or a site visit.

A firewall decides what crosses. Firebreak® decides whether the path exists.

See recent breaches

What Firebreak is

A switch, not a sensor.

Firebreak does one job completely: it decides whether the path exists at all.

A Layer 1 switch in the network path, commanded from off the network.

  • In the network path

    Each port pair is its own physical switch, copper or fibre. An air gap you can create and reverse on demand.

  • Commanded out of band

    Cellular SMS, a dedicated out-of-band Ethernet network or a token-gated API. Never the network being controlled.

  • Logged and reversible

    Every cut and restore is recorded with the actor, the channel and the outcome, locally and to SysLog.

What it changes

Take control of a zone, without stopping the rest.

An incident is still an incident. The difference is that you can remove one path deliberately, and prove you did.

Cut one zone. Leave the others connected.

  • Close a vendor window on schedule, not when someone remembers
  • Isolate a single circuit without touching the rest of the estate
  • Reverse the cut on the same out-of-band command, with no site visit
  • Show auditors and regulators a record of every action
See the range

Where it fits

Wherever a path should exist only on purpose.

Three kinds of organisation, the same question: what should be connected, and when.

Switch between the two endings.

Path open

NATO and defenceTier-1 programme

The moment

A classified test range needs partner connectivity, but only some of the time.

A standing link to partners is a standing route in.

The range stays reachable.

Between partner sessions, the path is still there for anyone who finds it.

An air gap on demand.

Operator-triggered disconnect on command, full audit log, no inline software in the path.

Path open

Critical national infrastructureMulti-site utility

The moment

Patching windows and SCADA incident response touch the IT and OT boundary.

Separating the two usually means a site visit or a rule change on a device that can be reached.

The boundary depends on software.

Severing IT from OT means changing rules, or sending someone to pull cables.

The boundary is severed when it needs to be.

Scheduled and ad-hoc cuts over SMS and REST API, with no re-architecture of the control network.

Path open

Regulated financeTrading floor

The moment

A settlement enclave must be provably separate from the wider corporate network.

Auditors want evidence of isolation, not a description of it.

Isolation is a claim.

The enclave is separated by configuration, and proving it takes time.

Isolation is a recorded physical state.

Verifiable physical isolation on demand. The out-of-band command path satisfied both internal audit and external regulator review.

The range

Four models, copper and fibre.

From a desktop edge unit to the patented 12-pair flagship. Every model runs fail-open or fail-closed, chosen for each deployment.

Firebreak R1200-12E unit
R1200-12EFlagship · Copper rack, 12 pairs

Quotedwithin a Control proposal

Large estates with many zones to control from one 1U unit

  • 1U, 19 inch rack
  • 12 × RJ45 port pairs
  • Up to 10 GbE per pair
  • Reed-switch Layer 1 switching
  • Dual redundant AC PSU, 100 to 240 V, 50/60 Hz
Request a datasheetOrganise a demonstration
Firebreak R1100-4F unit
R1100-4FFibre rack, 4 pairs

Quotedwithin a Control proposal

Fibre boundaries and higher-speed uplinks

  • 1U, 19 inch rack
  • 4 × SFP / SFP+ / SFP28 pairs
  • 1, 10 or 25 Gbps per pair
  • Physical optical switching, no inline buffer
Request a datasheetOrganise a demonstration
Firebreak R1200-4E unit
R1200-4ECopper rack, 4 pairs

Quotedwithin a Control proposal

A small number of critical copper paths

  • 1U, 19 inch rack
  • 4 × RJ45 port pairs
  • Up to 10 GbE per pair
  • Reed-switch Layer 1 switching
Request a datasheetOrganise a demonstration
Firebreak S1200 unit
S1200Edge · Desktop edge unit

Quotedwithin a Control proposal

Branch, edge and single-site boundaries

  • Small-form desktop
  • 4 × RJ45 port pairs
  • Up to 10 GbE per pair
  • Reed-switch Layer 1 switching
Request a datasheetOrganise a demonstration
Fail-open or fail-closed

You decide how each path behaves if power or command is lost, based on whether safety or isolation matters most for that zone.

Supplied within Control

Firebreak® is the Layer 1 cut, commanded through Control by Firevault, with the services around it. It is quoted as part of a Control proposal.

  • Out of bandThe command path never runs over the network it controls.
  • No software in the data planeNo inline protocol stack and nothing to inspect when the link is gone.
  • Per-zone controlUp to twelve independent zones in one 1U unit.
  • Logged to SysLogActor, channel and outcome for every cut and restore.

How it works

Command arrives off the network. The path opens or closes in hardware.

A physical disconnect, not another firewall. Pick a zone below to see one cut while the others stay connected.

Disconnected

One zone, start to finish

  1. Step 1Every zone connected

    Each port pair has its own physical switch, so every zone has its own path.

  2. Step 2The command arrives out of band

    An operator, scheduler or approved system sends it by SMS, out-of-band Ethernet or API.

  3. Step 3One zone is cut

    The Layer 1 path opens. The rest of the estate stays connected.

  4. Step 4Restored, with a record

    The same command path reconnects it. Action logging depends on the configured record-keeping.

What stays as it is

  • Your firewalls and network design
  • Your monitoring and detection tools
  • Zones you are not cutting stay connected
  • No agent or software on your hosts

Supplied by Firevault within Control.

  • Network configurationWe help map ports, zones and command paths to your existing architecture.
  • Support model designRoles, runbooks and on-call patterns so cuts and restores are routine.
  • Naming and command structuresClear conventions for ports, zones and Plans, so every action reads the same way.
  • Secure command processesApproval, authentication and audit flows that stand up to internal and external review.

Recognition

NATO DIANA award logoTechnology Reseller Awards 2023 Winner, Hardware/Endpoint Device of the Year award logoSC Awards Europe 2025 Winner award logo

Questions

What network and security teams ask.

Want your engineers to see it first? We will show a live cut and restore.

Is Firebreak an air gap?

On demand, yes. When Firebreak cuts a path, the segment is severed at Layer 1. It is disconnected on that interface, invisible to scans on it, and independent of any software that might have been compromised.

Does Firebreak replace firewalls?

No. Firewalls inspect and filter traffic on connections that still exist. Firebreak removes the connection itself. The two complement each other rather than substitute for each other.

Does Firebreak inspect or filter traffic?

No. Firebreak sits at Layer 1 and has no inline protocol stack in the data path. When the path is cut, there is no payload to inspect because there is no link.

How are commands authenticated?

The command path is out of band by design. The web interface uses multi-factor authentication with brute-force protection. SMS uses structured commands with number filtering and a secondary code. The API uses scoped access tokens.

How quickly does a cut happen?

The switching itself is in the millisecond range. End-to-end timing also depends on how the command is delivered, authorised and processed, so it is measured for each deployment rather than promised in advance.

How does Firebreak fit into Control?

Control by Firevault is the wider framework of nine modules, packaged into Control Plans and industry Blueprints. Firebreak is the physical control point that delivers the Layer 1 cut wherever a Plan or Blueprint calls for one.

How does Firebreak support compliance evidence?

Every cut, restore and command is logged on the appliance with the actor, the channel and the outcome. That evidential trail can help support the isolation and operational-resilience expectations in regimes such as NIS2 and DORA.

Do you offer help with deployment?

Yes. Our professional services team helps you choose the right model, plan the rollout and operate it well, through to handover to your operations team.

Who makes Firebreak?

Firevault manufactures Firebreak® and supplies it within Control by Firevault, with the professional services around it.

Your next step

See a path cut in front of you.

A member of the team will show you a live cut and restore, then map the right model to your ports and zones.