Documentation

Install, configure, and integrate.

Everything you need to deploy TRIVLA agents, connect them to your portal, and query the REST API.

Getting started

TRIVLA documentation

TRIVLA has three components: the agent (edge sensor), the portal & API (control plane), and analytics storage (MySQL, Redis, StarRocks). This guide walks through installation and configuration.

Licensing

Each agent requires a license key. Keys are bound to your account, signed by TRIVLA, and validated on first connection. The agent caches the license in local SQLite for offline operation.

  1. In your portal, open Manage โ†’ Licenses. Click Get free Community key, or buy a Professional / Enterprise key from your account at trivla.com.
  2. Copy the key and apply it during agent installation or via trivla-agent license set <KEY>.
  3. The agent registers with the portal API and begins streaming telemetry.
โ„น

The free Community key includes core features and free agent seats. Professional and Enterprise plans add advanced analytics, TLS decryption, and more seats โ€” see pricing.

Firewall rules

Firewall policy is defined in the portal and pushed to agents. Supported rule types:

  • โœ“ Block / allow IP and CIDR
  • โœ“ Block / allow country and ASN (Geo-IP via MaxMind GeoLite2)
  • โœ“ Rate limiting and protocol blocking

Backends are selected automatically: nftables + ipset on Linux, pf on BSD, WFP on Windows.

Portal connection

Configure the agent to point at your portal API endpoint. For self-hosted deployments:

/etc/trivla/agent.conf
[portal]
url = https://portal.example.com/api/v1
license_key = trvl_xxxxxxxxxxxxxxxx

[agent]
name = edge-fw-01
interfaces = eth0,eth1

For TRIVLA Cloud, use https://portal.trivla.com/api/v1 as the default endpoint.