Cloud storage
Block, object and file storage for your servers, with storage policies that decide where a disk sits and which pools can hold it.
Three kinds of storage, one account
Pick the access method your software already uses. All three run on VPSie storage clusters in the location you choose.
Block volumes
SSD volumes you attach to a server and format yourself. Use them for databases, boot disks and anything that expects a disk.
- Grow a volume without downtime
- Snapshots of single volumes
- Instant clones from one image
Object storage (Buckets)
An S3-compatible API for files that apps, websites and backup tools read and write over HTTPS. Covered on its own page.
- Object Lock (WORM) for immutable copies
- Versioning and share links
- See Buckets
File shares (Files)
One folder that many servers mount at the same time over NFS 4.2, reachable only on your private network.
- Linux and Kubernetes today
- SMB 3 for Windows and macOS on request
- Up to 64 access entries per share
Choose where data sits with storage policies
A storage policy is a named class of storage in one location, such as a standard class or an encrypted class. When you create a server or a volume you can pick the policy, and you can change it later.
- A location can offer several policies, each with its own product and visibility rules
- New disks go only to a pool that is below its fill limit; the request is refused when none is left
- Disks move between pools online, in the background, with a visible move list
- The change list shows only policies with the same price, so a change never alters your bill
Encryption you can check
VPSie encrypts at several layers. What is on by default and what you turn on is stated plainly.
At rest, on the storage
The encrypted policy accepts only pools that VPSie staff attested as encrypted, with the method and evidence on record. The attestation is audited.
- Data stays encrypted if a drive or array is lost, stolen or returned
- Plain to encrypted is allowed; encrypted to plain is refused
In transit, between storage hosts
Traffic between storage hosts, and between servers and storage, can be set to the encrypted mode of the storage network.
- Set per cluster
- Live migration of a running server keeps working
Backups
Backup supports client-side AES-256-GCM encryption, so data is encrypted before it leaves your machine and the keys stay with you.
- Keys can be supplied by you
- Integrity checks on a schedule or on demand
What it does not cover. Disk encryption protects the physical media. Data inside a running server is readable by anything that can read the disk from there. If data must stay private from the operator too, encrypt it yourself with keys you hold. Read the full detail on the security page.
VPSie Files: one share, many servers
Instead of copying the same content onto every server, create one share and mount it everywhere. A share lives in one location and one private network, and is never reachable from the internet.
- Mount with two lines on Linux; the share page shows the exact command with your address filled in
- Kubernetes ReadWriteMany volumes through the standard NFS driver
- Grow while mounted; shrink to the data held plus a margin, never below 10 GB
- Import from an S3-compatible bucket or an SMB share, with a SHA-256 checksum for every file written
- If the gateway host fails, mounted clients pause for up to 4 minutes and then continue without a remount
Limits worth knowing before you plan
| Item | Value | Applies to |
|---|---|---|
| Share size | 10 to 65,536 GB | Files |
| Shares per private network | Up to 64 | Files |
| Access entries per share | 1 to 64 (servers or IPv4 ranges inside the network) | Files |
| NFS version | 4.2, mount option hard | Files |
| SMB | SMB 3 only, signed; up to 64 SMB users per network | Files, by ticket |
| Placement | One location, one private network | Files |
| Pool fill limit | High-water mark up to 95 percent, set per policy by staff | Storage policies |
Private and sovereign clouds run on HCI storage
On a private cloud, compute and storage run on the same nodes. VPSie HCI storage is software-defined: block, file and object access share one pool of capacity, with no single point of failure.
- Grow by adding nodes; add or remove hardware while the system is online
- Self-healing and rebalancing after a failed drive or node
- Replica 2, replica 3 or erasure coding per workload
- Works fully air-gapped
Where storage fits in the rest of VPSie
Compute
Attach volumes to cloud servers and bare metal.
Backup
Backup writes encrypted copies; Buckets is a good immutable target.
Kubernetes
Share volumes between pods with managed clusters and Files.
Storage questions
Can a file share be reached from the internet?
No. It is reachable only over the private network that holds it.
Does growing a share or volume interrupt my servers?
Growing a share does not unmount anything. Growing a block volume does not need downtime either.
Am I charged for storage I am not using?
Yes. A volume or file share reserves its capacity while it exists, including when the server it is attached to is stopped. A removed (deleted) volume or share is not charged from the moment it is removed.
What happens when I delete a file share?
Its data is removed and cannot be recovered. The console asks you to type the share name first.
Can I move a disk from plain to encrypted storage?
Yes, while the server keeps running. The reverse, encrypted to plain, is refused.
Are storage policies available in every location?
No. The picker appears only in locations that run in policy mode. In other locations nothing changes.
Which of these can I use from the API?
Everything in the console is also in the VPSie REST API with an account token.
Learn more: Managing user storages S3 bucket storage with ransomware protection
Put your data where it belongs
Open an account and attach a volume, or talk to us about storage on your own site.