The platform division.
Helix AI Cloud exists to take the parts of Helix Cloud Solutions' work that belong in a product rather than a project, and maintain them like products: versioned, documented, contract-bound, and honest about their own defects.
A division, not a separate company.
Helix Cloud Solutions is a Kenyan technology company working across cloud, data engineering, AI, cybersecurity and software development — mostly as engagements, for enterprises, financial institutions and public bodies.
Engagement work and product work fail in different ways. An engagement ends; a platform has to still be correct in three years, on somebody else's infrastructure, after the people who wrote it have moved on. Helix AI Cloud is where the second kind lives, so it can be held to the second standard.
Six things a platform of ours has to have.
Not aspirations. These are the things we check before calling something a platform rather than a deliverable.
A version number that means something
Wire protocols are versioned separately from products, and adjacent releases interoperate during an update window — because a fleet does not upgrade all at once and pretending otherwise breaks somebody's evening.
A published contract at every boundary
Where another team's system integrates with ours, the shape of the exchange is a document they can generate types from, digest-pinned so neither side can change it silently.
A defect register, in public where it matters
Every platform page on this site carries a section listing what the product does not do yet. An operator who finds a limitation themselves stops believing everything else they were told.
Verification by driving, not by reading
Most of the real defects in this work were invisible to inspection and obvious on execution — a privilege escalation, a query the database would not parse, an access-control layer that had never once run. Text review passed all of them.
Guards that a test can tell apart from their own absence
A protection nothing can distinguish from not having it gets deleted by the next person tidying up, correctly and with a green test suite. So we pin the guard structurally, not just behaviourally.
Data boundaries enforced by code
Where a subscriber's data may cross to their provider, the permission is a live condition inside the query, not a flag checked once and cached. Revocation should be a fact, not a promise.
Built in Nairobi, for operators here first.
The assumptions differ. Subscribers pay by mobile money. Many connections sit behind carrier-grade NAT, which changes what an ISP can even do for a customer. Support conversations happen on WhatsApp before they happen in a ticket queue. A platform designed for a market where none of that is true arrives needing modification before it can be used at all.
None of that makes the software regional. It makes the defaults right for the people we build with, and correct everywhere else.
Work with the division.
Whether you operate a network, sell connectivity, or just want to know what your own line is doing.