Getting Started

Everything you need to know before deploying your first application to Flux

Prerequisites Checklist

Docker installed locally

Install Docker Desktop for your operating system

Learn more

Docker Hub account created

You'll need to push your images to a public registry

Learn more

Zelcore wallet setup

Download Zelcore wallet to manage your FLUX tokens

Learn more

FLUX cryptocurrency

Purchase FLUX tokens for deployment costs (varies by app size)

Basic command line knowledge

Familiarity with terminal commands and Docker basics

What You'll Learn

1

Flux Network Architecture

Understand how Flux's decentralized cloud works and the different node tiers

2

Component Communication

Learn how multi-component apps communicate using Flux internal DNS

3

Docker Image Preparation

Best practices for building optimized Docker images for Flux

4

Deployment Specifications

Understanding the Flux deployment spec format and all available options

5

Cost Estimation

Calculate monthly costs based on CPU, RAM, and storage requirements

6

Monitoring & Troubleshooting

How to monitor your deployments and fix common issues

Flux Network Architecture

Decentralized Cloud Computing

Flux is a decentralized cloud computing platform powered by thousands of FluxNodes around the world. Unlike traditional cloud providers, Flux distributes your applications across multiple independent nodes, providing censorship resistance, geographic redundancy, and competitive pricing.

Node Tiers

CUMULUS
Node Tier
2 V-Cores / 4 Threads8 GB RAM220 GB SSD/NVMe

Entry-level nodes, suitable for small applications

NIMBUS
Node Tier
4 V-Cores / 8 Threads32 GB RAM440 GB SSD/NVMe

Mid-tier nodes, recommended for most applications

STRATUS
Node Tier
8 V-Cores / 16 Threads64 GB RAM880 GB SSD/NVMe

High-performance nodes for resource-intensive applications

Multi-Component Networking

When deploying multi-component applications (like a database + backend + frontend), Flux provides internal DNS for component communication using this pattern:

flux{componentname}_{appname}

Example: For an app named "todoapp" with components "postgres", "api", and "frontend":

  • PostgreSQL: fluxpostgres_todoapp:5432
  • API Backend: fluxapi_todoapp:3000
  • Frontend UI: fluxfrontend_todoapp:8080

Cost Estimation

Deployment costs on Flux are determined by your resource requirements. Here's a rough guide:

ResourcesApproximate CostExample Use Case
1 CPU, 2GB RAM, 5GB storagecalculating...Simple web app
3 CPU, 4GB RAM, 20GB storagecalculating...Minecraft server
4.5 CPU, 8GB RAM, 35GB storagecalculating...Multi-component app stack

* Prices are calculated in real-time based on current FLUX market price, including tier discounts and 5% FLUX payment discount. Use the interactive playground for detailed pricing with additional options.

Ready to Deploy?