Table of Contents
Fetching ...

OpenCourier: an Open Protocol for Building a Decentralized Ecosystem of Community-owned Delivery Platforms

Yuhan Liu, Varun Nagaraj Rao, Sohyeon Hwang, Janet Vertesi, Andrés Monroy-Hernández

TL;DR

OpenCourier addresses the central challenges of the gig economy by proposing an open, interoperable protocol to decentralize delivery platform governance. It introduces a three-layer protocol architecture—Registry Layer, App-Instance Layer, and Instance-Requester Layer—together with a reference implementation to demonstrate practical interoperability. The contributions include standardized data formats, discovery mechanisms, courier preference inputs, community notes, and data-disclosure/auditing endpoints, all aimed at increasing worker agency and transparency. The work enables a landscape of community-owned, locally responsive delivery ecosystems with cross-platform portability and open-source collaboration.

Abstract

Although the platform gig economy has reshaped the landscape of work, its centralized operation by select actors has brought about challenges that impedes workers' well-being. We present the architecture and design of OpenCourier, an open protocol that defines communication patterns within a decentralized ecosystem of delivery platforms. Through this protocol, we aim to address three key challenges in the current economy: power imbalances between the platform and workers, information asymmetries caused by black-boxed algorithms and value misalignments in the infrastructure design process. With the OpenCourier protocol, we outline a blueprint for community-owned ecosystem of delivery platforms that centers worker agency, transparency, and bottom-up design.

OpenCourier: an Open Protocol for Building a Decentralized Ecosystem of Community-owned Delivery Platforms

TL;DR

OpenCourier addresses the central challenges of the gig economy by proposing an open, interoperable protocol to decentralize delivery platform governance. It introduces a three-layer protocol architecture—Registry Layer, App-Instance Layer, and Instance-Requester Layer—together with a reference implementation to demonstrate practical interoperability. The contributions include standardized data formats, discovery mechanisms, courier preference inputs, community notes, and data-disclosure/auditing endpoints, all aimed at increasing worker agency and transparency. The work enables a landscape of community-owned, locally responsive delivery ecosystems with cross-platform portability and open-source collaboration.

Abstract

Although the platform gig economy has reshaped the landscape of work, its centralized operation by select actors has brought about challenges that impedes workers' well-being. We present the architecture and design of OpenCourier, an open protocol that defines communication patterns within a decentralized ecosystem of delivery platforms. Through this protocol, we aim to address three key challenges in the current economy: power imbalances between the platform and workers, information asymmetries caused by black-boxed algorithms and value misalignments in the infrastructure design process. With the OpenCourier protocol, we outline a blueprint for community-owned ecosystem of delivery platforms that centers worker agency, transparency, and bottom-up design.

Paper Structure

This paper contains 23 sections, 4 figures, 5 tables.

Figures (4)

  • Figure 1: We show a conceptual overview of the architecture for the decentralized community-owned delivery network. Courier instances register with the system through the Registry layer, and courier mobile apps can discover available instances via the same protocol (see Section \ref{['section:registry']}). Couriers may use any app that implements the App-Instance layer to fulfill delivery tasks for the instances they are contracted with (see Section \ref{['section: app-instance']}). Instances manage delivery tasks and collect courier preferences through the App-Instance layer while interacting with service requesters via the Instance-Requester layer (see Section \ref{['section:instance-eco']}). This design enables flexible, decentralized coordination across the ecosystem.
  • Figure 2: Screenshots of the onboarding pages showing the hard-coded registry, and details of an instance.
  • Figure 3: Screenshots of mobile app, showing how the delivery workflow looks for a courier using it.
  • Figure 4: Screenshots of preference input interface in the mobile app client.