Skip to main content
AIDiveForge AIDiveForge

InputDojo vs Luca

InputDojo and Luca are both education & learning tracked by AIDiveForge. Below is a side-by-side comparison of pricing, capabilities, platforms, and ownership — sourced from each tool's live website and verified before publishing.

InputDojo

InputDojo

The core loop is structured around proficiency levels: you work through vocabulary in context, get speech feedback on conversation practice, and the system reschedules reviews based on what you're actually forgetting. That beats flashcard apps that treat every word the same. The constraint shows up when you need niche language pairs or want to export your progress data — the vendor does not describe an open API, so your learning history stays inside the platform. Teams using this to supplement formal instruction get the most mileage; learners who want to pipe data into a custom dashboard hit a wall fast.

Luca

Luca

LUCA's core loop is listen-analyze-build: SoundScout captures speech at the phoneme level, the real-time diagnostic engine identifies where the breakdown is occurring, and JourneyBuilder adjusts the practice path accordingly. StoryGen produces AI-generated stories personalized to the student's current skill ceiling, so the content stays relevant rather than recycled. The vendor grounds the system in Science of Reading methodology and cites Spring 2026 pilot data showing fluency gains and early-week progress markers. The platform is cloud-only with no self-hosted option and no API, which closes off custom integration work for districts that need to pipe data into their own SIS or MTSS dashboards. Families and small programs can get started independently; schools need a pilot agreement.

AttributeInputDojoLuca
PricingPaidPaid
Price$7.99/mo$27/reader/month
Free trial14 days7 days
Open sourceNoNo
Has APINoNo
Self-hosted optionNoNo
PlatformsWeb, iOS, AndroidWeb-based platform accessible across devices (mobile, tablet, desktop)
Pros
  • Exam-aligned study plans for JLPT and HSK mean practice time maps directly to what standardized tests score, so you're not drilling vocabulary that won't appear on the test you're sitting.
  • Vocabulary presented in native-media context rather than textbook sentences, which means words land with the register and colocation patterns you'll actually encounter in listening or reading sections.
  • Instant speech feedback on conversation practice closes the gap that silent review apps leave — you hear whether your pronunciation is off before bad habits calcify.
  • Spaced repetition tuned to individual mastery levels, so the system reschedules reviews based on where you actually struggle rather than applying a one-size decay curve to every learner.
  • Mobile and web access from a single account, so review sessions fit around a schedule that doesn't include dedicated study blocks.
  • Phoneme-level speech recognition via SoundScout rather than word-level accuracy scoring, which means the diagnostic can pinpoint the specific decoding breakdown rather than returning a reading level that tells a teacher nothing actionable.
  • Real-time diagnostic engine adjusts the student's learning path without waiting for a teacher to review scores and reassign content, so intervention continues outside of supervised sessions — at home, in after-school programs, or during independent work blocks.
  • AI-generated stories matched to the student's current phonics scope through StoryGen, which means students are not re-reading the same decodable texts that caused disengagement with their previous scripted program.
  • Science of Reading methodology grounding, so the skill sequence and instructional approach align with what MTSS and RTI frameworks require — avoiding the compliance friction that arises when a tool's pedagogy conflicts with a school's documented intervention model.
  • EducatorHub classroom analytics dashboard surfaces caseload-level progress data, which means a reading specialist managing twenty or thirty students is not manually compiling session notes to identify who needs a level change.
Cons
  • No API and no data export path: every progress metric, vocab list, and mastery score lives inside the platform. Learners or institutions that need to feed data into an LMS or run their own retention analysis have no route out — they're maintaining a parallel tracking system manually.
  • AI-powered features — personalized plans, speech feedback — are paid-only features. The free tier does not deliver the core differentiator, which means evaluating whether the tool actually fits your learning style requires committing to a paid account.
  • Learners whose goal is conversational fluency in an unsupported language pair, or who need a tutor-like correction model beyond speech feedback, will hit the ceiling of what a structured app can offer and move to a platform with live tutors or a larger language coverage list.
  • No API and no self-hosted option means any district that needs LUCA's diagnostic data inside its SIS, MTSS platform, or data warehouse must export and import manually — at scale across a multi-school deployment, that becomes a recurring data-ops burden that teams either absorb or use to justify switching to a platform like Amira or Lexia that has district integration agreements in place.
  • School access requires a custom pilot agreement rather than self-serve provisioning, which means a school or district cannot deploy quickly in response to mid-year assessment results — the procurement timeline adds friction that smaller schools with urgent intervention needs feel most acutely, and some will default to a competitor that allows immediate purchase.
  • The platform is built exclusively around foundational phonics and decoding intervention, so students who have cleared the phoneme-level ceiling and need fluency-building, vocabulary, or comprehension support will exhaust what LUCA addresses — teams at that stage need a second tool to continue structured literacy progression.
Bottom line

InputDojo and Luca are closely matched on pricing model, openness, and API availability — pick by feature set and platform support in the table above.

Frequently asked questions

What is the difference between InputDojo and Luca?

InputDojo is Paid, while Luca is Paid. Compare pricing, free trial, API, platforms, and pros/cons in the table above on AIDiveForge.

Is InputDojo better than Luca?

It depends on your workflow. Use the side-by-side attributes (pricing, open source, API, self-hosted, platforms) to decide. AIDiveForge does not rank a universal winner — we publish verified facts so you can choose.

InputDojo vs Luca: which should I pick?

Pick InputDojo if its pricing model, openness, or platform fit matches your constraints; pick Luca otherwise. Check free-trial availability on each listing if you want to test before committing.

Comparison data is sourced and verified by the AIDiveForge data pipeline. AIDiveForge is editorially independent.