Hub Installation
Make sure you have read Deployment planning and System requirements before starting. The Hub installer is run once per deployment.
Requirements
- PostgreSQL 14 or later, network reachable from the Hub server, with a UTF-8 default encoding
- A connection string in the form
postgresql://user:password@host:5432/exekra_hub. The installer creates theexekra_hubdatabase if it does not already exist - An HTTPS port and an internal backend port. Both are configured during install
- Administrator rights on the Hub server to install a Windows service
Redis is bundled and started by the installer on localhost:6379. If something is already listening on that port, the Hub reuses that existing Redis instead.
Installation
Download the installer
Sign in to the Customer Portal and download the Hub installer from the Downloads page.
Run as Administrator
Right-click the installer and select Run as Administrator.
Accept the agreement and choose a directory
Default installation directory is C:\Program Files\Exekra\Hub.
Enter database and Redis connection details
Provide your PostgreSQL connection string, the bundled Redis URL (or your existing one), and your chosen HTTPS and backend ports.
Let the installer finish
The installer generates TLS certificates, generates the encryption keys for credential storage, creates the database if needed, runs migrations, starts the bundled Redis if no Redis is already listening, and installs the Hub as a Windows service named ExekraHubService.
Open the dashboard
Browse to https://localhost:<https-port> on the Hub machine, or to https://<hub-host>:<https-port> from another machine on the same network.
Configuration values
| Field | Example | Notes |
|---|---|---|
| Database URL | postgresql://postgres:<password>@localhost:5432/exekra_hub | Database is created if it does not exist |
| Redis URL | redis://localhost:6379 | Default points at the bundled Redis |
| HTTPS Port | Operator choice | Used by Studio and Runners to reach the Hub |
| Backend Port | Operator choice | Internal only; not exposed externally |
After installation
- Activate your license and create the admin account: see License management.
- Day-to-day service operations (start, stop, logs): see Service management.
- Install Studio and Runner on their machines: see Studio installation and Runner installation.
Was this page helpful?
A quick signal helps us prioritise improvements.