SG SealGrid Athena Docs

Architecture

Athena is three parts you host yourself — the server, the Hermes agent, and pluggable providers — communicating over two TLS ports with no cloud dependency.

Components#

Ports & protocols#

PortSurfaceProtocolAuthentication
8443Web UI + REST APIHTTPS (Kestrel)JWT authentication
8444Agent gatewaygRPC over HTTP/2 (HTTPS)X.509 certificate authentication

Agent communication#

The agent opens an outbound gRPC connection to port 8444 — there are no inbound agent ports and no external broker.

The agent keeps a bidirectional streaming gRPC channel open to the server for live commands and telemetry, and makes a separate one-time registration call when it first enrolls. All of it runs over the single outbound connection on port 8444.

SettingValue
Keep-alive ping delay60s
Keep-alive ping timeout30s
gRPC max message size67108864 bytes (64 MB) — to allow video/file transfers

Database & plugins#

The database provider is chosen by Database:Provider. Providers shipped as plugins:

SQL Server is not shipped.

At startup the server scans plugins/Database/ and plugins/Audit/ and loads the provider plugins it finds there, registering each by name (Plugins:BasePath = "plugins").

Authentication model#

The web console and REST API use JWT bearer tokens (15-minute expiry, held in browser localStorage); agents authenticate with per-agent X.509 certificates issued by the server's Root CA.

See Agent Enrollment and Roles & Permissions.

Storage layout#

The server persists state on local disk:

LocationContents
dataDatabase + state
pkiRoot CA + issued certs
packagesDeployment payloads
agent-binariesInstallers / updates
certsServer TLS PFX
logsServer logs
backupsDatabase backups

These map to the Docker volumes in Installation.