Metagov

• Name: Metagov
• URL: https://metagov.org/
• Category: governance middleware / cross-platform action gateway
• Summary: Metagov is governance middleware, not a governor. The useful part is the gateway layer: plugins decide which outside systems a community can listen to, call into, and wrap in asynchronous governance flows. Good architecture note for cases where practical authority sits in integration coverage and plugin scope before any vote or policy script runs.
• What it does:
  • Provides an API gateway and Django backend between a governance driver and outside services
  • Uses plugins to expose third-party actions, event listeners, and asynchronous governance processes through one common interface
  • Routes webhook and event data from external platforms into community-specific governance logic
  • Lets each community choose and configure its own plugin set, so integration scope becomes part of the governance surface
  • Supports both Django-native drivers and HTTP-based drivers instead of forcing one application model
  • Served as the integration layer for PolicyKit, with the public README later noting that most Gateway development was folded into PolicyKit by mid-2024
• Key claims:
  • The docs define Metagov as a unified API gateway for digital governance services. That is the right frame for the note.
  • The core split is driver versus gateway: the driver decides policy, while Metagov decides how outside services are represented and invoked.
  • The plugin model is the mechanism that matters. Actions, listeners, and process flows determine what a community can actually govern across external platforms.
  • Community configuration matters because the same governance driver inherits a different power surface depending on which plugins are enabled.
  • The project now reads more as lineage and architecture than as a live standalone product. Keep it because the layer split is still clean.
• Whitepaper: No canonical standalone whitepaper surfaced in this pass. The strongest primary materials were the official site, official docs, and the official gateway repository plus design/plugin documentation; see ../whitepapers/metagov-primary-sources-2026-05-09.md.
• Sources:
  • https://metagov.org/
  • https://docs.metagov.org/
  • https://raw.githubusercontent.com/metagov/gateway/master/README.md
  • https://raw.githubusercontent.com/metagov/gateway/master/docs/design.rst
  • https://raw.githubusercontent.com/metagov/gateway/master/docs/plugin_tutorial.rst
  • https://raw.githubusercontent.com/policykit/policykit/master/README.md

Internal linkages

• Closest product-layer counterpart: policykit.
• Stronger voting-layer contrast: snapshot.

Control surface

• The leverage sits in plugin coverage, plugin configuration, webhook and credential access, and the process wrappers that decide which outside actions can be delayed, escalated, or routed through governance at all.

• Read it as the integration gateway beneath governance apps, not as a governance venue in its own right.

• Last reviewed: 2026-06-09 UTC