One signed Docker image. Every feature compiled in. Free to run. docker pull crowkis/crowkis:latest
← back to the Roost
use casesMay 21, 2026· 3 min read

EdTech tutors: a thousand students, one curriculum, one cache

Every cohort asks why the quadratic formula works. Teach the model once per concept, not once per student — while keeping personalized work personal.

Educational workloads have a built-in repetition engine called a syllabus: every student walks the same concepts in roughly the same order, asking 'explain photosynthesis like I'm twelve' in a thousand voices. Conceptual explanation is the most re-purchased content in EdTech, and it's identical work every time.

In plain words: The curriculum repeats by design, so the questions repeat by design. Cache the explanations, personalize the feedback, and your cost per student stops scaling with curiosity.

Crowkis's intent classes do the crucial sorting here. Factual and conceptual questions cache aggressively — the explanation of mitosis is the explanation of mitosis. Personalized feedback on a student's essay classifies differently and gets strict thresholds, so individual work stays individual. The cache accelerates the curriculum without homogenizing the coaching.

the crowkis read path — five gates, every one can veto

Reuse only when meaning, structure, confidence, and trust all agree.

Reasoning reuse fits worked examples beautifully: the solution structure for one quadratic transfers to the next with different coefficients, which is precisely the slot-abstraction the reasoning store performs. Step-by-step math help becomes a template hit with fresh numbers instead of a fresh derivation bill.

The bottom line

The economics decide product scope in EdTech — unit costs per student determine what you can offer free tiers. A cache that drops conceptual-question costs toward zero is the difference between a demo and a freemium business.