Infra
Distributed infrastructure management. Provision node fleets and droplets, configure storage and networking, and operate hosted, self-hosted, and hybrid infrastructure.
Start operating
Build and operate
- Nodes and fleetsEnroll hardware, inspect health, and manage placement.
- DropletsCreate, resize, protect, and remove virtual machines.
- Storage and backupsAttach block storage and protect application data.
- Private networkingSubnets, routes, firewalls, and service connectivity.
- Live migrationMove workloads between compatible nodes.
- Automation APIResource requests, asynchronous operations, and retries.
Infra manages physical nodes, virtual machines called droplets, block storage, and software-defined networks from one control plane. Use the same resource model for Solarius-hosted capacity, hardware you operate, or a hybrid fleet.
Choose a starting point
Deploy an initial workload through Get started with Infra. For an existing environment, begin with the resource whose behavior you need to change:
- Fleet operators: enroll nodes, establish a CPU baseline, and review placement constraints before admitting production guests.
- Application operators: create droplets, configure guest access, and use backend draining during replacement.
- Storage operators: inspect writer ownership, replica repair, and application-consistent recovery points.
- Network operators: plan subnet allocation, peering, routes, and public endpoints as separate changes.
- Installation administrators: use self-hosting, database failover, and certificate rotation.
Project Operators manage application resources. Infrastructure Operators manage permitted fleet regions. Installation administration is a separate authority; project membership alone cannot change control-plane deployment settings.
Understand the infrastructure
Organizations and projects define ownership and access. Regions and zones describe physical placement. Scheduling determines which nodes can run a droplet. Operations record the progress and outcome of infrastructure changes.
A resource's requested configuration and observed state are separate. A successful request can start work that has not finished. Read the operation and resource health before using newly created capacity or removing its previous location.
Follow an operating procedure
- Add capacity to a constrained fleet.
- Replace a host without deleting its workloads.
- Restore an application from a recovery point.
- Investigate a failed change using the operation journal.
- Connect hosted regions to a self-hosted installation.
Documentation conventions
Console paths use Section → Resource → Action. Resource IDs such as
drp_web01 identify objects independently of their names. Examples use the
project prj_payments and a private network named production. Replace those
IDs with resources from the selected organization.
The glossary defines Infra terminology. The API conventions describe request formats, units, and error handling.
Legal and policies
Review the Infra legal and policy section for terms, acceptable use, privacy, data processing, billing, security, and service commitments.