A managed database inside the country that asked for one

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.

The service is in build and has not opened for orders. Rather than publish a date that moves, we tell the waitlist directly: send [email protected] the engine and region you are interested in and you will hear when the first release is ready, before it appears on the site.

Not yet — there is no orderable instance today. What you can do now is size the workload with us, get launch pricing in writing, and be in the first group given access when the service opens. Teams with a migration to plan get the most out of doing that early.

ke-1a in Nairobi, tz-1a in Dar es Salaam and ng-1a in Lagos — the three regions Lineserve runs today for cloud servers, VPS, dedicated hardware and object storage. You choose the region when you create the instance.

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 rather than a tiered feature list per engine.

The launch price list runs from $14.58 a month for Small (1 vCPU, 2 GB RAM, 20 GB SSD, 100 connections) through $29.16 for Medium and $58.32 for Large to $116.64 for XLarge (8 vCPU, 16 GB RAM, 200 GB NVMe, 1,000 connections). Prices exclude VAT, and the same plan carries a KES, TZS or NGN price list in the local markets.

No. Those figures are the launch price list, and nothing bills until the service opens. If your budget cycle needs a number sooner than the launch, ask [email protected] for it in writing against your account.

We run the engine — provisioning, backups, patching, monitoring and failover. You create an instance, take the connection string, and spend your time on the application instead of on the database's day two.

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 retained for 35 days, with point-in-time recovery to any second inside that window, plus manual snapshots whenever you want one.

Yes. An instance created in ke-1a, tz-1a or ng-1a is held in Nairobi, Dar es Salaam or Lagos and is not moved out of that 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 which you choose.

It supplies the location, which is the part a hosting provider can supply. The assessment, the records of processing and the sign-off stay with your own compliance function and advisers — they are a shorter piece of work when the data never left the country asking about it.

Read replicas are planned for the first release, up to five per primary with typically under a second of lag. Placing one in another country is a cross-border transfer of whatever personal data it holds, so treat it as a decision rather than a default — Tanzania in particular requires a permit from its Commission before personal data leaves.

Over private networking. Instances live inside your VPC with no public access by default, reached through security groups and database users, or from on-premises over a peered VPC or VPN.

It is yours and it comes out the way it went in — standard dumps and standard replication, in the engine's own format, with no proprietary layer in between. That is worth confirming before you commit to any managed database, this one included.

Yes, at no extra charge, and the planning is better done before launch than after. Send the engine, the current size, the acceptable downtime and where it runs today to [email protected].

Email [email protected] or use the contact form, with the engine, the rough size and the region you would use. No card, no commitment — it puts you in the first group given access and gets the launch pricing written against your account.