Skip to main content
Brontes administers the Myrmex platform itself. It knows the assets you’ve registered — their health, their configuration, the software installed on them — and it also holds the switches: onboarding a new agent, authorizing a device, turning a module on, organizing folders, managing the automation library.
Brontes works over the assets registered in Myrmex — the devices you’ve onboarded and authorized. It is not a discovery tool: for what’s on the network without being registered, that’s Apolo.

​
What Brontes Tracks

For each registered device, Brontes maintains the same picture you see in a device’s System Info:

Health & status

Whether a device is online or offline, its agent version, and when it last reported in.

System information

Operating system and version, CPU and memory, the device’s Myrmex ID, and its public IP.

Installed software

The applications and software inventory reported from the host.

Configuration

How the device is set up and labeled — its role, folders, tags, and severity.

​
What Brontes Administers

Beyond reading the inventory, Brontes holds the platform’s own controls:

Onboarding and authorization

Generating installation tokens and installers, and authorizing a device once it reports in.

Module switches

The per-target Audit, Vulnerability and Topology switches that decide what gets collected — see Frameworks & scanning.

Folders and contexts

The folder hierarchy your assets live in, and the governance context each one belongs to.

The automation library

Books — the playbooks and runbooks available in your environment.
Ask Brontes things like “which of my devices are offline?”, “what’s installed on this server?”, or “show me the Windows machines running an old agent version”, and it answers from the assets in your context.

​
Brontes vs. Perseus

Brontes and Perseus both work with endpoints, but they do different jobs:
  • Brontes administers — it knows what your registered assets are, how they’re doing, how they’re configured, and it holds the platform switches that govern them. Think visibility, organization and enrolment.
  • Perseus acts — it investigates a host in depth and runs response actions on it (isolate, quarantine, kill a process, remediate).
When you need to understand your fleet, that’s Brontes. When you need to do something to a host, Centurion brings in Perseus.
Brontes is an AI agent. The software agent is the program installed on each host that reports the telemetry Brontes reads. The two share the word “agent” but are distinct — Brontes interprets what the software agent collects.

​
Where to Go Next

Endpoints view

Browse and organize the device inventory Brontes tracks.

Device details

Open a single host to see the same information, focused.

Perseus

The specialist that acts on hosts.

Apolo

What’s reachable on the network, registered or not.

Deploying the agent

Register a new asset so Brontes can track it.
Scope your question to one machine by @-mentioning the device — Brontes then answers about just that host.