Enterprise Deployments (Private Images, Secrets & Static IP)
Enterprise mode features — private Docker registries, secrets management, static IPs, node targeting, and pricing.
Enterprise Deployments: Private Images, Secrets & Static IP
Standard Flux deployments use public Docker images and shared IPs. For production and enterprise workloads that require private container registries, sensitive configuration secrets, dedicated IP addresses, or specific node targeting, Flux offers an Enterprise deployment mode with additional capabilities — at a small additional cost.
Enterprise Mode Overview
| Feature | Standard | Enterprise |
|---|---|---|
| Docker images | Public only | Public + Private registries |
| IP address | Shared (Flux-assigned) | Dedicated static IP available |
| Node targeting | Automatic placement | Target specific nodes |
| Base cost | Standard pricing | +6 FLUX + 2 FLUX per enterprise port |
| Static IP | Not available | +3 FLUX additional |
Enabling Enterprise Mode
Set the enterprise field to true in your app specification to enable enterprise features.
Enterprise app spec
{
"version": 4,
"name": "myenterprise-app",
"description": "Production enterprise deployment",
"owner": "YOUR_ZELID",
"instances": 3,
"enterprise": true,
"staticip": true,
"compose": [
{
"name": "app",
"repotag": "ghcr.io/myorg/private-app:v2.1",
"ports": [443],
"containerPorts": [8080],
"domains": ["app.mycompany.com"],
"environmentParameters": [
"DATABASE_URL=postgresql://...",
"API_SECRET=your-secret-key",
"NODE_ENV=production"
],
"commands": [],
"containerData": "/data",
"cpu": 2,
"ram": 1024,
"hdd": 10
}
]
}Private Docker Images
Enterprise mode allows pulling images from private container registries. This is essential for proprietary applications, internal tools, and any workload where the source code or compiled artifacts should not be publicly accessible. Supported private registries include Docker Hub (private repos), GitHub Container Registry (GHCR), Google Container Registry, and Azure Container Registry.
Without enterprise mode, all Docker images must be publicly accessible on Docker Hub. Enterprise mode adds registry authentication so Flux nodes can pull private images securely.
Static IP
The staticip field assigns a dedicated IP address to your deployment. This is useful when you need a stable IP for DNS A records, IP whitelisting, firewall rules, or third-party service integrations that require a fixed endpoint. The additional cost is 3 FLUX.
Node Targeting
Enterprise deployments can target specific nodes for deployment. This is useful for compliance requirements (data must stay in a specific geographic region), performance optimization (deploy near your users), or when you need specific hardware characteristics.
Secrets Management
Sensitive configuration values (API keys, database passwords, tokens) are passed via environmentParameters in the app spec. In enterprise mode, these values are handled with additional security:
- •Environment variables are encrypted at rest on Flux nodes
- •Values are only accessible within the running container
- •Secrets are not exposed in public API responses or node queries
- •Rotate secrets by updating the app specification with new values
Enterprise Pricing
| Cost Component | Amount | Note |
|---|---|---|
| Enterprise base fee | 6 FLUX | One-time per deployment cycle |
| Enterprise port fee | 2 FLUX per port | Per exposed enterprise port |
| Static IP | 3 FLUX | Optional, per deployment cycle |
| Standard resource costs | Normal pricing | CPU + RAM + Storage as usual |
When to Use Enterprise Mode
- •Proprietary software: Your Docker image contains proprietary code that should not be publicly accessible
- •Production APIs: You need a stable static IP for DNS and firewall configuration
- •Compliance: Data residency requirements demand specific node or region targeting
- •Sensitive data: Applications handling PII, financial data, or health records
- •Internal tools: Company-internal applications that should not be discoverable
Sources & Further Reading
Other articles in FluxCloud Advanced Deployment
Docker Prerequisites & Best Practices for Flux
Install Docker, create optimized Dockerfiles, multi-stage builds, image registries, containerData volumes, and common mistakes.
Compose v4: Multi-Component Applications
Deploy up to 5 components with Flux Compose v4 — internal DNS, inter-component communication, ports, and environment variables.
Deploy with Git (CI/CD & Auto-Deploy)
Auto-deploy from GitHub/GitLab/Bitbucket — webhooks, polling, zero-downtime updates, rollback, and CI/CD integration.
Flux-Orbit: Zero-Config Universal Deployment
Deploy any project without a Dockerfile — auto-detection for Node.js, Python, Rust, Go, Java, Bun, Ruby, and static sites.
Shared Databases & Auto-Replication
Deploy databases on Flux with persistent storage — MongoDB, PostgreSQL, Redis replication strategies and backup patterns.
Tiered Resources, Spec Builder & Cost Calculator
Basic/Super/BAMF resource tiers, Visual Spec Builder, Cost Calculator, pricing model, and cloud cost comparison.
App Troubleshooting & Post-Deployment Management
Diagnose deployment failures, domain issues, DB connection problems — plus updating specs, monitoring, and app lifecycle management.