← Back to use cases

Open-source contributors blocked by region-based GitHub rules

Maintainers reach repos and CI from regions where commercial sanctions block direct access.

Open-source projects rarely live cleanly inside national borders. A maintainer in a sanctioned region can find that GitHub blocks repository access, that Gitter and Discord communities are unreachable, that CI tooling refuses tokens issued from local IPs. The project is technically still open; the door to participate is closed.

QPOL offers narrow, lawful access for legitimate technical work. Route just the project-relevant hostnames — github.com, registry.npmjs.org, pypi.org, the project's own services — through a chosen node. Leave personal traffic native. The contributor can review pull requests, run CI on their fork, push commits, all without sending unrelated traffic through a tunnel.

Voucher-based identity matters here. The contributor isn't creating a profile linked to their real-world identity through the VPN; they're holding a bearer code. Their relationship with the project is whatever it is at the project level (GitHub identity, project-specific account); QPOL is just network plumbing.

This use case sits right at the edge of what's possible without violating actual law. We're not lawyers. The contributor must judge whether their participation is legally sound. The tool just makes the network layer not be the blocker — the rest is human judgment.