← → TO NAVIGATE · CLICK A BAR OR NODE
KUUMBAEngineering ledger · Feb – Sep 2026

Fifteen products.
Six months.
Two engineers.

What Kuumba designed, built and shipped between February and September 2026 — measured from the repositories themselves, and compared with what the same work usually takes.

The headline

What the repositories say

KUUMBA
0M
lines of code across the portfolio, counted on 8 September 2026
0
products and tools across six domains
0k
labelled images across two vision models trained in-house
0
engineers, working with AI coding agents
Where the 4.03 million lines sit · hover a segment
Portfolio map

How everything connects

Solid arrows: code, models or data flow into. Dashed: built on top of. Click a node to open its ledger entry.

FOUNDATION HEALTH INDUSTRIAL · AFST / AGF SAFETY HOSPITALITY SECURITY HARDWARE Operations platformboards · teams · docs · mail1,661,812 lines CliniqGP side + dental side1,557,150 linesAltron partnership Dental platform v1449,141 lines · 1,214 commits Dental vision models7 model families · 29 pathologies AFST operations toolcustom build in daily useautomation · email service · board rulessync engines · auth · deployment Kuumba Mail60,753 lines SAP Sync7,155 lines AGF Portal21,033 lines AGF Warehouse8,946 lines Advanced Detectionfire · smoke · PPE models81,832 training images HSEC AI29,945 lines · 66 endpoints AFS Demo Tooldesktop app4,962 lines The Archbooking + membership PWA86,158 lines · 47 tables Parquemember + staff platform · 13,817 lines NULL-veksransomware protection agent (Go + TS)99,520 lines · 81 endpoints Warehouse stock-take droneRFID inventory drone · Revision D PDR1,289 design files · 4 revisions8,997 lines of CAD code
IndustrialHealthSafetyHospitalitySecurityHardware
Timeline

What was built when

Grey bars started before February and were carried into the window. Most builds ran in parallel.

Sep 25 Dec 25 Feb 26 · window opens Apr 26 Jun 26 Aug 26 Dental vision modelssince 2025 · carried in Dental platform v1merged into Cliniq AFS Demo ToolJan – Feb Operations platform AFST operations tool NULL-veksbase built · Feb HSEC AI Advanced Detection AGF PortalJun → AGF Warehouse CliniqJul → The Arch · ParqueAug → Stock-take drone≈ 1 week of design output Kuumba Mail · SAP Synclate Aug →
Ledger · Industrial

AFST & AGF

Bar length is lines of code. Click a project to see what it contains and what a 25-person team would typically need.

0
Ledger · Health

Cliniq and the dental stack

Click a project to see what it contains and what a 25-person team would typically need.

0
Ledger · Safety, Hospitality, Security, Hardware

Six more builds

Click a project to see what it contains and what a 25-person team would typically need.

0
Up close · Advanced Detection

Fire detection on the cameras you already own

Most fire-detection products need specialised thermal cameras. Advanced Detection watches ordinary CCTV feeds and flags fire and smoke — every camera a site already has becomes a fire sensor.

12
public datasets merged and de-duplicated into two training sets
2
YOLO11 models trained on one workstation GPU
0.70 mAP50
fire model, first 50-epoch pass · 0.79 precision
≈ 2 months
from first download to deployed inference

Training images

Fire & smoke
44,892
PPE · 11 classes
36,940

Time to a first model

Kuumba
≈ 2 mo
Typical ML team
3 – 6 mo

An ML engineer plus annotators sourcing, cleaning and labelling ~80k images, then training and serving. Hardware-based detection adds thousands of rand per camera; this runs on the existing estate.

Up close · Warehouse stock-take drone

A drone designed to PDR in about a week

An indoor inventory drone that flies warehouse aisles reading RFID tags: protected 450 mm carbon X-frame, lidar and optical-flow navigation, compact mission shell, rear-loading battery cassette. Controlled mass 1,657 g against an 1,800 g limit. The design is code — the whole package regenerates from scripts.

4
revisions to build-intent PDR
3,554
solids in the validated assembly
29 + 17
part STEPs + printable STLs · 7 drawings · 8 renders
11
engineering documents · 170-row BOM

Design time to preliminary design review

Kuumba
≈ 1 week
Hardware team of 3–5
3 – 6 mo

Mechanical, electrical and systems engineers producing a design basis, CAD, drawings, BOM and validation — before anything is built.

Rendered view of the Revision D stock-take drone
Revision D product render — protected rotors, mission shell, top-mounted lidar.
Exploded systems render of the drone
Systems view — compute, flight controller, RFID reader and battery cassette.
Up close · Kuumba Mail + SAP Sync

A custom email client and an ERP sync engine in ten days

Two pieces of infrastructure companies almost always buy. Kuumba Mail is a complete mail platform — receiving, sending, threading, search, real-time sync — written from scratch. SAP Sync keeps the operations tool and SAP in step with mapping, reconciliation and an audit trail.

60,753
lines · Kuumba Mail · 96 test files
7,155
lines · SAP Sync · 20 test files
31
database migrations shipped with the mail platform
10
calendar days, both builds

Email client · time to first usable release

Kuumba
5 days
Team of 4–8
6 – 12 mo

Open-source mail clients have taken decades and hundreds of contributors to mature.

ERP connector · typical integration project

Kuumba
5 days
Integration consultants
3 – 6 mo
Up close · Cliniq

One platform, two clinics

Cliniq runs a practice's day with role-aware views for clinicians, reception and accounts. It inherits a year of dental research and the operations platform beneath the industrial tooling — which is why a two-month-old product already carries 1.56 million lines, 437 migrations and 779 test files.

1.56M
lines of code
29
dental pathology classes detected in-house
2 months
since the Cliniq repository began
2
partners secured: Altron, and South Africa's first AI data-centre company

General practice

  • Patients & practice diary
  • Visits, records, communication
  • Role-aware Home, Calendar, Patients
  • Reception and accounts workflows

Dental

  • Radiograph viewer with AI detection
  • Dental coding & imaging workflows
  • Intraoral camera integration
PathologyTeethPeriapicalBoneEnamelSinusSoft tissue

Practice platform · time to comparable breadth

Kuumba
14 mo
Open-source systems
10 – 20 yrs
Scale of the gap

What this output usually costs

Drag the sliders. Team-equivalent = lines ÷ (lines per developer-day × 220 days × team size).

Industry range for production software, including design, tests, review and rework: roughly 30 – 100.
years
Per project · months for that team
Scale of the gap

Against mature products in each category

KUUMBA
CategoryKuumba buildDelivered inMature comparison (public, approximate)
Email client / mail platformKuumba Mail5 active daysEstablished open-source mail clients: 20+ years, hundreds of contributors
Practice management / clinical recordsCliniq2 months + 1 yr dental R&DLeading open-source practice systems: 15–20+ years, hundreds of contributors
Fire & smoke detectionAdvanced Detection≈ 2 monthsCamera-based vendors: dedicated hardware per camera, multi-year product cycles
Warehouse inventory droneStock-take drone (Rev D PDR)≈ 1 week of designSpecialist inventory-drone companies: teams of 50–150, several years to a flying product
Ransomware protection for SMEsNULL-veksBase built, Feb 2026Backup-and-recovery vendors: thousands of staff, enterprise pricing
Booking & membershipThe Arch · Parque4 weeksCommercial studio-booking platforms: product teams in the hundreds
Distributor portal & warehouse fulfilmentAGF Portal · Warehouse3 months, part-timeModular ERP suites: 15+ years, thousands of contributors
SHEQ / complianceHSEC AI≈ 3 monthsEnterprise EHS platforms: companies of several hundred
Method

How the numbers were produced

KUUMBA

Counting

Every repository was scanned on 8 September 2026. Lines are non-blank lines of source. Dependencies, build output, lockfiles, generated files, datasets, model weights and vendored code are excluded. The operations platform and Cliniq include an adopted open-source foundation that Kuumba extended and adapted.

History

Commit counts and active days come from git history. Model metrics are from training-run logs. Drone figures come from the Revision D validation manifest. Timelines follow the dates the work started.

Team estimates

Per-project team estimates use 50 net lines per developer-day at the slider default, 22 working days a month, and the stated team size. Role lists describe the shape of a conventional team for that kind of product; they are indicative, not audited.

Boundaries

The drone package is marked not for flight or manufacture until engineering gates are closed. Vision-model metrics are first-pass results. Status labels reflect the state on the scan date.

KUUMBASecunda · South Africa

4 million lines.
Fifteen products.
Seven months.

Built by two engineers and a fleet of AI agents — and the pace is still rising.