Windows Installation Guide for digna Release 2026.11¶

Release: 2026.11

Last Updated: November 7, 2026

Table of Contents¶

1. Introduction
2. System Requirements
3. Pre-Installation Setup
4. PostgreSQL Server Setup
5. Web Server Configuration
6. Initial Installation
7. Backend Configuration
8. Dashboard Configuration
9. Running digna as a Windows Service
10. Upgrading to a New Release

Introduction¶

About digna¶

digna is a comprehensive AI-driven platform designed to optimize data quality management across various data environments such as warehouses, lakes, and lakehouses. Built to be highly scalable and adaptable, digna addresses modern data challenges through automation, real-time monitoring, and anomaly detection.

digna consists of two main components:

• digna: The core engine of the application, responsible for processing data and performing quality checks. It combines the backend and the command line interface in a single executable, replacing the separate dignabackend and dignacli of earlier releases.
• dignadashboard: A web-based interface hosted on a web server, providing a user-friendly way to interact with the digna platform and visualize data quality metrics.

What's New in Release 2026.11¶

This release adds digna Data Reconciliation, digna Agentic with the digna MCP Server, and the digna Engine, which can profile data inside digna and check referential integrity between different database technologies. See the release notes for complete details.

For an installation, the release brings a new repository migration mechanism, an optional [duckdb] section in config.toml for the digna Engine, and a new license file. The upgrade section covers each of them.

Looking for macOS or Linux?¶

This guide covers Windows. For other platforms, see the macOS Installation Guide or the Linux Installation Guide.

System Requirements¶

Before you begin the installation, ensure that your system meets the following minimum requirements:

Database Installation Options¶

If PostgreSQL is already installed: You can add a new database for digna to your existing PostgreSQL Server.

If installing PostgreSQL on the same machine as digna:

Pre-Installation Setup¶

Before installing digna, ensure that two key prerequisites are in place:

1. PostgreSQL Server – for storing calculated metrics and performance data
2. Web Server – for hosting the digna Dashboard

If these components are not already set up, follow the sections below to install and configure them.

PostgreSQL Server Setup¶

If You Already Have PostgreSQL¶

If PostgreSQL is already installed and running on your local machine or if you are using a managed remote PostgreSQL server, you can skip to the next section.

Installing PostgreSQL¶

Follow these steps to install PostgreSQL on Windows:

Step 1: Download PostgreSQL¶

1. Visit the PostgreSQL Downloads page
2. Select Windows
3. Download the latest installer

Step 2: Run the Installer¶

1. Double-click the downloaded installer file
2. Follow the prompts in the setup wizard

Step 3: Choose Installation Directory¶

Select the directory where PostgreSQL will be installed. The default location is usually appropriate.

Step 4: Select Components¶

For a standard setup, keep the default component options selected.

Step 5: Set PostgreSQL Superuser Password¶

Enter and confirm a password for the PostgreSQL superuser (postgres). Save this password securely — you will need it later.

Step 6: Configure Port Number¶

The default PostgreSQL port is 5432. You can use the default or specify a different port if needed.

Step 7: Choose Locale¶

Select the locale for your database. The default is usually suitable for most installations.

Step 8: Complete Installation¶

Click Next through the remaining steps, then click Finish.

Step 9: Verify Installation¶

Open Command Prompt and verify PostgreSQL is installed:

psql --version

You should see the PostgreSQL version if the installation was successful.

Web Server Configuration¶

digna requires a web server to host the dashboard. Choose one of the following options:

• Internet Information Services (IIS)
• Apache Tomcat

You only need to install and configure one of these servers.

IIS Setup¶

Overview¶

Internet Information Services (IIS) is Microsoft's web server for hosting websites and web applications.

Enabling IIS¶

1. Open Control Panel
2. Press Win + R

3. Type control and press Enter

4. Navigate to Windows Features

5. Click Programs

6. Select Turn Windows features on or off

7. Enable Internet Information Services

8. Scroll down and find Internet Information Services (IIS)
9. Check the checkbox to enable it

10. Click the + to expand and verify these subcomponents are selected:

    • Web Management Tools
    • World Wide Web Services

11. Click OK to apply changes

12. Verify IIS Installation

13. Open your browser
14. Navigate to http://localhost
15. You should see the IIS Welcome page

Required: URL Rewrite Module¶

IIS requires the URL Rewrite component. Download and install it from the official Microsoft page.

Required: MIME Type for Markdown Files¶

To ensure Markdown files (.md) are served correctly by IIS:

1. Open IIS Manager (press Win + R, type inetmgr, press Enter)
2. Navigate to Your Site > MIME Types
3. Click Add...
4. Configure:
5. File name extension: .md
6. MIME type: text/markdown

Apache Tomcat Setup¶

Overview¶

Apache Tomcat is an open-source Java servlet container and web server.

Installation¶

1. Download Apache Tomcat
2. Visit Apache Tomcat Downloads

3. Download the Windows ZIP distribution

4. Extract the Archive

5. Extract the ZIP file to a directory on your system

6. Example: C:\Program Files\Apache Tomcat

7. Verify Tomcat is Running

8. Open your browser
9. Navigate to http://localhost:8080
10. You should see the Apache Tomcat welcome page

Initial Installation¶

Step 1: Set Up the digna Repository¶

The digna repository stores all metrics calculated by digna. It acts as the central database for analytical and performance data.

Create Repository Schema and User¶

Open your PostgreSQL client (pgAdmin, psql, or similar) and execute the following SQL commands:

CREATE SCHEMA <digna_repo_schema>;

CREATE USER <digna_repo_user> WITH PASSWORD '<digna_repo_password>';

GRANT ALL PRIVILEGES ON SCHEMA <digna_repo_schema> TO <digna_repo_user>;

Replace the following placeholders:

• <digna_repo_schema> — Your desired schema name (e.g., dignarepo)
• <digna_repo_user> — Your desired username (e.g., digna_user)
• <digna_repo_password> — A secure password for this user

Example:

CREATE SCHEMA dignarepo;

CREATE USER digna_user WITH PASSWORD 'YourSecurePassword123!';

GRANT ALL PRIVILEGES ON SCHEMA dignarepo TO digna_user;

Step 2: Extract the digna Installation Package¶

1. Locate the digna installation ZIP file provided to you
2. Extract it to your desired installation location
3. After extraction, you should see the following items:
4. dashboard/ — Web dashboard interface
5. digna — Main executable (backend + CLI combined)

Step 3: Install the License File¶

1. Locate the license.toml file provided to you
2. Copy it into the root digna installation directory (where config.toml and the digna executable are located)

Why this matters: The license file contains your customer information, license expiration date, and digital signature. Do not modify this file — any changes will invalidate it.

Directory structure after setup:

digna_installation/
├── config.toml         (configuration file)
├── license.toml        (YOUR LICENSE FILE - copy here)
├── digna               (main executable)
└── dashboard/          (web interface)
    └── (dashboard files)

Backend Configuration¶

Step 1: Create and Edit the Configuration File¶

The config_template.toml file is provided in your digna installation directory. You only need to rename it to config.toml.

Location: digna_installation/config.toml

Open config.toml in a text editor and configure each section below.

[app] Section¶

This section configures cross-origin resource sharing (CORS) between the dashboard and the backend:

[app]
DIGNA_APP_CORS_ALLOW_ORIGINS = ["http://localhost:5173"]
DIGNA_APP_CORS_ALLOW_CREDENTIALS = true

[repo] Section¶

This section configures the connection to the PostgreSQL database:

[repo]
DIGNA_REPO_HOST = "localhost"
DIGNA_REPO_PORT = 5432
DIGNA_REPO_DB = "postgres"
DIGNA_REPO_SCHEMA = "dignarepo"
DIGNA_REPO_USER = "digna_user"
DIGNA_REPO_PASSWORD = "YourSecurePassword123!"
DIGNA_REPO_SSLMODE = "prefer"
DIGNA_REPO_NUM_CONNS = 16

[base] Section¶

This section contains security, cookie and inspection settings:

[base]
DIGNA_FERNET_KEY = "DU4a0yJ-OqvbKCL4hNQn_CsknH-V1vWmHZqBUl-AY44="
DIGNA_COOKIE_DOMAIN = "localhost"
DIGNA_COOKIE_SECURE = false
DIGNA_COOKIE_HTTPONLY = true
DIGNA_TOKEN_EXPIRES_IN = 86400
DIGNA_MAX_WORKERS = 4
DIGNA_FRONTEND_BASEURL = "http://localhost/"
DIGNA_SOURCE_QUERY_TIMEOUT_SEC = 3600
DIGNA_SOURCE_LOGIN_TIMEOUT_SEC = 30

[encryption] Section¶

This section holds the key used to encrypt sensitive values stored in the repository. It is required — config check reports the [encryption] section as FAILED if the key is missing.

[encryption]
DIGNA_ENCRYPTION_KEY = 'ycELf6IbcO55dYIZHpPv6kQv/bbnUXoIaHLh2bh1kMg='

[logging] Section¶

This section configures logging behavior:

[logging]
DIGNA_LOGGING_MODE = "INFO"
DIGNA_LOGGING_DIR = "logs"
DIGNA_LOGGING_MAX_FILES = 30

[duckdb] Section (Optional)¶

New in Release 2026.11. This section sets the resources of the digna Engine, which profiles data inside digna for database connections whose profiling location is digna Engine, and runs referential integrity checks between data sources on different database connections. See Profiling Location.

The section is optional. Without it, the defaults below apply.

[duckdb]
DIGNA_DUCKDB_MEMORY_LIMIT_MB = 1024
DIGNA_DUCKDB_TEMP_DIRECTORY = "C:\\path\\to\\digna\\tmp"

mkdir C:\path\to\digna\tmp

Step 2: Validate the Configuration¶

Before initializing the repository, check that config.toml is complete and well formed. In your digna installation directory, run:

digna config check

Every section is validated on its own, so a single mistake does not hide the state of the rest:

Configuration validation report (source: config.toml):
 - App config: OK
 - Repository config: OK
 - Base config: OK
 - Logging config: OK
 - Encryption config: OK
 - OIDC config(s): OK
 - Template overrides: OK
 - Unknown keys: OK

Overall: OK

Fix anything reported as FAILED and run the command again before continuing. A WARNING under Unknown keys lists keys in config.toml that digna does not read; they have no effect, so remove them or correct their spelling. See the CLI reference for the full list of options.

Step 3: Initialize the Repository¶

1. Open Command Prompt
2. Navigate to your digna installation directory (where config.toml and the digna executable are located)
3. Run the connection test:

digna repo check

On a new schema, the command connects and then reports that no repository is installed yet:

Error: No repo installed. Use the 'digna repo upgrade' command to install it.

At this point that is the expected result: it confirms that digna reaches PostgreSQL and the schema. A connection or authentication error instead points at the [repo] section or at the PostgreSQL setup.

Step 4: Install the Repository Schema¶

In the same directory, run:

digna repo upgrade

This command installs the necessary tables in the repository schema and finishes with:

✅ Repo schema 'dignarepo' is up to date.

Step 5: Create an Admin User¶

The admin user is created directly against the repository schema, so the server does not need to be running yet. In the digna installation directory, run:

digna user add <email> <password> "<display_name>" --admin

Example:

digna user add admin@example.com "AdminPassword123!" "Admin User" --admin

This creates a user with full administrative privileges.

Step 6: Start the digna Server¶

In the digna installation directory, start the server with:

digna serve --address <host> --port <port>

Parameters: - --address — Server hostname/IP (default 127.0.0.1) - --port — Server port (default 8000)

When the server is up, it prints the address it listens on:

Server running on http://127.0.0.1:8082

Dashboard Configuration¶

Step 1: Deploy Dashboard to Web Server¶

The digna dashboard reads its own configuration from dashboard/dashboard_config.toml. That file does not ship with the installation — you create it in the dashboard/ directory alongside the dashboard files.

Its contents are described under Single Sign-On, which is also where the file is needed: it carries the login options the dashboard offers and, for multi-instance deployments, the backend connection.

Choose your web server and follow the corresponding deployment steps.

Deploying to IIS¶

1. Open IIS Manager

2. Press Win + R, type inetmgr, press Enter

3. Create a New Website

4. In the left panel, right-click Sites

5. Select Add Website...

6. Configure the Website

7. Site Name: Enter a name (e.g., "dignaDashboard")
8. Physical Path: Click Browse and select your dashboard folder

9. Binding: Set IP address and port (default port 80 for HTTP, 443 for HTTPS)

10. Start the Website

11. Click OK to create the site

12. Right-click the new site and select Start

13. Test the Installation

14. Open your browser
15. Navigate to http://localhost (or your configured URL)
16. You should see the digna dashboard login page

Deploying to Apache Tomcat¶

1. Copy Dashboard to Tomcat
2. Copy the dashboard folder to your Tomcat webapps directory
3. Rename it if needed (e.g., to digna)

4. Example: C:\Program Files\Apache Tomcat\webapps\digna

5. Verify Deployment

6. Refresh or reload the Tomcat management page (http://localhost:8080)

7. You should see "digna" (or your chosen name) listed in the deployed applications

8. Access the Dashboard

9. Open your browser
10. Navigate to http://localhost:8080/digna
11. You should see the digna dashboard login page

Running digna as a Windows Service¶

Why Use a Windows Service?¶

Running the digna backend as a Windows service ensures it: - Starts automatically when the server boots - Runs in the background without an open Command Prompt - Restarts automatically if it crashes - Can be managed through Windows Services

The windows Commands¶

The service is managed by the digna executable itself, through the digna windows subcommands. There are no batch files to run.

Every command takes --name to address a service registered under a non-default name. The full option list is in the CLI reference.

Installing the Service¶

1. Open Command Prompt as Administrator
2. Right-click Command Prompt

3. Select "Run as Administrator"

4. Navigate to your digna installation directory

   cd C:\path\to\digna
   

5. Register the service

   digna windows install
   

digna windows install --address 0.0.0.0 --port 8082

The service is registered with automatic startup, so it will start with Windows. It does not start immediately — see the next section.

Install Options¶

Starting and Stopping the Service¶

To Start the Service¶

digna windows start

To Stop the Service¶

digna windows stop

Moving the Service to a New Directory¶

If you need to relocate the digna installation:

1. Stop and unregister the current service

   cd C:\old\path\digna
   digna windows stop
   digna windows uninstall
   

2. Move the Application Files

3. Move the entire digna installation folder to the new location

4. Register the service again from the new location

   cd C:\new\path\digna
   digna windows install
   

Repeat any --address, --port or --account values you used the first time — the previous registration is gone.

1. Start the Service

   digna windows start
   

Uninstalling the Service¶

1. Stop the Running Service

   cd C:\path\to\digna
   digna windows stop
   

2. Unregister the Service

   digna windows uninstall
   

The digna server is now unregistered as a Windows service.

Upgrading to a New Release¶

This section upgrades an installation of Release 2026.06 to Release 2026.11. If your installation is older, read Upgrading From a Release Before 2026.06 first.

Before You Upgrade¶

Creating a digna Repository Backup is Mandatory

Before upgrading digna, back up your repository (PostgreSQL) to protect against data loss. A backup ensures you can recover if the upgrade encounters unexpected issues.

Requesting the License File for Release 2026.11

Release 2026.11 needs a new license.toml. Request it from the digna team before you start, and have it ready for Step 7.

Upgrading From a Release Before 2026.06¶

Release 2026.06 brought three changes that still apply when you upgrade an older installation straight to 2026.11:

• ODBC only. digna reaches every source technology over ODBC. Every database connection that does not use ODBC yet must be changed to ODBC after the upgrade; there is no automatic conversion. Install the ODBC drivers on the digna host beforehand, see Install the ODBC Driver on the digna Host, and have the properties of each connection ready from the technology guides. The Databricks Legacy connector no longer exists; move those connections to the Databricks connector.
• One executable. dignabackend and dignacli are replaced by the single digna executable, which combines the backend and the CLI.
• config.toml. The [encryption] section is required, and DIGNA_APP_HOST and DIGNA_APP_PORT are no longer read: the server takes its address and port from digna serve. Compare your file with Backend Configuration.

The steps below point out where an older installation needs something different. The repository upgrade in Step 8 brings a repository of any earlier release straight to 2026.11.

Upgrade Process¶

Step 1: Stop the digna Service¶

Open a Command Prompt as Administrator and stop the service with the digna executable of your current installation:

cd C:\path\to\digna
digna windows stop

The service stays registered. The new executable takes the place of the old one in the same directory, so the registration keeps pointing at the right file.

If digna is running in the foreground, press Ctrl+C in its Command Prompt window.

cd C:\path\to\digna\bin
stop_service.bat
uninstall_service.bat

Step 2: Backup Current Installation¶

In your digna installation directory, rename the executable and the dashboard folder of your current installation, so that the new release can be deployed alongside them:

cd C:\path\to\digna
ren digna.exe digna_old.exe
ren dashboard dashboard_old

Keep digna_old.exe until you have verified the upgrade, and dashboard_old until you have restored your configuration files from it (see Step 4). Afterwards you can delete both.

Step 3: Extract and Deploy New Version¶

1. Extract the new digna installation ZIP file
2. Copy the new digna executable and dashboard folder to your installation directory

Step 4: Restore Your Configuration Files¶

copy dashboard_old\dashboard_config.toml dashboard\dashboard_config.toml

Release 2026.11 needs no change to config.toml: a file that works with Release 2026.06 keeps working. Two changes are optional:

• Add a [duckdb] section if database connections are to use the digna Engine and its defaults don't suit your host.
• Leave out the [app] section if a reverse proxy serves the dashboard and the backend under one origin.

[[oidc_clients]]
DIGNA_OIDC_KEY = 'microsoft'
DIGNA_OIDC_CLIENT_ID = '<client_id>'
DIGNA_OIDC_CLIENT_SECRET = '<client_secret>'
DIGNA_OIDC_REDIRECT_URI = 'http://localhost:3000/oidc/callback'
DIGNA_OIDC_CONFIGURATION_URL = 'https://login.microsoftonline.com/<tenant_id>/v2.0/.well-known/openid-configuration'

Step 5: Reload the Web Server¶

The dashboard is a set of static files, so your web server — and the browser — may still be serving the previous version. Reload or restart whichever web server hosts the dashboard folder, then reload the page with a hard refresh (Ctrl+F5).

Step 6: Validate the Configuration¶

Confirm that config.toml is complete before touching the repository:

digna config check

Every section must report OK. Fix anything reported as FAILED, remove the keys listed under Unknown keys, and run the command again before continuing.

Step 7: Replace the License File¶

A license file normally carries over from one release to the next. Release 2026.11 is an exception: it adds two licensed modules, digna Data Reconciliation and digna Agentic, and a license issued before 2026.11 does not contain them. Copy the license.toml that the digna team provided for Release 2026.11 into the installation directory, replacing the old one:

copy /Y C:\path\to\new\license.toml license.toml

digna license check

Step 8: Upgrade the Repository Schema¶

In your digna installation directory, run:

digna repo upgrade

Release 2026.11 manages the repository schema with versioned migrations. The first upgrade from an earlier release brings the schema to the last version of the previous scheme, records that as its starting point, and then applies the migrations of Release 2026.11. It finishes with:

✅ Baseline migration recorded as applied.
✅ Repo schema 'dignarepo' is up to date.

All existing data is preserved. To see the state of the repository at any time, run digna repo check: it lists the latest applied migration and any pending ones.

Error: Legacy repo version 3.0.2 installed. Use the 'digna repo upgrade' command to upgrade it.

Step 9: Restart Services¶

If digna runs as a Windows service, start it again:

cd C:\path\to\digna
digna windows start

If you upgraded from a release before 2026.06 and unregistered the service in Step 1, register it again with the digna executable first:

cd C:\path\to\digna
digna windows install --address <address> --port <port>
digna windows start

Give --address and --port the values the old service served on, unless you want the defaults of 127.0.0.1 and 8000. Add --account and --password if the old service ran under a domain account. See Running digna as a Windows Service for the full option list.

If running manually, restart the server:

cd C:\path\to\digna
digna serve --address <address> --port <port>

If using IIS or Tomcat, restart the respective web server.

Step 10: Verify the Upgrade¶

1. Confirm the release of the new executable:

   digna version
   

   The first line must read Release: 2026.11.

2. Access the digna dashboard and verify that the interface loads correctly.

3. Check the files in the logs directory of the installation for errors.
4. Test your database connections — see Testing a Connection. After an upgrade from a release before 2026.06, change every connection that did not already use ODBC over to ODBC first.

To start with the new modules, see digna Data Reconciliation, Connect an AI Agent for the digna MCP Server, and Profiling Location for the digna Engine.