On-Prem Deployment
Self-hosted Control Seat is a common deployment path for customers who want the platform running on their own infrastructure. The native installer ships with everything inside, so you can install it and open the gateway in about 30 seconds.
Native installer
Download from controlseat.com/download.
| Platform | Installer | What it does |
|---|---|---|
| macOS 11+ | .pkg | Installs to /Applications/Control Seat.app, registers a LaunchAgent so the gateway starts at login. |
| Windows 10 / 11 | .msi | Installs to C:\Program Files\Control Seat\, registers a Windows Service. |
| Linux (Debian / Ubuntu) | .deb | Installs to /usr/lib/controlseat/, creates a systemd unit. |
| Linux (RHEL / Fedora / Rocky) | .rpm | Same as the .deb, for the RPM family. |
Double-click → install → browser opens to http://localhost:8090. No environment-file editing, no certificate setup, no terminal. The installer includes the database, so you do not need to provision one separately.
Licensing
Self-hosted deployments use signed license files. Cloud customers do not need to manage this.
Contact us for pricing. We'll set up a controlseat.com account, then you'll mint a license against your specific install.
To activate, open the gateway's Platform → License page and click Activate online. A popup signs the license against your gateway's install ID + host fingerprint and applies it without restart or copy-paste.
Each license is bound to one gateway. Moving to new hardware invalidates the binding by design — re-activation is one click. Past expiry there's a 24-hour grace period, then the gateway shows a renewal prompt. The editor and configuration UI keep working through expiry so you can renew; only runtime endpoints (live tags, historian, runtime page rendering) are gated.
Updates
The gateway's Platform → Updates page shows your current version and a Check for updates button. Control Seat only checks for updates when you click it.
To update, re-download the installer from controlseat.com/download and double-click. Your data, license, and TLS certs carry over. To roll back, install the previous version's package.
TLS
The gateway listens on :8090 for HTTP and :8443 for HTTPS. To enable HTTPS, go to Platform → TLS, paste your PEM cert and private key, and save. The new certificate takes effect immediately.
If you'd rather terminate TLS at a reverse proxy (nginx, Caddy, your existing edge), point it at :8090 and set CS_BASE_URL=https://your-domain so links and redirects use the public URL.
Backup
All durable state lives in one data directory:
| Platform | Path |
|---|---|
| macOS | ~/Library/Application Support/Control Seat/ |
| Windows | %PROGRAMDATA%\Control Seat\ |
| Linux | /var/lib/controlseat/ |
Snapshot this directory and you've captured the whole install: data, license, TLS certs, and configuration. The directory survives updates and version changes, but not a full uninstall.
Other deployment paths
Docker Compose and air-gapped deployments are supported for shared infrastructure or fully-offline environments. Contact us and we'll send a signed bundle for your specific release.