01
Named relay
Every leg is run by a person we have verified — with a name, a face, a signed handover and a record that cannot be quietly edited after the fact.
Pilot corridor accepting partners
Every handover witnessed.
Every arrival anchored.
People cross borders on hope, phone credit and the goodwill of strangers. Malayit replaces that with a managed relay: named witnesses at every handover, timed check-ins on every leg, and a signed evidence bundle that follows the traveller all the way to the anchor.
Managed relayTimed check-insEvidence bundle on every legHuman escalation, always
Live record
Subject
T. Mokoena
Custody
Intact
- Corridor
- SADC Northbound · 01
- Leg
- 03 of 09 · Transit
- Relay
- L. Ndlovu · verified
- Last check-in
- 08:42 · on time
Next check-in
T-00:42:18
Miss the window by 30 minutes and the escalation ladder starts — automatically, then humanly.
Built for travellers, families and the people who receive them at the other end.
The relay
A journey is only as strong as its weakest handover.
Malayit breaks the corridor into legs. Each leg has a named operator, a defined evidence requirement and a check-in window. Select a stage to see exactly who is accountable and what happens when it fails.
Chain status
Custody intact · leg 01 of 06
Stage
Verified intake
Duty
Identity, route intent and next of kin are captured in person, with consent and two witnesses.
Evidence required
Identity record · signed consent · route plan
Check-in window
Check-in every 6 hours
If this stage fails
Intake is refused. No leg begins without a complete record.
01 / 06
The problem
The journey is managed by nobody.
Corridors do not fail because people are careless. They fail because nobody holds the chain. Trust is asked for at the start, and then assumed all the way to the end.
Failure 01
Invisible handovers
Between the person who says "I can help" and the person who actually takes the next leg, there is almost always a gap. Nobody is named. Nobody is photographed. Nobody is accountable when it goes wrong.
Failure 02
Silent gaps
A phone goes unanswered at 23:00 and the family finds out three days later. Without timed check-ins, silence is only noticed after it has already become a story somebody else is telling.
Failure 03
Unanchored arrivals
Reaching a destination city is not arrival. Without documents, housing, work and a named person who receives you, the journey simply continues under a different name.
The cost
“We paid, we prayed, and we waited by the phone. Nobody could tell us which part of the road she was on.”
Composite of intake interviews · name withheld
The approach
We replace hope with a chain of custody.
Malayit is not a tracking app and not a transport company. It is the accountability layer that sits underneath a journey — who had custody, when, where, and what proves it.
02
Timed check-ins
Each leg carries a check-in window. Miss one and escalation begins: repeat contact, then the witness tree, then the named human on call.
03
Evidence bundle
Photos, timestamps, locations, messages and signatures assembled into one record that travels with the traveller from intake to anchor.
04
Anchor
Arrival is confirmed by the person who receives them. The record closes with a signature and a follow-up at day 7 and day 30 — not a rumour.
How it works
Five stages. One record. No gaps.
The process is deliberately unglamorous. Accountability is mostly a matter of doing the same boring thing every single time.
01
Intake
Duration: 40–90 minutes · In person
A traveller is registered through a trusted community operator, or directly over WhatsApp. Identity, route intent and next of kin are captured with informed consent.
02
Route build
Output: signed route plan
The corridor is broken into legs. Each leg gets a named relay operator, a check-in window, an ETA band and a defined evidence requirement.
03
Relay execution
Evidence: continuous
Handovers happen in person, photographed and signed by both parties. Between handovers, timed check-ins and position pings keep the chain alive.
04
Exception handling
Grace period: 30 minutes
A missed check-in triggers escalation: repeat contact, then the witness tree, then the named human on call. Nothing waits for office hours.
05
Anchor & close
Closure: countersigned
The receiving anchor confirms arrival in person and signs the evidence bundle. Follow-up runs at day 7 and day 30 before the case is closed.
AccountabilityAccountability is not a feature.
Accountability is not a feature.
It is the product.
Every stage names a person, not a department. Every obligation has an artefact attached to it. Every failure has a defined next action that does not depend on someone noticing.
Standing rule
No relay operator takes a second leg until the first is signed off. No anchor signs until they have seen the person. No case closes on a phone call alone.
Stage
Accountable
Evidence required
On failure
Origin
Intake officer
Identity record, signed consent, next of kin
Intake refused — no leg begins
Handover
Outgoing + incoming relay
Handover photo, two signatures, timestamp
Transfer void; custody reverts
Transit
Leg relay operator
Position pings, check-in log, ETA band
Escalation ladder after 30 minutes
Threshold
Standby escalation contact
Pre-brief record, outcome note
Auto-activation within 10 minutes
Arrival
Destination anchor
Arrival photo, anchor signature, location
Missing-person protocol; family notified
Anchor
Case owner
Handover pack, referrals, 7 & 30 day notes
Case stays open; owner remains assigned
Duty stack · reviewed at every handover · immutable once signed
The evidence bundle
Proof that travels with the person.
Not a dashboard. Not a report generated at the end. A single accumulating record that is written as the journey happens — and that belongs to the traveller and their family.
The bundle is exportable by the subject and their next of kin at any time. It is never sold, never used to train a model, and never shared with a third party without written consent.
malayit://bundle/ev-01
VERIFIEDEV-01 · Evidence bundle
Subject identity & consent
Captured at intake · countersigned by two witnesses
SUBJECT ............ T. Mokoena (redacted on public record)
IDENTITY ........... National ID — inspected in person
CONSENT ............ Signed · informed · withdrawable
NEXT OF KIN ........ Recorded · reachable · notified per leg
RISK PROFILE ....... Medium — medical note attached
CAPTURED ........... 2026-08-11 · 09:24 SAST
Recorded as it happens · signed at each stage
1 of 6
Who it servesThree people hold a journey together.
Three people hold a journey together.
All three deserve proof.
For the traveller
You stop being invisible.
Someone always knows which leg you are on. Your name, your face and your signature are attached to every person who moves you. If anything goes wrong, the record already exists.
- A named person on every leg
- Your own copy of the evidence bundle
- Escalation that does not wait for you to ask
For the family
You stop waiting by the phone.
Status updates arrive on a schedule you agreed to, not when someone remembers. Silence becomes a visible, escalated event within thirty minutes — not three days.
- Timed updates in your own language
- Immediate notification on any missed window
- Access to the same record the operators use
For the anchor
You receive a person, not a problem.
You know who is arriving, when, in what state, and what they need in the first forty-eight hours. Your confirmation is what closes the chain — and it is recorded.
- Arrival brief before they reach you
- Documents and referrals already assembled
- Your signature is the closing act
Pilot corridor
One corridor, done properly.
We are not launching everywhere. We are proving one route end to end — with real operators, real travellers and a record that survives scrutiny.
Corridor 01
SADC Northbound
Community partners at origin and anchor. Relay operators verified in person. Every leg carries a full evidence requirement from day one.
PHASE 00
CompleteDiscovery
Community mapping, operator interviews and risk modelling along the corridor. What actually happens, not what we assumed happens.
PHASE 01
In progressRelay recruitment
Verifying the first cohort of relay operators — identity, references, route knowledge and a signed duty stack before any leg is assigned.
PHASE 02
NextPilot cohort
The first accompanied journeys with a complete evidence bundle end to end. Small enough to watch every record personally.
PHASE 03
PlannedEvidence review
Independent review of the bundles with community and legal partners. What held, what broke, and what the record actually proves.
PHASE 04
PlannedCorridor 02
Replication on a second corridor with the same duty stack, the same evidence standard and the same named accountability.
Progress
DiscoveryCorridor 02
The interface layerNobody installs anything.
Nobody installs anything.
It runs on WhatsApp.
The most reliable interface on the continent is already in every pocket. Malayit operates through it — because a system that requires a new app, a new login and a new habit is a system that gets abandoned at the worst possible moment.
Works on any phone
Feature phone compatible. No smartphone required for core check-ins.
Own language
Status, instructions and escalation in the language the traveller actually thinks in.
Zero learning curve
If you can reply to a message, you can run a leg of the corridor.
Evidence by default
Every message is part of the bundle. Nothing has to be remembered later.
Malayit Relay
L. Ndlovu · online
Morning, Thabo. Leg 3 starts at 08:30. I’m Lindiwe, your relay to Polokwane. Reply YES when you see this.
07:52
YES
07:54
Check-in 04 of 27 · 08:42 · position shared
Border queue is long. New window 15:00–16:30. Your family has been updated automatically.
12:18
Window revised · family notified · 2 witnesses
ok
12:20
Message Malayit Relay
Illustrative thread · not a real journey
Design principle
The best system is the one a person can still use at 2am, in the rain, on 2% battery, in a language that is not English.
The trust engineSystems notice what
Systems notice what
people cannot.
A single missed check-in proves nothing. A pattern across nine legs proves a great deal. Malayit watches the record for the shapes that a tired family member and a busy operator will both miss at three in the morning.
Non-negotiable
The system raises. A person decides. No automated judgement is ever passed on a traveller, a relay operator or a family, and no model output is ever used to deny someone a leg. Human accountability is not delegable to software — that is the whole point.
Check-in drift
A pattern of check-ins that are each individually late by a few minutes — invisible to a human, obvious in sequence.
Route deviation
Position pings that leave the planned corridor band, or an ETA window that quietly stretches on every leg.
Language shift
Changes in who is sending messages, in what language, and in what register — the first thing to move when control changes hands.
Duplicate identity
The same contact details, device or phrasing appearing across supposedly independent journeys.
Payment irregularity
Requests for funds that fall outside the agreed schedule, or instructions to pay someone not named on the route plan.
Anchor mismatch
An arrival confirmation that does not match the named anchor, or that arrives without a matching arrival record.
Assistive, never autonomousExplainable flags, not scoresNo training on subject dataEvery flag auditable
Product visionBuild the boring part first.
Build the boring part first.
It is the hard part.
Most of the value here is not clever. It is consistency — the same record, the same standard, the same named accountability, every single time.
The relay core
Intake, route building, named handovers, timed check-ins and the evidence bundle. The unglamorous middle that everything else depends on.
- Intake & consent capture
- Leg scheduling & duty stack
- Check-in ledger
- Evidence bundle export
The witness tree
Community operators, families and anchors on the same record — with visibility calibrated to role, and escalation that reaches a human automatically.
- Family status layer
- Anchor arrival briefs
- Operator verification
- Multi-language escalation
The corridor network
Cross-operator accountability across corridors. A record that holds when the journey involves three organisations, two countries and a decade of history.
- Inter-operator custody transfer
- Portable subject record
- Independent audit portal
- Corridor risk intelligence
Why this existsMovement is not the problem.
Movement is not the problem.
Unaccountable movement is.
People have always moved. They will keep moving — for work, for family, for safety, for a reason that is theirs. What has not kept pace is the infrastructure that makes a journey legible to the people who depend on its outcome.
Most journeys across this region are coordinated in chat threads, phone calls and word of mouth. The record exists — scattered across four phones, three languages and a dozen memories that disagree with each other.
When something goes wrong, the first thing anyone asks is: who had custody at the time? On almost every corridor, the honest answer is that nobody can say. Not because people are lying, but because nobody ever wrote it down.
Malayit is an attempt to make that record a normal part of the journey rather than an afterthought assembled during a crisis. It is deliberately slow, deliberately boring, and deliberately biased toward evidence over assurance.
We think of it the way you would think of a chain of custody for anything else that matters: medicine, money, evidence. If it is worth moving a person across a border, it is worth knowing exactly who had them at every point along the way.
Working principles
- Evidence over assurance
- A signed record beats a sincere promise. Every time.
- Named, never collective
- Accountability belongs to a person. Departments cannot sign.
- Slow on purpose
- Speed is how gaps get introduced. We would rather be late and legible.
- The subject owns the record
- The bundle belongs to the traveller and their family, not to us.
- Never punitive by automation
- Software raises flags. People make judgements.
A note on numbers
This page makes no statistical claims. Where we later cite figures about migration, risk or corridor volumes, the source will sit beside them. Unattributed numbers cost a trust product more than they earn.
About
Malayit is a Linfytech project.
We build products that make invisible processes visible. This one started with a simple question that nobody in our industry seemed to be asking: who is accountable for a person between the moment they leave and the moment they arrive?
Malayit — the relay — is named for the thing it manages: the passing of something precious from one pair of hands to the next. A relay only works if every handover is clean. Lose one and the whole race is over, no matter how good the other runners were.
We are building this in the open, with community operators and the people who actually make these journeys, because the alternative is to design a system from a spreadsheet and hope it survives contact with a border post.
Built in South AfricaCommunity-informedOpen to pilot partnersDocumented, not assumed
We did not set out to build an app. We set out to make a promise hold — and then to write down, every single time, who made it.
L
The Malayit team
Linfytech · Johannesburg, South Africa
01
Corridors mapped
02
Relay operators verified
03
Bundles closed & audited
Founder’s note
The question that would not
leave me alone.
I have spent enough time around logistics, systems and people moving through difficult circumstances to know the difference between a process that works and a process that merely survives being written down. Most of what fails in this space fails in the gap between two responsible people, each of whom assumed the other had it covered.
Malayit is my attempt to close that gap — not with more technology than the problem requires, but with a record that makes it structurally impossible to hand off without being seen. It is slower than people would like. It is meant to be.
If you work with communities on a corridor, run an operator network, fund this space, or have made a journey like this yourself — I would like to hear from you. The design is only as good as the people who correct it.
Linfytech · Johannesburg, South Africa · 30 September 2026
QuestionsStraight answers,
Straight answers,
no soft edges.
If something here is not clear, that is a defect in the design, not in the reader.
No. We do not own vehicles, employ drivers or sell tickets. Malayit is the accountability layer underneath a journey — the record of who had custody at each stage and what proves it. Transport is arranged with verified local operators on the corridor.
No. Legs are run by verified relay operators who work the corridor already and know it well. What changes is that their role is named, documented, witnessed and signed — instead of informal and unrecorded.
A tracking app tells you where a phone is. Malayit tells you who is responsible for a person, what evidence exists at each handover, what happens when a check-in is missed, and who confirms that the journey actually ended safely. Location is one input, not the product.
The bundle belongs to the traveller and their next of kin. It is exportable on request, never sold, never used to train a model, and never shared with a third party without written consent. Retention periods are stated at intake in plain language.
Yes. Core check-ins run over SMS or USSD where data is unavailable, and WhatsApp where it is. A smartphone improves the evidence quality but is not a requirement for the chain to hold.
Send a short note describing your role — community organisation, operator, family advocate, funder or potential anchor — and we will reply with the pilot scope and what partnership involves. We keep cohorts deliberately small.
That depends on the corridor and who is funding it. Our commitment is that cost is never a barrier for an individual traveller on a corridor where a partner is covering the cohort. Pricing conversations happen with institutions and operators, not with people mid-journey.
Get involvedThe corridor is open.
The corridor is open.
Help us hold it.
We are looking for community organisations, verified relay operators, destination anchors, legal and funding partners, and people who have made these journeys themselves. Small pilot. Serious record. No theatre.
Typical reply within two working days · Johannesburg, South Africa
What a briefing covers
- 01
The duty stack
Who is accountable at each stage, and what artefact proves it.
- 02
Escalation design
What actually happens in the first thirty minutes after silence.
- 03
Evidence standards
What goes into the bundle, who owns it, and how it is exported.
- 04
Pilot terms
Cohort size, corridor scope, review process and exit criteria.