Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

Arm usually does not manufacture the processors that carry its name. It licenses instruction-set specifications, CPU implementations, system IP, software and design tools to semiconductor companies. Those companies create or integrate a system-on-chip (SoC), send the design to a foundry, sell the finished chips and pay Arm a combination of license fees and per-chip royalties.

The important distinction is between an Arm CPU-core license, which supplies an Arm-designed implementation, and an Arm Architecture License Agreement (ALA), which permits a company to design its own processor implementation that complies with the Arm instruction set architecture (ISA). The choice determines engineering responsibility, differentiation, time to market and the shape of the commercial contract.

What an Arm license actually covers

An Arm license is a contract for intellectual property (IP), not a purchase order for finished CPUs. Arm describes its offering as technology building blocks, software and tools for developing silicon chips and specialized computing platforms. A customer selects the rights needed for a product, incorporates the licensed material into a chip design and arranges fabrication through a semiconductor foundry.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The ISA is a behavioral contract

The Arm ISA specifies the instructions a processor understands, the programmer-visible registers, memory behavior, privilege model and other rules that software relies on. It is a specification of behavior, not a physical circuit. Two processors can implement the same ISA while using different pipelines, caches, branch predictors, power controls and manufacturing processes.

Operating systems, compilers and applications target the ISA. The processor implementation translates those instructions into electrical operations. This separation allows an architecture licensee to create a custom microarchitecture while remaining compatible with software built for the licensed Arm ISA.

A CPU core is an implementation

An Arm CPU-core license delivers an Arm-designed processor implementation, usually with documented configuration choices, integration guidance, verification collateral and software support. The customer places that core in an SoC and connects it to memory, graphics, security and other blocks. The customer can configure the options allowed by the contract, but it is not redesigning the core’s fundamental microarchitecture.

System IP, software and tools complete the package

A modern SoC contains far more than a CPU. Depending on the deal, a customer may license interconnect, security components, system controllers, graphics or other system IP, along with software, development tools and technical support. The exact bundle is negotiated; no single Arm license automatically includes every product in Arm’s portfolio.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The three main commercial routes

Arm’s commercial layers are related but not interchangeable. The following comparison describes their usual role; actual rights, prices and restrictions are set in individual contracts.

Route What the customer receives Design freedom Engineering and verification responsibility Payment pattern
Arm Total Access Portfolio access to CPU designs and related technologies Choose among covered products rather than inventing a new Arm-compatible microarchitecture Integration, configuration and SoC-level validation remain with the customer Annual fee; additional royalties and contract terms apply to shipped products
Technology Licensing Agreement (TLA) A specific Arm CPU design or other technology design Use the delivered design within the permitted product and term Integrate and verify the licensed implementation and the surrounding SoC Fixed license fee, normally followed by agreed per-chip royalties
Architecture License Agreement (ALA) Rights to develop a customized CPU compliant with the licensed Arm ISA Highest: the licensee controls its CPU microarchitecture Licensee performs substantially more design, verification and software enablement work Fixed architecture license fee plus royalties under the negotiated contract

Arm Total Access

Arm Total Access is a portfolio arrangement paid for annually. It is intended for organizations that need access to multiple CPU designs or related technologies over time rather than a single, isolated core. The annual structure can simplify access to a changing set of covered IP, but the agreement still defines which products, versions, territories, design starts and manufacturing activities are permitted.

Technology Licensing Agreement

A TLA is a fixed-fee license for one CPU design or another defined technology design. The term can restrict incorporation into new designs or limit the number of concurrent designs. Once a licensed design exists, manufacturing rights are typically perpetual, subject to the contract and any continuing royalty obligations. “Perpetual” does not mean unlimited use of future Arm designs; it generally concerns the completed design covered by that agreement.

Architecture License Agreement

An ALA charges a fixed architecture license fee and lets the customer develop its own highly customized CPU design compliant with the Arm ISA. The customer, rather than Arm, chooses the microarchitecture and must prove that the implementation behaves correctly, meets performance and power targets and integrates with the rest of the SoC.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

An ALA therefore buys freedom, not a ready-made CPU. It can support meaningful differentiation in performance, power efficiency, cache organization or specialized execution features, but it requires a large engineering organization and a longer validation effort. Architecture licensees sometimes also license Arm CPU designs: they may use an Arm core as a complementary processor alongside their custom core, or in chips where their own design is unsuitable.

How a license becomes a finished processor

The path from contract to a product on the market has several distinct stages. Arm supplies IP and enablement; the licensee owns the product design and manufacturing relationship.

  1. Select the rights. The customer decides whether it needs portfolio access, a particular Arm-designed core or an ALA. It also identifies required system IP, software, tools, support and the products or geographies covered by the contract.
  2. Define the chip. Product engineers set performance, power, security, memory and connectivity goals. They determine how many CPU cores are needed and which accelerators, graphics, media engines, input/output controllers and memory interfaces must share the die.
  3. Integrate or design the CPU. A TLA or Total Access customer integrates Arm’s delivered implementation and configures permitted options. An ALA customer designs and verifies its own Arm-compliant microarchitecture. It may still add licensed Arm cores for other workloads or product variants.
  4. Build the SoC. The CPU is connected to memory controllers, interconnect, graphics, security engines, accelerators and power-management logic. Engineers also integrate firmware, boot code, operating-system support and the development tools needed by customers.
  5. Verify the complete design. Verification covers the CPU or licensed core, interfaces between blocks, security behavior, power states, software boot and expected workloads. An architecture licensee carries the additional burden of demonstrating ISA compliance for its custom implementation.
  6. Tape out. After the design is complete, the licensee sends the manufacturing database to a semiconductor foundry. Arm generally does not own or operate the wafer-fabrication step for these customer chips.
  7. Manufacture, package and qualify. The foundry produces wafers; the licensee and its manufacturing partners handle packaging, testing, qualification and supply planning. Any manufacturing rights, approved foundries and reuse limits come from the license contract.
  8. Ship and report. The licensee sells chips or products containing them and reports the covered shipments under the agreement. Arm receives royalties calculated either as a percentage of average selling price or as a fixed amount per chip, depending on the contract.

How Arm makes money without fabricating most CPUs

Arm’s model combines upfront or annual payments with royalties. License fees compensate Arm for access to its architecture, cores, system IP, tools and support. Royalties let Arm participate in the customer’s commercial success after products ship.

Arm’s FY2025 annual-report disclosure describes contract values ranging from “hundreds of thousands to hundreds of millions of dollars.” That is a broad disclosed scale, not a standard price list. The amount depends on the license type, duration and product. Customer-specific fees, royalty rates and minimum commitments are not publicly uniform.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Royalty calculations also vary. A percentage of average selling price can increase Arm’s revenue when a customer sells a higher-value chip; a fixed per-chip amount provides a different economic profile. The applicable definition of a covered chip, reporting rules, minimums and audit rights are contract matters.

This model explains why Arm can earn revenue from chips it neither designs in full nor manufactures. Arm invests in reusable architecture and IP; many licensees reuse that work across product generations and ship large volumes through foundry partners. Arm receives payments at licensing and shipment stages while the customer funds SoC development, fabrication and commercialization.

Contract rights that change the practical value of a license

Two licenses with similar technical descriptions can have very different business value because of their legal terms. Before comparing offers, a customer must examine:

  • Design-start and incorporation rights: whether the IP may be placed in new designs during the contract term.
  • Concurrent-design limits: how many chips or projects may use the licensed technology at once.
  • Manufacturing rights: which foundries, entities, regions and products are authorized, and whether rights to manufacture a completed design continue after the license term.
  • Reuse and derivative rights: whether a completed implementation can be reused in later chips, modified, or transferred within a corporate group.
  • Product and geography scope: the markets, device categories and subsidiaries covered.
  • Support and tool access: the versions of software, verification collateral, updates and technical assistance included.
  • Royalty definitions: the covered products, reporting period, calculation base, minimum payments and treatment of returns or bundled systems.

Arm’s public filings emphasize that terms vary by customer, product, duration and other negotiated conditions. A company should therefore treat published descriptions as a framework, not as a promise about its own contract.

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Choosing between a core license and an architecture license

Choose an Arm-designed core when time and execution risk dominate

A core license is generally the practical route when a company needs a proven CPU implementation, predictable integration work and access to established software and tool support. The customer still has substantial SoC engineering to do, but it avoids creating and validating a new CPU microarchitecture.

Choose an ALA when differentiation justifies the burden

An ALA can make sense when CPU behavior, performance, power efficiency or integration is central to the product strategy and the company can sustain a dedicated processor-design and verification team. The licensee gains control over the implementation but assumes responsibility for design correctness, ISA compliance, toolchain enablement and long-term maintenance.

Use a mixed strategy when products have different needs

Architecture licensees often combine a custom Arm-compliant CPU with licensed Arm cores. A custom core can target a flagship workload, while an Arm-designed core handles complementary tasks, lower-cost products or designs where building another custom implementation would not be economical.

What changed with the Arm AGI CPU

Arm’s 2026 materials describe the Arm AGI CPU as production silicon, with production expected by the end of calendar year 2026. That is an exception to the historical pattern in which Arm primarily supplied licensable IP and customers produced the chips. It does not erase the licensing model: most Arm-based processors remain customer-designed products manufactured through foundry partners, while this announcement represents a newer Arm-produced silicon offering.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Common misconceptions

“An Arm license means Arm built my chip.”

No. A license normally grants IP and related enablement. The customer designs the SoC, selects manufacturing partners and brings the product to market.

“An ISA license includes a finished CPU.”

No. An ISA defines software-visible behavior. An ALA gives permission to create a compliant implementation; it does not deliver the implementation itself.

“Every Arm license has the same royalty rate.”

No. Royalties may be a percentage of average selling price or a fixed amount per chip, and the applicable rate and definitions are negotiated.

“Perpetual manufacturing rights remove every restriction.”

No. Manufacturing rights for a completed TLA design can be perpetual, but contracts can still limit new design starts, concurrent designs, products, territories, foundries, reuse and reporting.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

“An architecture license is always better.”

No. It offers more control and differentiation at the cost of substantially greater design, verification, software and maintenance work. A delivered Arm core can be the better business decision when schedule, staffing or risk matters more than custom microarchitecture.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.