Skip to content

Support Definitions, Criteria and Relationships


As mentioned in our announcement, made adjustments to ease the burden on the team, make the meaning “supported” status of an SBC clear to the community and vendors.

Support Status from Lowest to Highest are the following:

  1. EOL
  2. CSC
  3. WIP
  4. Standard
  5. Gold
  6. Platinum

EOL - End of Life

EOL devices are not under active development by any entity or community. Can be removed from Armbian code base at any time. Left as a courtesy in case a community member wants to attempt to resurrect development.

No benefits provided

Community Support

Community Support SBCs are exclusively supported by the community.

No Images are provided for Community Supported SBCs

  • no stable
  • no periodic / nightly
  • users must use Armbian Build Framework to produce an image

Benefits for Community Support

  • pull requests are accepted
  • Armbian team will interact on Github with contributors considered to be acting in good faith
  • periodic / Nightly Debian packages are built and published into Armbian’s community apt repository

Requirements for Community Support

  • patch or component does not break Armbian Build Framework
  • patch or component does not break build of supported or other CSCs
  • generally considered to “work most of the time”
  • generally considered to recieve periodic maintenace from community

WIP - Work in progress

WIP status is for when a maintainer has commited to an SBC, but is not ready to ship stable images.

Benefits of Community Supported SBCs apply to WIP.

Additional Benefits provided for a WIP SBC

  • periodic / nightly CLI images are published by Armbian
  • Armbian will work with SBC maintainer to assure compatiblity within the Armbian Build System
  • eligible for promotion to Standard Support

Criteria for WIP status

  • must satisfy standard support criteria
  • must show active development

Armbian Standard Support

Benefits provided for a Supported SBC

  • Armbian will publish and distribute “stable” CLI images through its mirror network
  • Armbian will publish and distribute “periodic / nightly” CLI and desktop images
  • Armbian will work with SBC maintainer to assure compatiblity within the Armbian Build System
  • Armbian will provide the team’s unique expertise to assist maintainer with general challenges
  • best-effort compensation will be provided to maintainer from the “Armbian Community Fund”

Criteria for Supported

For an SBC to be considered supported:

  • a named individual as “maintainer” along with GitHub ID must be clearly identifed in the Board Configuration File
  • a named individual must commit to providing “best effort” support for their SBC on the Armbian forums
  • maintainer must participate in the Release Process
  • maintainer must sign-off that device has been tested, is stable, and ready for release during release process
  • maintainer must have physical access to the SBC they are supporting

Additional Caveats:

  • If the burden placed on the Armbian team is too high funding maybe needed to assure:
    • R&D bills paid. Failsafe in case Armbian members or a team was hired
    • support bills covered by vendor or end users with crowdfunding campaign
  • supported is not applied to a “board family” or group of related SBCs. It is per SBC
  • a maintainer can support multiple devices but must satisfy all requirements above per SBC
  • any individual can be a maintainer for a standard support SBC
  • missed released will result in immediate forfeit of “Armbian Supported” status and demotion to CSC status unless Armbian team grants exemption

Gold and Platinum Support

Gold and Platinum Support are intended to be business relationships with the Armbian project or team and are out of scope of this document. Please connect with Armbian team for more information.