Minimum system requirements and install guide
Everything a customer needs to know before installing self-hosted GaugeFlow: server sizing, supported environment, the secure install process, and what happens after first boot.
Fastest path
Ubuntu 24.04 LTS
Minimum starter size
4 vCPU / 16 GB RAM
Setup experience
Browser-based first-run portal
Start with the right server footprint
GaugeFlow is designed to be simple to deploy, but it still needs a stable Linux host with enough memory and CPU for document handling, OCR, background jobs, and PostgreSQL.
What the installer already handles
- ✓Installs Docker Engine and Docker Compose if they are missing
- ✓Generates the database, JWT, and encryption secrets for the new instance
- ✓Downloads the signed GaugeFlow release bundle from the GaugeFlow update server
- ✓Builds the local app and worker images on your server
- ✓Starts the stack and waits for the app health check to pass
Important
The default self-serve installer is for Linux. If a customer needs a special network model, a private cloud deployment, or an air-gapped environment, route them through a guided deployment instead of the default path.
The actual install path customers follow
GaugeFlow's self-hosted install is designed to be predictable: secure installer access on the server side, then one guided setup flow in the browser.
Secure installer access
Installer commands and license delivery are provided only through the secured post-purchase install flow.
Customers get the actual install details after purchase or through a guided deployment handoff.
Signed updates later
Existing servers receive signed updates through the GaugeFlow update flow and the in-app updates screen.
Exact update commands stay inside the authenticated customer environment instead of being published on the marketing website.
Prepare a Linux server
Start with a clean Ubuntu server on your network. Make sure the machine can reach the internet for the first install and that you can log in with sudo access.
Have your install key ready
GaugeFlow installs use a `gflo_...` license key. Keep that key available before you begin so the installer can download the signed release bundle.
Launch the secure installer
Approved customers receive installer access and license delivery through the secured post-purchase flow instead of through a public command on the marketing site.
Finish setup in the browser
When the installer completes, open the server URL in your browser. The first-run setup portal lets you create the first super admin and optionally seed the ISO / QMS starter pack.
What customers see after the server is up
After the Docker stack starts, the browser opens into the first-run setup portal. That portal is where the customer creates the first super admin and finishes the initial configuration.
- →Create the first super admin from the setup portal
- →Enable the ISO / QMS starter pack if the customer wants a default framework
- →Review generated quality documents in Documents before releasing them
- →Set backups, notifications, users, and compliance options in Settings
- →Use Settings -> Updates for future signed releases on your own schedule
First-run setup
Welcome to GaugeFlow
The setup portal is what turns a running server into a ready-to-use GaugeFlow workspace. It is not just a login screen.
Need help with deployment planning?
If the customer needs a private cloud rollout, an ITAR-conscious deployment, or help sizing a production server, the GaugeFlow team can guide the install.