NYC / NEIGHBORHOOD LOGISTICS / BRONX

Vehicle-agnostic
neighborhood logistics

The right package. The right vehicle. The right neighborhood.

Miniature-style Bronx street at golden hour, with a VANL truck, three cargo vehicles and their riders, neighbors, storefronts and an elevated train.
BRONX / NEIGHBORHOOD LOGISTICS
Built to connect incoming freight with the people and vehicles working at street level. Concept illustration.
MOBILE HUBS → DELIVERY CELLS
THE VEHICLE IS SELECTED FOR THE WORK
Scroll to enter ↓
A different last mile / The VANL model

The warehouse.
At street level.

Bring incoming freight closer to the people waiting for it. VANL's model connects carrier injection, a mobile warehouse and neighborhood delivery cells—matching each parcel wave with the territory, vehicle and agent for the work.

Explore the mobile hub
01 / RECEIVE

Carrier injection

Receive incoming parcel volume at an agreed injection point.

02 / POSITION

TRK-001 mobile hub

Stage and reposition inventory close to neighborhood demand.

03 / DEPLOY

Neighborhood cells

Release defined waves to right-sized vehicles and local agents.

The warehouse doesn't have to wait for the neighborhood.
We bring the warehouse to it.

MOBILE INVENTORY
LOCAL EXECUTION
01 / City → Network

Every block
is a node.

Carrier freight enters where the city can accept it. VANL turns that injection point into a responsive neighborhood network—rather than routing every parcel through another distant warehouse.

Birdseye view of a neighborhood street with a VANL truck, a loading worker, and three cargo vehicles with riders labeled Cell 01, Cell 02 and Cell 03.
BRONX / NEIGHBORHOOD OPERATING MODELTRK-001 stages volume for Cells 01–03, illustrated here with cargo quads and their agents.
02 / Network → Mobile Hub

Inventory
in motion.

TRK-001 is VANL's first mobile hub: a moving warehouse built for the operating tempo of New York—receiving, staging, dispatching and repositioning parcel volume without asking the neighborhood to come to us.

Carrier freight → sort → mobile hub → cell release
Worker holding a parcel between a VANL truck and an enclosed cargo quad, beside a hand cart and packages, with a W 34 St sign in the background.
TRK-001 / TRUCK-TO-CELL LOADINGOne physical unit. A continuously recalculated position in the network.W 34 St, Manhattan / separate New York concept illustration of a loading transfer.
03 / Mobile Hub → Delivery Cells

Right-sized vehicles.
Exact work.

VANL divides neighborhood volume into delivery cells: localized operating units matched to a defined parcel wave, territory and vehicle. Each cell deploys, delivers, reloads and redeploys as the network moves.

Not every delivery needs a van. Not every street needs the same machine.

The cell is the operating unit. The vehicle is selected for the work.

REV X

Technical-style illustration of a REV X cargo tricycle, showing its rear cargo enclosure, extended frame, pedal drive and steering controls without a rider.
CELL 01 / ILLUSTRATIVE ASSIGNMENTCargo enclosure · pedal drive · steering and controls.

Cargo quad

Technical-style illustration of a VANL cargo quad, showing its rear cargo enclosure, curved rider canopy and front lighting without a rider.
CELL 08 / ILLUSTRATIVE ASSIGNMENTCargo enclosure · rider canopy · front lighting.

Reference-based vehicle studies / not to scale. Cell assignments vary with the work. Walking agents also form part of the vehicle-agnostic operating model.

04 / Delivery Cell → Agent POV

The next task.
Right in view.

A mounted phone brings the next stop and its check-in steps into view. The illustrated VANL workflow gives agents a clear way to confirm arrival, flag a location issue, or request support while stopped at the delivery point.

Mounted-phone workflow / demo

Confirm arrival.
Flag a location issue.
Request support.

Clear next steps at the point of work, with the agent in control.
Agent perspective from a cargo cycle on a New York neighborhood street, with a VANL mobile hub ahead and a handlebar-mounted phone showing a demo delivery-cell check-in workflow.
AGENT VIEW / NEIGHBORHOOD CHECK-INIllustrative phone-based demo workflow: confirm arrival, report a location issue, or request support.
05 / Agent → Intelligence

VANL OS
keeps time
with the city.

VANL OS is the operational layer behind the network. It connects parcel movement, vehicle telemetry, delivery cells, agent activity, exceptions and operating economics—turning physical movement into measurable intelligence.

ILLUSTRATIVE OPERATING WAVE / 17:20 → 18:05
  1. JFK carrier injection
  2. Whitestone Bridge
  3. Bronx mobile hub
  4. Neighborhood cell release
Illustrative VANL OS network map with lime route markings linking JFK, Queens, the Whitestone crossing and the Bronx on a graphite background.
JFK carrier injection → Whitestone Bridge → Bronx mobile hub → neighborhood delivery cells.Concept visuals and example figures. Cell 08 on this map is a distinct example from Cells 01–03 in the bird’s-eye view.
Injection received
138 parcels
TRK-001 staged
42 parcels
Cell 08 released
31 parcels
Cargo quad active
12 stops
Proof of handoff
86 complete
Exceptions
02 open

Separate operational measures within an illustrative snapshot; these values are not additive.

A NETWORK, NOT A DASHBOARD. EVERY MOVEMENT BECOMES INTELLIGENCE.

06 / Network → Neighborhood Hub

Your volume.
Our neighborhood operating model.

VANL is piloting a flexible last-mile model that connects carrier injection, mobile staging and multiple delivery vehicles. We’re looking for partners to help test the model against real routes, real parcel volume and measurable operating results.

Choose your role to explore how it connects to VANL.

01CarriersExtend injection, improve final-mile control, and serve dense neighborhoods with a more flexible operating model.
PARTNER WORKFLOW / ILLUSTRATIVE

Freight meets the neighborhood.

01020304
  1. Carrier injection
  2. TRK-001 staging
  3. Cell release
  4. Local handoff
Measures to connectInjection acceptanceRelease timingHandoff confirmation

Define injection windows, parcel profiles and the neighborhood territory.

Explore carriers partnership ↗
02MerchantsBring inventory, delivery, pickup, and returns closer to the customers already around you.
PARTNER WORKFLOW / ILLUSTRATIVE

Inventory closer to demand.

01020304
  1. Merchant inventory
  2. Neighborhood hub
  3. Customer order
  4. Delivery or pickup
Measures to connectInventory availabilityOrder readinessFulfillment status

Explore local inventory positioning, delivery windows, pickup and returns.

Explore merchants partnership ↗
03PropertyTurn buildings and portfolios into useful neighborhood touchpoints without sacrificing resident experience.
PARTNER WORKFLOW / ILLUSTRATIVE

A useful front door.

01020304
  1. Property access
  2. Neighborhood hub
  3. Resident service
  4. Pickup or return
Measures to connectAccess readinessParcel custodyCollection confirmation

Identify access rules, available space and the resident experience.

Explore property partnership ↗
04Vehicle Partners & OperatorsPut specialized vehicles and experienced local operators into a network that measures each platform against the work it actually performs.
PARTNER WORKFLOW / ILLUSTRATIVE

Match the machine to the work.

01020304
  1. Vehicle + operator
  2. Defined territory
  3. Assigned parcel wave
  4. Reload + redeploy
Measures to connectVehicle availabilityRoute completionOperating cost

Evaluate the platform, operator coverage and the territory it can serve.

Explore vehicle partners & operators partnership ↗
Explore a pilot with VANL ↗
06.1 / Define the pilot

Pilot with VANL.
Put the model to work.

Start with a real operating question. Together, we define a manageable scope, agree who does what, and measure the results before deciding what comes next.

01 / WHAT YOU BRINGSELECT A CONTRIBUTION ↓

Parcel volume

Define parcel profiles, injection windows and an agreed operating wave.

PARTNER INPUTMOBILE HUBDELIVERY CELLS
02 / WHAT WE DEFINE TOGETHER

Injection windows · delivery cells · handoff procedures · responsibilities

03 / WHAT WE MEASURE
Completion rate
Completed deliveries within the agreed scope.
Exceptions
Issues recorded, resolved and reviewed.
Time per stop
Time spent serving each delivery stop.
Cost per completed delivery
Agreed operating costs against completed work.

Illustrative pilot structure. Scope, availability, measures and commercial terms are agreed with each partner.

Start the conversation

Tell us where
you fit.

A brief introduction is enough to begin.

Opens an email draft to partners@vanl.pro. Nothing is sent until you send it from your email app.

How we handle inquiries ↗
07 / The operating surface expands

It starts with delivery.
It doesn't end there.

Explore each service through the neighborhood network.

DELIVERY MODEL / ILLUSTRATIVE

From the mobile hub to the doorstep.

A parcel wave moves through staging, cell release and agent-led delivery.

010203
  1. Mobile inventory
  2. Delivery cell
  3. Customer handoff
Workflow recordsParcel custodyRelease eventHandoff record
Discuss delivery with VANL ↗
PLANNED SERVICE EVOLUTION / ILLUSTRATIVE

A neighborhood collection point.

A local touchpoint holds a parcel for collection, with readiness and custody tracked through the workflow.

010203
  1. Incoming parcel
  2. Neighborhood hub
  3. Customer collection
Workflow recordsReady for collectionHolding locationCollection confirmation
Discuss pickup with VANL ↗
PLANNED SERVICE EVOLUTION / ILLUSTRATIVE

The same network, in reverse.

A return enters locally, is recorded and consolidated, then moves back into the appropriate carrier flow.

030201
  1. Customer return
  2. Local intake
  3. Carrier handback
Workflow recordsReturn intakeConsolidation statusCarrier handback
Discuss returns with VANL ↗
PLANNED SERVICE EVOLUTION / ILLUSTRATIVE

Stock within reach of the work.

A neighborhood hub can position inventory for a merchant or service team and release it against local needs.

010203
  1. Business inventory
  2. Local storage
  3. Replenishment
Workflow recordsStock positionStorage locationRelease request
Discuss business storage with VANL ↗
PLANNED SERVICE EVOLUTION / ILLUSTRATIVE

Local demand. Local fulfillment.

Local orders connect available merchant stock with pickup or neighborhood delivery.

010203
  1. Customer demand
  2. Merchant stock
  3. Local fulfillment
Workflow recordsOrder requestStock availabilityFulfillment record
Discuss local commerce with VANL ↗
08 / New York → Anywhere

Built in New York.
Designed to scale anywhere.

The city is the proving ground. The system is portable: mobile hubs, right-sized delivery cells, local intelligence and neighborhood infrastructure assembled around the needs of each market.

Build with VANL ↗