A First Look at the New FluxCloud

Fluxers! The next FluxCloud is here to try. The new interface is live as a public preview at cloudpreview.app.runonflux.io, and it starts somewhere no cloud console has started before: with a sentence.

Tell it what to run. The assistant sizes it, prices it and deploys it across more than 6,000 independently operated servers in 53 countries. That is the whole home page — and behind it sits one application for everything Flux does, rebuilt from the ground up.

One application instead of several

Today, running something on Flux can mean visiting several places: one site for containers, another for GPUs, another for storage, a separate tool for node operators. The new FluxCloud is one application for customers, AI agents and node operators, covering FluxCloud and FluxEdge together.

This is the “rebuilt interface” item on the Q4 roadmap, and it is the front end of the bigger merge: two clouds, two dashboards and three billing systems becoming one product. The interface is arriving first, so you can see where it is all going.

The home page is a conversation

Type what you want — a Minecraft server for twenty friends, a WordPress site, a Postgres database behind an API — and the home page turns into a chat. The assistant works out the resources, fetches a live price from the network, and hands you a validated deployment to review.

A few touches make it feel fast. Workloads the interface already recognises fill the deploy form instantly, while the model is still composing its answer, so you are never staring at a spinner. Paste a Git repository URL instead of a description and you land straight in the deploy-from-Git flow. An elapsed counter shows exactly how long a round has taken.

The assistant is our own model, FluxAI, trained specifically for Flux and running on Flux — there is a separate article on how we built it. And one rule is written into the application itself: the assistant can never sign. It can size, price, navigate and prefill. Anything that spends money goes through your own wallet signature, every time.

Deploying, properly

Behind the conversation is a complete deployment editor for when you want full control:

Live pricing and verification against the network before you commit to anything.
Ports and custom domains, with automatic port assignment and the network’s rules checked as you type.
A structured mount builder for persistent data, with sync modes.
Placement by continent, country or region, drawn from live node counts, with an availability check.
Private applications with enterprise encryption, automatic secret detection and private registry credentials.
Import and export of specifications, so you can move a deployment between tools or keep it in version control.

Running what you deployed

The deployment page is where the new interface really pulls ahead. Each instance gets a set of tools in tabs:

Logs that follow from where you got to, with download.
A live monitor with CPU, memory, network and disk sparklines and the running processes.
Control per node, per component, or across every node at once.
A volume file browser with upload, download, rename, delete and new folders.
A terminal into the instance.
Backup and restore — create backups per component, send them to Flux Drive, and restore from a Flux Drive checkpoint, an uploaded archive or a remote URL.

Subscriptions can be extended, edited, ended or redeployed as new from the same page, and expired registrations come back with a one-click redeploy.

Everything else, in one place

Templates — the live marketplace catalogue, with game servers priced per tier and a guided settings form for every template.
GPUs — the FluxEdge marketplace and rentals, with inventory filters, machine cards, and rent and stop in a click.
Storage — a Flux Drive file manager, plans, and API keys.
Agents — setup for the Flux Cloud MCP server and agent tokens, for anyone deploying from an AI agent.
Network — live node counts by tier, a country table and a node map.
Governance — read and vote on open proposals with your session key, or register a new one.
Balance — the single USD-first balance page, ready for the unified billing that arrives with the merge.

Press ⌘K anywhere for a command palette across pages, deployments, templates and the assistant. The interface speaks 21 languages, including right-to-left scripts, and comes in light and dark.

Built for node operators too

Here is the part that is uniquely Flux. The new FluxCloud is a static application with no server behind it — and every FluxNode serves it. When you open it from your own node and sign in as that node’s administrator, it switches into operator mode: FluxOS status and maintenance, running applications, benchmarks and peers, daemon control, node settings, log tails and file sharing.

The same code, served by thousands of machines, is both the customer console and the operator console. There is no central server to go down, because there is no central server.

Try the preview

Open cloudpreview.app.runonflux.io and type what you want to run. The current cloud.runonflux.com keeps working exactly as before while the new interface rolls towards launch, so there is nothing to migrate and nothing to lose by exploring.

It is a preview, and we are shipping improvements to it daily. Tell us what you would change — the best time to shape an interface is before everyone is used to it.