As workloads mature, compute alone is not enough. Teams need persistent storage for stateful services and simpler control over networking when they move from experiments to production.
Today, we’re adding two core building blocks to Fluence Console: storage volumes and network management.
You can now attach persistent disks to virtual machines and create public IP addresses directly in the console. That makes it easier to run databases, keep data across reboots, move storage between instances, and manage network identity without rebuilding infrastructure.
TL;DR
- Persistent storage volumes are now available for virtual machines
- You can attach additional disks during VM creation or later
- Disks support stateful workloads like databases, applications, and large datasets
- Storage can be detached from one VM and attached to another when needed
- Public IP management is now available in the console
- The API has been updated to support these new workflows
Persistent Storage for Virtual Machines
Until now, virtual machines were mainly optimized for compute. With storage volumes, Fluence can now support a broader set of production workloads that need data persistence beyond the lifecycle of a single instance.
Disks are network-attached block storage volumes that provide persistent storage for applications and data. You can attach them to virtual machines to expand capacity, run stateful services, or store larger working datasets without redesigning your deployment.
This is useful for teams running databases, indexing services, backend applications, and any workload where storage needs to remain available independently of the VM itself.
Why Storage Volumes Matter
Expand storage without recreating infrastructure
You can add more disk capacity to an existing deployment instead of provisioning a new machine and migrating everything over. That makes it easier to scale storage as requirements grow.
Support stateful workloads
Some workloads are not disposable. Databases, queues, internal services, and application backends need persistent storage that survives VM changes. Volumes make these setups much easier to run on Fluence.
Move storage between VMs
Storage and compute do not always need to stay tied together. You can detach a disk from one virtual machine and attach it to another when needed, which is useful for maintenance, recovery, or workload migration.
How It Works in the Console
When creating a VM, you can now configure both the boot disk and an additional disk.
The boot disk remains the system disk used for the operating system. You can then attach an additional disk for application data, databases, or other persistent storage needs.
You can choose between creating a new disk or attaching an existing one. Disks are created in the same region as the VM they are attached to. After a disk is created, its size can be increased later, but not reduced.
At launch, NVMe storage is available. NVMe disks use local storage on a dedicated physical server and offer high performance, though capacity depends on the resources available on that server.
For users who prefer full control, disks can be attached and then manually formatted and mounted over SSH. Automatic formatting and mounting is planned next.
Network Management and Public IPs
We are also making networking simpler.
You can now create public IP addresses directly in the console and assign them to workloads as needed. This gives you more control over how services are exposed and makes it easier to manage deployments that need stable public connectivity.
IPv4 is available now, with IPv6 planned next. You can also assign a public IPv4 address during VM creation, which removes an extra setup step for internet-facing services.
This is a basic feature, but an important one. Once teams start running real applications, they need predictable network identity, not just raw compute.
What This Unlocks
These updates make Fluence virtual machines more useful for production infrastructure.
With persistent disks and public IP management, teams can now run a wider range of workloads on Fluence, including:
- databases and other stateful services
- backend applications with persistent data
- long-lived development and staging environments
- services that need stable public endpoints
- deployments that require storage to outlive a single VM
This is part of a broader effort to make Fluence Console more practical for real infrastructure teams, not just for short-lived compute.
API Updates
These features are also reflected in the Fluence API.
The API now includes the necessary updates to work with disks, public IPs, and the related VM deployment flows, making it easier to integrate these capabilities into automation and infrastructure tooling.
For teams using Fluence programmatically, this means the same storage and networking workflows available in the console can also be managed through the API.
What’s Next
Storage volumes and network management are foundational pieces. They make the platform more flexible today and create a base for more advanced infrastructure capabilities over time.
We will continue improving the VM experience in Fluence Console with a focus on practical features that help teams deploy faster, manage infrastructure more easily, and run more serious workloads on the platform.
