Understanding Axelera product names
An Axelera product name tells you three things at a glance: what it's optimized for, which architecture it uses, and its form factor.
The pattern
Axelera <descriptor> <number><form> — for example, Axelera Embedded 113m.
Descriptor — what it's optimized for
| Descriptor | Optimized for |
|---|---|
| Embedded | space-constrained designs |
| Edge | edge systems and appliances |
| Server | server deployments |
The number and form factor
| Part | Tells you |
|---|---|
| 1st digit | silicon architecture — 1 is Metis; as new architectures arrive, each takes a number here |
| 2nd digit | the optimization lane (matches the descriptor) |
| 3rd digit | relative performance |
| letter | form factor — m M.2, p PCIe, c compute board |
So Embedded 113m = Metis architecture, Embedded, performance tier 3, M.2.
"Optimized for" is a starting point, not a limit
The descriptor tells you where a card performs best — not the only place you can use it. Choose the card that fits your workload. If an Embedded card is the most efficient fit inside a server, use it there.
Architecture vs. product
Metis is the silicon architecture inside today's products; the Embedded / Edge / Server names
are the products themselves. Voyager, our software platform, is unchanged — as are product part
numbers (AX-xxxxxx).
Current range
| Product | Optimized for | Form factor |
|---|---|---|
| Axelera Embedded 110m | Embedded | M.2 |
| Axelera Embedded 111c | Embedded | Compute board |
| Axelera Embedded 113m | Embedded | M.2 |
| Axelera Edge 130p | Edge | PCIe |
| Axelera Server 150p | Server | PCIe |