Skip to main content
Documentation

Guide baseline: Aelira Core v0.9.11

Getting Started with Aelira

Scan course materials, generate supported changes and review the evidence before publishing.

Current open-source release: v0.9.11; product maturity: beta. These guides describe the source release indicated above. Hosted plans have separate configuration, allowances and provider terms. Inspect the evidence and evaluation limits.

Choose your next task

Quick Start

Evaluate the API locally using the explicit evaluation Compose file.

Self-Hosting

Run the full stack with accounts, a dashboard, TLS and backups.

Features

Check format support, integration status and automation limits.

Scores and Review

Compare original and saved files and review unresolved issues.

CLI Reference

Use the released commands and understand their output limits.

API Reference

Authenticate, submit a scan, poll its progress and retrieve results.

Troubleshooting

Check API and worker health and collect safe diagnostics.

A practical document workflow

  1. Scan an original document you are authorized to process. Start with a synthetic file while evaluating a deployment.
  2. Review the issues found. Supported checks and available fixes differ between PDF, Office, LaTeX, media and web content.
  3. Run remediation where supported, then compare the saved output with its original. Applied changes and verified fixes are separate counts.
  4. Resolve manual findings, inspect generated content and approve only the output you have reviewed. Download or integration writeback depends on the applicable workflow and authorization.

OCR can add a searchable text layer to supported scanned PDFs. Structure-tree remediation is a separate operation. Neither establishes complete accessibility. See the format-by-format guide and review workflow.

Integrations and deployment choices

Connector maturity and supported operations vary. Consult the integration status reference before promising scanning, remediation or writeback for a particular LMS. A connector's presence does not establish a complete tested user journey.

Core is free self-hosted software. The hosted pricing page covers managed plans and processing allowances. Self-hosting, contracts and provider selection require an institutional privacy review; no hosting choice alone establishes FERPA compliance. See the privacy policy and LMS AI authorization guide.

Frequently asked questions

Is Aelira Core free to self-host?

Yes. The engine is AGPL-3.0 and the CLI is MIT. Core has no paid feature tier or Aelira per-page licence fee. You operate the infrastructure and pay any providers you enable. Operational limits and administrator quotas still apply.

Does a high score certify accessibility?

No. Automated scores describe the checks performed, not full WCAG or PDF/UA conformance. Review the saved file, unresolved findings and generated descriptions, and perform appropriate manual and assistive-technology testing.

Does self-hosting keep AI processing local?

Only when you deliberately configure local providers and control network access. Core supports local and cloud providers; its default provider choice is none. Review fallback routes, storage, logs, backups and access controls before making a data-residency claim.

How accurate are generated descriptions and captions?

Quality depends on the source, context and configured model. These guides do not publish a general accuracy percentage. Check descriptions against the actual image and learning objective, and captions against the audio, including meaningful non-speech sounds.

U.S. ADA Title II planning

DOJ lists April 26, 2027 for state or local governments with a population of at least 50,000, and April 26, 2028 for smaller public entities and special district governments. A university's student enrolment does not determine its deadline. Applicability, exceptions and continuing obligations need institution-specific assessment.

Use the DOJ first-steps guidance with your institution's accessibility and legal teams. These product docs are not legal advice. For captions, W3C guidance explains why automated output needs accuracy checks and correction.