Founded 2017

Software engineering for
the work your organisation depends on.

We work with teams on custom software, integrations, and product delivery. From Nairobi, we help organisations replace manual work, connect the systems they already use, and maintain the software that supports their operations.

A software partner for
work that matters.

Statum was founded in 2017 to give Kenyan businesses access to thoughtful software engineering without the distance and complexity that can come with a large consultancy.

Why the company exists

Many teams have a process that does not fit an off-the-shelf product, but do not need a large consulting programme either. We work in that space: understand the process, design a sensible solution, and stay involved long enough for the software to be useful.

What we bring

We are a Kenyan team that understands the practical details of local operations, including payment integrations, connectivity, business reporting, and data handling. We focus on clear ownership, maintainable code, and documentation that remains useful after launch.

Our aim is not to use the most fashionable tool. It is to make sound decisions, communicate them clearly, and leave each client with a system their team can understand and build on.

Illustration of a software engineering workflow
2017
Founded in Nairobi
Nairobi
Kenyan engineering team
Clear
Ownership agreed up front
Direct
Communication with the team

Our Engineering
Philosophy

We treat software as part of the organisation's working knowledge. It should solve a real problem today, remain understandable tomorrow, and be possible for another developer to maintain. That principle informs how we choose the architecture and where we spend time.

We avoid unnecessary complexity. A modular monolith may be the right answer for one project; separate services may make sense for another. The decision follows the product, the team, and the constraints rather than a fixed formula.

Maintainable architecture

We separate responsibilities clearly and choose a structure the client team can work with.

Security in the design

We discuss access, validation, data handling, backups, and release checks as part of the build.

// A maintainable system
class EnterpriseSystem {
public function buildSystem() {
// 1. Clear responsibilities
// 2. Strict type safety and error handling
// 3. Performance-first database indexing
return "Documented and maintainable";
}
}

Responsible delivery
and data handling

Security and privacy are part of the project conversation. The exact controls depend on the data, users, integrations, and obligations involved.

Security planning

We identify the information that matters, who should access it, how it moves through the system, and what needs to be checked before release.

Kenyan data requirements

Where a project handles personal data, we consider collection, access, retention, hosting, and any transfer requirements under the applicable Kenyan rules.

International requirements

If a project involves users in other jurisdictions, we document the relevant requirements and involve the client's legal or compliance advisers where specialist advice is needed.

Enterprise Systems

Custom ERPs, CRMs, customer portals, and inventory systems tailored to your unique business workflows.

  • • Custom Workflows
  • • Role-Based Access
  • • Audit Trails

Mobile Apps

Field data collection tools, customer apps, and fintech solutions built natively or cross-platform for iOS & Android.

  • • Offline-First Mode
  • • Native Performance
  • • Biometric Security

API & Integrations

Connecting internal software with payment gateways, banking APIs, ERP systems, and cloud middleware.

  • • High-Throughput REST/gRPC
  • • Cloud Middleware
  • • Enterprise SAP / Oracle Sync

AI & Automation

Adding practical AI features such as document search, summaries, assisted support, and workflow automation where they are useful.

  • • Document search and summaries
  • • Assisted workflows
  • • Data handling agreed early

A considered
technology stack

We use a small set of familiar tools and select others when the project calls for them. The important thing is that the choices are documented, supportable, and appropriate for the people who will run the system.

Backend

  • Java (Spring Boot)
  • PHP (Laravel)
  • Node.js (NestJS)

Frontend

  • Vue.js / Nuxt
  • React / Next.js
  • Tailwind CSS

Mobile

  • Flutter (Dart)
  • React Native
  • Native iOS / Android

Database

  • PostgreSQL
  • MySQL
  • Oracle Database

AI & Vector

  • Models
  • Proprietary APIs (GPT, Claude)
  • Open-Weights (Llama, DeepSeek)
  • Storage
  • Vector (pgvector, Pinecone)
  • Optimization
  • Semantic Caching (Redis)
Statum Tech Stack
Working with Statum

How we work with clients

We work remotely and meet clients in Nairobi by appointment. Each engagement starts by clarifying the problem, the people involved, the existing systems, and what a successful first release should include.

Clear responsibilities

We agree who makes decisions, who reviews the work, and what is included in the handover.

Practical risk review

We discuss integrations, access, data, hosting, and rollout risks before they become surprises.

Regular communication

Reviews and written decisions keep the project understandable to both technical and business stakeholders.

A useful handover

We provide the agreed source code, access, documentation, and support arrangements at the end of the work.

Have a project in mind?
Let us talk it through.

Tell us what you are trying to improve, build, or connect. We will help you work out the next sensible step.