Moodle plagiarism checker integration.

Moodle OSS + Noplag OSS = full institutional data sovereignty.

The reason Moodle dominates EU public-sector higher education (and the reason Canvas doesn't) is that institutions can run the entire LMS inside their own data centre — no traffic to a US cloud, no FERPA/Schrems II contortions, no licence renegotiation when the vendor changes pricing. Noplag matches that posture from the other direction: the engine is Apache 2.0 and the plugin is GPL v3, both runnable inside your institutional VPC. Pair them and the stack from student submission → plagiarism check → grade passback stays entirely on your infrastructure. The detection engine reads from a public-corpus snapshot you update on your schedule (typically monthly OpenAlex + CORE + arXiv refresh); no other outbound connections required. For institutions with strict data-residency requirements — German Länder universities, French grandes écoles, Italian state-funded research institutions, UK NHS-affiliated teaching hospitals, EU H2020 research-data clauses — this is the deployment shape that passes the data-protection officer's review without lengthy negotiation. The institutional IT team can read both codebases line by line, run them in a staging environment for the standard 90-day acceptance test, and approve based on what the code actually does rather than what a vendor's marketing claims. Closed-source plagiarism tools cannot match this because their integration code AND their detection algorithm are both opaque to the institution running them — review becomes a trust exercise rather than a verification exercise.