Henaho LabsProduct studioSite v2.0 · 2026

Built with taste. Shipped with speed.

We build our own products and yours. Ours include a life sim of everyday Nigeria, a Mac screen recorder that keeps your recordings as plain files, and a marketplace built around protected payments.

See the work How we work

ScrollBuild · Accelerate · AdviseNo analytics · No ad trackers

Henaho LabsWho we are

Engineers make every call and review every change.

AI tooling takes the repetitive work, so our hours go where judgement matters: the product, the details, the trade-offs.

Ways to work with us: Build, Accelerate, Advise: 03
Attempts per ticket, then a person reads why: 05
Merge queue, one branch at a time: 01
Analytics or ad trackers on this site: 00

Chapter 01Yaba, Lagos · 6.51° N 3.37° EIn development

Gbege

Everyday Nigeria, as a game. Including the part where NEPA takes the light.

You hustle, struggle, win and celebrate, and it is fun even when life is hard. Even when NEPA takes the light.

No public build yet.

Inside Gbege

Fig. 01.1Power cut, played out. Cut the power and see.

Light is on. For now.

Turn on JavaScript to cut the power.

NEPA: On
Gen: Standby
Fuel: 100%

Fig. 01.2The system

One set of rules, in two places.

The server decides what happens. The rules live in one Rust crate that both the server and the game compile, so they never disagree about them.

Gbege · Rust authoritative server · shared sim crate

Chapter 02macOS · Built with TauriPre-release

Nzuko

Record the screen. Keep the files. Search what was said.

Record your screen and camera on your Mac, get a transcript, and keep every recording as plain files on your own disk.

No download yet. The Mac app is waiting on an Apple Developer ID.

Inside Nzuko

Fig. 02.1A recording, start to file. Simulated: no camera or microphone is used.

TranscriptOn this Mac

Press Record. What is said appears here, transcribed on the Mac.

00:00
Morning, everyone.
00:01
Quick update from me.
00:03
The export fix is done, and library search is in review.
00:06
Captions next.

00:08Interactive with JavaScript

Preview · simulated, no camera or mic

MoviesNzukoStandup

Name	Kind	Size
video.mp4	MPEG-4 movie	6.4 MB
captions.vtt	WebVTT captions	1 KB
transcript.json	JSON	3 KB
metadata.json	JSON	1 KB
thumbnail.jpg	JPEG image	84 KB

Fig. 02.2The system

Your disk is the database.

Capture, transcription and storage all happen on the Mac. A recording only leaves it when you share, and then it goes to a bucket in your own account.

Nzuko · Captur SDK · on-device GGUF transcription

Chapter 03Lagos & Abuja · Phones and gadgetsPre-launch

Held

Jiji shows you the listing. Held is being built to protect the deal.

Held is building protected payments through a licensed escrow partner. Not live yet.

Not live yet. Launch waits on a licensed escrow partner.

Inside Held

Fig. 03.1One deal, step by step. A demo: no real money moves.

PreviewNot live yetA demo: no real money moves

Buyer

9:41

HeldBuying · #0417

iPhone 13 · 128 GBUsed · Pickup in Yaba

You pay₦185,000

Pay by: Bank transfer
Protected by: Licensed escrow partner
Released: When you share your code

Fund ₦185,000

Protected

With the escrow partner until handover. Meet the seller to collect.

Your handover code••••

Share it at pickup, once you have checked the phone.

Released

The seller entered your code. The deal is complete.

Paid
Protected
Code shared
Released

Demo · Not live yet

Escrow partner · licensed

Ledger · append-onlykobo

EP-0417-01FUNDED+18,500,000
EP-0417-02RELEASED−18,500,000
No entries yet

Balance, derived018,500,00018,500,0000

Seller

9:41

HeldSelling · #0417

iPhone 13 · 128 GBUsed · Pickup in Yaba

You get₦185,000

Awaiting payment

You will see when the buyer's payment is protected.

Payment protected

₦185,000 is with the escrow partner. Hand over the phone, then enter the buyer's code.

Enter the buyer's code1234567890⌫

Paid ₦185,000

The code matched, so the money was released at once.

Paid
Protected
Code shared
Released

Demo · Not live yet

The buyer pays ₦185,000 for a used phone.

Pay. The buyer pays ₦185,000 for a used phone.

Held. The payment is protected with the escrow partner until handover. The seller can see it is there.

Handover code. At pickup, the buyer shares a code. The seller enters it.

Released. The code matches, and the seller is paid.

Fig. 03.2The system

Money moves only through the ledger.

Every naira is an append-only entry in kobo; balances are derived, never stored. Held is building protected payments through a licensed escrow partner. Not live yet.

Held · state machines · derived-balance ledger

Work with usBuild · Accelerate · Advise

We also build for other teams.

The same way we build our own products: small written slices, tests first, an engineer reviewing every change, and AI-assisted tooling for the repetitive parts.

Start a project See the services

Chapter 04 / The studioTicket → test → build → merge

How a change reaches main.

Taste you can't automate. Speed you can. We write the ticket and the failing test, review every change and own the merge; AI-assisted tooling takes the repetitive parts in between. It is more discipline than most teams run, and it is how we move fast without shipping a mess.

The eight rules

01
A ticket
An engineer writes what changes, which files it may touch and which tests prove it. Missing a fact? The work stops and we ask.
02
A failing test
The test is written first and must fail before it counts. Once merged it is frozen: later work cannot quietly rewrite it.
node --testFrozen on merge
```
✗ correct code releases at once
  expected: 'released'
  actual:   'funded'
✗ wrong code is refused
✗ third wrong code locks it

# pass 0  # fail 3
```
03
We build, AI-assisted
Our tools take the repetitive parts inside a time box: five attempts, five dollars, two hours. When it runs out, we stop and write down what blocked it.
Attempt 2 / 5$1.40 · 0:23
```
+ if (matches(code, deal.codeHash))
+   return release(deal, 'pickup_code');
- return deal;

✓ correct code releases at once
✓ wrong code is refused
✓ third wrong code locks it
```
04
One merge
An engineer reviews every change. One queue merges one branch at a time and refuses anything behind main. We check every screen by eye.
Merge queuemain
1. t-0409Merged
2. t-0412Premerge ✓ · merging
3. t-0415Waiting · rebase
4. t-0416Behind main · refused

NotesFrom the blog

Written down, as we go.

All notes

OverviewOctober 10, 20264 min read
How we ship fast without shipping a mess
How Henaho Labs ships fast with a small team. Written tickets, tests first, review on every change, and where AI tooling fits inside that discipline.
Deep diveOctober 10, 20265 min read
Tickets, frozen tests and loop budgets: our engineering discipline
One ticket from start to merge, and the engineering rules behind it. Tests first, frozen tests, time boxes, guards that must fail, review and one merge owner.
OverviewOctober 8, 20263 min read
Why Nzuko keeps your recordings as plain files
Nzuko saves every recording as ordinary files in a folder you can open. Why we built it that way, what is in the folder, and what it costs us.

ContactReplies from a person

Say hello.

Questions, ideas, a project, or want to hear when something ships?

hello@henaholabs.com

Start a projectTell us what you are building, in a short form.

Henaho Labs LLC30 N Gould St, Ste NSheridan, WY 82801, United States

Built with taste. Shipped with speed.Built with taste. Shipped with speed.

Who we are

Gbege

One set of rules, in two places.

Nzuko

Your disk is the database.

Held

Money moves only through the ledger.

We also build for other teams.

How a change reaches main.

A ticket

A failing test

We build, AI-assisted

One merge

Written down, as we go.

How we ship fast without shipping a mess

Tickets, frozen tests and loop budgets: our engineering discipline

Why Nzuko keeps your recordings as plain files

Say hello.

Built with taste. Shipped with speed.