A native Moodle local plugin that surfaces TextSight's AI detection inside the Assignment grading workflow is in planning. Sentence-level highlights, an ESL-aware Authenticity Score, and a per-scan audit trail next to the rubric. Nothing is shipped yet. Join the waitlist and your demand signal moves it up the queue.
What does not exist today: no TextSight plugin in the Moodle plugin directory, no LTI 1.3 tool, no install URL for your administrator. If you came here for a download link, that link does not exist yet.
What does exist today: the detection engine, the Authenticity Score, the ESL-calibrated reference set, and the web app at app.textsight.ai. Moodle educators today paste a submission into the web app and get the same per-sentence evidence the plugin will surface inline once it ships.
Why this page exists anyway: waitlist signal is build-prioritisation evidence. Moodle is in the top three LMS targets behind Canvas and Blackboard; if this waitlist grows faster, Moodle ships first.
Specific to Moodle's grading workflow, its self-hosted reality, and the kinds of institutions that pick Moodle in the first place.
No public form endpoint yet, so the waitlist runs through email. Two minutes, one message.
We use the information to size the build, prioritise the LMS queue, and contact you when the plugin reaches beta. We do not sell or share the list.
Honest stage labels. Subject to demand signal from the waitlist. Dates are targets, not commitments.
Defining the plagiarism-plugin contract surface, the grading-view hook, and the audit-log shape. No code yet. Waitlist signal shapes priority.
Full technical spec, Moodle version matrix, FERPA/GDPR DPA, and a private design preview shared with waitlist members for feedback before build starts.
Local plugin under the Moodle plagiarism plugin type. Targeting Moodle 4.x and PHP 8.1+. Internal QA on a self-hosted reference instance.
Up to ten waitlist institutions. 60-day pilot, weekly feedback loop. Public release follows once the closed beta confirms no regression in the grading flow.
All dates above are targets and depend on waitlist demand signal versus the Canvas and Blackboard queues. If a regulatory item (DPA scope, FERPA review, MoodleCloud approval) takes longer than expected, the public ship date slides; we will not ship a plugin that cannot be audited.
Set as requirements at scoping time, not retrofitted. Each item below is what we are building toward, with the gap between today and ship called out where relevant.
No submission leaves the Moodle instance unless an educator clicks the scan button. No background batch, no auto-flag, no student-side enforcement.
FERPA alignment is a build requirement. The plugin will operate as a school official under the legitimate educational interest exception. EU and UK scans route through EU-region workers (Hetzner, Frankfurt). A DPA covering FERPA scope and SCCs will be available before any production install.
Submissions are processed in-memory and discarded after the response. No training on submission text. Per-scan metadata logs to the Moodle plagiarism log table, so registrars pull the audit trail directly from their own database.
No live plugin means no SOC 2 scope, no FERPA certification, no ISO claim. The posture above is what we are building toward. If a vendor claims their unreleased plugin is already SOC 2 certified, ask for the audit report.
The educator hub, the sibling LMS roadmap pages, and the workflow you can use today while the plugin is in build.
Waitlist signal moves Moodle up against Canvas and Blackboard. Beta members get a 60-day pilot, pricing input, and a direct line to the build team while the plugin lands.