LINESERVE
Coming soon

Block Storage — hosted in Dar es Salaam

Block volumes in Dar es Salaam

Grow the disk. Keep the server. Leave the data in Tanzania.

There is a particular afternoon this product is built for. The volume is at 94%, the database is slower than it was in March, and the only plan anybody has is rebuilding a machine that has been running quietly since the last grant cycle. A block volume takes that apart: storage created separately from the instance, attached to it, grown while it is mounted, snapshotted before anything irreversible, and still there when the server is not. It is coming to tz-1a in Dar es Salaam on SSD, NVMe and HDD tiers, from 10 GB to 16 TB, priced in shillings. Tell us what you would put on one and we will tell you when it is ready.

FromTZS 300/GB/month
  • Volumes in tz-1a, our Dar es Salaam region
  • Data residency for Tanzania's Personal Data Protection Act — your data stays in-country
  • SSD, NVMe and HDD tiers, 10 GB to 16 TB
  • Grow a volume without rebuilding the server under it
  • Launching soon — priced and billed in TZS

Launching soon · Billed in TZS

Pricing

Three tiers, one per-GB price

Pick SSD, NVMe, or HDD to match your workload, then pay only for the size you provision. In your currency, no forex.

TierPrice /GB/moIOPSThroughputVolume sizes
Standard SSDPopularTZS 506Up to 10,000 IOPS250 MB/s10 GB – 16 TB
High-Performance NVMeTZS 850Up to 64,000 IOPS1 GB/s10 GB – 16 TB
Standard HDDTZS 300Up to 500 IOPS200 MB/s50 GB – 16 TB

Volumes are billed on their provisioned size, metered hourly and totalled monthly — detached volumes are still billed until deleted. Snapshots are $0.15/GB/mo, and cross-region snapshot copies are $0.02/GB one-time. Prices exclude VAT; local currency figures are indicative and settled at checkout.

The platform

Everything a production volume needs

Provisioning, snapshots, encryption, and monitoring come wired in — so your data outlives any single server.

Instant provisioning

Create a volume and have it ready to attach in seconds, straight from the console or API.

Live resizing

Grow a volume on the fly and extend the filesystem with no downtime and no reattach.

Instant incremental snapshots

Point-in-time snapshots capture only changed blocks, so backups are fast and cheap.

99.999% durability

Every block is replicated three times within the region to survive hardware failure.

Encryption at rest

Volumes are encrypted with AES-256, with optional bring-your-own-key management.

Flexible attachment

Detach a volume from one instance and reattach it to another in the same region.

Boot volume support

Use a block volume as a bootable root disk, or as extra data disks alongside it.

Full API access

Create, attach, resize, and snapshot volumes from Terraform, the CLI, or your CI.

Monitoring & alerts

Track IOPS, throughput, and latency per volume, with alerts when they cross a threshold.

Regions

tz-1a is home. Nairobi and Lagos are on the same account.

Deploy in Dar es Salaam and your data stays in Tanzania, in the same city as most of the people using it. ke-1a in Nairobi and ng-1a in Lagos are one API call away on the same console and the same shilling bill, so a standby or an offsite copy is a line in a config file rather than a supplier to onboard. Typical in-metro round trips are around 6 ms in Dar es Salaam, ~2 ms in Nairobi and ~4 ms in Lagos.

Traffic between Tanzanian networks is exchanged in Dar es Salaam. The Tanzania Internet eXchange has run there since 2003 as a project of TISPA, the Tanzanian ISP association; PeeringDB records 32 networks and 798G of connected capacity there, with Akamai, Meta, Cloudflare and TTCL among them, and no fee to join. The point of a local exchange is a plain one: a packet from one Tanzanian network to another changes hands in the city, instead of being hauled to Europe and back to travel four kilometres.

International capacity comes ashore in the same city: SEACOM, EASSy and SEAS land at Dar es Salaam, a named landing point on 2Africa as well. Inland, the National ICT Broadband Backbone carries it onward — government fibre managed by TTCL, 13,820 km laid of a 16,280 km target as of FY2024/25, reaching every region and crossing into Zambia, Malawi, Kenya, Uganda, Rwanda and Burundi. One origin in Dar es Salaam therefore has a real answer for a user in Mwanza, a site office outside Geita and a clearing agent at Tunduma.

TCRA's count for the quarter ending March 2026 tells you who is at the other end: Vodacom 36.19 million subscriptions, Yas 31.85 million, Airtel Tanzania 23.75 million, Halotel 18.32 million, against 58.9 million internet subscriptions nationally, roughly 99% of them mobile wireless. The largest reaches under a third of the country: no carrier arrangement covers a Tanzanian audience, and being inside Tanzania covers all of them at once.

Live

Tanzania

Dar es Salaam

~6 ms

typical, within metro · Data stays in Tanzania

Live

Kenya

Nairobi

~2 ms

typical, within metro · Data stays in Kenya

Live

Nigeria

Lagos

~4 ms

typical, within metro · Data stays in Nigeria

Live

Uganda

Kampala

~3 ms

typical, within metro · Data stays in Uganda

Expansion zonesSouth Africa · za-1aGhana · gh-1a

Use cases

Built for what you're building

Database storage

Consistent IOPS for MySQL, PostgreSQL, and MongoDB, with the durability transactional data demands.

Kubernetes persistent volumes

Our CSI driver provisions volumes straight from your PVCs, so stateful pods keep their data.

Logs & analytics

HDD throughput at a low per-GB price for append-heavy logs, media, and analytics stores.

Backup & DR

Instant snapshots plus cross-region copies give you point-in-time backups and disaster recovery.

How it works

From zero to mounted in three steps

1

Create a volume

Pick a tier and a size from 10 GB to 16 TB, and your volume is ready in seconds.

2

Attach & format

Attach it to an instance and format it as ext4, XFS, or NTFS — then mount and go.

3

Grow as you go

Resize the volume live as you fill it, and snapshot it on demand for backups.

Uptime SLA

99.9%

  • When hardware fails
  • When the region is the risk
  • Service credits applied automatically when we miss the SLA

Support

A Tanzanian line, and a clock that already matches yours

Call +255 761 847 121. Tanzania is on East Africa Time all year with no daylight saving, so there is no drift to track and no arithmetic before you dial — business hours mean the same thing in March as in November. A ticket opened at the start of a Dar es Salaam morning lands inside a working day, rather than at the bottom of a queue that wakes up as yours is ending.

That match is worth the most at the moment you can least afford it. Month-end, last Friday, 16:40: the reconciliation job has stalled, the settlement file has not written, and the deadline is Monday. What you want then is an engineer who is awake and at work with your instance ID in front of them — a resize that needs a reboot window, a snapshot restored into a new instance, a routing question, a port that has stopped answering. Not a form, and not a five-hour wait for somebody's morning.

[email protected] takes the commercial half, and it is worth using before you order: your TIN and registered name as the TRA holds them, a purchase-order or grant code the invoice must carry, an annual invoice that fits the budget year. Migration planning and assistance come at no extra charge, from a rack in Frankfurt or from across town. Customer references are available under NDA.

Why Lineserve

Beyond the local disk

An instance's local disk disappears the moment the instance does, can't move, and can't grow. Block volumes are independent, portable, and durable — while still keeping your data on the continent.

CapabilityLineserveInstance-local disk
Survives instance deletion
Detach & move between instances
Resize without downtime
Instant incremental snapshots
Choice of SSD, NVMe or HDD tier
99.999% durability, 3× replicated
Data stays on the continent

Pricing & invoicing

A shilling price, on a line that behaves the same in November as in March

Block storage bills on the size you provisioned rather than the size you filled. A 500 GB volume is a 500 GB volume whether the filesystem is empty or full, metered hourly and totalled monthly, and it is still billed while it sits detached after the instance is gone; billing stops when the volume is deleted. Worth knowing before you size anything, and it is also what makes the line easy to plan: the charge does not move when your traffic does, because nothing about it depends on how well the system is doing.

Tanzania prices in shillings for a reason that goes past preference. The Finance Act 2024 amended the Bank of Tanzania Act, and the implementing regulations — Government Notice 198 of 2025 — took effect on 28 March 2025: goods and services within Tanzania are priced, quoted, advertised and paid in Tanzanian Shillings, with named exemptions. So a TZS figure is not a courtesy conversion of a dollar rate, it is the way domestic business is conducted here. Indicative launch pricing puts Standard HDD at TZS 300 per GB a month, Standard SSD at TZS 506 and High-Performance NVMe at TZS 850, which makes the tier rather than the size the real cost decision.

Then the tax mechanics, which are where an overseas supplier stops being able to help. Mainland VAT is 18%, administered by the Tanzania Revenue Authority and applying to digital and electronic services; Zanzibar administers its own VAT on digital services through the Zanzibar Revenue Authority. Displayed prices exclude VAT and it is calculated and shown separately at checkout, so a volume budgeted at TZS 506,000 a month is TZS 506,000 of infrastructure in your forecast with the tax on its own line. Tanzania is also unusually exact about what a claimable receipt looks like: mainland suppliers turning over TZS 14 million or more issue through an Electronic Fiscal Device, and under EFD protocol 2.1 every invoice carries a verification code.

Bring the checklist to the order, not to the year end

Send [email protected] your TIN, your registered name exactly as the TRA holds it, and any purchase-order reference your system needs, and it is on the invoice from the first billing run. If you are buying against a grant line, ask about annual billing in the same message: ten months for twelve, one approval, one payment, one document for the file.

Volumes grow, they do not shrink

Resizing up happens live while the volume is attached and in use, then you extend the filesystem. There is no equivalent going the other way, so the discipline on a provisioned-size product is to start close to what you need and grow into it. On a grant-funded system that is the better habit anyway — the budget line matches the year rather than the ambition.

Withholding, for the finance officer who asks first

A Tanzanian business paying a non-resident for services withholds 15% of the gross consideration unless a double tax agreement reduces it, and since the 2016 amendment that applies irrespective of where the service is performed. There is also a 2% digital service tax on gross payments to non-resident providers inside the electronic-services rules. On a storage line it is a small number that recurs indefinitely, which is exactly the kind of thing to settle with your adviser at account opening.

Prices are indicative launch pricing and exclude VAT; mainland VAT of 18% is calculated and shown at checkout. Talk to [email protected] or +255 761 847 121 about invoicing requirements before you order.

Data residency

A permit application asks for the duration of the transfer. A live database does not have one.

Tanzania's Personal Data Protection Act, 2022 — Chapter 44 — has been in force since 1 May 2023, and the Personal Data Protection Commission has been fully operational since 3 April 2024. Controllers and processors register with the Commission before processing, five years at a time, and the deadline for entities already trading expired on 30 April 2025. This is a working regulator with a live regime, not a statute waiting for its commencement order.

The clause that decides where a disk belongs is the cross-border one. Personal data leaves Tanzania on a permit from the Commission, supported by adequacy in the destination country or by safeguards evidenced in an international, bilateral or contractual arrangement. The Regulation 20 application asks for the applicant and the recipient, the data subjects, the categories of personal data, the purpose and duration of the transfer, the destination country and entity, and the security arrangements there. The Commission may approve, ask for more, or refuse — and it monitors the conditions afterwards.

Now hold a running database up against that form. The purpose of the transfer is everything the application does. The categories of personal data are whatever a field team collected this morning and whatever it collects next month. The duration is however long the system runs. A backup that leaves the country once a night is at least a describable event; a live volume in another jurisdiction is a continuous one, changing while the form is being filled in. That is why teams serving Tanzanian users increasingly stop trying to characterise it and simply keep the whole of it in Dar es Salaam.

Prior authorisation is a different animal from a self-assessment. Elsewhere in the region a controller commonly satisfies itself that safeguards exist and documents the reasoning; here the Commission decides first and answers you, on its own timetable rather than yours. Administrative penalties under the Act run to TZS 100,000,000, and criminal fines reach TZS 5,000,000,000 for corporations. A regime that publishes numbers like those is a regime whose questions arrive in donor audits, bank onboarding and procurement long before they arrive from the regulator.

At launch, a volume created in tz-1a will be held in Dar es Salaam and will not leave Tanzania without your instruction — data residency for Tanzania's Personal Data Protection Act. Registration, notices, lawful basis and breach reporting remain yours as the controller. What Lineserve supplies is the location, and the location is the part that decides whether a permit conversation happens at all for the data inside it.

1 May 2023

Personal Data Protection Act, 2022 in force

TZS 100M

Ceiling on administrative penalties under the Act

16 TB

Largest single volume planned for the first release

TZS

Quoted, invoiced and settled — nothing converts

Beneficiary data is the data on the disk

If your system holds ODK or KoBoToolbox submissions, DHIS2 records, membership registers, driver photographs or KYC files, it holds personal data about identifiable Tanzanians. The archived copies of it are one question. The live tables a programme officer queries all day are another, and they sit on a volume — the most current and most complete version of everything the regime is written about.

A snapshot copied out is a transfer

Snapshots are instant, cheap and easy to point at another region, which makes them the quiet way a residency position moves. A snapshot kept in tz-1a is durability. A snapshot copied to Nairobi or Lagos is Tanzanian personal data in another country, and the Commission's permit regime applies to it. Both are legitimate; only one of them needs an application.

A volume is not a backup

Replication inside the region survives a failed drive. It does not survive a dropped table, a bad upgrade or a script run at the end of a long day, and it is not a second copy in a second place. Snapshots and dumps into object storage in tz-1a cover those without leaving the country, and each is its own decision about where a copy lives.

Who is asking for this

The Tanzanian systems that are really waiting on a volume

Nobody buys block storage because of a strategy document. They buy it because a disk is filling, a database wants more from it than it is getting, or a server has become too important to rebuild. These are the Tanzanian versions of that problem.

Donor programmes and the M&E database

The heaviest single segment in the Tanzanian buyer mix — TANGO alone counts over 485 member organisations, and the large international programmes run country operations from Dar es Salaam. Underneath the dashboards is a live database: DHIS2, an ODK or KoBoToolbox form server taking submissions from field teams on mobile data, ERPNext or Odoo carrying grant accounting. Volumes suit that shape unusually well, because a programme knows its data will grow for the length of the grant and has no idea what happens after it. Size for this year, resize when the next tranche lands, and keep the disk when the server is rebuilt at handover.

The port, transit and freight forwarding

Dar es Salaam is the transit gateway for six land-linked countries, and the Standard Gauge Railway is reshaping what moves inland. The database is the whole system here: consignments, customs declarations and TANCIS submissions, container movements, and a telematics stream from truck fleets writing small records continuously all day. Continuous small writes are precisely the workload that punishes a shared disk and rewards provisioned IOPS, which puts freight operators squarely on the NVMe tier. Retention is long because disputes are long.

ISPs, WISPs and network operators

RADIUS and AAA, billing and provisioning stacks, NetFlow collectors, Zabbix and LibreNMS retention, IPAM, authoritative and recursive DNS. These systems write constantly, must be inside the country they serve to be useful at all, and are run by buyers who will check where a machine is before they read a marketing page. One volume per system, sized independently, resized when subscriber growth says so, and snapshotted before every stack upgrade.

Mining, survey and the contractors around them

Gold exports reached USD 4,968.4 million in 2025, and the hosting buyer is very often the service contractor rather than the mine. The data is geological and survey datasets aggregated from remote sites over thin links, drill logs, incident and HSE records — large files written once, then processed and re-read from an office in Dar es Salaam. That is the HDD case: throughput over IOPS, at the lowest per-GB tier, on a volume that grows with the survey rather than with a plan somebody chose two years ago.

Financial services and fintech

Agent-banking backends, USSD gateways, reconciliation and settlement jobs, reporting into the Bank of Tanzania. Transactional databases with an audit trail attached, where the current state of the ledger is both the most valuable data the business holds and the most sensitive. This segment cares about the tier, the snapshot policy and the country all at once, which is a rare combination and the reason it is usually first in the queue.

Tourism, and a booking system that is busy elsewhere

2,289,867 international arrivals and USD 3.9 billion in travel receipts in 2025, with Arusha and Zanzibar as the operational centres. Booking engines, channel managers and property management integrations hold guest records, passport details and payment references — personal data about people who are mostly not in Tanzania, in a system whose staff, rates and reservations desk are. The images travel; the database does not have to.

Agencies, ISVs and resellers

Dar es Salaam holds 66.5% of Tanzanian startups, clustered on the Ali Hassan Mwinyi Road corridor. The pattern is many client systems on one account, each with its own database and its own habit of outgrowing whatever it was put on. Independent volumes turn that from a rebuild per client into a resize per client, plus a snapshot before every upgrade, migration and handover.

Indicative launch pricing in shillings: Standard SSD from TZS 506 per GB a month, High-Performance NVMe from TZS 850, Standard HDD from TZS 300, billed on provisioned size. Prices exclude VAT. These are the launch figures rather than a charge you can incur today.

Planning ahead

How your data gets onto a volume when it lands

From the disk your server came with

The most common Tanzanian starting point and the quickest move, because the data is already in Dar es Salaam on a Lineserve instance — sitting on storage that dies with the machine and cannot grow past the plan it arrived on. At launch, the move is to attach a volume, copy the directory across, remount it at the same path and continue; the application never learns that anything changed. What you gain is separation. The server becomes a machine you can rebuild without ceremony, and the database stops being the reason you do not. If you have been carrying a production database on instance storage because moving it was never anybody's Tuesday, this release is aimed at you.

From a volume with a provider abroad

This is not the bucket-to-bucket story, and it saves time to know that early. Two block volumes do not talk to each other over a protocol; they are disks, and disks are copied at the filesystem level. The ordinary shape is to bring the instance up in tz-1a with its volume attached and formatted, move the data with rsync, and cut over — or use the database's own replication if you would rather measure the downtime in seconds. Snapshot the source first. Two things change afterwards that have nothing to do with disks: the bill arrives in shillings and stops moving with an exchange rate, and the live data is inside Tanzania, which is the permit point above.

Tell [email protected] how much data you would put on a volume, what reads it today and when your grant or budget cycle needs it, and you will hear from us when there is something to attach. Migration planning and assistance are included at no extra charge.

FAQ

Questions, answered

Your instance's local storage lives and dies with the instance. A Block Storage volume is independent — detach it, reattach it to another instance, resize it live, and snapshot it. Delete the server and the volume, and your data, survives.

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.

In tz-1a, our Dar es Salaam region. A volume is created in a region and stays there — it attaches to instances in that same region, and it does not leave Tanzania unless you copy a snapshot out yourself.

It is in build and there is no public date. Send [email protected] the workload and the rough size and you go on the list — you hear from us when there is something to attach, rather than when a calendar says so.

Indicative launch pricing is TZS 506 per GB a month for Standard SSD, TZS 850 for High-Performance NVMe and TZS 300 for Standard HDD, billed on provisioned size and metered hourly, with snapshots billed separately. Prices exclude VAT. These are the figures we expect to open with, published so you can plan against them.

Tell [email protected] what you would run on it, on which tier and at what size. Those conversations decide what comes first, and the teams having them are the ones we come back to when there is something to try.

Yes. Volumes created in tz-1a are held in Dar es Salaam and are not moved out of the country without your instruction, which gives you data residency for Tanzania's Personal Data Protection Act. Your duties as a controller, registration included, are unchanged.

Not for data that stays in Tanzania — the Commission's permit regime governs transfers out of the country, and that question does not arise for a volume held in Dar es Salaam. Whether any of your other processing needs a permit is between you and the Personal Data Protection Commission.

Because it lives and dies with the server, cannot move, and cannot grow past the plan it came with. A volume outlives the instance, detaches and reattaches to another machine in the same region, and resizes while it is mounted. The difference shows up on the day you want a bigger machine, or the day you no longer want that one.

Object storage is an S3 API you write buckets to over HTTP — right for archives, field submissions, backups and anything served to a browser. A block volume is a disk attached to one instance, with a filesystem on it, that your database reads and writes through ordinary file operations. Buckets hold what you keep; volumes hold what you are working on. Most Tanzanian systems end up wanting both, in the same region.

No — a block volume attaches to one instance at a time. Shared access across a fleet is what File Storage is for, and it is on the same launch path.

Cross-region snapshot copies are planned, on the same account as tz-1a. Make the call deliberately for personal data: a copy in ke-1a or ng-1a is a transfer out of Tanzania under the Act, and the permit regime applies to it. Application images, build artefacts and logs without personal data raise no such question.

In TZS, with M-Pesa and other mobile money, bank transfer, or card — the same methods as the rest of your account. Nothing converts, no international transaction lands on the statement, and no bank adds a foreign-transaction fee.

No. Displayed prices exclude VAT. Mainland VAT on digital and electronic services is 18%, administered by the Tanzania Revenue Authority, and it is calculated and shown separately at checkout. Zanzibar is administered separately.

Annual billing runs ten months for twelve on eligible plans — one approval, one payment, one document for the file. Tell [email protected] when your grant or budget year starts and it can be lined up with it rather than cutting across it.

Yes. Creating, attaching, resizing and snapshotting are API and CLI operations on the same account and credentials as the rest of the platform, so a volume is something your pipeline provisions rather than something somebody remembers to click.

Customer references are available under NDA for the products that are live today, object storage in tz-1a among them. Tell [email protected] what you are building and you will be pointed at the closest match.

Yes: +255 761 847 121, alongside [email protected] and the ticket system. Tanzania is on East Africa Time year-round with no daylight saving, so business hours mean one thing all year.

Persistent volumes are almost here

Block Storage is launching soon, close to your users and billed in local currency. Talk to us to line up early access and be first to attach a volume.

Launching soon · 99.999% durability · Billed in TZS