S3-compatible object storage for backups, archives, media and data lakes
Regions: tr-ist-01 (İstanbul) · tr-ank-01 (Ankara).
The file is written to the S3-compatible endpoint under a bucket and a key.
The object is split into chunks; metadata and version information are kept separately.
Chunks are placed across the İstanbul and Ankara regions; both regions are in Türkiye.
The cross-region durability copy keeps the object reachable if a single region is lost.
Answer
Object Storage (PVOS) is S3-compatible object storage that keeps data in buckets. It is used for backups, archives, media and data lakes.
Cost depends on stored data volume, request and data transfer pattern, retention and lifecycle approach. Review the current estimate in the cost calculator.Calculate Cost
Live capacity and quota depend on the selected resource; service level terms are explained on the SLA page.
Features
How it works
Evaluate object storage when an application can read and write data by bucket and object key rather than through an attached disk. Media, static assets, logs, archives, backup packages and datasets are typical candidates. Block storage can be more natural for operating-system disks, database files or frequent random block updates. Choose by access and update pattern before capacity.
You access buckets and objects through an S3-compatible API. The endpoint, region and credentials are created in the console. Supported operations are in the documentation.
Inventory source buckets, object count and size distribution, total data, metadata, ACLs or policies, versioning, lifecycle, encryption, object lock, the application endpoint and data-egress cost. Copy a small dataset and check checksums. Define dual-write or a maintenance window, endpoint cutover and rollback.
Object Storage runs on infrastructure located in Türkiye. Regions are limited to İstanbul (tr-ist-01) and Ankara (tr-ank-01). Cost follows stored data, request count and data transfer. You can see current prices in the cost calculator.
Scenarios
Decision criteria
Hover or press play; the steps light up in time with the recording.
FAQ
Evaluate object storage when an application can read and write data by bucket and object key rather than through an attached disk. Media, static assets, logs, archives, backup packages and datasets are typical candidates. Block storage may be a better fit for operating-system disks, database files or frequent random block updates.
Object storage manages data in buckets by object key and metadata through an API. Block storage attaches a disk-like volume to a server so the operating system can run a filesystem or database on it. The right choice depends more on access, update and latency needs than on capacity alone.
You access buckets and objects through an S3-compatible API. Endpoints and credentials are created in the console. Supported operations are in the documentation.
Copy your existing buckets to PortvMind Cloud Object Storage with S3-compatible tools. Endpoints and credentials are created in the console.
PortvMind Cloud uses a pay-as-you-go model with per-minute billing. Total cost depends on resource type, selected configuration, storage, network and runtime. Current unit prices are in the console and at calculator.portvmind.com.
Next step
Create the resource in the console. For a migration or scaling plan, continue together in an architecture consultation.
Model your scenario in the cost calculator.Calculate Cost
