LINESERVE
Coming soon

File Storage — hosted in Nairobi

File Storage

One file system, mounted everywhere.

A fully managed NFS file system, mounted by thousands of instances simultaneously. It grows elastically from gigabytes to a petabyte and is replicated across zones — so every server sees the same files, with no capacity to provision.

FromKES 2.4/GB/month
  • NFSv4.1, full POSIX
  • Elastic — pay for what you store
  • Three locally-hosted regions — Nairobi, Dar es Salaam & Lagos
  • Data residency for Kenya's Data Protection Act — your data stays in-country
  • 99.99% availability SLA

Launching soon · Local billing in KES, TZS & NGN

Pricing

Pay for what you store, nothing more

Three storage classes, one per-GB price each. No pre-provisioning, no minimums — capacity follows your data, measured hourly. In your currency, no forex.

Storage classPrice /GB/moThroughputLatency
UniversalPopularGeneral-purpose shared storage for most workloads.KES 21100 MB/s, burst to 1 GB/s~2 ms
FastAnalytics, ML training data, media pipelines.KES 36500 MB/s, up to 10 GB/s provisioned<1 ms
BasicInfrequently accessed files, archives, backups.KES 2.4100 MB/s10–50 ms

You are billed on the data actually stored, measured hourly — there is no capacity to pre-provision. Fast provisioned throughput is $0.05 per MB/s, Basic reads are $0.01/GB, and snapshots are $0.05/GB/mo. Prices exclude VAT; local currency figures are indicative and settled at checkout.

The platform

Everything shared storage should be

Managed, elastic, and replicated — mounted by your whole fleet, with no file server to run.

Fully managed

No NFS servers to provision, patch, or fail over — we run the whole file system for you.

Elastic scaling

Capacity grows and shrinks with your data, from gigabytes to a petabyte, with nothing to provision.

Multi-AZ replication

Every file is synchronously replicated across availability zones and survives the loss of a zone.

Unlimited concurrent mounts

Thousands of instances mount the same file system at once, with real-time consistency across them.

POSIX-compliant NFSv4.1

Full file locking, permissions, symlinks, and hard links — your apps work unchanged.

Encryption everywhere

AES-256 at rest and TLS in transit, with keys managed for you or brought yourself.

Lifecycle policies

Auto-tier cold files down to Basic and save up to 60% without moving a thing.

Snapshots

Instant, incremental snapshots let you restore a whole file system or a single file in seconds.

Access points

Per-tenant roots and permissions give each app or team its own view of the file system.

Regions

Nairobi is home. The other two are there when you need them.

ke-1a is in Nairobi, and for a Kenyan business that is most of the argument. Your customers arrive on Safaricom, on Faiba, on Zuku, on Poa — 2.65 million fixed subscriptions and 84.1 million active SIMs, nearly all of them inside the country. Lineserve peers at KIXP, the neutral exchange TESPOK runs across four Nairobi facilities, so traffic between your instance and another of its 136 networks is handed over a few kilometres away. A round trip that starts and finishes inside the metro is typically around 2 ms.

That matters because of where Kenya's bandwidth comes ashore. Every international subsea cable lands at Mombasa — SEACOM, EASSy, TEAMS, PEACE, DARE1 and LION2 — and the capacity is hauled roughly 480 km inland before it reaches a Nairobi rack. Anything leaving the country still makes that trip. Domestic traffic takes the other route entirely, exchanged in Nairobi between networks in the same city, and choosing ke-1a decides which of those two journeys your checkout depends on.

Dar es Salaam and Lagos sit on the same account, the same API and the same shilling invoice. Open tz-1a when you start selling into Tanzania and want the data held there under Tanzanian law, or ng-1a when Lagos becomes a market rather than a pin on a map. They are also where a copy goes when you want one outside Kenya — a standby database, a backup bucket — which makes disaster recovery a configuration change instead of a second supplier.

Live

Kenya

Nairobi

~2 ms

typical, within metro · Data stays in Kenya

Live

Tanzania

Dar es Salaam

~6 ms

typical, within metro · Data stays in Tanzania

Live

Nigeria

Lagos

~4 ms

typical, within metro · Data stays in Nigeria

Expansion zonesUganda · ug-1aSouth Africa · za-1aGhana · gh-1a

Use cases

Built for shared workloads

Shared web content

Every server sees the same uploads, themes, and media — no rsync, no drift, no sticky sessions.

Kubernetes RWX volumes

Many pods, one volume. The CSI driver gives you ReadWriteMany persistent volumes out of the box.

ML & analytics

Share datasets across GPU workers with high-throughput reads, no copying between nodes.

CI & dev environments

Shared source, build artifacts, and caches across runners and workspaces, live for every job.

How it works

Shared storage in three steps

1

Create a file system

Pick a storage class — Universal, Fast, or Basic. There is no size to provision.

2

Mount over NFS

Run one mount command on any instance — or request a RWX volume in Kubernetes.

3

Store and share

Capacity follows your data as it grows, and lifecycle policies tier cold files down.

Uptime SLA

99.9%

  • DDoS filtering is included, not an upsell
  • Service credits applied automatically when we miss the SLA
  • Measured monthly, per region, on network and power availability

Support

A Nairobi number, and East Africa Time all year

Kenya has its own line: +254 119 039 063. Alongside it are [email protected] and the ticket system, and Lineserve Limited keeps an office on Utalii Lane, View Park Towers, in the Nairobi CBD. A supplier with a street address in your own city is a different kind of counterparty from a web form and a billing address in another hemisphere.

Kenya runs on East Africa Time, UTC+3, and has never observed daylight saving. That reads like trivia until you are the one holding the phone. Business hours here mean the same thing in January and in July; nothing slides by an hour twice a year because another country changed its clocks. When your checkout starts throwing 502s at 09:20 on a Tuesday, it is 09:20 for whoever picks up — an ordinary working morning in the same city, rather than the small hours of somebody's Monday night, eight time zones west.

The other half of local support is vocabulary, not hours. The person you reach knows what a Safaricom callback is, what KIXP has to do with the trace you are staring at, and why your finance team wants a KRA PIN on the invoice. None of that has to be explained before the actual problem can be. Buy from somewhere that has never sold into Kenya and the first twenty minutes of every serious ticket go on describing the country.

Kenya

+254 119 039 063

Why Lineserve

Managed NFS beats running your own

Running your own NFS server means patching, capacity planning, and failovers when a node dies. A managed, elastic file system takes all of that off your plate.

CapabilityLineserveSelf-run NFS server
No NFS server to run or patch
Elastic capacity, no pre-provisioning
Replicated across availability zonesSometimes
Thousands of concurrent mountsSometimes
Automatic lifecycle tiering
Billing in KES, TZS & NGN
Data stays on the continent

FAQ

Questions, answered

A Block Storage volume attaches to one instance, like a disk. A file system mounts on thousands of instances at once over NFS, with every mount seeing the same files in real time. Use Block for databases; use File when fleets share data.

NFSv4.1 with full POSIX semantics — file locking, permissions, hard and symbolic links. Any Linux distribution mounts it natively; macOS and Windows work through their NFS clients.

There's nothing to provision. The file system grows and shrinks with the data you store, from gigabytes to a petabyte, and you pay only for what you actually use, measured hourly.

Yes. The CSI driver supports dynamic provisioning and ReadWriteMany (RWX) volumes, so many pods across many nodes can share the same persistent volume.

Universal gives a 100 MB/s baseline with bursts to 1 GB/s — right for most workloads. Fast starts at 500 MB/s with provisioned throughput up to 10 GB/s and sub-millisecond latency for analytics, ML training, and media pipelines.

Set a policy and files that go unused — say for 30 days — move automatically to the cheaper Basic class, cutting storage costs by up to 60%. The move is transparent; applications keep the same paths.

Yes. Every file system is replicated across multiple availability zones within the region at no extra cost, backed by a 99.99% availability SLA. Cross-region replication is available for disaster recovery.

Point-in-time snapshots are instant and incremental. Restore individual files from a read-only mount or roll back the whole file system, on demand or on a schedule.

Yes. Connect over VPN or a direct link and on-prem machines mount the file system exactly like cloud instances — useful for hybrid setups and migrations.

Yes. Your data is hosted in Kenya and stays in-country, giving you data residency for Kenya's Data Protection Act. It isn't moved out of Kenya without your instruction.

In our Nairobi data centre (ke-1a). Your content is stored and served from Nairobi, close to your users.

Pay in your local currency using M-Pesa and other mobile money, bank transfer, or card. No foreign card or forex conversion is required.

You're billed in KES. Prices can be viewed in USD, KES, TZS, or NGN, but as a Kenya customer you pay in KES with no forex conversion.

Shared storage for your whole fleet, almost here

Managed NFS is launching soon, close to your users. Talk to us for early access, and pay in local currency with no card required to start.

Launching soon · 99.99% availability SLA · Local billing in KES, TZS & NGN