Flexible block storage for your servers
Full Flash block disks that are independent of the server and can be attached and detached live. Grow them without restarting the server; pay only for the GB you allocate.
Full Flash · pay for the GB you use · zero-downtime growthOne disk type, pay per GB
No tiers, no complexity — all disks are on the same Full Flash storage. You pay only for the size you allocate, for as long as you use it.
The flexibility a production disk needs
Grow the disk without shutting the server down; then extend the file system in the operating system. Shrinking is not supported.
Attach the disk to a running server with no restart; detach it safely when you are done.
The disk lives separately from the server; even if you delete the server the data is preserved.
Detach the disk from one server and attach it to another in the same region; the data comes with the disk.
Every block storage volume runs on flash storage — uniform and predictable.
Create, attach and grow with the panel, the REST API, Terraform and MCP.
What do teams using Block Storage say?
Block Storage (Full Flash Cloud Disk) Guide
A cloud server's performance is not measured by CPU and memory alone; the disk layer where data is read and written is often the real bottleneck, especially for databases and transaction-intensive applications. What is more, staying tied to a server's own disk limits flexibility: when you delete the server the data is gone, growing the disk requires downtime, and moving data to another server is cumbersome. Block storage solves these problems: it is a cloud disk service that attaches to a server like a physical disk but lives independently of the server's lifecycle, can be grown without interruption, and delivers full flash performance. In this guide we examine end to end what block storage is, how it differs from object and file storage, its full flash architecture, its live grow and move capabilities, management via code (API, Terraform, MCP), and the right usage scenarios.
What Is Block Storage?
Block storage is a type of storage in which data is kept in fixed-size blocks, attached to a cloud server like a physical disk, and on which the operating system can build a file system (ext4, XFS, NTFS, etc.) and use it directly. The operating system sees this volume as a raw disk; it formats, partitions and uses it just like an SSD in a computer. Block storage is designed for databases, virtual machines and low-latency, transaction-intensive applications.
It is commonly known as block storage or cloud disk, and in the international literature as block storage or block volume. Amazon EBS and Google Persistent Disk are well-known examples of this model; Tres offers the same capability on full flash infrastructure, with a pay-as-you-go per-GB model, manageable via code.
How Does Block Storage Work?
With block storage, you create a volume and attach it to a server. The server recognizes this volume as a new disk; you build a file system on it and write your data. In the background, the data is split into fixed-size blocks and stored in a high-performance flash storage pool. The volume is a resource independent of the server it is attached to: even if you delete the server, the volume and the data on it are preserved; you can detach the volume and attach it to another server.
The Difference Between Block, Object and File Storage
There are three fundamental storage types in the cloud, and the difference between block storage and object storage is the most frequently confused topic. The three are not rivals; each is optimized for different workloads.
| Criterion | Block Storage | Object Storage | File Storage |
|---|---|---|---|
| Access method | Attached to a server as a disk | Via HTTP/API (S3) | Network share (NFS/SMB) |
| Data structure | Blocks, a file system is created | Objects + metadata | Folder/file hierarchy |
| Performance | High IOPS, low latency | Scale-oriented | Medium |
| Scale | Grown per volume | Practically unlimited | Per share |
| Typical use | Database, VM disk, application | Backup, media, archive, static files | Shared files, team directory |
| Example | Tres Block Storage | Tres Object Storage (S3-compatible) | Network file share |
In short: block storage is like a server's fast working disk (database, application); object storage is an unlimited-scale archive and media store (backup, static content). The two are used together in most architectures.
Which should I choose? If an operating system needs to access the data directly with low latency (database, VM disk), choose block storage; if applications will access the data via HTTP/API and scale/durability matter (backup, media, static files), choose object storage. Running your database on block storage while sending its backups to object storage is a typical and efficient combination.
Full Flash Block Storage: Why Does Performance Matter?
Storage performance is measured by two metrics: IOPS (input/output operations per second) and latency. Spinning disks (HDD) create a bottleneck in modern workloads because of their high latency and low IOPS. On Tres block storage, all volumes run on full flash (SSD/NVMe class) storage — there is no mixed disk tier.
The practical result of this is predictability: some providers offer variable speed due to different performance tiers (standard/premium) and the “noisy neighbor” effect. In a full flash, uniform architecture your disk performance is consistent; your database response time does not fluctuate throughout the day. For read/write-intensive databases, e-commerce and real-time applications, this consistency is more valuable than peak IOPS figures.
Tres Block Storage Features
You can grow a volume without shutting down the server; afterwards you simply expand the file system in the operating system. There is no need to plan downtime for your growing database or log volume. For security and data integrity, shrinking is not supported — this is standard across the industry in block storage.
You can attach a volume to a running server without a restart and safely detach it when it is no longer needed. When you have an immediate need for extra disk space, you do not stop the server; business continuity is preserved.
A volume lives separately from the server it is attached to: even if you delete the server, the data is preserved. This decouples the data from the lifetime of the server — reinstalling, replacing or upgrading the server does not put your data at risk.
You can detach a volume from one server and attach it to another server in the same region; the data comes with the disk. It offers great convenience in server-upgrade, blue-green deployment or failed-server data-recovery scenarios.
All block storage volumes run on flash storage — uniform and predictable. You do not have to choose a performance tier or work out “which disk type is faster.”
You can create, attach and grow volumes from the panel, the REST API, with Terraform or via MCP. With Terraform you manage volumes as versioned definitions and integrate them into CI/CD pipelines, or with MCP you can have an AI assistant do it in natural language.
Tip: Block storage is a persistent resource, but it is not a substitute for a backup. If the data on a volume is accidentally deleted or corrupted, that data is gone even though the volume lives independently. For critical data, you need to use block storage together with snapshots and regular backup.
What Is Block Storage Used For? Use Cases
- Database disk: Ideal for the data directory of high-IOPS databases such as MySQL, PostgreSQL and MongoDB.
- Application and server disk: An expandable disk for application files, user uploads and business data.
- Log and data growth: Handling log, archive or transaction data that grows over time with uninterrupted growth.
- High-availability scenarios: Fast access to data by detaching the volume from a failed server and attaching it to a healthy one.
- Server upgrade and migration: A smooth transition by moving the data to the new server along with the disk.
- CI/CD and automation: Test and build environments created dynamically with Terraform/API.
Who Should Use Block Storage?
Anyone who needs more than their server's internal disk, wants to safeguard data independently of the server, runs high-IOPS workloads such as databases, and manages their infrastructure with code: software teams, e-commerce and SaaS companies, database-intensive applications and DevOps teams.
Block Storage Pricing
The model in Tres block storage is simple: a single, uniform disk, billed per GB. There is no complexity of choosing a performance tier or comparing prices between different disk types; because all volumes are full flash, a single, predictable unit price applies. With pay-as-you-go logic, you pay only for the capacity you allocate and grow the volume as your needs increase.
| Factor that determines the price | Description |
|---|---|
| Allocated capacity (GB) | Flat per-GB pricing |
| Usage duration | Pay-as-you-go; the time you keep the resource allocated |
| Location | Turkey or Europe (Sofia/Frankfurt) |
Note: In block storage a disk can be grown but not shrunk; therefore, starting with a capacity close to your needs that you will grow as required is the most economical approach. You can start from a minimum capacity (for example 10 GB) and grow it as needed.
Block Storage and Data Security
Block storage is a persistent resource, but data security should be considered in multiple layers:
- Persistence: The volume is stored in the flash storage pool independently of the server; even if the server is deleted, the data is preserved.
- Use together with snapshots: The ability to roll back quickly by taking a snapshot before a risky operation.
- Backup: Backing up critical data with a separate policy; the volume itself is not a substitute for a backup.
- Network isolation (VPC): Keeping the servers that access the storage in an isolated private network.
- KVKK and location: Hosting data domestically with the Turkey location; Sofia/Frankfurt for Europe.
What Makes Tres Block Storage Different?
Predictable performance; no tier/noisy-neighbor uncertainty.
Growing without a reboot and attaching to a running server.
Even if the server is deleted, the volume and data are preserved and portable.
IaC and AI-assisted management via the panel, REST API, Terraform and MCP.
Flat per-GB pay-as-you-go; no hidden tier fees.
KVKK-compliant Turkey, and Sofia/Frankfurt for access to Europe.
Frequently Asked Questions (FAQ)
What is block storage? +
Block storage is a type of storage in which data is kept in fixed-size blocks and attached to a cloud server like a physical disk. The operating system builds a file system on it and uses it directly; it is ideal for databases and transaction-intensive applications.
What is the difference between block storage and object storage? +
Block storage is attached to a server as a disk and used directly by the operating system (high IOPS, low latency); object storage, on the other hand, is accessed via HTTP/API (S3) and offers practically unlimited scale (backup, media, archive). Block storage suits databases, while object storage suits archive/backup.
Are block storage and cloud disk the same thing? +
Yes. Block storage, cloud disk and block volume refer to the same service: a virtual disk that attaches to a server and lives independently of it.
What does full flash storage mean? +
It means that all storage volumes run on flash (SSD/NVMe class) hardware. Because there is no spinning disk (HDD) or mixed tier, performance is high and predictable.
Can I grow the disk without shutting down the server? +
Yes. A volume can be grown while the server is running (without a reboot); afterwards you need to expand the file system in the operating system. Growing requires no downtime.
Can block storage be shrunk? +
No. For security and data-integrity reasons, shrinking is not supported; this is an industry standard for block storage. That is why it is recommended to start with a capacity close to your needs and grow it as required.
Can I attach and detach the disk on a running server? +
Yes. A volume can be attached to a running server without a restart and safely detached when it is no longer needed.
If I delete my server, will my data be lost? +
No. A block storage volume lives independently of the server; even if you delete the server, the volume and the data on it are preserved. You can attach the volume to another server.
Can I move the disk to another server? +
Yes. You can detach the volume from one server and attach it to another server in the same region; the data moves with the disk. It is useful in server-upgrade and migration scenarios.
Does block storage replace backup? +
No. A volume is persistent but it is not a backup; if the data on the volume is accidentally deleted or corrupted, it is lost. For critical data it should be used together with snapshots and regular backups.
How is block storage managed? +
It is managed via the panel, REST API, Terraform and MCP. Creating, attaching and growing volumes can be automated with code; with MCP it can also be done in natural language through an AI assistant.
Can I manage block storage with Terraform? +
Yes. You can version volumes as Terraform definitions, integrate them into CI/CD pipelines and include them in your infrastructure-as-code (IaC) processes.
Which workloads is block storage suitable for? +
It is suitable for databases, virtual machine disks, application data, growing logs/archives and transaction-intensive applications that require high IOPS.
How is the block storage price calculated? +
A single, uniform disk is billed per GB. With the pay-as-you-go model you pay only for the capacity and duration you allocate; because there is no performance-tier choice, the price is predictable.
What is the minimum capacity I can start with? +
You can start with a small capacity as needed (for example 10 GB) and grow it as required. Because shrinking is not possible, starting close to your needs is the most economical approach.
Is my data kept in Turkey? +
When the Turkey location is selected, data is hosted domestically, in compliance with KVKK and data residency. For projects serving Europe, the Sofia and Frankfurt locations are also available.
Is performance consistent in block storage? +
Yes. Because all volumes are full flash and uniform, performance is predictable; the fluctuation caused by different tiers or noisy-neighbor load is minimized.