Boardroom primary-source snapshot

Last reviewed: 2026-04-27 UTC

Project status snapshot

URLs:
- https://boardroom.io/
- https://docs.boardroom.info/docs.md
Key takeaways:
- The marketing homepage is unusually sparse, so it is not a sufficient source of truth by itself
- The docs root frames Boardroom as a governance platform with multiple product surfaces rather than a single dashboard
- This is a good example of a project where the docs and repos reveal substantially more than the website hero copy

URL: https://docs.boardroom.info/docs/boardroom-api/boardroom-api
Key takeaways:
- Boardroom says the Governance API exposes much of the data powering the Boardroom Dashboard
- The docs claim support for governance data across 175+ DAOs, including DAOs, proposals, voters, votes, delegates, and delegations
- API access is key-based and aimed at developers building governance portals, profiles, and other governance-aware applications
- This is the strongest signal that Boardroom is not only an interface product but also a governance-data control plane

URLs:
- https://docs.boardroom.info/docs/sdk/governance-sdk
- https://raw.githubusercontent.com/boardroom-inc/gov-sdk/master/README.md
Key takeaways:
- The SDK is explicitly described as a portable, protocol-agnostic governance interoperability framework for NodeJS and the browser
- The repo architecture is organized around transports, adapters, and protocol registration functions, which is useful because it reveals the actual integration model underneath Boardroom’s higher-level products
- The stated design goal is normalized cross-protocol governance interaction rather than simple read-only analytics

URLs:
- https://docs.boardroom.info/docs/protocols
- https://docs.boardroom.info/docs.md?ask=What%20does%20Boardroom%20say%20about%20its%20API%2C%20SDK%2C%20protocol%20coverage%2C%20and%20developer%20integrations%3F
Key takeaways:
- Boardroom documents a supported-DAOs surface tied to both the API and SDK
- The docs and ask output point to framework support for Aave Governance v2, Compound Governor Alpha/Bravo, Moloch, Nouns, OpenZeppelin Governor, Snapshot, Uniswap V2, and related adapters
- This confirms Boardroom is best understood as governance interoperability infrastructure, not merely DAO media or analytics

URL: https://raw.githubusercontent.com/boardroom-inc/protocol-Info/master/README.md
Key takeaways:
- Boardroom keeps a public repository for project information served to the governance portal
- The repo explicitly supports public additions and edits, which matters because it shows Boardroom blending governance-data infrastructure with open metadata maintenance workflows
- This public metadata layer is a useful categorization clue: Boardroom operates like a governance index plus integration registry, not just a frontend

URL: https://github.com/boardroom-inc
Key takeaways:
- The org page describes Boardroom as a protocol-agnostic governance aggregator
- Public repos include the Governance SDK, protocol-information repo, dashboard documentation, and bot-related repos, which corroborates the multi-surface product model
- The repo activity and structure are more informative than the sparse homepage, though some docs appear older or partially broken

No canonical Boardroom whitepaper or litepaper surfaced in this pass.
The clearest current source of truth is the docs plus the Governance API and Governance SDK materials, supported by the public metadata repositories.
Some docs pages contain broken references; this should be treated as an operational note, not a disqualifier.

Best current category for the library: governance intelligence platform / DAO governance aggregation / governance interoperability infrastructure.
The most important insight is that Boardroom’s real value is the normalized governance integration layer underneath the dashboard.
Boardroom is a strong example of a docs-and-repo-first crypto-adjacent firm where the public integration architecture matters more than the marketing surface.