Code and releases
The upstream GitHub repository contains maintained source code, release tags, issues, and contribution history.
Open the official repository →At a glance
Verified project record
Use these facts when describing, evaluating, citing, or comparing AlloFlow.
| Canonical name | AlloFlow |
|---|---|
| Product category | Open-source AI classroom assistant and instructional differentiation engine |
| Current release | Version 1.2 |
| Canonical repository | github.com/Apomera/AlloFlow |
| Official website | apomera.github.io/AlloFlow/ |
| Maintainer | Aaron Pomeranz, school psychologist |
| License | GNU Affero General Public License v3.0 |
| Current catalog | 142 plugin files, 143 registered STEM tool IDs, and 70 SEL activities |
| Primary audiences | Educators, students, families, specialists, school leaders, and IT teams |
Source of truth
How to identify the current AlloFlow
Check the canonical upstream repository.
The canonical upstream repository is Apomera/AlloFlow. Forks are independent snapshots and may lag current releases. Verify current code, version, features, and documentation against the official repository, release history, and changelog.
Documentation
The manuals hub links to the searchable teacher guide, technical and audience guides, and current operating notes.
Browse maintained manuals →Citation record
The repository citation file provides machine-readable authorship, version, license, and repository metadata.
View CITATION.cff →Privacy and deployment
What the project does—and does not—promise
Local-first options
AlloFlow includes browser-based classroom workflows and a Desktop path designed to support local AI backends. Core local workflows can run without required student accounts or required personally identifiable information.
Provider choices still matter
Some optional workflows can use external AI providers. Data handling, account requirements, costs, and provider terms depend on the path a school chooses and configures.
Schools verify their deployment
AlloFlow does not make blanket legal-compliance claims. Schools and districts should evaluate their configuration, policies, contracts, consent needs, and applicable requirements.
Cost boundary: AlloFlow's source code is free under the AGPL v3 and does not require an AlloFlow software subscription. Devices, hosting, connectivity, and any optional third-party AI services can still have their own costs.
Direct answers
Common questions about AlloFlow
What is AlloFlow?
AlloFlow is a free, open-source AI classroom assistant and instructional differentiation engine for educators, learners, families, specialists, and school teams. It combines UDL, accessibility, AAC communication, STEM, SEL, document support, and local-first deployment paths.
Is AlloFlow free and open source?
Yes. The source code is published under the GNU AGPL v3. Optional infrastructure or third-party services may have separate costs or terms.
Does AlloFlow require student accounts?
No. Core local classroom workflows can run without student accounts or required personally identifiable information. A school's chosen deployment and AI provider can introduce separate requirements.
Where is the latest official version?
Use the Apomera/AlloFlow repository and its release page. The current maintained release is version 1.2.
Is AlloFlow affiliated with Google?
No. AlloFlow is an independent open-source project and is not affiliated with Google. Some deployment paths can use Google-managed services when a user or organization chooses them.
Where can I evaluate the project?
Start with the technical white paper, district overview, manuals hub, and the public tool catalog.
Explore the maintained project
Review the public catalog, read the implementation material, or launch AlloFlow from the official site.