Is it really S3 compatible?

Yes. It implements the S3 API, so the AWS CLI, boto3, s3cmd, rclone, Veeam, MinIO clients and most backup software work by changing the endpoint.

What does egress cost?

Ingress is free. Egress is metered per gigabyte and billed monthly. Traffic to your CloudTechtiq instances in the same region is free.

Can I use it for backups and archives?

Yes. Lifecycle rules move objects to lower-cost tiers on a schedule, versioning protects against accidental deletion, and object lock supports write-once retention.

How do I serve files publicly?

Buckets are private by default. You can make specific objects public, issue time-limited signed URLs, or put a CDN in front.

Block storage · UAE region

NVMe volumes that grow while your application keeps running.

Attach, resize and snapshot persistent volumes without stopping the instance. Triple-replicated inside the UAE region, encrypted at rest, and priced per gigabyte with no minimum commitment.

Up to 16 TB per volume
Live resize
Triple replication
AES-256 at rest

Pricing

Block storage pricing

One rate per gigabyte per month, prorated hourly. You pay for provisioned capacity, not for the IOPS you happen to use in a busy month.

Item	Unit	Price (AED)
Block storage volume	per GB / month	0.36
Volume snapshot	per GB / month	0.18
Scheduled backup (daily, 7-day retention)	per GB / month	0.22
Snapshot restore	per operation	Free
Volume attach / detach / resize	per operation	Free

Prices exclusive of 5% UAE VAT. Prorated hourly from the moment a volume is created until it is deleted.

Use cases

Where teams put block storage to work

One volume type, provisioned by the gigabyte, covers everything from a single database to a fleet of Kubernetes persistent volumes.

Databases

Primary storage for transactional workloads

Provision by IOPS as well as capacity so MySQL, PostgreSQL and SQL Server get consistent low-latency disk under write-heavy loads.

Kubernetes

Persistent volumes for stateful pods

Mount block volumes as PersistentVolumeClaims through the CSI driver, so StatefulSets keep their data across pod rescheduling.

Backup target

Snapshot-based backup chains

Schedule daily or weekly snapshots with configurable retention and restore into a fresh volume in minutes, without touching the source.

ERP & line-of-business

Predictable disk for SAP and ERP systems

Dedicated-core instances plus triple-replicated volumes give finance and inventory systems the consistency auditors expect.

Media processing

Scratch disk for encode and render jobs

Attach a large NVMe volume for the duration of a transcoding or rendering job, then detach and delete it once the output is uploaded.

VDI & dev boxes

Per-user disks that resize on request

Grow a developer's volume live when a project outgrows its allocation, without a reboot or a support ticket queue.

Capabilities

What you can build on it

Object storage is the cheapest durable place to put data that is written once and read many times.

Consistent low latency

NVMe throughout, with no burst-credit model that quietly throttles you three hours into a batch job.

Triple replication

Writes land on three nodes inside the region before acknowledgement. Disk and node failures are invisible to the guest.

Point-in-time snapshots

Snapshot before every deployment. Restores create a new volume, so the original stays untouched while you verify.

Encrypted at rest

AES-256 on volumes and snapshots, with platform-managed keys and no configuration required from you.

Per-volume metrics

IOPS, throughput and queue depth per volume, so you can tell a slow query from slow storage.

API-driven

Create, attach, resize and snapshot through the API or Terraform as part of your deployment pipeline.

AES-256

encryption at rest, on by default

Reliability

Durability that doesn't depend on you remembering to back up

Replication happens on every write, before it is acknowledged back to your instance. Snapshots and scheduled backups sit on top of that as a second, independent layer of protection.

3×

replicated writes inside the region

< 1 ms

typical write acknowledgement latency

16 TB

maximum size per single volume

downtime required to resize live

Questions we get asked

Frequently asked questions

Yes. Volumes expand live — the block device grows immediately and you extend the filesystem inside the guest without rebooting. Volumes cannot be shrunk; if you need less capacity, create a smaller volume and migrate the data.

Every block is written to three separate storage nodes inside the region before the write is acknowledged. A single node or disk failure is transparent to the instance. Replication is not a substitute for backup, so we also recommend scheduled snapshots.

NVMe-backed volumes deliver consistent low-millisecond latency with IOPS scaling by volume size. For database workloads we recommend provisioning by IOPS requirement rather than capacity, and we will size it with you.

No — a block volume attaches to one instance at a time, which is how block storage works everywhere. For shared access across many instances, use object storage or a network filesystem, and we can advise which fits.