Managed Databases — hosted in Nairobi, Dar es Salaam & Lagos
Coming soonManaged Databases
Production databases without the pager duty.
Fully managed PostgreSQL, MySQL, MongoDB, Redis and MariaDB — we handle backups, patching, monitoring and failover.
- PostgreSQL · MySQL · MongoDB · Redis · MariaDB
- Multi-AZ failover under 60s
- Three locally-hosted regions — Nairobi, Dar es Salaam & Lagos
- Data sovereignty — your data stays in-country
- 99.99% uptime SLA
Launching soon · Local billing in KES, TZS & NGN
Pricing
One flat price per instance
Pick a size and engine — every plan includes automated backups, point-in-time recovery, and multi-AZ high availability. In your currency, no forex.
Small
Hosted in Nairobi, Dar es Salaam & Lagos
- 1 vCPU
- 2 GB RAM
- 20 GB SSD included
- 100 connections
- Daily backups, 35-day PITR
Medium
Hosted in Nairobi, Dar es Salaam & Lagos
- 2 vCPU
- 4 GB RAM
- 50 GB SSD included
- 200 connections
- Daily backups, 35-day PITR
Large
Hosted in Nairobi, Dar es Salaam & Lagos
- 4 vCPU
- 8 GB RAM
- 100 GB NVMe included
- 500 connections
- Daily backups, 35-day PITR
XLarge
Hosted in Nairobi, Dar es Salaam & Lagos
- 8 vCPU
- 16 GB RAM
- 200 GB NVMe included
- 1000 connections
- Daily backups, 35-day PITR
Every plan includes automated backups with 35-day point-in-time recovery, and multi-AZ high availability is available on all sizes. Additional storage is billed per GB. Prices exclude VAT; local currency figures are indicative and settled at checkout.
The platform
Everything a production database needs
High availability, backups, security, and observability come wired in — so day two looks like day one.
Five engines
PostgreSQL 14–16, MySQL 8.0/8.1, MongoDB 6/7, Redis 6.2/7, and MariaDB 10.11/11 — your choice.
Multi-AZ high availability
Synchronous standbys across zones with automatic failover in under 60 seconds and zero data loss.
Automated backups & PITR
Daily backups plus continuous archiving — restore to any second within the last 35 days.
Read replicas
Add up to five read replicas with sub-second lag to scale reads and offload analytics.
Encryption everywhere
AES-256 encryption at rest and TLS 1.3 in transit, on by default for every instance.
VPC isolation
Private by default — databases live inside your VPC, reachable only from your own services.
Connection pooling
Built-in PgBouncer and ProxySQL keep thousands of client connections efficient and stable.
Performance insights
Slow-query analytics and live metrics surface the queries that need your attention.
Automated patching
Minor versions and security fixes applied during the maintenance window you choose.
Regions
Nairobi, Dar es Salaam or Lagos — and what decides it
The rule is unglamorous and it holds nearly everywhere: put the workload in the country whose users and whose records it serves. Per-unit prices are identical in all three regions, so the decision is geography and law rather than cost — and there is no useful midpoint, because traffic between the three cities is still commonly carried through Europe.
ke-1a is for Kenyan users and Kenyan records, and for regional teams whose head office is already in Nairobi. Every Kenyan subsea cable — TEAMS, SEACOM, EASSy, LION2, DARE1 and PEACE — comes ashore at Mombasa, and that capacity is carried roughly 480 km inland to the city where the carriers and the customers are. Domestic traffic never makes that trip: it is exchanged inside Nairobi at KIXP, the neutral exchange TESPOK has run since 2002, with 136 peer networks and 2.9 Tbps of connected capacity. Lineserve peers there.
tz-1a is for Tanzanian users, and it is where moving an origin changes the most: Tanzania has no content-delivery edge of its own, so a Dar es Salaam viewer is served from another country however the CDN is configured. There is no inland haul either — SEACOM, EASSy and SEAS come ashore in the city itself, and Dar es Salaam is a named landing point on 2Africa. Tanzanian networks meet at TIX, run since 2003 by the country's service-provider association, and 13,820 km of state fibre carries one origin on to Mwanza, Arusha and Dodoma.
ng-1a is for scale and for regulated Nigerian workloads. Eight subsea systems land in and around Lagos, among them MainOne, SAT-3, WACS, Equiano and 2Africa, which comes ashore at Lekki. Nigerian networks exchange domestic traffic at IXPN, founded in 2006 to stop domestic packets being hauled to London and now running 13 points of presence across seven states. Lagos also has a date attached: a Central Bank circular directs payment transaction data generated in Nigeria to be stored there from 1 January 2027.
All three give a buyer based elsewhere the same pair of things: a request from a user in the city reaches a machine in that city, typically in single-digit milliseconds, and the records it touches sit under one named country's law.
Kenya
Nairobi
~2 ms
typical, within metro · Data stays in Kenya
Tanzania
Dar es Salaam
~6 ms
typical, within metro · Data stays in Tanzania
Nigeria
Lagos
~4 ms
typical, within metro · Data stays in Nigeria
Use cases
Built for what you're building
Web & mobile backends
Managed PostgreSQL or MySQL that scales with you, so your app team never babysits a database.
E-commerce
Read replicas and connection pooling absorb traffic spikes without dropping a single order.
Caching & sessions
Managed Redis with sub-millisecond latency for sessions, queues, and hot data.
Content management
Run WordPress, Drupal, and custom apps on managed MySQL or PostgreSQL, kept patched and backed up.
How it works
From zero to database in three steps
Pick engine & size
Choose your engine, version, and instance size — from Small to XLarge.
Connect
Grab the connection string and connect — private by default, inside your VPC.
We keep it healthy
Backups, patching, failover, and monitoring — all handled, day and night.
Uptime SLA
99.9%
- Service credits applied automatically when we miss the SLA
- Measured monthly, per region, on network and power availability
- Tier III colocation facilities across all live regions
Support
You are on a different continent from your infrastructure
That is the real reservation, and it is answerable with what exists. Architecture, quotes, contracts, a data processing agreement, the registered names and tax identifiers that have to appear on your invoices: [email protected], in writing, in a thread you can forward to your own legal and finance people. Running services are driven from the console, the API and the ticket system on your account. Two phone lines are published for the region — +254 119 039 063 in Kenya and +255 761 847 121 in Tanzania.
Scheduling across the distance is the practical problem, and the arithmetic is friendlier than it looks. Nairobi and Dar es Salaam run on East Africa Time, UTC+3; Lagos on West Africa Time, UTC+1. Neither observes daylight saving, so the gap between your clock and theirs moves only when your own clocks change, and a window agreed in June still means what you thought it meant in December. From London, Nairobi is three hours ahead in winter and two in summer, and Lagos an hour ahead in winter and level in summer. From New York in July, a 09:00 call is 14:00 in Lagos.
Most of what would be a phone call elsewhere is a call you make yourself. Building, resizing, rebooting, snapshotting and rebuilding an instance are API and console operations that behave identically at three in the morning your time or theirs, and a browser console reaches a machine that has lost its own networking. What needs a person in the building is a physical fault — and that person is there already.
Why Lineserve
Managed beats midnight maintenance
Running your own database on a VPS means backups you hope work, manual failovers, and patching at 2 a.m. This is the option where we do all of that for you.
FAQ
Questions, answered
We run the database engine for you — provisioning, backups, patching, monitoring, and failover. You create an instance, get a connection string, and focus on your application.
PostgreSQL 14–16, MySQL 8.0 and 8.1, MongoDB 6.0 and 7.0, Redis 6.2 and 7.0, and MariaDB 10.11 and 11.0 — all with the same managed features.
HA instances replicate across availability zones. If the primary fails, an automatic failover promotes the standby — typically in under 60 seconds, with zero data loss — behind a 99.99% uptime SLA.
Daily automated backups are retained for 35 days with point-in-time recovery to any second in that window. You can also take manual snapshots whenever you like.
Up to five read-only copies of your primary that serve read queries, synced automatically with typically under a second of lag. Use them to scale read-heavy workloads without touching the primary.
Yes. Scale vertically to a larger size within a brief maintenance window, or horizontally by adding read replicas with no downtime at all.
Yes. AES-256 at rest and TLS 1.3 in transit, with platform-managed keys or your own via KMS.
Instances live in a private network with no public access by default. Reach them through security groups and database users, or peer your VPC and connect over VPN from on-premises.
Standard tools work directly — pg_dump and mysqldump for one-shot moves, or logical and binary-log replication for near-zero-downtime migrations. Our team helps plan the move at no charge.
Your data stays in the region you deploy to. Across our data centres in Nairobi (Kenya), Dar es Salaam (Tanzania), and Lagos (Nigeria) it never has to leave the continent — deploy in the country closest to your users and your data is held there.
In whichever of our three regions you choose — Nairobi (ke-1a), Dar es Salaam (tz-1a), or Lagos (ng-1a). Your content is stored and served from that in-country facility.
Pay in USD by card or bank transfer — or switch to our Kenya, Tanzania, or Nigeria market to pay locally in KES, TZS, or NGN with methods like M-Pesa.
You can view and pay in USD, or switch to a local market to pay in KES (Kenya), TZS (Tanzania), or NGN (Nigeria). You're settled in the currency you choose at checkout.
Production databases, minus the ops
Managed Databases are launching soon. Talk to us to reserve early access and pricing in your local currency, with no card to start.
Launching soon · 99.99% uptime SLA · Local billing in KES, TZS & NGN