LearningFlow LearningFlow vs Retool
Retool is where engineers build the internal tools an organisation runs on, like an admissions console over the live student record system. LearningFlow is built for the teaching itself, and gives each published app a contract naming the tables, columns and rows it may touch.
App builders · Sources last read 13 September 2026
Choose Retool if
Choose Retool when the thing you need is an operational tool sitting on top of systems you already run.
- An admissions triage queue reading and writing the live student record database.
- A team that wants app changes reviewed as pull requests on GitHub before release.
- An IT department that requires the whole platform inside its own Kubernetes cluster.
Choose LearningFlow if
Choose LearningFlow when the work is teaching or training, and several audiences need different rights over the same records.
- A parent consent form and a staff console over one table, on different rights.
- A head of department who writes rubrics and quizzes but has never written SQL.
- Two hundred Year 7 students who each need an account, a join code and an assignment.
What each one does.
Written from each product's own documentation. Where something is true only on a higher tier, the row says so.
| Retool | LearningFlow | |
|---|---|---|
| Live production systems | Apps query production Postgres, MySQL, MongoDB, Snowflake, Salesforce and REST or GraphQL endpoints directly. | Apps read and write Bases, which are LearningFlow's own shared tables, and call a named list of services such as Gmail, Resend, WhatsApp and web search. |
| Versioning and release | Source Control, on Enterprise, puts app changes through pull requests on GitHub or GitLab, with Releases. Staging environments start on Team. | A solution has no pull request review and no separate staging environment. |
| Building without code | Layout is drag and drop, but the data layer is SQL, REST and JavaScript. | 59 ready-made teacher tools sit in a public gallery, and the canvas refuses a wrong connection as you drag it. |
| Rights on the data | Access policies restrict table, column and row access on PostgreSQL resources, tied to permission groups, from the Business plan upwards. Other resource types get resource-level permissions only. | Each app holds its own contract: seven independent permissions scoped to named tables, named columns and a row filter, with an expiry, enforced on the data plane. |
| Learner accounts | Three user classes exist: builders, internal users and external users. There is no class, roster, assignment or gradebook. | Students are a first-class user type with their own accounts, join codes and assignments. |
| Cost per extra editor | Anyone who edits an app during a billing cycle is billed as a builder for that cycle, $10 a month rather than $5 on Team and $50 rather than $15 on Business, billed annually. | Credits rather than seats, with the organisation wallet kept separate from a member's personal one. |
| Model choice | A model picker covering OpenAI, Anthropic and Google models, though individual models carry plan labels, the Google models are Enterprise only, and your own provider keys are Enterprise only. | Flow Designer reaches Claude, OpenAI, Gemini, Grok and DeepSeek among others, with no plan gate and only a per-organisation admin override. |
| Switching features per member | Custom groups and organisation roles arrive on Business. Free and Team have only All Users and Admin, with access levels that cannot be changed. | Seven capabilities are switched per member, and a role grants the permission key before the member opts in. |
What comes with it here.
The file, not the recipe
Work with AI runs on a sandboxed Linux machine with LibreOffice and python-pptx, and hands back a .pptx, a .docx or an .xlsx whose formulas still calculate.
A narrated video from one sentence
Whiteboard Studio renders an MP4 in 16:9, 9:16 or 1:1, with subtitles off, as a sidecar .srt or burned in, and redraws only the scene you corrected.
xAPI records you keep
Ingest an xAPI package, use the self-hosted SQL learning record store, or point the organisation at its own LRS.
Resell it under your own name
Sub-organisations sit under an enterprise with wholesale credit pools, per-currency exchange rates, volume tier pricing, margin guardrails, Stripe and senangPay.
Where Retool is the better choice
If the deliverable is one internal tool over systems you already run, Retool is the shorter road and the better product. A university IT team building a clearing dashboard against the live student record system, Salesforce and half a dozen REST endpoints gets mature hosting and sign-in, separate staging and production environments, and app changes reviewed as pull requests. LearningFlow has none of that, and Bases are its own tables rather than yours. Running the whole platform on your own Kubernetes cluster is a first-class path there, and not one we offer.
The whole stack against Retool.
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 | Retool | |
|---|---|---|
| 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 both, and what would migrating actually involve?
Running both is the common answer: Retool for the operations console over the student record system, LearningFlow for lesson material, student assignments and xAPI records. Nothing imports between them. A Retool app is queries and JavaScript against your resources, and LearningFlow cannot read that. The connection runs the other way: every LearningFlow flow has an address, so a Retool app can POST to it with an x-api-key and show what comes back.
Will teachers or trainers be able to build things themselves?
In Retool, up to a point. Layout is drag and drop, a GUI mode covers simple database writes, and an Ask AI helper drafts a query from plain English. Past that the data layer is SQL, REST and JavaScript, and the product is aimed at developers and technical operations staff. There is a billing consequence too, since a teacher who edits one app for five minutes is charged at the builder rate for that whole cycle. In LearningFlow a teacher starts from one of 59 published tools, such as a rubric or a text leveller, and the canvas refuses a wrong connection as you drag it.
What does it cost as more people use it?
Retool is per seat with metered add-ons. Team is $10 per builder and $5 per internal user each month billed annually, Business is $50 and $15, and Enterprise is quoted. AI credits renew monthly, do not roll over, and AI features stop until the next cycle once they are spent, with top-ups at $100 per 1,000 credits on Team and Business. Prices are as listed on retool.com/pricing on 13 September 2026. LearningFlow has no seats and no subscription to renew. Credits are the unit rather than seats, and personal, organisation and enterprise wallets stay separate, so a teacher's free monthly grant never pays for the school's work.
Can students have their own accounts?
Not in Retool. Its user model is builders, internal users and external users, the last meaning partners and clients outside the organisation, and there is no learner type, class roster, assignment or gradebook. Retool publishes its security practices, holds SOC 2 Type 2 and ISO 27001, and does not store the data your apps query, but nothing in it is shaped around learner records. In LearningFlow students are a first-class user type with their own accounts, join codes and assignments, and learner activity can be written to xAPI.
Will either one hand us finished documents and media?
Retool ships a PDF exporter that takes Markdown and returns a PDF, exports the current app view as a PDF, generates AI images, and exports data as CSV, TSV, JSON or Excel. A PowerPoint deck, a Word file, video or audio has to be produced by code you write or a service you call, then passed to the download helper as base64. LearningFlow returns .pptx, .xlsx, .docx, .mp4, .mp3 and .png as files. Two limits are worth knowing: its sandbox has no network access, and it cannot transcribe a video or read a scanned page.
Where this came from. Read on 13 September 2026. Retool 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.