For everyone who runs more than one server

Every attack on your servers in one place. One signed click to respond.

ARES Central joins every server running ARES Server Guardian into a single dashboard. See the whole fleet's health, alerts and attackers, trace any address across every server, and push firewall changes to one server, a tag or the whole fleet, each one signed, confirmed with 2FA and audited.

ARES Central ยท Overview
The ARES Central overview: servers online, active bans, open alerts and attacks over the last 24 hours across six demo servers.
0inbound ports to open on your servers: they dial out
15 sbetween reports from each server
5 minlifetime of each signed firewall command
41exploited vulnerabilities (CVEs) in the web signature pack
3 rolesviewer, operator and admin, with 2FA required by default

From a dozen consoles to one

Attackers do not pick one server. They try the same addresses, passwords and exploits on all of them.

Attacks arrive server by server

Each server only knows its own logs.

Central merges them: an address that hits five servers is one attacker, with one timeline.

Banning means logging in everywhere

The same ban typed on every box, or forgotten on one.

One action reaches one server, a tag or every server. Offline servers get it when they reconnect.

Logs nobody has time to read

Thousands of lines a day, per server.

Alerts, attack traces, rates and an optional AI analysis tell you what matters and what to do next.

What you can do with it

Every screen below is from the live demo, with invented data.

Fleet overview

Know at a glance which servers are under attack

Servers online, load, active bans and open alerts for the whole fleet, with attacks per hour over the last day. Open any server to see its health, firewall rules, processes and history.

  • Live updates while the page is open
  • Tags such as prod, web or mail to group servers
  • Offline servers and clock drift raise alerts
The Servers page listing six demo servers with status, tags, load and bans.

Attackers and attack trace

Follow one address across every server

Attackers lists every address that attacked any server, merged across the fleet, with country, network and attack types. Trace attack shows everything known about one address: timeline, servers and sites hit, requested paths, user agents and bans, as a table, raw lines or JSON.

  • Ban, unban or allow from the same page
  • Download what you see as raw lines or JSON
  • Optional one-click AI reading of a trace
An attack trace for one demo address: attack types, servers, paths and a timeline.

Firewall everywhere

Change the firewall on one server, a tag or all of them

See every distinct rule across the fleet and which servers carry it. Ban, allow, block a port or rate-limit, then watch each server confirm with its own answer under Commands.

  • Permanent fleet bans for repeat offenders
  • Allowed and denied DNS names that follow IP changes
  • Anti-DDoS rate-limit presets
The Firewall page: rules across the fleet with the servers carrying each one.

Web attacks

Stop exploits against your sites before they land

Web apps shows the sites and applications under attack, from the web servers' own access logs. Push blocking rules and a signature pack for 41 exploited vulnerabilities to your servers, in alert or block mode.

  • WordPress sign-in guessing, .env probes, plugin uploads
  • Rules per site or for every site
  • Hits and last match per rule
The Web apps page: demo sites under attack and the web firewall rules applied to them.

AI analysis and reports

A clear risk picture, on request or every week

Optional analysis with Claude reads the attacks collected across your servers and returns a risk score, risk by area, findings with evidence, threats and recommendations. Reports can be scheduled and emailed as HTML with a PDF, and every query's cost is tracked.

  • Off until an admin turns it on
  • The model gets no tools: its answer is only displayed
  • Mask the last part of each address if you prefer
An AI analysis report with an overall risk score, risk by area, findings and recommendations.

Logs, audit and API

Prove what happened, and feed your other tools

One Logs page for attacks, alerts, commands and the application's own log. Audit & Activity records every sign-in, change and API call, with CSV and JSON export. Everything is also a JSON API with personal tokens, and events go to your SIEM over syslog or HTTPS.

  • Append-only audit and activity logs
  • API tokens with read, write or admin scope and an expiry
  • Splunk, Elastic, Graylog, Loki, Wazuh or any syslog collector
The Audit and Activity page with filters and an export button.

Up and running in three steps

  1. 1

    Protect each server

    Install ARES Server Guardian. It detects attacks in the server's logs and bans them at the firewall on its own, with or without Central.

  2. 2

    Join it to Central

    In Add server, create a one-time join code and run the command it shows on the server. The server makes its own key and dials out; you open no port on it.

  3. 3

    Watch and respond

    Reports arrive every 15 seconds. Investigate from Attackers and Logs, and respond with one signed change for one server, a tag or the whole fleet.

Security by design

Built so that taking over Central gains an attacker as little as possible

Central can change firewalls on every server, so it is the first thing an attacker would want. It is designed around that.

  • No remote shell. Commands are a fixed list of firewall operations. There is no way to run programs or read files on a server.
  • Two independent proofs. Mutual TLS 1.3 proves who is connected; a separate Ed25519 signature on each command names one server, expires in 5 minutes and cannot run twice.
  • Servers can say no. Each Guardian keeps its own safety rules (it never bans private, whitelisted or Central's own addresses), and its owner can make it read-only.
  • A fresh 2FA code for anything dangerous. Firewall changes, adding servers and user changes ask again, and every action is in the audit log.

Works with the tools you already use

Your SIEM

ECS JSON events over syslog (RFC 5424, UDP, TCP or TLS) or HTTPS: Splunk HEC, Elastic, Graylog, Loki, Wazuh or a Sentinel collector. Audit events are never lost during an outage.

Scripts and automation

Every function is a JSON API under /api/v1/, with personal tokens limited by scope and expiry, and an OpenAPI description for signed-in users.

Monitoring and backups

Health endpoints for uptime monitors and APEX Pingmora. Scheduled backups, kept locally or copied to another server over SFTP.

Questions

Do I need to open a port on my servers?

No. Each server connects out to Central's gateway over mutual TLS. Only Central needs a reachable gateway port.

What happens if Central is down?

Each Guardian keeps detecting and banning on its own. When Central is back, the servers reconnect, send what Central missed, and receive any queued changes.

What can I do in the demo?

Look at everything a viewer can: overview, servers, alerts, attackers and traces, firewall, policies, web apps, logs and the AI report. The demo is read-only, its six servers are invented, and its addresses come from ranges reserved for documentation.

Is my data sent anywhere?

Only where you choose. AI analysis is off until an admin turns it on, and then sends attack data to Anthropic. Log forwarding and SFTP backup copies go only to the destinations you configure.

Who can do what?

Viewers read. Operators also change firewalls and policies. Admins also manage users, settings, backups and AI analysis, and read the audit and application logs. Two-factor authentication is required by default.

See your fleet the way an attacker does

Open the demo and look around, or sign in to your own Central.