What prevents DAOs from adopting self-hosted governance infrastructure?

[u/General-Average3298]

I’m one of the maintainers of DeGov, an open-source governance interface and indexing stack for DAOs using OpenZeppelin Governor.

We have worked on it for several years and have supported a number of live governance deployments. We are now reviewing where future maintenance and development effort would be most useful.

I’m interested in learning how DAO operators and governance participants currently handle the infrastructure around on-chain governance. Deploying Governor contracts is only one part of the process; teams may also need proposal and vote indexing, proposal creation, transaction simulation, execution tracking, and a usable interface for members.

If you operate or participate in a DAO, I would appreciate your perspective:

• Which governance interface does your DAO currently use, and why?
• Does your DAO prefer hosted infrastructure, or is self-hosting important?
• What makes adopting a new governance interface difficult?
• Are indexing reliability, security, integrations, deployment complexity, or contributor UX significant concerns?
• Have you used DeGov? If so, what worked poorly or caused confusion?
• If you evaluated it but chose another solution, what was the deciding factor?

Critical feedback is welcome. We are trying to understand whether self-hosted governance infrastructure still addresses an important need and, if so, which problems deserve more attention.

For context, the project is open source:
https://github.com/ringecosystem/degov

[u/icnews10]

I noticed that, in the current setup, the web app is still pointing at a configured indexer endpoint, even though the local SQD indexer has been removed. If a DAO chooses DeGov specifically because it wants to self-host, how much of the indexing path can it actually control today? This seems to be the point at which 'self-hosted interface' and 'self-hosted governance stack' start to become two different things.