Track market-moving stories before they get noisy

Fluxers! If you have never deployed anything on Flux, this is the article for you. Getting an application running on the decentralized cloud takes minutes, costs from $0.99 a month, and there is more than one way to do it — so you can pick whichever fits how you already work.

Here are four routes, from the easiest to the most hands-on.

Route one: just say what you want
Open the new FluxCloud preview at cloudpreview.app.runonflux.io and type what you want to run, in plain words:

“A WordPress site for a small bakery.”
“A Minecraft server for ten friends.”
“Postgres with an API in front of it.”

The assistant, FluxAI, works out the resources, fetches a live price from the network, and hands you a ready deployment to review. Common workloads fill the form instantly. Check it, adjust anything you like, then sign and pay with your own wallet or a card — the assistant prepares everything, but only you can approve the spend.

This is the best starting point if you know what you want running but not how to describe it to a cloud.

Route two: push your code with Orbit
If your project already lives in a Git repository, Orbit is the fastest way onto Flux. Paste your repository URL into orbit.runonflux.com, set the port your app listens on, and launch.

Orbit detects your framework from more than 100 — Next.js, Vite, Django, Rails, Laravel, Go, Rust, Spring Boot, .NET and many more — builds it, and deploys it. From then on, every push to your branch redeploys automatically, and a build that fails never replaces the version that works.

No Dockerfile, no server to manage. This blog is deployed exactly this way.

Route three: let your AI agent do it
If you work with Claude Code, Cursor, Windsurf or another AI coding tool, add the Flux Cloud MCP server and ask your agent to deploy for you:

npx @runonflux/flux-cloud-mcp

There is no account to create — two keys are the whole identity, and the server can generate them for you. Your agent can price a deployment before you fund anything, and it only spends after you confirm. Ask it what something would cost first; that part is free.

Route four: the full control panel
For complete control over every setting, use the deployment editor in FluxCloud or the new preview. You describe each component directly:

Image — any public Docker image, or a private one with registry credentials.
Resources — CPU, memory and storage per instance.
Instances — how many copies to run across the network.
Ports and domains — what to expose, and your own domain if you have one.
Storage — local, replicated, or primary/standby so your data survives a node going away.
Private mode — encrypt the whole specification so only ArcaneOS nodes can run it.

Or pick a ready-made template
Many popular applications are a single click. The apps hub covers WordPress, n8n, Hermes and OpenClaw, and the games hub covers nineteen game servers, from Terraria and Minecraft to ARK and Factorio. New accounts get the first week of a game server free.

What it costs
Pricing follows the resources you request: CPU, memory and storage, multiplied by the number of instances, with discounts for small applications and for longer subscriptions. Every deployment has a $0.99 minimum, and prices round to a figure ending in .49 or .99, so quotes are easy to read.

A small web app — half a CPU, 500 MB of memory and 5 GB of storage, on three instances — comes to $0.99 a month. Pay by card, or in FLUX for a 5% discount. You always see the price before you commit.

What happens when you deploy
Your signed specification is registered on the Flux network, and nodes around the world pick it up, pull your image and start your instances. Within minutes your app is reachable at its own address — and from then on it runs on independently operated machines, with no single company in the middle.

Want help along the way? The Ask AI button on the Flux documentation answers questions about every part of this, from resource limits to custom domains.

Start now
The quickest first step: open the FluxCloud preview and type what you want to run. Your first app on the decentralized cloud is a sentence away.

Fluxers! Welcome back to another ecosystem update! On Wednesday, July 15, we had an AMA, and in today’s blog, we are going to recap everything, so let’s dive in. 

High-Level Ecosystem Shifts To start off, Flux is restructuring its operations around a leaner, more community-driven model. The core team remains in place, but the project expects less direct corporate involvement from InFlux, greater community participation, and a transition of its corporate focus from the United Kingdom to the United States. 

Next up, we will soon be sending notifications to FluxNode operators still running legacy nodes, stating that if they do not update to PoUW v2, they will be brought offline. Essentially, operators running legacy nodes will be given a deadline to migrate to the currently supported node environment. Nodes that remain on the legacy system after that deadline will be banned from FluxCloud. 

Additionally, we plan to implement community referral codes and profit sharing. For example, if a Fluxer helps bring 30 new machines to the network, they would receive a portion of that revenue by entering their personal code on any deployments they make. 

Expanding further on revenue sharing, Flux is exploring partnerships in which it supplies infrastructure and development support in exchange for a share of the participating company’s revenue or business. The community would be asked to approve how proceeds from these arrangements are incorporated into PNR. 

FluxAI Developments Flux is building its own Large Language Model (LLM), and we will train it on FluxEdge GPUs. Our aim is not to compete with ChatGPT or Claude; we want to build an LLM that is highly specific to Flux and does not train on user data. 

This specialized LLM will operate for particular FluxAI and customer applications. The team emphasized that FluxAI is designed around business privacy and does not harvest customer data in the manner associated with many mainstream AI platforms. 

PNR Update Next, Progressive Node Rewards (PNR) are almost ready. With PNR, there will be an allocation specifically for node operators for what we refer to as “flex time,” where if your machine runs workloads at a higher rate, you will be compensated accordingly. 

PNR differs from conventional mining economics. In a proof-of-work system, increasing competition can reduce an individual miner’s share of a largely fixed block-reward pool. Under the proposed PNR model, increased paid workload demand would instead expand the amount distributed to eligible node operators. 

For PNR, as demand increases, payouts rise; conversely, when demand wanes, payouts decrease. When PNRs are implemented, node operators will be paid in proportion to their machines’ runtime depending on whether assigned workloads scale up or down.

Building out a PNR pay structure that dynamically adjusts to network demand requires extensive development. The team has largely finalized its proposed approach to PNR and hopes to introduce it during Q4 2026, subject to development progress, publication of a governance proposal and community approval.

Flux Foundation Update The Flux Foundation will adopt a bounty-payout feature that operates like a job marketplace. Flux community members can post a job they need completed with a bounty, and other community members can complete it to earn FLUX. Part of the Foundation’s yield-generating infrastructure will be allocated to fund the bounty program. 

Conclusion This AMA reinforced that Flux is entering its next phase with a sharper focus on sustainability, community participation, and real-world adoption. 

From restructuring operations and strengthening FluxAI to developing Progressive Node Rewards, referral incentives, and community bounties, the goal is to create an ecosystem in which contributors, operators, developers, and community members can all benefit from the network’s growth.

Many of these initiatives are still being developed and will require further technical work, governance proposals, and community approval before they are fully implemented. 

However, the direction is clear: Flux is working toward a leaner, more decentralized ecosystem that rewards meaningful participation and ties node-operator earnings more closely to genuine platform demand. The future runs on Flux.