Object Storage as a Service

Object storage keeps files under unique identifiers instead of a folder hierarchy, scales without limit and is accessed through the S3 API. DataKobi's object store is fully compatible with the Amazon S3 API.

Get a Quote 0312 945 36 42

12 years of field experienceTR data centers24/7 on-site support

Backups, logs, media files and data lake workloads are expensive and hard to manage on conventional disks. With DataKobi Object Storage, your existing SDKs and tools (rclone, Veeam, MinIO client, AWS CLI) work without modification; the only thing that changes is the endpoint address.

Data is split with 4+2 erasure coding and written across different disks and servers. With optional geo-replication, a second copy is kept across Ankara and Istanbul. The target data durability is 99.999999999% (eleven nines), so your data remains accessible even if a single disk, a single server or an entire data center is lost.

Key features

Full S3 compatibility

Bucket policies, presigned URLs, versioning and lifecycle rules are supported.

Geo-replication

A dual data center copy across Ankara and Istanbul, enabled with a single checkbox.

Eleven nines of durability

A 99.999999999% data durability target with 4+2 erasure coding.

Predictable pricing

A flat fee per GB; no surprise data egress charges.

What is erasure coding, and how does it differ from RAID?

Erasure coding is a mathematical protection method that splits an object into K data chunks plus M parity chunks and distributes them across different disks. The standard profile at DataKobi is 4+2: each object is split into 6 chunks and can be read back in full from any 4 of them, so losing 2 disks or servers at the same time does not cause data loss. RAID protects the disks of a single server, whereas erasure coding spreads across servers and even data centers, and its capacity overhead is 50% lower than full replication. This is the technical reason why both durability and price per GB beat conventional storage.

How does immutable storage protect against ransomware?

We support the S3 Object Lock standard: when you lock a bucket in compliance mode, the objects written to it cannot be deleted or modified by anyone, not even by an administrator, for the duration of the retention period. According to Veeam's 2024 Ransomware Trends report, attackers targeted backup repositories in 96% of ransomware attacks; immutable storage is a strong barrier against attempts to delete or alter backups. We operate as a certified "S3 Compatible immutable" target for Veeam, Veritas and Commvault, and we define the retention policy together with you during setup.

Technical Specifications

API: S3 v4 signing, STS temporary credentials supported
Security: Server-side encryption (SSE), per-bucket access control
Versioning: Object versions + Object Lock (immutable)
Lifecycle: Rules for automatic transition to an archive tier
Compliance: KVKK (Türkiye's personal data protection law) — data stays in Türkiye

Frequently Asked Questions

What is the difference between object storage and block storage?

Block storage is attached to a server as a disk and requires an operating system; object storage is accessed directly over an HTTP API, scales without limit and costs far less per GB. For backups, logs and media, object storage is the right choice.

Can I migrate data from AWS S3?

Yes. You can sync your buckets directly with rclone or the AWS CLI, and we provide free migration support for large data sets. Unlike AWS, we do not charge egress fees on data leaving the platform.

Can I send my Veeam backups here?

Yes. It works as a certified "S3 Compatible" target for Veeam, and with Object Lock, immutable (tamper-proof) backups protect against ransomware.

A 30-minute discovery call with your architect

We will listen to your needs and outline the right architecture and a clear pricing framework in the same call. The first consultation is free.

Book a Call