Infrastructure engineering for East Africa's operators, platforms and regulators See the work →
Infrastructure engineering · East Africa

We run the systems
East Africa depends on.

CloudSpinx engineers and operates the infrastructure behind internet providers, payment platforms, manufacturers and a national regulator. Kenyan, certified engineers, and we will tell you when the answer is not to spend the money.

14Organisations served
6Engagements published
7Years engineering
The roster

We engineer for the organisations others depend on

A good portion of our work is infrastructure for companies whose own product is infrastructure. When an ISP or a payments platform has a problem it cannot solve in house, this is the kind of thing it calls us about.

Telecoms, ISPs and cloud providers

  • Safaricom PLC
  • Angani
  • CATS-NET
  • LightSpeed Internet
  • Vilcom Networks

Financial platforms and payments

  • Cellulant
  • Mojaloop
  • Netpap Global

Enterprise, public sector and impact

  • Bakhresa Group
  • Competition Authority of Kenya
  • CortexCom
  • Food4Education
  • Tiko
  • Yassir
Sectors

Generic IT advice does not survive a plant floor

A regulated payment platform and a production line fail in different ways. We bring the sector's real constraints to the design, from PCI-DSS scope to what happens when the power goes.

See the work

Finance & Banking

Core banking integrations, PCI-DSS compliance, M-Pesa gateway management.

Retail & E-commerce

POS systems, WooCommerce, inventory sync and M-Pesa checkout.

Logistics & Transport

Fleet management systems, real-time tracking platforms and ERP.

Manufacturing

Production planning, stock control, Odoo MRP and machine monitoring.

Healthcare & NGOs

HIPAA-aware data management, donor reporting systems and secure comms.

Real Estate & PropTech

Property management platforms, lease automation and client portals.

Why CloudSpinx

Consultants who actually run the systems

Most of this market splits into two: global firms that sell a methodology and fly juniors in, and local shops that resell hardware they cannot engineer. We sit in neither camp. Our engineers design the platform, build it, and are still on the pager the night it matters.

Certified across AWS, Azure, GCP, Kubernetes, Red Hat and Cisco
Architecture, runbooks and credentials handed over at every close
SLA-backed response times, not best-effort promises
About the practice
01

The engineer who scoped it does the work

No partner sells the deal and hands it to juniors. You meet the person who will be on the console, and they stay on it.

02

We build on what we can hand back

Upstream open source, the major clouds, and standards. No proprietary layer that only we can operate, because lock-in is a charge, not a feature.

03

We say when not to spend

The honest answer is sometimes a smaller project, your existing team, or nothing at all. We would rather lose the line item than the client.

04

Kenyan hours, Kenyan engineers

On site same day in Nairobi, next day in Mombasa and Kisumu, delivering across East Africa and remotely past it. You are not calling a queue in another timezone.

05

You own the documentation

Architecture diagrams, runbooks and credentials handed over in your own vault. Every engagement ends with you able to operate without us.

06

Security and compliance from the design

Hardening, MFA, audit logging and Kenya Data Protection Act scope built in at design time, not retrofitted when an auditor asks.

Make the case

Global integrator, local reseller, or us

Those are usually the three names on a shortlist in Kenya. Here is where each genuinely wins, including the columns where we do not.

Global Integrator Deep bench, distant Local Reseller Close, but sells boxes CloudSpinx Engineers, in Kenya Recommended
Who does the work Partner sells, juniors deliver Whoever is free that week The engineer who scoped it
Engineering vs reselling Deep, vendor-aligned Resells, cannot engineer We build and run it ourselves
Vendor independence Tied to alliance partners Sells what it distributes Open source and any major cloud
On the ground Regional office, flown in Local In Kenya, same day on site
Time to start Weeks of process Immediate Scoping call within days
Will they talk you out of it Scope grows Sells the bigger box We say when not to spend
What you own at the end Their methodology Rarely documented Diagrams, runbooks, credentials
How it works

From first call to handover

01

Scoping call

Thirty minutes with the engineer who would run the work. Bring the problem and what it costs you when it breaks, not a spec.

02

Assessment

We look at what you actually have. Undocumented estates and untested backups surface here, before they become a surprise in month two.

03

Written proposal

Scope, explicit out-of-scope, deliverables, acceptance criteria, milestones and the named engineers. Nothing is billed before you sign it.

04

Build and hand over

We deliver, then hand you architecture diagrams, runbooks and credentials in your own vault. Ongoing operation is a separate choice, never assumed.

Let's talk

Tell us what is actually breaking

Thirty minutes with the engineer who would run the work. You get an honest read on what you have, what it would take to fix, and whether we are the right people to do it.

Free, and commits you to nothing · You speak to an engineer

Monthly, no filler

Infrastructure notes from Kenya

Platform shifts, licensing changes and security incidents worth your attention across East African infrastructure.

WhatsApp