Cortex Installer
The Cortex Installer is the recommended way to install Cortex in IIS on Windows Server.
It automates IIS configuration, application pool setup, file deployment, and upgrade handling. Most customers should use this method unless deploying via containers.
The installer is available as one of the download options inside any post-v2.6.0 build at:
https://releases.synapsesoftware.com/
Server Prerequisites
Cortex requires the following components to be available on the target server:
- Windows Server with IIS enabled
- The appropriate .NET Hosting Bundle (matching the Cortex runtime version)
- Administrative privileges on the machine
- A SQL Server instance available (if required for your Cortex version)
These components do not need to be installed manually prior to launching the installer.
When the installer starts, it will validate all required prerequisites and display their status at the top of the window.
If any prerequisite is missing, it will be indicated clearly in the installer UI.
Installing Cortex
Step 1 - Download the Installer
Download the latest Cortex Installer from:
https://releases.synapsesoftware.com/
Step 2 - Launch the Installer
Run the installer as an administrator.
On launch, the installer will display a Prerequisites Status section at the top of the window.
Insert screenshot of prerequisite validation section here
If all prerequisites are satisfied, you may proceed directly with installation.
If one or more prerequisites are missing:
- Click Install Prerequisites.
- Allow the installer to configure the required components.
- Once complete, verify all prerequisite checks show as satisfied.
- Continue with installation.
Step 3 - Choose Installation Type
You will see two options:
- Install
- Upgrade
Choose Install for a new deployment.
What the Installer Configures
During installation, the installer will:
- Create or configure the IIS Application Pool
- Configure the site in IIS
- Copy Cortex application files to the selected directory
- Apply required .NET settings
- Apply application configuration settings collected during setup (such as connection strings and environment values)
You will be prompted to:
- Select the installation directory
- Specify the IIS Application Pool identity
- Provide any required configuration values (such as connection strings)
Application Pool Identity
You may choose:
- ApplicationPoolIdentity (recommended for most deployments)
- A custom service account (if required by your environment)
If using a custom identity, ensure:
- The account has access to the installation directory
- The account has appropriate SQL permissions if connecting to a database
Completing Installation
Once installation completes:
- Click Finish.
- Open a browser.
- Navigate to the configured URL.
- Confirm that Cortex loads successfully.
If the application does not load:
- Verify the IIS Application Pool is running.
- Confirm the site bindings are correct.
- Review IIS logs and Windows Event Viewer for errors.
See: Troubleshooting
Enabling HTTPS (SSL Configuration)
By default, Cortex may be installed using HTTP depending on your IIS configuration.
If your environment requires HTTPS (recommended for production environments), you will need to configure an SSL certificate in IIS after installation.
This is performed within IIS Manager:
- Open IIS Manager
- Select the Cortex site
- Click Bindings
- Add or edit an https binding
- Select the appropriate SSL certificate
- Apply changes
If an SSL certificate is not yet installed on the server, it must first be added to the Windows certificate store before it can be selected in IIS.
Once HTTPS is configured:
- Confirm the site loads successfully over
https:// - Optionally configure HTTP → HTTPS redirection if required by your security standards
SSL configuration is not managed by the Cortex Installer and must be handled at the IIS/server level.
Upgrading Using the Installer
For detailed upgrade information, see:
When Not to Use the Installer
Do not use the installer if:
- You are deploying Cortex via Docker
- You are running in Kubernetes
- You are using a fully custom hosting environment
In those cases, see: