Skip to content

Impact

MoaV is built on a practical theory of change: censorship becomes harder to enforce when access capacity is distributed across many small operators, many protocols, and many fallback paths.

The project does not depend on one perfect transport. It makes it easier to keep adding routes.

The problem

When governments block the internet, people lose access to news, family, organizers, emergency information, and the outside world. Existing circumvention tools help, but many are centralized, protocol-specific, or difficult for ordinary supporters to operate.

Censors exploit that fragility. They block known VPN protocols, domains, app stores, payment routes, and large infrastructure providers. A tool that works today can fail during the next crisis.

The intervention

MoaV gives trusted operators a repeatable way to deploy multi-protocol access nodes. The project combines:

  • setup automation
  • transport diversity
  • per-user bundles
  • operator documentation
  • safety guidance
  • monitoring and health checks
  • bandwidth donation paths

This turns spare servers and community support into usable circumvention capacity.

Expected outcomes

MoaV aims to produce:

  • more independent access nodes before censorship events
  • faster deployment when demand spikes
  • more fallback routes when one protocol is blocked
  • better operator safety and documentation
  • reusable open-source infrastructure for the wider internet-freedom ecosystem

What success looks like

Success is measurable. Useful metrics include:

  • number of deployed nodes
  • number of supported protocols
  • time from fresh server to working node
  • setup success rate
  • number of user bundles generated
  • number of operators onboarded
  • protocol availability under blocking conditions
  • security issues found and fixed
  • documentation and localization coverage
  • reuse by other open-source projects

Not every metric should be public. Live node inventory, active-user counts, and sensitive operational details can create risk. Public reporting should focus on aggregate progress and reusable outputs.

Why open source matters

Open source is not just a value statement here. It is part of the safety model.

Public code lets operators inspect what they run, lets researchers audit the implementation, and lets other projects reuse the parts that work. Grant money and volunteer time should compound into public infrastructure, not a closed service.

Where MoaV fits

MoaV sits between end-user VPN apps and low-level protocol research. It packages protocols, operational practice, and deployment automation into something a trusted operator can run.

That makes it useful to:

  • internet-freedom funders
  • open-source infrastructure maintainers
  • diaspora support networks
  • censorship measurement projects
  • protocol developers who need real deployment paths