DAO-managed operational infrastructure

Consider migrating our Ops stack from admin-dependent 3rd party services to tools that are...
1. **Autonomous**. Resilient to external interference (not reliant on closed-source corporate software)
2. **Decentralized**. Resilient to internal malfeasance (not reliant on trusted admins)

| | SaaS | 1. Self-Hosted (autonomous) | 2. Peer-to-Peer (decentralized) |
|-|-|-|-|
| *Code* | Github | [Gitlab](https://scotch.io/tutorials/how-to-setup-gitlab-a-self-hosted-github)? | [Radicle](https://radicle.xyz/)? |
| *Email & Calendar* | Zoho | | [Fleek Space Daemon](https://fleek.co/space-daemon/)? |
| *Chat* | Keybase | [Element](https://element.io/)? | [Fleek Space Daemon](https://fleek.co/space-daemon/)? |
| *Calls* | Jitsi | Jitsi Self-Hosted | [Livepeer](https://livepeer.org/)? |
| *Website* | Netlify | | [Fleek Hosting](https://fleek.co/hosting/)? |
| *Database* | Airtable | | Fleek Database (coming soon) |

Start with the SaaS, self-hosted, and peer-to-peer comparison in the issue, then review the linked GitLab, Radicle, Fleek, Element, Jitsi, and Livepeer resources. Clarify which operational services are in scope and compare the listed alternatives against autonomy and decentralization. Done means an agreed migration plan with selected tools and documented next steps.

Written by the indexing model from the issue text.