Managed Databases — hosted in Nairobi
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 residency for Kenya's Data Protection Act — 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 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.
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%
- 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 063Sales
[email protected]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.
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.
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