Founder profile
Founder and Chief Architect, NiGeNje
Systems Architect | Backend and Platform Engineer | Distributed Systems Researcher
Biography
George Ocharo Onchaba is a Kenyan software engineer, systems architect and technology founder. He is the founder and Chief Architect of NiGeNje, where he works on governance and control infrastructure for autonomous and distributed systems.
He has roughly eight years of software engineering experience across backend services, enterprise integrations, microservices, automation, cloud infrastructure and distributed application design. Most of that work has been in systems where correctness, integration boundaries and operational reliability mattered as much as delivery speed.
His work now spans architecture and research: formal constraints and invariant-based design, runtime governance, compiler and language work, and the engineering question that connects them — how a complex system can keep the properties it was built to preserve when conditions change.
Professional experience
The professional record is concentrated in Java and Spring Boot backend engineering, enterprise integration and distributed service architecture — the work that shaped the platform’s view of boundaries and failure.
Service implementation, API design and the operational care that keeps a backend dependable.
The primary professional language and framework for service development.
Connecting systems with different contracts, identities, data models and failure behaviour.
Service boundaries, partial failure and coordination across independently deployed components.
Interface design, versioning and the contract between a service and its consumers.
Asynchronous flows, message contracts and the ordering and delivery assumptions behind them.
Schema design, data modelling and the persistence constraints that shape a service.
Services designed for cloud environments, managed infrastructure and elastic deployment.
Containerised packaging and orchestration for deployable platform services.
Build and release pipelines, automation and reproducible delivery paths.
Runtime behaviour, observability and the practices that keep a system accountable in operation.
Capability groups
Grouped by the kind of work rather than by job title. Primary professional experience sits in the first three groups; the formal and research work is concentrated in the last two.
The professional base: services that have to integrate, persist and keep working.
Coordination across services, resources and execution boundaries.
The delivery and runtime environment the services actually live in.
The formal side: describing what a system must preserve before building it.
Turning a direction into specified, decomposed and reviewable work.
Technical portfolio
The distinction matters: not every language in a portfolio carries the same depth. Primary means sustained professional work. Additional means working familiarity from research, prototypes and supporting work.
Primary professional experience
Additional exposure
Working familiarity, not a claim of equal mastery. Research and prototype work is not presented as equivalent professional depth.
Engineering journey
A progression rather than a list of projects: practical backend engineering, then architecture, then research directions that converge in the platform.
Foundation
Started with practical software engineering: Java and Spring Boot services, enterprise application integration, REST APIs, messaging and databases in systems that had to work in operation.
Progression
Moved from individual services to system-level design: decomposition, service boundaries, distributed coordination, runtime behaviour and the reliability of the whole.
Research direction
A research direction exploring state evolution, rhythmic computing, infinite-state models and alternative computational representations.
Research direction
A direction asking how software can express and preserve its invariants under normal and degraded conditions, including compiler work that turns declared constraints into checkable artifacts.
Research direction
A direction concerned with declared intent, architecture conformance, identity, authority, evidence and drift.
Integrated platform
Brings the threads together as an integrated platform: intent and authority governance, invariant preservation, controlled execution, safe degradation, independent observation, reconciliation and evidence-based conformance.
NiZiNG, λ-Safe and Chinje are research and engineering directions within the platform effort. Not every concept described here is a production product.
Founder statement
I started with practical software engineering and became increasingly interested in a deeper systems problem: how can complex systems continue to operate, adapt and recover without losing the properties they are supposed to preserve?
NiGeNje is the result of that engineering journey. It brings together my work in backend systems, distributed infrastructure, computational models, formal constraints and runtime governance.
The ambition is to build infrastructure that makes autonomous and distributed execution more controlled, understandable and accountable.
George Ocharo OnchabaFounder and Chief Architect, NiGeNje
Verified links
Only destinations that have been verified are listed. Platform repositories are private and are not linked from this profile.
Work with NiGeNje
Technical discussions, design-partner evaluation and research collaboration begin the same way: a concrete problem, the evidence that would count and a bounded scope.
