Block volumes inside Kenya, Tanzania and Nigeria

Standard SSD delivers up to 10,000 IOPS and suits web apps, dev environments, and small databases. High-Performance NVMe reaches 64,000 IOPS and 1 GB/s for demanding databases and real-time analytics. Standard HDD favours cheap throughput for logs, media, and backups.

Yes. Volumes resize instantly while attached and in use — then you extend the filesystem (resize2fs for ext4, xfs_growfs for XFS). Volumes can only grow, not shrink.

Snapshots are instant and incremental — only changed blocks are stored after the first one. Restore a volume to any snapshot, or clone a snapshot into a new volume. Snapshot storage bills at $0.15/GB per month.

Every volume is replicated three times across separate physical drives, and failed drives are reconstructed automatically. That yields 99.999% durability with a 99.99% availability SLA.

Yes. Use volumes as boot disks with custom OS images, resize the boot disk as you grow, and move a bootable volume between instances.

Yes. Volumes are encrypted with AES-256 before data touches disk, using platform-managed keys or your own via KMS. Data in transit is encrypted too.

You pay for provisioned size, metered hourly, whether or not the volume is attached — a 100 GB Standard SSD volume costs $25.30 a month. Billing stops when you delete the volume.

Volumes range from 10 GB (50 GB on HDD) up to 16 TB, with up to 16 volumes attached per instance. Account limits are raised on request.

ke-1a in Nairobi, tz-1a in Dar es Salaam and ng-1a in Lagos, on one account and one API. A volume is created in a region and stays there — it attaches to instances in that same region, and it does not cross a border unless you copy it across yourself.

It is in build and there is no public date yet. Join the waitlist through [email protected] with the region you need and what you would put on the volume, and you will hear from us when it is ready rather than when a marketing calendar says so.

Indicative launch pricing is $0.253 per GB a month for Standard SSD, $0.425 for High-Performance NVMe and $0.15 for Standard HDD, billed on provisioned size and metered hourly, with snapshots billed separately. Those are the figures we expect to open with, published so you can build a forecast — not a price you can pay today.

Tell [email protected] what you would run on it, in which region, and how much data is involved. Early conversations shape which tier and which region come first, and the teams in those conversations are the ones we come back to when there is something to try.

Yes. A volume created in ke-1a is held in Nairobi, one in tz-1a in Dar es Salaam, one in ng-1a in Lagos, and none of them leaves its country without your instruction. That is data residency for Kenya's Data Protection Act, Tanzania's Personal Data Protection Act or Nigeria's Data Protection Act, depending on the region.

No, and that is deliberate. Volumes attach, detach and reattach within their own region. Moving data between countries is a snapshot copy that you initiate, which keeps the cross-border question an explicit decision rather than something a scheduler can do to you.

Object storage is an S3 API you write buckets to from anywhere — good for archives, media, backups and anything a browser or another service fetches over HTTP. A block volume is a disk attached to one instance, with a filesystem on it, that your application reads and writes through ordinary file operations. Buckets hold what you keep. Volumes hold what you are working on.

A volume attaches to one instance at a time. File storage is a managed NFS file system that many instances mount at once. If a single database or application owns the data, that is block; if a fleet has to see the same directory, that is file.

No. Amazon's African region is Cape Town and Microsoft's is in South Africa. Lagos and Nairobi carry edge and content-delivery infrastructure, which caches content rather than running your database. A volume needs compute in the country, which is what these three regions are.

Of whatever personal data is on it, yes. A snapshot kept in the same region is durability; a snapshot copied to another one is a copy of that data in another country, with the destination country's law and the source country's transfer rules both in play. Build artefacts, package caches and logs carrying no personal data raise no such question.

US dollars by card or bank transfer if you are buying from outside the three countries. If a Kenyan, Tanzanian or Nigerian entity should carry the cost instead, that entity can hold its own account and settle in KES, TZS or NGN — Kenya and Tanzania add M-Pesa alongside bank transfer and card, and Nigeria settles in Naira by bank transfer or card.

Displayed prices exclude VAT, and where it applies it is calculated and shown separately at checkout. The domestic rates differ — Kenya 16%, mainland Tanzania 18%, Nigeria 7.5% — and which one reaches your invoice follows which entity is billed, not which region holds the volume.

Yes. Creating, attaching, resizing and snapshotting volumes is API and CLI work rather than console work, on the same account and credentials as the rest of the platform, so a regional deployment stays something your pipeline builds rather than something somebody clicks.

No. The account is yours wherever you are, and the region is a choice at creation. A local entity changes how you would like to be billed and taxed, not where you can put data.

Customer references are available under NDA for the products that are live today, including object storage in all three regions. Tell [email protected] what you are building and which country it has to sit in, and you will be pointed at the closest match.

Two things. Decide which country the live data has to be in, because that decision is independent of us and it is the one with a lead time. Then send [email protected] the region, the rough volume size and the workload, so the first release is shaped by the people who are actually waiting for it.