Skip to content

How it works

From the command to the first verified block.

Generate a single-use token in the dashboard, paste the command on the server and watch. No inbound port open: the agent only speaks outbound HTTPS.

root@web-sp-02: ~

$ curl -fsSL https://get.sentinnel.com.br/install.sh | sudo bash -s -- --token <TOKEN>

→ checking system: Ubuntu 24.04 · amd64 · iptables-nft

→ downloading atalince-agent (ed25519 signature checked)

→ systemd service installed and started

✓ connected · mode: Monitor only

01Architecture

Four parts, one path.

The agent sends events over HTTPS and keeps a WebSocket open to receive dashboard requests right away.

  1. 01 · agent

    atalince-agent

    A Go binary on your server. Reads logs, applies and checks the firewall.

    systemd · amd64 · arm64

  2. 02 · telemetry

    Telemetry

    Ingestion, queues and a persistent WebSocket.

    hosted in Brazil

  3. 03 · dashboard

    Dashboard

    app.sentinnel.com.br, in real time.

    pt-BR · en · es

  4. 04 · you

    You and your team

    Alerts by email, Slack, Telegram and webhook.

    2FA · roles

heartbeat
60 s
configuration sync
20 s
no contact → unknown
90 s
read-back of every block
1 h

02Step by step

The first fifteen minutes.

  1. 1

    Generate the token

    In the dashboard, under Servers › Add. The token is valid for a single registration.

  2. 2

    Run the command

    The installer checks the system, downloads the agent with its ed25519 signature and SHA-256 verified, and installs the systemd service.

  3. 3

    Watch the server arrive

    It shows up in the list a few seconds after the command finishes, already sending data, in Monitor only.

  4. 4

    Add your IP to the allowed list

    Before any block, make sure your own access will never be blocked.

  5. 5

    Turn on protection mode

    From here on, every block goes through the trail: detected, requested, applied and verified.

  6. 6

    Pick your alerts

    Email, Slack, Telegram or webhook, with daily and weekly digests if you prefer less noise.

03When something fails

Designed for the bad day.

Unstable network
Events go to a durable local queue and reach the dashboard when the connection is back. Local protection doesn't wait for the network.
Updates
Signed (ed25519 + SHA-256). If the new version gets into a crash loop, the agent rolls back to the previous one on its own.
Firewall reloaded
If a ufw, firewalld or CSF reload removes the jump to the block chain, the agent notices and restores it.
Uninstall
The same installer with --uninstall removes the agent and only atalince's own state.

04Questions

Technical questions.

Do I need to open any port on the server?

No. The agent only needs outbound HTTPS on port 443 to talk to the dashboard.

Does the agent run as root?

Yes, as a systemd service. Reading system logs and applying rules in the kernel firewall require that access.

What if I use Docker or Coolify?

It works. The agent runs on the host and also covers ports published by Docker, like the ones Coolify and Compose create. See the compatibility page.

What happens if the dashboard is down?

The agent keeps reading logs and protecting the server. Events wait in a local queue and are sent when the connection is back.

How do I remove atalince?

Run the installer with --uninstall. It removes the agent and atalince's state, without touching your other rules.

Founders program

Use atalince from the start.

Pro features for up to 3 servers, free of charge, for 12 months. Every application is reviewed by the team.

Become a Founder