Avail Technology company primary sources — 2026-08-12

Primary-source capture for the operator/entity layer above avail.

Source highlights

1) Avail public site

• URL: https://www.availproject.org/
• Useful for: how Avail Technology currently packages the stack for builders and apps.
• Key takeaways:
  • The homepage sells one combined system rather than a narrow DA product: Avail DA, Nexus, deposits, and atomic execution all sit under one Avail-controlled entry shell.
  • The copy frames the company as enabling any dApp to go multichain without rebuilding anything, which is a routing-and-defaults claim, not just an infrastructure claim.
  • The site also highlights connected chains, active validators, and staked AVAIL, reinforcing that Avail is presenting the live network plus the app-facing multichain shell together.

2) Avail Mainnet Terms

• URL: https://www.availproject.org/terms
• Useful for: the strongest current operator-boundary language.
• Key takeaways:
  • The terms are explicitly between the user and Avail Technology Limited, incorporated in the DIFC.
  • The terms say mainnet is designated and operated by us, which is the sharpest current primary-source statement that a named company sits at the practical operator boundary.
  • Node Rules, Node Software, and Node Hardware Requirements are defined by reference to Avail-controlled materials.
  • Operators must use the provided software and system images, and the company reserves the right to object to modified or forked node software in connection with mainnet participation.
  • The terms also define Network Companies, which suggests a broader entity shell above the single website brand.

3) Avail node repository README

• URL: https://raw.githubusercontent.com/availproject/avail/main/README.md
• Useful for: implementation stewardship and release workflow.
• Key takeaways:
  • The repo calls itself the Official Client for the Avail blockchain.
  • It publishes supported SDK paths, operator run instructions, and binary-signature verification steps under the Avail brand.
  • The README reinforces that the main implementation, release, and operator path are still first-party and centralized enough to matter as an entity boundary.

4) Announcing the Avail Foundation

• URL: https://blog.availproject.org/announcing-the-avail-foundation/
• Useful for: the emerging foundation-versus-company split.
• Key takeaways:
  • Avail said the Avail Foundation would be established in Switzerland.
  • The announcement says IP related to Avail DA, Avail Nexus, Avail Fusion, and related protocol components will transition to the foundation over time.
  • That makes the current state legible as a transitional company/foundation map rather than a cleanly foundation-owned public-good protocol today.

Bottom line

The strongest operator read today is: Avail Technology is still the named company boundary for live mainnet participation terms, node-software stewardship, and app-facing routing/package defaults, while the Avail Foundation is the declared future stewardship destination for protocol IP.