About Athena & Version Information
Before you plan an upgrade, compare two servers or open a support request, you need to know exactly which Athena build is running. Athena shows this in two places: a short version line in the footer of the sign-in screen, and the full About page inside the console.
Version on the sign-in screen#
The footer of the sign-in page (and of the start page at the server's root address) shows a line like this:
JWT session · local only · 59f5a70d · 0.9.2
| Part | Meaning |
|---|---|
59f5a70d | The short commit: the first 8 characters of the commit the server was built from. |
0.9.2 | The product version. Every kind of Athena server reports the same number: Docker, the virtual appliance and any other install. |
You can read this line without signing in, so it is a quick way to check which release a server runs, even when you don't have an account on it. The footer shows only the commit and the version. Host and configuration details are on the About page, which requires sign-in.
The About page#
To open it, click your initials (the avatar) at the top right of the console and choose
About. You can also go straight to https://<athena-server>:8443/about.
Any signed-in user can open the page. It needs no special permission.
The banner at the top shows a Version badge and an environment chip. Below them are four panels.
Version badge and environment chip#
- Version: the build version, a timestamp of when the server was built, in the
form
yyyy.MM.dd.HH.mm(for example2026.10.21.17.28). Use it to tell apart two builds that share a product version. - Environment chip: the environment the server process runs under. The chip is green when it
reads
Productionand amber for anything else (for exampleDevelopment). If no environment is set, Athena reportsProduction. It is set with theASPNETCORE_ENVIRONMENTenvironment variable. The chip is not a health indicator. For health, see Server Health & Monitoring.
01 · System Information#
| Field | What it shows |
|---|---|
| .NET Version | The version of the .NET runtime the server runs on. |
| Operating System | The host operating system and build, as the server process sees it. In a container, this is the container's OS. |
| Machine Name | The host name of the server. In a container, this is the container's host name. |
| Processor Count | The number of logical processors available to the server process. |
| Server Time | The server's local clock when you opened the page (yyyy/MM/dd HH:mm:ss). It does not tick, so reload the page to refresh it.
Use it to spot clock drift between the server and your machine. |
02 · Build Information#
| Field | What it shows |
|---|---|
| Build Date | When this server build was made (yyyy/MM/dd HH:mm:ss). This is the same moment as the Version badge. |
| Commit | The full commit identifier of the build. Its first 8 characters are the short commit in the sign-in footer. It is plain text, not a link, because Athena runs air-gapped. |
| Environment | The same environment as the chip in the banner. |
| Language | The console language in use for your session, as a code (for example EN). See
Languages & Localization. |
03 · Configuration#
This panel shows the configured values for the server's ports and data stores. If a setting is not configured, the page shows Athena's default.
| Field | Setting | Shown when not set |
|---|---|---|
| Web Port | Server:WebPort: the HTTPS port for the console and REST API | 8443 |
| API Port | Server:ApiPort: the port agents connect to | 8444 |
| Database Provider | Database:Provider | SQLite |
| Audit Provider | Audit:Provider | File |
The About page reads these values from configuration. It does not connect to the database or the audit store, so it can't tell you whether they are reachable or healthy. For live checks, use Server Health & Monitoring. To change the values, see Configuration and Network Ports & Firewall.
04 · Credits#
The product credit line and copyright notice.
When a field says “dev”#
Release builds always carry a commit and a product version. If the commit or the product version shows
dev, the build was made without that information, typically a locally built server.
Mention this in a support request.
What to include in a support request#
When you contact support@sealgrid.ai, copy these values from the About page:
- The product version from the sign-in footer (for example
0.9.2). - The Version badge (build version) and the full Commit.
- The Operating System and .NET Version.
- The Database Provider and Audit Provider.
On the virtual appliance, Settings → Appliance → Overview also shows the appliance release and its operating-system version, and you can attach a support bundle from the appliance's support tools. See Appliance overview and Support: bundles, server log and OS journal.
Versions and backups#
An appliance backup records the build version of the server that made it. When you restore, the preview shows the backup's build next to the build installed now. A backup from a newer build is refused until you update the appliance. Backups from the same or an older build are accepted. See Appliance Backup & Restore.