Nothing keeps infrastructure running more than updates and enhancements. That is why we are back with another FluxCloud update, brought to you by Valter and our incredible engineering team!
This month, Flux released v2.5.0 for FluxCloud, a meaningful update that introduces Single Instance Deployments, Enhanced Payment monitoring, and new UI/UX improvements. Let’s dive in.
Single-Instance Deployments
Apps launched on FluxCloud are typically deployed across at least three instances for redundancy and failover, with a backup system taking over operations if the primary system fails.
This is inherent to distributed computing and what gives FluxCloud the reliable uptime it demonstrates; if one instance goes down, the others will ensure the app still runs. However, deploying the app across multiple FluxNodes means more costly compute resources.
To reduce operating costs for apps on FluxCloud and make deploying to the network more affordable for a broader range of builders, v2.5.0 introduced single-instance deployments.
This feature allows users to select a single instance to deploy their application on, making hosting much more cost-effective. To reflect the pricing differences between single- and multi-instance deployments, compute provider pricing has been adjusted.
Enhanced Payment Monitoring
FluxCloud update v2.5.0 has totally revamped the payment experience for app deployment. There is a two-phase detection system that shows two clear distinctions for payments: firstly, when the transaction confirming the app launch is confirmed on-chain; secondly, when the app is actually deployed on FluxNodes.
Additionally, there is now a live countdown timer to let users know exactly what’s happening with payments and when they are due. Context-aware status updates are delivered in real-time, notifying users of the exact payment stage they’re in.
Lastly, regarding payments, v2.5.0 introduces fixed subscription renewal logic to automatically and accurately calculate renewal periods.
UI/UX Improvements
Update v2.5.0 brought new UI/UX improvements:
- Better resource formatting: CPU is now shown with one decimal place (so you’ll see something like 2.5 vCPU instead of a long, messy number), and RAM is displayed in GB, so you don’t have to waste time figuring out memory capacity.
- Labelled storage tags: Storage is now labeled as “SSD/NVMe” to clarify that your application is receiving efficient disk storage.
- Boosted FluxShare error handling: If app storage is maxed out, FluxShare now displays error messages more clearly, rather than leaving users guessing what happened.
Conclusion
We want app deployment on FluxCloud to be efficient and cost-effective for new users and experienced developers alike. Single-instance deployments will enable greater flexibility and cheaper operating costs for apps deployed on the network.
Enhanced payment monitoring provides greater visibility into payment stages, now shown when deployments are registered on-chain and when the app is deployed to nodes.
UX/UI improvements bring more clarity for resource formatting, storage tags, and FluxShare error messages. Be sure to follow us on X and stay tuned for more updates. The future runs on Flux.

Leave a Reply
You must be logged in to post a comment.