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.
        8. Migrating data?
          If the reason for installing PostgreSQL on a new server is that you are migrating intrasis-databases to a new server you must change the server name in all *.idf files. That can easily be done using tools like Notepad++

        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/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/Db Converter
          • PostgreSQL 17.x (to replace the old version)
        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.

        Intrasis 3D Requirements

        Intrasis 3D – Minimum Hardware Requirements (Local Laptop / Workstation)

        Intrasis 3D is built on Sweco’s Elements 3D engine and requires a dedicated graphics card for reliable performance. Integrated graphics (Intel UHD, Iris, etc.) are not supported.

        Minimum recommended specifications:

        • CPU: Intel Core i7 / AMD Ryzen 7 or better
        • RAM: 16 GB (32 GB recommended for large models)
        • GPU: Dedicated NVIDIA or AMD graphics card
          • Minimum: NVIDIA RTX A2000 / RTX 3060 (6 GB VRAM)
        • Storage: NVMe SSD
        • OS: Windows 10/11 64-bit

        For smooth handling of large excavation models and point clouds, higher GPU memory (8–12 GB VRAM) is recommended.

        Intrasis 3D – Minimum Hardware Requirements (Remote Desktop / RDS / Citrix)

        If Intrasis 3D is run via Remote Desktop or Citrix, the GPU must be installed on the server, as the client only displays the streamed graphics output.

        Minimum recommended server specifications:

        • CPU: Server-grade multi-core CPU (Xeon / EPYC)
        • RAM: Minimum 32 GB (64 GB recommended for multi-user environments)
        • GPU: Dedicated Server-class NVIDIA GPU
          • Minimum: NVIDIA RTX A2000 / A4000
          • For multiple simultaneous users: RTX A4000 / A5000 or higher
        • Storage: NVMe SSD for active projects
        • OS: Windows Server 2019/2022

        The number of simultaneous 3D users directly affects GPU sizing. Each active 3D user requires dedicated GPU resources for acceptable performance.

        How to Activate Your Intrasis License

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

      2. 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.

        High-level architecture

        Intrasis does not normally require a separate application server and is typically installed locally on each workstation.
        However, Intrasis can also be run in a shared Remote Desktop or Citrix environment. In such cases, multi-user (floating) licenses are required, as multiple users access the same installation simultaneously.

        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 and one dedicated tablespace directory per Intrasis database.
        Each Intrasis database therefore has:

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

        Client connectivity

        Database access

        Intrasis clients connect directly to the PostgreSQL server using the server hostname or IP address, the TCP port (default 5432),
        and the database name with PostgreSQL role 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.

        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, the .idf file is stored in the root of the corresponding IntrasisData folder.
        The file contains the PostgreSQL server hostname, database name, and other connection parameters used by Intrasis.

        Permissions

        • End users need read access to the .idf file
        • End users need full 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

        PostgreSQL installation and configuration

        Installation via Intrasis setup

        For Intrasis 4, PostgreSQL 17 must be installed using the Intrasis installation program.
        This ensures that PostgreSQL is installed with the correct settings for Intrasis and that required extensions such as:

        PostGIS and PostGIS raster are installed automatically.

        The following PostgreSQL roles are created with correct permissions:

        • postgres – PostgreSQL superuser for cluster administration
        • intrasis – application runtime role used by Intrasis

        For PostgreSQL 17, authentication is configured using standard password-based authentication via pg_hba.conf.
        By default, only local host and internal network connections are allowed. External public networks are not permitted.

        Database directories and tablespaces

        For each Intrasis database, a dedicated tablespace directory is created and mapped by PostgreSQL.
        The Windows account running the PostgreSQL service must have full NTFS permissions 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,
        access problems, and data corruption in worst-case scenarios.

        The fact that there is a system database folder per Intrasis database only means that PostgreSQL uses that directory as a tablespace location.
        Users do not open any files in that directory directly.

        Offline / field installations

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

        • Intrasis and PostgreSQL are both installed on the client machine
        • The user works against a local Intrasis database on the laptop without a connection to the central server
        • 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

        Summary

        • Intrasis clients connect directly to PostgreSQL and SMB file shares
        • Each database has a PostgreSQL tablespace directory and an IntrasisData folder with a single .idf file
        • Authentication is password-based and restricted to internal networks
        • Full offline field work is supported with later central synchronisation

        ↑ Back to top