OpenParcelBox is an open ecosystem for smart parcel delivery infrastructure, retrofit parcel boxes, open locks and self-hosted access control.
The project is in the early planning and specification phase. No production hardware, firmware or security guarantees exist yet.
OpenParcelBox explores how existing parcel boxes, cabinets, lockers, garage boxes and other containers can be upgraded into smart parcel drop-off stations without locking users into one carrier, one cloud or one proprietary controller.
The ecosystem is intended to support:
- local-first device operation
- optional self-hosted bridge
- optional hosted cloud service
- optional integrations such as MQTT, Home Assistant, HomeMatic, Matter, webhooks and LoRa/LoRaWAN
- open lock modules and lock profiles
- retrofit paths for existing parcel boxes
- dynamic carrier access concepts inspired by CEN/TS 17457:2020
- The device must keep its basic local function without internet, cloud or Home Assistant.
- Cloud services are optional convenience services, not platform requirements.
- Home Assistant and HomeMatic are optional integrations, not prerequisites.
- Carrier integrations are optional plugins, not platform dependencies.
- Delivery access and pickup access must be separate rights.
- Hardware should use documented ports, profiles and adapters instead of hidden proprietary assumptions.
- Prototype hardware must not include mains voltage on the board. Use certified external power supplies.
OpenParcelBox is not a single finished product. It is planned as a set of open building blocks:
- OpenParcelBox Core: hardware/backplane concept for power, ports, sensors, locks and expansion
- OpenParcelBox Device: local controller firmware and standalone behavior
- OpenParcelLock: open lock module and lock interface profile
- OpenParcelBox Bridge: optional self-hosted server for users, events, notifications and integrations
- OpenParcelBox Cloud: optional hosted bridge for people who do not want to self-host
- OpenParcelBox Retrofit: migration paths for existing parcel boxes and cabinets
- OpenParcelBox Profiles: documented profiles for locks, readers, sensors and controllers
- OpenParcelBox Plugins: integrations for tracking, carriers, smart home systems and notifications
OpenParcelBox should use CEN/TS 17457:2020 as an important reference for interoperable digital opening and closing systems for parcel receptacles.
The standard is not copied into this repository. Project work should refer to it legally and summarize requirements in original project language.
See:
- Standards baseline
- Opening rights
- Privacy-preserving audit events
- Keyring and delegated key model
- Remote command security
- Carrier adapter interface
- Wiegand ACCESS-Port profile
- M1 ready-made hardware module matrix
OpenParcelBox welcomes community input while keeping clear responsibility for security, official releases, project identity and local-first principles.
English is the primary technical project language for code, APIs, specifications and architecture decisions. The community is intentionally bilingual: English and German are both welcome in issues and discussions.
See:
- Contributing
- Developer Certificate of Origin
- Governance
- Security policy
- Language policy
- GitHub Discussions structure
- Development hub (draft)
- Project principles
- License overview
- Trademark policy
- Brand usage
Early project work focuses on:
The first concrete roadmap target is a standalone ESP-based retrofit kit for existing DHL parcel boxes.
V1 should prove the local-first retrofit idea on real hardware:
- keep the existing parcel box useful
- replace or adapt the closed lock/control layer
- support keypad, NFC and prepared fingerprint access where feasible
- run locally without cloud, bridge, Home Assistant or internet
- use a stable low-voltage supply design, with solar support to be explored
- support 4 households with up to 2 people each
- support up to 6 carrier/service-provider PINs
- provide local logging, local web management, MQTT, local API foundation and OTA in the beta target
- keep household/group capability in the data model from the beginning
- start with ready-made low-voltage modules before deriving a later reference board
See:
Supporting project work continues around:
- CEN/TS 17457:2020 research
- access-control model and opening rights
- keyring, delegated keys and scoped integration keys
- secure remote command authorization
- OpenParcelLock concept
- Wiegand and access-module profiles
- security and privacy requirements
- carrier access and dynamic code concepts
- specs: ecosystem, planning, documentation and roadmap
- openparcellock: open lock module and interface profile
- .github: organization profile and community health files
The canonical project domain is:
The website is planned to be GitHub-based, using GitHub Pages.
This repository currently contains planning material. It is not yet an implementation repository for production-ready hardware or firmware.
Use issues and discussions for ideas, research, architecture decisions and early specification work.