Why We Made Aelira Open Source (And Why That Matters for Universities)

We made Aelira Core open source so institutions can inspect the implementation, operate their own deployment and contribute improvements. Source visibility helps a technical evaluation; it does not by itself establish accessibility, security or fitness for a particular institution.

Inspect the implementation and licences

The public repository is the reference for the current code, release instructions and licence notices. The project uses MIT and AGPL components. Check the applicable licence for each component you deploy or modify. AGPL obligations can arise when users interact with modified software over a network, including institutional use; internal hosting is not a blanket exemption.

An institution can evaluate a proposed integration or contribute a patch. Integration still requires engineering, testing and maintenance. Open source makes that work possible; it does not promise immediate compatibility with every LMS, LaTeX package or institutional reporting system.

Free software and paid services

The self-hosted software is free and open source. Paid services cover support or managed hosting. Operational allowances, provider charges and service commitments depend on the chosen deployment and written terms; free software does not mean unlimited processing or zero operating cost. Use current US pricing or current Australian pricing, and obtain a written pilot quote covering continuation terms.

Budget for compute, storage, backups, upgrades, security operations and staff review. A consortium deployment needs agreed access controls, governance, capacity and applicable licence compliance. Splitting infrastructure costs is a possible planning approach, not a reported university saving.

Understand the beta scope

Aelira Core v0.9.11 is beta. Supported workflows can detect issues, suggest changes and apply eligible partial fixes. Other findings need manual work, and some inputs may not produce a downloadable remediated artifact. Review the actual saved file, its recorded fixes and its unresolved findings. An automated score does not establish WCAG conformance.

The same public code is available for self-hosting; paid support and hosting are services rather than additional paid feature tiers. Check the release's supported processors and saved-output evidence before assuming a proposed feature exists.

Deployment control and privacy

Self-hosting does not automatically mean documents never leave the institution. External inference providers, telemetry, logs, backups and integrations may create additional data flows. Confirm the configured providers, permissions, retention and destinations with the institution's security and privacy teams. A software licence does not establish FERPA compliance or another legal assurance.

Build an adoption plan

Start with approved representative documents. Test installation, processing, human review, retained evidence, backup and recovery. Assign ownership for updates and unresolved content. Compare total operating cost with alternatives using current quotations and measured review work.

Open source also offers options if a supplier changes direction: retain the code, assess a fork or seek another maintainer. Those options require staff and funding, and do not guarantee uninterrupted operation or future maintenance. Follow the repository's current installation instructions rather than an older command copied into a blog post.