LearningFlow LearningFlow vs Curipod
Curipod does one thing well. A class writes to a prompt, each student gets feedback against the rubric the teacher picked, and they revise before the bell. LearningFlow covers the rest of the job too, from building the lesson to handing you the files: a scheme of work as a .docx, a spreadsheet whose formulas still calculate, a narrated MP4, and an app the school keeps.
Education AI · Sources last read 13 September 2026
Choose Curipod if
Choose Curipod when the job is K-12 English writing practice against a state test, and students must not have accounts.
- Your district has ruled out student sign-ups, and a PIN at curi.live gets a whole class writing without one. Curipod does offer student SSO and rostering through Clever, ClassLink and Google on the paid plan, so a PIN is not the only way in.
- You teach STAAR or CAASPP writing and want prompts already mapped to your adopted curriculum.
- Two teaching sessions a week on the free plan is enough, and you have no budget cycle to wait for.
Choose LearningFlow if
Choose LearningFlow when the work outlives the lesson, and the school needs the files, the accounts and the controls.
- A head of department wants the scheme of work as a .docx and the marks as a working .xlsx.
- A teacher leaves in July and the school must keep the tools she built.
- You need a Year 7 revision app with its own sign-in, not another set of slides.
Where the two are built differently.
One part of the job, done well.
This is a good product at what it does. The question for a school is what else is on the invoice: each remaining job is another product, another bill, another set of logins, and a handover you do by hand every time.
Idea to a class that has done it.
One login, one pool of credits, one place the spending shows up. A video drops into a lesson, the lesson becomes an assignment, the assignment writes to a base and an app reads it — nothing is exported and re-imported.
What each one does.
Written from each product's own documentation. Where something is true only on a higher tier, the row says so.
| Curipod | LearningFlow | |
|---|---|---|
| Who owns the work | The teacher owns what they make, accounts belong to one person, and sharing a lesson produces a copy. | Every flow, base and app is stamped with the organisation at creation and stays when a member leaves. |
| Files you can keep | A PDF of the lesson, on paid tiers only, described as being for absent students and paper backup. | Work with AI returns .pptx, .xlsx, .docx, .mp4, .mp3 and .png, with spreadsheet formulas that still calculate. |
| Student accounts | Students never sign themselves up and join at curi.live with the lesson PIN. Districts on the paid plan can roster and provision student accounts through Clever, ClassLink or Google. | Students are a first-class user type with their own accounts, join codes and assignments. |
| Ready-made test prep | Writing tasks mapped to 55+ adopted curricula, with STAAR, CAASPP, GMAS and PSSA libraries. | 59 teacher tools in a public gallery, general purpose, and not mapped to any state test. |
| Published price | Free at $0 a month; both paid tiers are custom pricing sized to student count, by quote only. | Credits rather than seats, with personal, organisation and enterprise wallets kept separate. |
| Running it from your systems | No developer, API or webhook documentation on any plan; ClassLink, Clever and Google cover identity and import. | POST /task/:taskId with an x-api-key and optional streaming, plus signed webhooks and cron schedules on published apps. |
| Choosing the model | Curipod picks the models and publishes the list, including o3, gpt-5, gpt-4o, Gemini 3 Pro and Gemini 3 Flash. | Flow Designer reaches Claude, OpenAI, Gemini, Grok and DeepSeek among others, with no gating by plan. |
| Reporting into your stack | Lesson reports and per-student Glow and Grow summaries ship on the School and District plan, for lessons taught after 6 May 2026, and following one pupil across the year needs district SSO. The reports live inside Curipod and do not send records anywhere else. | Results leave as xAPI statements, the standard schools use to log learning activity. Upload an xAPI package, keep the records in LearningFlow's own store, or send them to the record store your district already runs. |
A role, not a set of switches.
Everyone inside gets the product. If a feature is not right for a group — thirteen-year-olds, or a department mid-pilot — the answer is to not give them an account at all.
Seven switches, per group.
Year 7 opens the library and can chat. They cannot build apps or reach the database. Change your mind at 9am and it is different at 9.01, for that group only — without removing anyone's account.
What comes with it here.
A narrated video from a sentence
Whiteboard Studio turns one sentence into an MP4 in 16:9, 9:16 or 1:1, with subtitles off, burned in, or as a separate .srt.
An app with its own sign-in
Describe a revision app and get a working one at its own address that a class can log into on Monday.
Several apps, one database
One solution can hold three apps: a page people sign into, an address another system posts to, and a job that runs on a timetable. They share one spreadsheet-style database, and each gets its own contract naming the tables, columns and rows it may read or change. Switch one off and the others keep running.
A canvas for the tool you need
When none of the 59 gallery tools fits, build your own on the node canvas, which refuses a wrong connection as you drag it.
Where Curipod is the better choice
If you are an ELA coordinator buying writing practice on top of a curriculum you have already adopted, buy Curipod. It ships prompts mapped to 55+ programmes plus STAAR, CAASPP, GMAS and PSSA test-prep libraries, and we have nothing like that library. Its free plan is genuinely usable: two teaching sessions a week, unlimited lesson creation and unlimited student writers, with no card and no procurement. It also publishes a 50-state DPA table, so in many districts the paperwork is already done.
The whole stack against Curipod.
The table above compares the two at the job they share. This one runs every capability past both, because what a school is choosing between is usually a tool that does one job and a workspace that does many. Hover any mark to see what it means, and a partial one to see exactly what is limited.
| LearningFlow | Curipod | |
|---|---|---|
| Ask and read | ||
| Chat with AI | ||
| Research the web and write it up | ||
| Read text off an image or a scan | ||
| Agent browses the live web | ||
| Make | ||
| PowerPoint deck | ||
| Spreadsheet with working formulas | ||
| Word document | ||
| Image generation | ||
| Video generation | ||
| Narrated whiteboard video, corrected scene by scene | ||
| Voice-over | ||
| Song generation | ||
| Interactive web page | ||
| Edit what it made, online | ||
| Slide and design templates | ||
| Presenter on camera, from a photo you supply | ||
| Teach | ||
| Ready-made teacher tools | ||
| Build your own tool, no code | ||
| Lesson that branches on the answer | ||
| Hears them read aloud, checks pronunciation | ||
| Assign to a class with a join code | ||
| Assignments and submissions | ||
| Student accounts | ||
| LTI link from your LMS | ||
| Learning records to your own LRS | ||
| SCORM 1.2 package out | ||
| Build | ||
| Working app | ||
| Full working platform templates | ||
| Several apps over one database, rights each | ||
| App sends email or WhatsApp | ||
| App runs on a schedule | ||
| App accepts webhooks | ||
| Generate real-time apps | ||
| Generate AI-driven apps | ||
| Shared database | ||
| Revoke one app's access, not the others | ||
| Run | ||
| Run any tool from your own software | ||
| Choose the AI model, on every plan | ||
| Switch a feature off per group | ||
| Organisation keeps the work when staff leave | ||
| We do not do this | ||
| Transcribe a video or audio file | ||
| Custom domain for a published app | ||
Before they decide.
Can we run Curipod and LearningFlow side by side?
Yes, and many schools should. Keep Curipod for the weekly whole-class writing session, and use LearningFlow for the work that leaves the lesson: the spreadsheet with working formulas, the revision app, the video, the xAPI records. The two do not share data, so treat it as two tools rather than one migration.
We built a term of lessons in Curipod. Can we move them across?
Not automatically. The only documented export is a PDF of a lesson on paid tiers, and there is no public API, so a bulk move is not possible. Copy the prompt and rubric text into a flow by hand. How long that takes depends on how many prompts and rubrics each unit holds.
Our teacher leaves in July. What happens to her work?
In LearningFlow the organisation is stamped on the object at creation, so her flows, bases and apps stay. Removing her from the organisation takes away her access, not her work, and an admin can list org-library tools whose owner has left and reassign them. In Curipod the creator retains ownership and the documented admin action is to remove the user.
Can an admin switch a feature off for one department?
Not by department, but one member at a time. Seven capabilities are switched per member: org-library, chat, flow-creator, assignment-creator, solution-designer, base and work-with-ai. A role grants the permission first, then the member opts in, and assignment-creator needs flow-creator. There is no department object in LearningFlow. Curipod documents a binary admin or member role, and its copy-paste and writing-assistant guardrails are set by the teacher per lesson.
Do students need accounts with LearningFlow?
They can have them, with join codes and assignments, so you can follow one pupil across a year. If your district's rule is that students must not hold accounts, Curipod's PIN model fits that rule better than ours does.
Where this came from. Read on 13 September 2026. Curipod changes its product and its prices without telling us, so check anything that decides a purchase.
Try it on your own work.
Teachers get credits every month, free. No card, no seat count.