Install

Requirements ​

• .NET 10+ Runtime
• Microsoft SQL Server with change tracking enabled

The encryption key ​

Trignis encrypts connection strings and credentials in its configuration files. It needs a key before the first run, supplied as TRIGNIS_ENCRYPTION_KEY.

On Windows, store it as a machine environment variable:

$bytes = New-Object byte[] 48; [Security.Cryptography.RandomNumberGenerator]::Create().GetBytes($bytes); [Environment]::SetEnvironmentVariable("TRIGNIS_ENCRYPTION_KEY", [Convert]::ToBase64String($bytes), "Machine")

In containers, pass the same variable through your compose file or secret store.

Docker ​

The setup script prepares environments/ and appsettings.json, then starts the container:

sh -c "$(curl -fsSL https://raw.githubusercontent.com/melosso/trignis/refs/heads/main/docker-setup.sh)"

To do it by hand, start from the docker-compose.yml in the repository.

Windows ​

1. Download the latest release and extract it to your deployment folder.
2. Set TRIGNIS_ENCRYPTION_KEY as above.
3. Run the executable once to confirm it starts, then install it as a service.

Enable change tracking in SQL Server ​

Trignis reads change tracking; it does not turn it on for you.

-- Database level
ALTER DATABASE YourDatabase
  SET CHANGE_TRACKING = ON (CHANGE_RETENTION = 2 DAYS, AUTO_CLEANUP = ON);

-- Per table
ALTER TABLE dbo.YourTable ENABLE CHANGE TRACKING;

CHANGE_RETENTION sets how long history is kept. If Trignis is offline longer than the retention window, the stored version becomes too old and the next run falls back to a full sync.

Verify ​

Start Trignis and open http://localhost:2455. The dashboard shows the environments it loaded and the objects it is tracking.