Avalon Media System

Open-source audiovisual repository and access platform with an upstream AWS turnkey deployment.

3 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Terraform

  2. Operated by

    Your team

    Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.

Deployment boundaries by provider
  • AWS: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    avalon-terraform ↗ · Source checked 2026-11-19

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodTerraform
InfrastructureServers / containers
Avalon application and media-processing/storage services provisioned by the project's Terraform scripts. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.
Licensing modelOpen Source / Open Core
Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
LicenseApache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

5 of 12 fields researched (42%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

Avalon v8.2.2 publishes an OmniAuth integration that loads configured providers, includes the SAML strategy and maps the returned identity through its user callbacks. The published source confirms this integration path; the default local-account setup does not enable SSO. Supply and test the institutional IdP, attributes and account mapping.

Avalon v8.2.2 configurable OmniAuth/SAML application login; institution-specific provider configuration required · Source ↗ · Published SAML strategy dependency ↗ · Application sign-in callback ↗ · Provider identity mapping ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The official project publishes a Terraform AWS deployment with application containers, networking, persistent services and initial-admin instructions. It targets low-to-medium traffic. Configure DNS/state, credentials, compatible application/dependency images, storage and email; this is not certification of an arbitrary HA workload.

Avalon AWS Terraform deployment; provisioner and application releases must be version-matched · Source ↗ · Deployment artifact ↗ (main (moving branch); select compatible Avalon/container and Terraform/provider versions) · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The AWS Terraform recipe defaults to a t3.large application/Compose host with a 75 GB root volume, plus separate supporting database/storage resources. These are adjustable recipe defaults for low-to-medium traffic, not a minimum for every media library or a validated 100-user, 1 TB HA design.

Avalon project AWS example allocation; transcoding, derivatives, database, object storage, backups and replicas must be sized together · Source ↗ · Recipe goals and architecture ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Avalon Media System; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

Reviewed upstream v8.2.2 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence.

Avalon Media System upstream application; verify compatibility with the selected package · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (7 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

Avalon application versions and turnkey Terraform versions are separate. Confirm current media-processing dependencies, storage policies and institutional access controls before production use.

Community & maintenance

The reviewed upstream contributor history includes cjcolvar, masaball, Dananji, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Category fit

Archives & collections management
Open-source audiovisual repository and access platform with an upstream AWS turnkey deployment.
Digital asset management
Open-source audiovisual repository and access platform with an upstream AWS turnkey deployment.

Compare within Archives & collections management

  • ArchesOpen-source cultural-heritage inventory and resource-information platform.
    • AWS
    Customer-operated · Open Source / Open Core
  • ArchivematicaOpen-source digital-preservation processing system with an institutional AWS deployment recipe.
    • AWS
    Customer-operated · Open Source / Open Core
  • ArchivesSpaceSelf-hosted archival description and collections management with searchable finding aids.
    • AWS
    Customer-operated · Open Source / Open Core
  • BrowsertrixOpen-source browser-based web archiving and collection-management application.
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • Dataverse Self-HostedInstitutional research-data repository for dataset preservation, metadata, access and citation.
    • AWS
    Customer-operated · Open Source / Open Core
  • DSpace Self-HostedInstitutional digital repository for scholarly works, datasets and cultural collections.
    • AWS
    Customer-operated · Open Source / Open Core
  • Fedora RepositoryOpen-source preservation repository with an AWS Terraform deployment.
    • AWS
    Customer-operated · Open Source / Open Core
  • FormKiQ Archives and Collections Management Directory PublisherConnect archival description, linked metadata, digital collections, curated exhibits, and controlled researcher access in your AWS environment.
    • AWS
    Customer-operated · Commercial Only

Showing 8 of 11 other listings in Archives & collections management. These products address related workflows; read their category-fit notes before comparing scope. See all of Archives & collections management →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • avalon-terraform ↗ · AWS

      Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      Avalon application and media-processing/storage services provisioned by the project's Terraform scripts. Avalon application versions and turnkey Terraform versions are separate. Confirm current media-processing dependencies, storage policies and institutional access controls before production use.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory