Skip to main content
This section is under construction. FloxHub on-prem documentation is being written section by section. Pages marked as placeholders have not been written yet.
FloxHub is normally a cloud service that Flox operates for you at hub.flox.dev. FloxHub on-prem is the same product running on hardware you control, inside your own network, with your own identity provider and your own database. You reach for it when your environments, packages, or the identity of the people using them cannot leave your infrastructure — a regulated network, an air-gapped segment, or a security policy that rules out a third-party service holding your dependency graph.

​
What you get

A FloxHub on-prem deployment runs the whole product, not a subset:
  • A package catalog. Your deployment holds its own catalog, populated from upstream and refreshed on a schedule you configure. Clients resolve and install packages from it without reaching the public internet.
  • Environment hosting. Users flox push and flox pull environments against your deployment, with the same generations and audit trail as the hosted service.
  • The web UI. The same interface for browsing environments, packages, and organization membership.
  • Builds and publishing. Your users build and publish packages into your own catalog.
  • Identity and authorization. Sign-in brokered through your existing identity provider, with organizations, roles, and per-catalog access control.

​
How it differs from hosted FloxHub

The client experience is intended to be the same: the same flox CLI, the same commands, pointed at your deployment instead of hub.flox.dev.

​
What you operate

Installing FloxHub on-prem makes you its operator. That means:
  • The host. Provisioning it, sizing it, and keeping its operating system patched.
  • PostgreSQL. The deployment does not ship a database. You supply one, and its availability and durability are yours.
  • The external URL, DNS, and TLS. The URL you choose is baked into the tokens the deployment issues, so it is a decision to make before the first login rather than after.
  • Identity. Connecting your identity provider and keeping that connection working.
  • Object storage, where you want published packages to carry binaries.
  • Backups and recovery. Taking them, storing them, and verifying that they restore.
  • Upgrades. Choosing when to move to a new FloxHub generation and running the upgrade.
Flox supplies the software, the base environment that composes it, and the documentation in this section.

​
Next steps

Installation requirements

Check your host, network, and database against the prerequisites.

Reference architectures

See the supported topology before you provision anything.

Install FloxHub

Work through the installation procedure.

Administer FloxHub

Configure, monitor, and maintain a running deployment.