Running a DAO is not one product but a stack: a set of specialised tools, mostly independent of each other, that a community assembles to make decisions, hold money, pay people, control who takes part and stay legible. There is no “DAO operating system” that does all of it – instead a typical DAO layers a voting venue over a treasury wallet, bolts on funding and payroll modules, and points analytics and legal wrappers at the result. This page maps that stack by function and links to the deep page for each tool, so you can see how the pieces fit before diving into any one of them.
Before any of it, there is the deliberation layer: the forum where a proposal is drafted, argued and often killed. Most DAOs run a self-hosted Discourse; Commonwealth is the crypto-native alternative, adding wallet login, token-gated topics and a two-way Snapshot integration – though it has since turned toward token launches, and the deliberation layer remains the least standardised part of the stack.
The layer that turns members into decisions. Snapshot is the near-universal off-chain venue – gasless, wallet-signed votes stored on IPFS – used for temperature checks and non-binding signaling. Tally (now Cactus) covers the on-chain side, providing the interface for OpenZeppelin Governor contracts where a passed vote executes a transaction directly. Agora is the other major on-chain interface, running binding votes for Optimism, Uniswap and ENS. Most large DAOs run both layers: cheap Snapshot signaling first, binding on-chain execution second.
A newer layer sits beside the ballot rather than under it: Futarchy Labs attaches paired conditional markets to each proposal and shows the predicted price impact next to the Snapshot vote, an advisory signal now running at Kleros, Velora and GnosisDAO. A related layer resolves subjective disputes a vote cannot settle – did the work ship, is this listing genuine – through decentralized arbitration such as Kleros, whose crowdsourced jurors return a binding ruling that a contract can act on. Snapshot has also opened its venue to AI agents: its MCP server can cast votes, create proposals and follow spaces on a user’s behalf. (Snapshot docs, Tally docs)
Deciding who is in the room before any vote is cast. Guild is the widely-used authorization layer: it turns an on-chain fact – hold this token or NFT, complete this action – into an off-chain permission, automatically granting and revoking Discord roles, Telegram access, and GitHub or Google permissions as wallets meet or fall out of a role's requirements. It is the plumbing behind most token-gated communities, including social DAOs like Friends With Benefits, and pairs with proof-of-personhood signals such as Human Passport to keep one person from entering as many. This layer governs access, not vote weight – it decides who may participate, while the voting and framework layers decide what that participation does.
The scaffolding that defines what a DAO is on-chain – its permissions, membership and upgrade rules. Aragon OSx models a DAO as a lean permission manager with swappable governance plugins. The Moloch framework – minimal, audited contracts whose defining feature is rage-quit – underpins a generation of grants DAOs and lives on today through DAOhaus. Colony adds reputation-weighted, task-based structure – influence is earned reputation that decays, not tokens held. Nouns Builder deploys the Nouns design – a recurring NFT auction funding a treasury governed one vote per token – for any community. Frameworks trade flexibility for safety: you inherit battle-tested contracts instead of writing your own. Hats Protocol narrows this layer to roles and permissions alone: revocable, non-transferable ERC-1155 "hats" arranged in an admin tree, read by tools like Safe and Snapshot to gate who may act (Hats Protocol). (Aragon docs, Moloch contracts)
Where the money actually sits. Safe (formerly Gnosis Safe) is the default: an m-of-n multisig smart-contract wallet that holds the treasury for most of the DAO world, extended by modules and guards – most commonly the Zodiac standard – so a passed Snapshot vote can execute against it without a trusted signer. Because Safe stayed deliberately minimal, a separate operations layer grew above it: Den adds no contracts at all and instead attacks the coordination bottleneck – reminder bots that tag signers who have not yet signed, decoded and simulated transactions, and gas reimbursed from the Safe. Custody is the highest-stakes layer – a treasury is a DAO’s most valuable and most attacked asset – which is why the ecosystem standardised hard on one well-audited account model. (Safe docs)
Getting money in and back out to the people doing the work. Juicebox is the programmable treasury/fundraising layer that powered ConstitutionDAO and thousands of crowdfunds. Gitcoin runs quadratic-funding rounds for public goods. Questbook hosts milestone-paid grant programmes, including Arbitrum DAO's and Compound's, in which an elected allocator approves grants inside a budget the DAO voted. Coordinape pioneered peer-allocated compensation – contributors reward each other’s work directly – though its app wound down in 2025.
Sablier streams vesting grants, salaries and unlocking airdrops second-by-second, so a payment is earned over time instead of handed over up front. Hedgey issues revocable vesting and lockup plans as NFTs, and lets the unvested tokens vote. Once the work is done, the invoice and the books are their own layer: Request Finance turns contributor and vendor claims into approved bills a multisig pays in a batch, then exports the result to ordinary accounting software. This layer is where governance meets payroll, and it is historically the least standardised part of the stack.
The instruments that make a DAO legible to its members and to outsiders. The single cross-DAO index has fragmented: DeepDAO was the canonical directory – treasury sizes, membership and voter turnout across thousands of DAOs – but it stopped updating in November 2025 and went dark through mid-2026, and what came back is a snapshot its own operator tells readers not to use, now fronted by a final sale of the dataset to academic researchers (read 16 September 2026). Its role is split across narrower tools.
Boardroom, acquired by Agora in 2025, still serves proposals and delegates across ecosystems as an API, though its public app now errors on every data route (checked 22 August 2026), and Messari Governor covers similar ground in a browser; Karma scores delegate participation; Token Terminal carries the financial half, standardizing fees, revenue and expenses so protocols can be compared on the same basis; and DAOstar works the layer beneath, standardizing how a DAO publishes its own data. The same Snapshot MCP server doubles as an analytics surface, since one of its tools runs any GraphQL query over the spaces, proposals, votes and voting power Snapshot records (Snapshot MCP README). Between them they answer “how healthy is this DAO?” – the metrics covered on DAO metrics and treasury management.
The off-chain shell that gives an on-chain organisation legal personhood and limited liability. MIDAO forms Marshall Islands DAO LLCs; Wyoming’s DAO LLC statute offers a US equivalent. Without a wrapper, members of an unincorporated DAO can face unlimited personal liability – a risk the legal-structures page covers in depth. This layer is optional but increasingly standard for any DAO holding real assets or signing contracts.
The right stack follows the DAO’s type and size. A small grants collective may need only a Safe plus Snapshot and a Moloch-style rage-quit. A large protocol DAO governing a live contract needs on-chain Governor execution (Tally/Cactus), a formal legal wrapper, and analytics for accountability. The rule of thumb: start minimal – a treasury and a way to vote – and add layers only when a concrete failure (a captured multisig, an unclear payout, a liability scare) demands one. Over-tooling an early DAO adds coordination cost without adding safety.
Choosing also means choosing what to depend on. Several tools once considered obvious picks in this stack no longer exist, and what a shutdown costs depends on whether the tool held a view of on-chain state or the only copy of the record: see DAO tooling discontinuity.
Caper collapses most of this stack into a single protocol. Custody, voting, execution and exit are not separate tools bolted together but one contract-governed flow: a proposal is voted and executed on-chain in one binding step, the treasury is a protocol-controlled vault rather than a separate Safe, and members can exit for their fair share of it, set by the same earned vote weight that governs their say rather than by balance alone, consuming both their governance tokens and the soulbound vote tokens they earned by voting. The trade-off is deliberate: a caper gives up the pick-your-own-tools flexibility of the assembled stack in exchange for having no seams – no multisig to capture, no off-chain vote to later ratify, no gap between deciding and doing. For teams that want the modular approach, the tools above remain the reference.