A guided workspace grounded in your curriculum. AI that asks instead of answers, building insight teachers, advisors, and parents can act on.
Why now? Read the research →Orchen is a school-governed learning environment where students do their learning: guided sessions grounded in their classes, a Writing Studio, assignments, flashcards, and quizzes built from their own work. As they learn, a growing picture of how each student thinks forms underneath it.
Teachers, advisors, and parents see that picture through their own window, at levels the school controls. It compounds over time: what a school learns about a student in October doesn’t disappear in June. The context stays, even as classes and teachers change.
See the full platform architecture →
Protect the journey from not knowing to understanding.
A correct answer can still leave a student unable to explain it. Orchen supports the work between receiving an answer and understanding why it makes sense.
A student can get a worked answer before attempting the problem.
Help may miss the readings, methods, or context the class is working with.
The finished response alone cannot show what the student understands.
Questions, explanations, examples, and feedback help students work through the problem.
Teachers connect readings and worksheets to lessons and choose what is active.
Separate exposure, engagement, and understanding demonstrated on a graded check-in or quiz.
Orchen uses guiding questions to help students work through problems and develop their own understanding. Flashcards, quizzes, and a Learning Profile grow from their own work, not a generic curriculum.
Add readings, worksheets, and lesson materials to the class knowledge bank. Orchen uses active material to support students as they work through your lessons.
Teacher view · Adding class material
Add material, connect it to the unit, and review what is active. Demo class.
Student view · Guided help in class context
Enlarge screenshot ↗
The class/unit label and follow-up question show the context of this demo exchange.
What your child worked on, where they pushed through, and what to ask at dinner, every week, in plain language. Zero scores, zero jargon.
Separate exposure, substantive engagement, and demonstrated understanding. See the recorded evidence against curriculum standards and where evidence is still missing.
Missing evidence is a reason to ask what to assess next; it does not establish a lack of understanding.
Explore standards evidence →
Enlarge screenshot ↗
ELA example: visible counts are zero, with no latest evidence recorded.
Enlarge screenshot ↗
Math example: three rows show one student and a latest-evidence date, not a completed class report.
Orchen runs as a software application on your school's existing devices, iPads, MacBooks, or any managed fleet. For schools that want network-level enforcement on managed devices, a pre-configured device layer is available as an optional add-on. No IT setup required either way.
The Orchen demo is open, no signup, no sales call. Ask it something a student would ask, and watch it teach instead of answer.
“When kids replace effortful learning with generative AI to shortcut assignments, it is quantifiably bad for their cognitive development. Students must make mistakes to become independent thinkers.”National School Boards Association · January 2026
I built Orchen because the two answers schools were being offered, ban AI, or look away, both seemed designed to fail the students. The research made the stakes clear; what was missing was an environment a school could actually take responsibility for: one that teaches instead of completing work, and treats student data like it belongs to the student.
Orchen is early-stage, and I'd rather say that plainly than dress it up. What early means in practice: schools that join now work directly with me, on configuration, on the pilot, on the roadmap. Every privacy commitment on this site is one I can show you in the architecture, live, with your technical reviewer in the room.
If you're weighing this decision for your school, write to me. You'll get a straight answer, including honest guidance on timing, if a later cohort would serve your school better.
Your school decides what visibility looks like. Orchen turns student work into role-appropriate learning insight, while schools control what teachers, advisors, and parents can see, including conversation access. Parent visibility is configured separately. Staff access is role-scoped and audited.
Orchen is built around both statutes: row-level security at the database layer, immutable audit logs of every staff access, per-school retention policies, and under-13 protections via the role gate. Your technical reviewer can verify every claim against the live architecture during the walkthrough, the platform page covers the details.
No new hardware and no IT project. Orchen runs in the browser on whatever fleet you already manage, iPads, Chromebooks, MacBooks. Configuration is an afternoon, not a semester. Schools that want network-level enforcement can add the optional managed device layer later.
Teachers read Orchen like a morning briefing, the platform does the managing. The class view shows who’s on track, who’s quietly stuck, who needs attention today. Creating assignments through Orchen is optional; the insight flows either way.
The Socratic design lowers the stakes of any single answer: Orchen asks students to reason and check, rather than handing down statements to accept. Subject-specific modules constrain how it teaches each discipline, and because teachers see concept-level trends across the class, a misunderstanding surfaces as a pattern, not a secret.
That’s the design problem Orchen is built around. The tutor meets each student where they are, adapting to how they learn, down to the study mood they pick that day, and the flashcards, quizzes, and learning profile are generated from their own work, which makes progress visible and personal. Assignments launch inside Orchen, so it’s where schoolwork already lives. Guided help that works beats an answer they have to hide.
A flat per-school site license, sized by headcount, a school-level decision, not a per-seat negotiation. Pilots are free: one class, about six weeks, working directly with the founder, then you review the results together and decide. The founding program spells out terms, timeline, and the clean exit, and emil@orchen.ai answers with straight numbers, not a quote funnel.
Leave your details and we'll reach out to book your walkthrough.
Or write to us at emil@orchen.ai
Every student, understood.
