Your database is only as fast as the disk underneath it. portvMind Block Storage offers full-flash persistent disks attached directly to your servers. Even if you delete your server, your data stays on the disk; when capacity runs out, you grow the disk.
Block storage is a storage model that keeps data in fixed-size blocks and presents it to the server as if a physical disk were attached. The operating system sees this space as a normal disk; you build a file system on it, place a database on it and write your application’s data.
What sets this model apart from object storage is the way it is accessed. You reach Object Storage over HTTP as files; block storage is accessed at the operating system level, block by block. That makes it the right choice for applications that do random reads and writes — especially databases.
portvMind Block Storage is independent of your server’s lifecycle. Even if you delete the server, the disk and the data on it remain; you can attach it to another server. When your capacity needs grow you don’t have to recreate the disk, you expand the existing one.
NVMe-based infrastructure; high IOPS and low latency for databases and transaction-heavy applications.
The disk is independent of the server it is attached to. Your data is preserved even if the server is deleted.
When your capacity needs grow you enlarge the disk; no data migration or reinstallation is needed.
Capture the state of a disk at a point in time, return to that point when needed or create a copy of it.
Data on the disk is stored encrypted at rest.
Attaches to your container workloads as a persistent volume through the CSI driver.
| Feature | Detail |
|---|---|
| Disk type | Full-flash NVMe |
| Expansion | Non-disruptive growth supported; shrinking not supported |
| Snapshots | Supported; a new disk can be created from a snapshot |
| Encryption | Encryption at rest |
| Kubernetes | Persistent volume support via the CSI driver |
| Metering | Per minute — based on allocated capacity |
Capacity ranges and performance values are listed in the calculator and the documentation.
For detailed technical specifications and release notes, see Documentation
Enter your disk capacity and see the total cost instantly.
Metering: Per minute — based on allocated disk capacity
It is metered from the moment the disk is created until it is deleted; whether the server is on or off does not change this, because the data is preserved in every case. Snapshots are metered separately for the space they occupy.
Your resources are metered for as long as they are running — you never pay for time you don’t use. In the console you can define a monthly or period-specific budget and get alerts when your spending reaches the 50%, 80% and 100% thresholds. Turn on overrun forecasting to see in advance whether your current consumption rate will take you over budget by the end of the period.
Alerts arrive by e-mail; with webhook support they can also be sent to Slack, Microsoft Teams or your own application.
Budget alerts send notifications; they do not stop resources automatically. You decide which resource to scale down.
The full pricing modelDisks can be expanded without disruption; shrinking is not supported. If you want to move to a smaller disk, you need to create a new disk and migrate the data.
In standard use a disk is attached to a single server. For scenarios that need shared access, consider Object Storage.
A snapshot gives quick rollback but is not a substitute for a full backup strategy. For critical data, keeping a backup in a separate region or on Object Storage is recommended.
The disk is not deleted. It remains as an independent resource and can be attached to another server.