Become a Beta Tester

Containers · Platform

Frabs for Incus

On an Incus host, Frabs lists instances through Incus and watches each one's host-side interface.

Become a Beta TesterTry the Demo

Incus

Protects
Incus containers and VMs
Recognised by
The incus package
Watches
veth…
Panel links
Not needed

How it works

How Frabs works on Incus

  1. 01

    Install

    One command as root on the server. It reads the setup without changing anything.

  2. 02

    Recognise Incus

    The incus package tells the sensor which platform it is on.

  3. 03

    Find every guest

    incus list --format json.

  4. 04

    You confirm

    You review what it will watch. Protection starts within 30 seconds of confirming.

Networking

What it watches, and what it leaves alone

veth…

The host side of each instance's network device

Bridges. The bridge your instances use, such as incusbr0.

How traffic is counted. A Frabs-only nftables table on each guest interface. Your own firewall rules and the host's interfaces are not touched, and nothing changes until a rule or a person acts.

An example plan

PlatformIncus
Watchesveth…, …
Leaves aloneBridges with no guests
Changes madeNone until you act

Get started

Install on Incus

On the server, as root

curl -fsSL https://install.frabs.net | sh -s -- --token frb_...

Questions

Is anything installed inside the containers?
No. The sensor runs on the server itself, never inside a customer's guest.
Does Frabs change my bridges or firewall?
No. It counts traffic in its own nftables table on each guest interface, and only acts when your rules or your team say so.
What happens if I add a bridge or move guests?
The server's page shows that the layout changed. Run frabs reconnect, review the updated plan and confirm.
What if the sensor stops?
Its network changes are removed and traffic carries on, unless you chose fail-closed.

Also supported

Other platforms

See it with real data

Become a Beta TesterTry the Demo