"Banlu: 100 miles. You save gas, you save time, and another job comes your way home. That's a winner."
Relay logistics platform · Prototype testing & validation
We meet you
in the
middle.
Banlu is a logistics platform for long-distance freight. Two drivers share one route and transfer the load at a designated midpoint. Built first for healthcare equipment: hospital beds, oxygen, mobility and diagnostic gear, with the same model applied to general B2B freight.
Working prototype · functional testing underway
Demo route · New York → Boston
Illustrative
Single driver
~430 mi
One driver runs the full corridor
and returns empty
and returns empty
Relay model
~100 mi
Each driver covers one leg
and stays near home base
and stays near home base
Illustrative comparison · distances modeled, not measured operating data
"You save gas, you save time, and another job comes your way home. That's a winner." Long-haul courier driver, New England routes · driver research interview
What Banlu moves
Any load.
Any corridor.
One midpoint.
Banlu isn't designed for small parcels. It's designed for loads that are too large, too critical, or too complex for traditional last-mile services, with a recorded handoff at every transfer.
Hospital Beds
Electric, bariatric, pediatric
Oxygen Tanks
Portable and large-scale O₂
Wheelchairs
Power, manual, transport
Medical Supplies
Diapers, dressings, PPE
Diagnostic Equipment
Monitors, ultrasound units
Medication
Rx, IV fluids, cold-chain
Podiatric Supplies
Pedicure care, wound kits
IV Equipment
Poles, pumps, fluid bags
Corridors
One corridor in test.
Designed to scale.
Banlu is designed to support a scalable driver network. Testing is deliberately narrow: a single corridor, a small number of drivers, and a real midpoint, enough to prove the relay before widening it. The model applies wherever two drivers work opposite ends of the same lane.
Corridor under test · Boston ↔ New York
Corridor examples
| Route | Midpoint | Miles | Status |
|---|---|---|---|
|
New York, NY
Boston, MA
|
Hartford, CT | ~215 mi | In testing |
|
Chicago, IL
Indianapolis, IN
|
Not in test | ~180 mi | Illustrative |
|
Los Angeles, CA
Phoenix, AZ
|
Not in test | ~370 mi | Illustrative |
|
Dallas, TX
Houston, TX
|
Not in test | ~245 mi | Illustrative |
|
Atlanta, GA
Charlotte, NC
|
Not in test | ~250 mi | Illustrative |
Rows marked illustrative show the shape of the model, not active service.
The Banlu method
Post once.
We handle the rest.
From posting to delivery, Banlu coordinates both drivers, the transfer at the midpoint, and the record of custody along the way.
-
Post your delivery
Enter your pickup, destination, load type, and delivery window. Banlu proposes a suitable midpoint along the route.
-
Two drivers matched
Banlu coordinates compatible delivery opportunities based on route, timing, and availability. Both drivers confirm before anything moves.
-
Midpoint handoff
The Transfer Hub guides drivers through a verified delivery handoff and records the completion of the transfer.
-
Delivered and confirmed
The receiving facility confirms delivery. The delivery record is available in your dashboard, and both drivers can be rated.
Platform capabilities
Built around the handoff.
Trust & compliance
A recorded handoff, not a handshake.
The Transfer Hub guides both drivers through a verified handoff and records its completion, so the moment custody changes hands is documented rather than assumed. Compliance requirements are assessed per engagement.
✓
Equipment verified at pickup
14:02:31
✓
Driver A identity confirmed
14:03:14
✓
Driver B identity confirmed
14:18:55
→
Transfer photo logged
Pending
Real-time tracking
Live GPS for both drivers simultaneously.
Follow both drivers and the state of the delivery from one dashboard, with status updates as the load moves through each leg.
Driver network
Verification built into the journey.
Banlu incorporates verification steps designed to support accountability throughout the delivery journey.
Return routing
Drivers earn on the way home.
After finishing a leg, drivers can be shown work heading back toward where they started, so the midpoint becomes a place to pick work up, not only to drop it off.
Secure messaging
Coordination without sharing numbers.
Direct in-app messaging between the sender and both drivers, tied to the delivery it belongs to.
B2B billing
Built for org accounts, not individuals.
Designed for organization accounts rather than individuals: per-delivery billing, multi-seat access, and delivery history for procurement and logistics teams.
What Banlu is testing
Banlu is testing whether its relay model can reduce delivery mileage,
improve driver economics, and
increase delivery visibility. Those outcomes are the subject of testing, not yet a claim.
1
End-to-end relay completed
August 2026
Prototype test result
August 2026
Prototype test result
Research
Shaped by driver research.
The relay model came out of conversations with the people who would have to drive it. The quote below is from a long-haul courier driver interviewed during discovery.
Interactive prototype · public demo
Click through the relay.
A selection of screens from a working build connected to a live backend, covering both the sender and driver journeys. Figures shown are illustrative demo values. The remaining screens and the operational flows behind them are walked through live rather than published.
Built, not published · operational flows shown live
Business model
Per-delivery pricing,
currently in validation.
Banlu is designed to bill per delivery rather than per mile, so costs stay predictable for procurement teams. Rates are being validated against real corridor testing and are quoted per engagement.
Pilot
In validation
single corridor · limited volume
- Delivery tracking dashboard
- Recorded transfer at handoff
- In-app messaging
- Driver rating
Target model
Organization
Per delivery
multi-seat org accounts
- Everything in Pilot
- Multi-seat access
- All load categories
- Delivery history and records
Enterprise
Custom
volume terms
- Everything in Organization
- Compliance requirements assessed per engagement
- Integration discussions
- Named point of contact
Prototype testing
Past static design.
Into real testing.
Where it stands
A working mobile prototype with connected backend functionality.
Banlu has progressed beyond static design into functional prototype testing. Early testing has been used to evaluate the end-to-end delivery workflow, identify technical issues, and refine the product experience.
✓
Interactive design prototype
Complete
✓
Functional build, connected backend
Complete
✓
End-to-end relay test
Aug 2026
→
Corridor validation with drivers
In progress
Case study · August 2026
Boston to Brooklyn, handed off in Connecticut.
An end-to-end relay test was completed in August 2026: a load posted in Boston, claimed by two drivers, transferred at a midpoint in Connecticut, and confirmed through the Transfer Hub. Testing identified a technical issue that was not visible during the design review, providing an important opportunity to improve the product before further testing.
Current stage
Prototype testing and validation.
Banlu is currently in the prototype testing and validation stage. The product is being refined through functional testing, research, and iterative design.
What's next
Validate the model, then widen it.
Next steps include continued prototype testing, user feedback, workflow refinement, and validation of the operational model.
What's being validated
Does the relay hold up outside the demo?
Whether drivers on opposite ends of a corridor will reliably meet and transfer a load, whether the economics work for both of them, and whether senders trust a delivery that changes hands mid-route.
Want to see
the full demo?
The full prototype and deeper operational workflows are available on request. We're talking with courier operators, healthcare logistics teams, and prospective partners as testing continues.
Early-stage product · prototype testing and validation