Can you imagine a future where food delivery isn’t controlled by single profit-driven platforms,
but powered
by an ecosystem composed of community-owned platforms? In this ecosystem, workers gain agency,
data become
auditable and tools built by one can be shared to everyone within the ecosystem.
This is not just a shift in technology—it’s a transformation in who gets to build and benefit
from the
future of work.
Be part of the decentralized revolution. Join the growing number
of communities.
Open Courier is building a new kind of food delivery ecosystem to counter the key problems
nowadays:
unfair power dynamics between the platform and the workers, lack of transparency with algorithms
that make decisions behind closed doors and infrastructural designs that don’t reflect workers'
values or community needs . We envision a decentralized ecosystem of community-owned food
delivery
platforms that:
Let couriers choose where to work based on their preferences and values.
Increase interoperability, so anyone can audit the ecosystem.
Support open-source developments, so tools made by one can benefit everyone in the
ecosystem.
Protocol
The Open Courier protocol defines three core layers of communication within the ecosystem:
between the mobile app and instances, between instances and service requesters, and the
governance of the instance registry.
Read more about the protocol here 📄
Source Code
We have a reference implementation of the protocol in a multiplatform mobile
app with
backend
endpoints and an admin dashboard for
instance-level management.
This enables organizations within the ecosystem to customize how the system operates—for
example, instance operators can tailor delivery matching or compensation models to better
reflect community needs.
We are committed to continue the development of this open-source codebase and invite others to
contribute. Areas for collaboration include:
Enhancing the granularity and flexibility of the worker preference-input endpoints.
Expanding features that support community information exchange via the community-notes.
Building tools for analyzing and auditing at both the instance and ecosystem levels.
Exploring risks and refining governance models for the instance registry.