Frequently Asked Questions
Quick answers for teachers, schools, tutors, parents, students, and game developers. Something missing? Email support@edu.games, or see the full documentation at docs.edu.games.
The platform
What is edu.games?
edu.games is a learning-games platform: a curated marketplace of educational games, lightweight class management for teachers and tutors, and built-in learning analytics. Teachers assign games, students play them in the browser, and educators see real progress data — scores, time spent, completion — for every student.
Is edu.games free?
Browsing the catalogue and previewing games is free, and many games are published free. Paid games are licensed as seat pools priced per seat per year in Australian dollars — auto-renewing yearly by default, or a one-time purchase covering a 1–10 year term.
Do games run in the browser?
Most do — HTML5 games play directly at edu.games with nothing to install. Some titles are desktop executables, licensed per seat like browser games but downloaded and installed on the student’s machine.
What ages and subjects are covered?
The catalogue spans all school subjects and age ranges. Every game lists its subjects and a recommended age range, so you can filter to what fits your classroom or child.
For teachers and schools
How do I use edu.games with my class?
Create a free teacher account at teacher.edu.games, create a class, and share its class code. Students join with the code, you assign games from the marketplace, and their progress appears in your dashboards as they play.
How does licensing work?
Paid games are bought as a pool of seats. Seats are consumed by distinct students across all your classes, first-come first-served, and the game appears on those students’ dashboards automatically. Free games can be assigned to any class without seats.
Does edu.games work with our LMS?
Yes, as an early-access integration. edu.games supports LTI 1.3: teachers deep-link games into LMS courses, students launch them from the LMS without a separate login, and scores flow back to the LMS gradebook. Moodle, Canvas, Blackboard, Brightspace/D2L, and any other LTI 1.3-compliant platform work — contact support@edu.games and we'll set yours up with you. See docs.edu.games/lti.
What do schools and districts get beyond individual teacher accounts?
An institution account groups your teachers into one organisation, lets you license games institution-wide with shared seat pools, gives read-only visibility of every licence, and can carry your own branded edu.games subdomain.
How is student data handled?
Learning activity is recorded as xAPI statements in the platform’s own Learning Record Store and is used to power educator dashboards — never sold or shared for advertising. Where edu.games processes student data on behalf of a school, we act as a data processor under the institution’s direction; see edu.games/privacy and edu.games/dpa.
For tutors and parents
Can I use edu.games as a private tutor?
Yes. A tutor account works without a school, class code, or academic email. Each student is linked to you through an invitation their parent approves, and your game seats cover your linked students automatically.
What control do parents have?
Parents approve who tutors their child and can revoke a tutor’s access at any time from the parent portal at parent.edu.games. When access is revoked, the student leaves the tutor’s roster and the tutor no longer sees their progress.
For students
How do I join my class?
Register at edu.games, choose the student role, and enter the class code your teacher gave you. Games your teacher assigns appear on your dashboard at student.edu.games — click one to play.
Do I have to pay to play?
No. Students never pay — teachers, tutors, or schools license the games, and anything assigned to you is ready to play.
For game developers
How do I publish a game on edu.games?
Create a developer account at dev.edu.games and upload your game — standard HTML5, an xAPI package, or a desktop executable. Every submission is reviewed within 2–5 business days; rejections come with written feedback. See docs.edu.games/quick-start.
What do developers earn?
Developers receive 70% of every sale. edu.games retains 30% to cover platform costs, payment processing, hosting, and support.
What is xAPI and do I need it?
xAPI is the standard edu.games uses to capture learning events. It’s optional — plain HTML5 games are fully supported — but xAPI-instrumented games give teachers per-student scores, time and completion data, and support LMS grade passback. See docs.edu.games/xapi.