Aragon Platform
The Aragon platform is a vertically integrated, full-stack solution for governing treasuries and protocols on EVM-compatible blockchains. The application builds on Aragon OSx, with shared product concepts, rules, and design principles that keep its features consistent, coherent, and scalable.
Protocol mechanics (the DAO contract, permissions, the plugin framework, and the governance plugins) are documented in the protocol docs; the pages here link to them for the mechanism and add the product meaning on top.
Three-layer model: protocol mechanism → product capability → interaction pattern. Aragon OSx supplies the contracts and execution rules; the platform organizes those capabilities into accounts, governance processes, and actions; interaction patterns make them understandable and usable. These layers have distinct concepts, with a direct correspondence where it helps.
Use Aragon
Ask product questions, explore what Aragon can do, or submit feedback through Aragon Assistant.
For custom development, deployment of an existing capability through Aragon, or paid governance advisory and workshops, see Getting help.
Guides help people accomplish concrete tasks in the Aragon platform. Start by choosing a voting-power mechanism for token governance, choosing between a Safe and an Aragon multisig, adding a multisig gate to an advanced governance process, or hardening token governance against governance attacks.
Understand the platform
Read Aragon OSx and the platform for how the app relates to the contracts behind accounts, governance, and permissions. Its protocol reference routes deeper questions to specific topics, with GitHub links for sharing.
Start with the value proposition for what the platform enables, then the concepts the rest of the graph hangs off: the account, what the deployed entity is and why the product says "account" where the protocol says "DAO"; the governance process, body, and member, the central relationships behind the governance surface; and scoped authority, how the account's effective authority is divided among governance processes. From there, follow the area your question touches.
Browse by area
- Accounts — account entities, creation, upgrades, selected-account views, and linked-account relationships.
- Governance — the platform's governance semantics: processes, bodies, members, proposals, the governance designer, and staged governance patterns like multisig gates.
- Treasury — what the account holds and how the app shows it: the account as vault, assets, transactions, and reward distributions.
- Application — global discovery, wallets and participant identity, address input and display, action preparation, transaction submission, shared collection behavior, support, and curation.
- Access control — how decisions become authorized calls and how people inspect that configuration: the authorization and execution model, concrete OSx authorization paths, the Permission Viewer, and scoped authority, layered over the protocol's permission system.
For capabilities deployed through an arrangement with the team, see Aragon-deployed plugins. Reward recipients can use Capital Distributor to inspect and claim their allocations.
Last updated on