Loading...
Loading...
Aelira's core is public at github.com/Aelira-AI/aelira-core, released as v0.9.11. The engine is AGPL-3.0; the command-line client is MIT. Scanning, supported remediation, connector code, dashboard and CLI are included, with no paid feature tier. Product maturity remains beta; human review is required.
Published September 13, 2026. Aelira Core is beta software. Supported workflows can apply partial fixes and produce review artifacts. Human review remains necessary; automated scores do not establish accessibility conformance. Some inputs cannot produce a downloadable remediated file. Deployment configuration and connector maturity affect what is available; evaluate the actual saved output and workflow before rollout.
Accessibility tools should be free, transparent, and community-driven
Accessibility is a human right, not a profit center
Universities shouldn't have to commit to expensive, quote-based licenses for closed-source software. We believe accessibility tools should be free and transparent.
Keep student data on your servers, not ours
A fully local configuration can keep document content inside institution-controlled infrastructure and support FERPA, residency, and privacy review.
Community contributions make Aelira better
Open source enables universities to customize Aelira for their specific needs. Your improvements can help thousands of other institutions.
The self-hosted core has no paid feature tier. Supported operations and validation limits remain visible in the public documentation.
The core that finds issues and fixes them
Connects to the systems your campus already runs
The full compliance UI, not a cut-down viewer
In the cli/ directory of the same repo, MIT licensed
Clone, configure, and bring the stack up with Docker Compose
git clone https://github.com/Aelira-AI/aelira-core.git
cd aelira-core
docker compose -f docker-compose.quickstart.yml up -dNo .env file needed. Brings up the API, dashboard, PostgreSQL, and Redis.
# API + interactive docs
http://localhost:8000/docs
# Health check
http://localhost:8000/healthOllama can process supported AI tasks on institution-controlled hardware. Review provider selection, fallbacks, storage, logs, backups, and network egress before asserting that document content stays inside your boundary. Configuration options are documented in docs/deployment/local-ai-models.md.
Both are available today. Same software either way — the difference is who runs it.
You provide infrastructure, we provide software
Managed hosting, with institutional review and governance retained
Yes. The self-hosted core is open source at github.com/Aelira-AI/aelira-core: the engine under AGPL-3.0, the command-line client under MIT. There is no paid feature tier or Aelira per-page software fee. You provide infrastructure and pay any providers you enable; operational limits and administrator quotas still apply. Paid support starts at $799/month for installation help, supported upgrades, model guidance, and maintenance. The core software remains free.
The engine is AGPL-3.0; the command-line client in cli/ is MIT. Both are in the public repository. The split gives the CLI a permissive licence while retaining copyleft conditions on the engine. Read the actual licences when planning modifications or network deployment. AGPL obligations can apply to users interacting with a modified version over a network, including an internal deployment. The CLI licence does not change the licence of the engine it calls.
Accessibility is a human right, not a profit center. Universities shouldn't have to commit to expensive, quote-based licenses for closed-source software just to remediate their documents. Our business model: we give away the software for free and sell support, hosting, and professional services. This aligns our incentives - we make money by helping you succeed, not by locking you into expensive licenses.
Self-hosted (free): • You run and operate the core • You provide servers, storage and backups • Community support via GitHub Issues • No support SLA Paid support (from $799/month): • Guided installation and upgrade planning • Documented response targets • Supported release and model guidance • Quarterly reviews on institution plans Paid plans add support or managed infrastructure. The core has no paid feature tier. Configuration, deployed versions, capacity and acceptance evidence need to be checked for each deployment.
v0.9.11 is the current published release, dated September 13, 2026; product maturity remains beta. Supported workflows can apply partial fixes, but validation continues. Some inputs require manual work and cannot produce a downloadable remediated artifact. Scores do not establish accessibility conformance. Review format limits, connector maturity and public test evidence before a pilot. Agree acceptance checks for your institution's files and user journeys. Public issues at github.com/Aelira-AI/aelira-core track known work.
Yes, subject to the applicable licences. You can add features, integrate systems, replace the branding, fix bugs, and contribute improvements. Review AGPL-3.0 requirements for the engine, including modified network deployments; MIT applies separately to the CLI. Maintaining an institutional fork can be scoped as professional services ($200-$350/hr).
Minimum requirements: • 4-8 CPU cores • 8-16GB RAM • 50-100GB storage (SSD recommended) • Docker and Docker Compose Recommended for production: • 8-16 cores (better AI performance) • 16-32GB RAM (parallel processing) • 200-500GB storage (scan history) • PostgreSQL database • Redis cache • A reverse proxy for TLS You can host on: department servers, AWS, Azure, GCP, DigitalOcean, Hetzner, OVH, or any VPS provider.
You do not need to train a model. The evaluation quickstart starts the API and supporting services, with AI disabled by default. The full production Compose file includes the dashboard. Administrators select a local or cloud provider and review fallback routes, network egress, permissions, storage and backups. Docker/Linux administration and accessibility review remain necessary. The repository documents model and deployment choices.
Yes. We welcome contributions: • Bug fixes • New features (especially higher ed-specific) • Documentation improvements • Translations • Test coverage • Performance optimizations See CONTRIBUTING.md in the repository for guidelines. All contributors are credited in CHANGELOG.md.
We offer professional services for custom development: • API integration with existing systems • Custom workflow development • Migration from legacy tools (YuJa, Ally, ReadSpeaker) • Training for IT staff (1-5 days) • On-site implementation Rates: $200-$350/hr depending on complexity. Or hire your own developers - both licences allow it.
Clone it, run it, break it, and tell us what happened. Bug reports from real university deployments are the fastest way to get v0.9.11 to 1.0.
Questions about open source? Email us at [email protected]