[ SCHOOL EVALUATION GUIDE ]
Nexus and Dust
Compare Nexus and Dust with the same classroom tasks and school requirements.
Run the same learning task
Ask Nexus and Dust for a staged hint, an explanation with uncertainty, and feedback on a student revision.
Verify the school controls
Check Dust directly for class instructions, student and teacher roles, review scope, model access, retention, and provider arrangements.
Compare the full commitment
Record platform cost, model usage, setup work, support ownership, and exit options. This page does not claim what Dust currently provides.
Evaluate Dust against your classroom workflow
Use the same approved lesson, teacher instructions, and student attempt when you evaluate Nexus and Dust. Product plans and capabilities change; this page offers a school evaluation framework rather than a permanent feature ranking.
The Nexus workflow to inspect
Check the class help policy, the approved model set, prompts and responses visible to the assigned teacher, and the separation from unrelated personal work. Ask the student to complete a related task independently after the assisted conversation.
Questions for your evaluation
Ask each vendor or project to demonstrate these checks in the version your school would use. Record the result and configuration for Dust and Nexus separately.
- Can a teacher set the help level for the intended class?
- Who can review the student's prompts and all responses?
- How are model access, source permissions, and spending controlled?
- What are the actual platform, provider, and operating costs?
Make the decision with the people who will use it
Include students, teachers, and the team responsible for identity, purchasing, and support. A general-purpose workspace may fit one school task while a class-centered workflow fits another. Choose based on observed behavior and the school's requirements.