Hivemapper primary-source snapshot

Last reviewed: 2026-04-27 UTC

Project status snapshot

Official site: https://www.hivemapper.com/
Docs root: https://docs.hivemapper.com/
Governance process: Hivemapper Foundation + Map Improvement Proposals (MIPs)
No canonical standalone whitepaper or litepaper was surfaced in the official docs during this pass.

URL: https://www.hivemapper.com/
Key takeaways:
- Hivemapper positions itself as a decentralized network of people, cameras, and apps mapping the world in real time.
- The public site highlights HONEY as the economic engine and frames Bee Maps and Beekeeper as practical commercial outputs of the network.
- This makes it clear the project is not only about contributor hardware rewards; it is also trying to sell recurring enterprise map-data products.

URL: https://docs.hivemapper.com/welcome/introduction
Key takeaways:
- The docs describe a market problem around expensive, stale, and concentrated global mapmaking.
- Hivemapper argues that everyday driving can be turned into a decentralized map-refresh network, with AI and contributors jointly maintaining the map.
- The introduction is unusually strong at explaining why the project exists and why the team thinks a decentralized mapping network is economically viable.

URL: https://docs.hivemapper.com/use-map-data/hivemapper-app-developers
Key takeaways:
- The docs enumerate real developer-facing products: Beekeeper, Street Level Image APIs, Scout, Static Map Features API, Dynamic Map Features API, HD Maps, and AI Driver Events.
- The listed target industries include autonomous vehicles, commercial fleets, logistics, ridesharing, real estate, travel, government, and utilities.
- This strongly supports cataloging Hivemapper as geospatial data infrastructure rather than as a niche contributor app.

URL: https://docs.hivemapper.com/welcome/network-governance
Key takeaways:
- The Hivemapper Foundation is presented as the organized body responsible for network proliferation, token economics, and management of open technologies.
- Governance changes run through Map Improvement Proposals (MIPs), which are published, discussed with the community, and then finalized, modified, or abandoned.
- The docs explicitly separate Foundation responsibilities from Bee Maps / Hivemapper Inc. operations, which is useful when mapping the steward/company versus network distinction.

URL: https://docs.hivemapper.com/cameras/open-camera
Key takeaways:
- Hivemapper documents an Open Camera specification covering hardware, firmware, and API software.
- The docs list compliant devices and explicitly invite third-party manufacturers to build compatible devices if they meet the specification.
- This is a key clue that Hivemapper wants to behave like an open network with hardware standards, not just like a proprietary dashcam vendor.

URL: https://docs.hivemapper.com/honey-token/what-is-honey
Key takeaways:
- HONEY is used to coordinate contributor rewards and map-data consumption.
- The docs describe a maximum 10 billion token supply and a burn-and-mint mechanism in which map consumers burn tokens while a capped portion is reissued as consumption rewards.
- This makes the project legible as a tokenized data marketplace with explicit supply-side and demand-side mechanics.

No canonical Hivemapper whitepaper or litepaper was found in the accessible docs during this pass.
The docs themselves, plus MIPs, appear to be the authoritative written source of truth.
For current behavior and economics, the governance pages and token pages are more useful than trying to locate a missing single PDF.

Best current category for the library: decentralized geospatial data infrastructure / mapping network / DePIN.
The key categorization insight is that Hivemapper is much better understood as map-data and geospatial-control-plane infrastructure than as “drive to earn.”
The strongest clues are the explicit enterprise product catalog, the foundation/MIP governance structure, the open hardware specification, and the burn-and-mint map-data economy.