You can download the installation package from here:
Intrasis 4 | Intrasis

⚠️Important: PostgreSQL is not backwards compatible.
If you restore a PostgreSQL 17 backup to a server running an older PostgreSQL version, PostgreSQL will become fully corrupted.
Only PostgreSQL itself is affected, but fixing the issue requires a full server restore, which causes significant downtime.

Install Intrasis 4 / PostgreSQL on a Windows Server

Install Intrasis 4 on a clean Windows server

  1. Download the installation package
    Go to Intrasis 4 | Intrasis to download the Intrasis installation package.
  2. Unzip the installation file
    Extract the downloaded file to a suitable location on your computer.
  3. Start the installation
    The installer will guide you through the setup. You will:

    • Run: Intrasis_Installer_4.2.0.xxxx.exe
    • See suggested components for installation
    • Install the default PostgreSQL version 17.x
  4. Select components to install
    Choose which components to install. Recommended:

    • Intrasis
    • Intrasis DB Administrator
    • Optional: DB Converter
  5. Apply any available patch
    If a patch with the latest fixes is available, install it after completing the main Intrasis 4 installation.
  6. Share the Intrasis Database folder
    Make sure the Intrasis Database folder is accessible for client systems.
  7. Test the installation
    Verify that Intrasis and PostgreSQL 17 work correctly by creating a test database from a client and then deleting it.

Install Intrasis 4 on a Windows Server with existing PostgreSQL

  1. Download the installation package
    Click the button below to download the Intrasis installation package.
  2. Back up your Intrasis databases
    Before making any changes, ensure all Intrasis databases are safely backed up.
  3. Stop the old PostgreSQL service
    Take the following steps:

    • Stop the existing PostgreSQL service.
    • Set its startup type to Manual.
    • Leave it stopped — you cannot run two PostgreSQL services at the same time.
  4. Unzip the installation file
    Extract the downloaded file to a suitable location on your computer.
  5. Start the installation
    The installer will guide you through the setup:

    • Run: Intrasis_Installer_4.2.0.xxxx.exe
    • The installer will suggest which components to install
    • The default PostgreSQL version for a new installation is 17.x
  6. Select components to install
    Choose which parts of Intrasis you want to install. Recommended:

    • Intrasis
    • Intrasis DB Administrator
    • Optional: DB Converter
  7. Restore your Intrasis databases
    Restore all Intrasis databases from the backups created earlier.
  8. Apply any available patch
    If a patch with the latest fixes is available, install it after completing the Intrasis 4 installation.
  9. Test the installation
    Verify that Intrasis and the databases work correctly with PostgreSQL 17.
  10. When the tests are complete uninstall the old version of PostgreSQL and Intrasis 3.

Install Intrasis 4 on a Windows Client

Install Intrasis 4 on a clean Windows client

  1. Download the installation package
    Go to Intrasis 4 | Intrasis and download the Intrasis installation package.
  2. Unzip the installation file
    Extract the downloaded file to a suitable location.
  3. Start the installation
    Run: Intrasis_Installer_4.2.0.xxxx.exe
  4. The installer will automatically suggest which components to install.
    For a new client installation, the default PostgreSQL version is PostgreSQL 17.x.
  5. Select components to install
    Choose the components required on the client machine.
  6. Recommended for clients:
    • Intrasis
    • PostgreSQL 17.x (if the user needs to create or work with local databases)
    • Intrasis DB Administrator (needed for users managing local databases)
  7. Optional:
    • DB Converter
  8. Apply (if any) available patch
    If a patch with the latest fixes is provided, install it after completing the main Intrasis setup.
  9. Test the installation
    Verify that Intrasis can restore a database and the user can access it.
    If PostgreSQL was installed locally, confirm that you can create and delete a test database.

Install Intrasis 4 on a Windows client with existing PostgreSQL

  1. Download the installation package
    Download the Intrasis 4 installation package from
    Intrasis 4 | Intrasis.
  2. Back up all local databases
    If the client has local Intrasis 3 databases, ensure they are backed up before upgrading.
  3. Stop the old PostgreSQL service
    Stop the existing PostgreSQL service used by Intrasis 3.
    Set its startup type to Manual — you cannot run two PostgreSQL instances at the same time.
  4. Unzip the installation file
    Extract the downloaded installer to a suitable location.
  5. Start the installation
    Run: Intrasis_Installer_4.2.0.xxxx.exe
  6. The installer will suggest which components to install
    Note: The installer does not automatically select PostgreSQL 17.x when an older version is already installed.
    You must actively tick the PostgreSQL 17.x checkbox.
  7. Select components to install
    Common selections for clients upgrading from Intrasis 3:

    • Intrasis
    • Intrasis DB Administrator
    • PostgreSQL 17.x (to replace the old version)
    • Optional:
      • DB Converter
  8. Apply (if any) available patch
    Install the latest patch after completing the upgrade.
  9. Restore the databases
  10. Test the installation
    Verify that Intrasis 4 can connect to the databases.
    Confirm that Intrasis 4 / PostgreSQL 17 runs correctly and that the user can create and delete local databases.
  11. After the tests are complete uninstall the old version of PostgreSQL and Intrasis.

PostgreSQL 17 requirements for Windows Server

Server OS:

  • Windows Server 2019 or 2022 (64-bit)

CPU:

  • Minimum 4 vCPU (8 vCPU recommended for expanding systems)

RAM:

  • Minimum 8 GB, recommended 16–32 GB for production

Disc:

  • C: 100 GB (OS + program)
  • D: SSD/NVMe, e.g. 1 TB (depends on expected data input; 500 GB can be enough for PostgreSQL data; preferably RAID1)
  • Option: Separate volume for backup solution

Net:

  • 1 Gbit/s

Other:

  • Open TCP port 5432 (or chosen port) in Windows Firewall / Network Firewall
  • 64-bit PostgreSQL 17 installed with official Windows installer (included in the Intrasis installation package)
  • System service account for PostgreSQL with rights to run services

To be able to use Intrasis 4 you need a license. We can provide you with a free test license, valid for 1 month.
The test license is a full license, without limitations. Licenses can be ordered from
info@intrasis.com.

How to Activate Your Intrasis License

Once Intrasis is installed, follow these steps to activate your license:

Stay in Control of Your Licenses

It’s important for your organization to keep track of the licenses you’ve purchased
and which devices they’re assigned to. If you don’t, and you try to activate a license
that’s already in use, it could lead to extra costs or service interruptions.
A little attention now saves you from big surprises later! If you need to wipe a computer, deactivate the license first. See below.

Important:
Do not connect the laptop to a hub, docking station, external monitor, or any other device
that might override the built-in Wi-Fi MAC address during the licensing process.
While not all external devices cause this issue, many do, and it can prevent the license
from being correctly linked to your system.

  1. Run as Administrator
    Right-click on Intrasis under the Windows Start menu and select Run as administrator.
  2. Enter License Information
    A license window will appear. Enter the following:
    License key: [your license key]
    Licensed email address: [your licensed email address]
  3. Send the Activation Code
    A long activation code will be generated in the same window. Copy this code and send it to
    license@intrasis.com.
  4. Apply the License File
    You will receive a license file by email. Save the file to your computer. In the license window, click
    Upload license key, then browse to and select the file.
  5. Ready to Use
    Intrasis is now activated and ready to use.
    Note: The license file is not reusable and may be deleted after activation.

If you need to move the license to another machine, you must first deactivate it:

  • Go to Help → About Intrasis
  • Click Deactivate license
  • A deactivation code will appear — send it to
    license@intrasis.com.

If you need to wipe a computer, you must first deactivate the license:

  • Go to Help → About Intrasis
  • Click Deactivate license
  • A deactivation code will appear — send it to
    license@intrasis.com.

Intrasis 4 – System Architecture Overview

This document describes how our Intrasis 4 installation is structured, how clients connect, and how PostgreSQL,
file shares and authentication are configured.

  1. High-level Architecture

We do not normally use a separate application server for Intrasis, but it is possible if you have
multi-user licenses.

  • Intrasis clients connect directly to:
    • PostgreSQL on the database server (normally TCP port 5432)
    • File shares via SMB for project data, orthophotos and other files
  • There is no direct client access to PostgreSQL data files; all database access goes through the PostgreSQL service.

The PostgreSQL cluster is configured with:

  • A standard data directory
  • One tablespace directory per Intrasis database, referenced by PostgreSQL tablespaces

Each Intrasis database therefore has:

  • A corresponding tablespace directory (for the actual PostgreSQL data files)
  • A corresponding IntrasisData folder on the file server, containing:
    • One .idf file (Intrasis Database File) in the root of the IntrasisData folder
    • Project-specific folders and files (except the System folder, which is restricted)

  1. Client Connectivity

2.1 Database access

  • Intrasis clients connect directly to the PostgreSQL server using:
    • Server hostname or IP
    • TCP port (default 5432)
    • Database name and PostgreSQL role (user) credentials

The actual database files are never accessed directly by the client. They are read and written only by the
PostgreSQL service on the server.

2.2 File share access

Users also access SMB file shares to:

  • Read the .idf file for each Intrasis database
  • Create, read, update and delete project files (except in the System folder)

For each Intrasis database:

  • There is a single .idf file in the root of the corresponding IntrasisData folder.
  • The .idf file stores:
    • The PostgreSQL server hostname
    • Database name
    • Other connection parameters used by Intrasis

Permissions:

  • End users need read access to the .idf file.
  • End users need create / read / write / modify / delete permissions on all subfolders
    except the System folder.
  • The System folder is reserved for internal system files and is typically read-only or not accessible to normal users.

  1. PostgreSQL Installation and Configuration

3.1 Installation via Intrasis setup

For Intrasis 4 we require that PostgreSQL 17 is installed using the Intrasis installation program. This ensures that:

  • PostgreSQL is installed and configured with correct settings for Intrasis.
  • Required extensions are installed automatically, including:
    • PostGIS
    • PostGIS raster
  • The following PostgreSQL roles are created with correct permissions:
    • postgres – PostgreSQL superuser for overall administration
    • intrasis – application role used by Intrasis

Both roles are needed:

  • postgres is used for cluster-level administration and maintenance.
  • intrasis is the normal runtime role used by the Intrasis application to access databases.

3.2 Authentication and pg_hba.conf

Authentication is performed using standard PostgreSQL roles and passwords.

For PostgreSQL 17 we base our configuration on a pg_hba.conf similar to:

  • # ”local” is for Unix domain socket connections only
  • local   all          all                         scram-sha-256
  • # IPv4 local connections:
  • host    all         all         127.0.0.1/32       scram-sha-256
  • # IPv6 local connections:
  • host    all         all         ::1/128            scram-sha-256
  • # Replication from localhost:
  • local   replication    all                      scram-sha-256
  • host    replication    all         127.0.0.1/32       scram-sha-256
  • host    replication    all         ::1/128            scram-sha-256
  • # Connections from the internal network:
  • host    all         all         samenet         md5
  • host    all         all         samehost        md5

In practice this means:

  • Only local host and internal network clients (samenet / samehost) may connect via TCP.
  • Authentication is always password-based (scram-sha-256 or md5).
  • No external/public networks are allowed in pg_hba.conf by default.

  1. Database Directories and Tablespaces

For each Intrasis database, a dedicated tablespace directory is created. PostgreSQL maps this directory via a tablespace definition.

Key requirements:

  • The Windows account running the PostgreSQL service (by default Network Service) must have
    full NTFS permissions (read/write/modify) on:

    • The main PostgreSQL data directory
    • All tablespace directories
  • Permissions created by the PostgreSQL installer must not be changed. Modifying these ACLs can lead to:
    • Database startup failures
    • Inability to create or access databases
    • Data corruption in worst case scenarios

The fact that there is a “database folder” per Intrasis database means only that:

  • PostgreSQL uses that directory as a tablespace location.
  • Users do not open any files in that directory directly.

  1. Offline / Field Installations

Archaeologists often work in locations without stable network connectivity. To support this, we allow a
fully local installation on field laptops.

For field installations:

  • Intrasis and PostgreSQL are both installed on the client machine.
  • The user works against a local Intrasis database on the laptop:
    • No network connection to the central PostgreSQL server is needed.
    • All data is stored locally during field work.

When the user returns to the office:

  • The local database is backed up and restored to the central PostgreSQL server, or
  • Data is otherwise synchronised according to project procedures.

This architecture allows:

  • Full functionality in the field (offline)
  • Central consolidation of data when network access is available

  1. Summary

  • Intrasis clients connect directly to PostgreSQL and SMB file shares; there is no separate application server.
  • Each Intrasis database has:
    • A PostgreSQL tablespace directory for data files (server-side only)
    • An IntrasisData folder on the file server with a single .idf file and project data
  • Authentication uses standard PostgreSQL roles (postgres, intrasis) and password-based logins, restricted to internal networks via pg_hba.conf.
  • The PostgreSQL service account must have full NTFS permissions on data and tablespace directories; these ACLs should not be modified.
  • Offline/field use is supported by local installations of Intrasis + PostgreSQL on laptops, with later restoration to the central server.