About Alpha Processor, Inc. — Company Overview
Alpha Processor, Inc. (API) was founded in 1998 by Samsung and Digital Equipment Corporation to take the Alpha 64-bit RISC architecture out of high-end proprietary systems and into mainstream motherboards, processors and Linux solutions. From its headquarters in Concord, Massachusetts, it grew from an Alpha supplier into a platform and networking silicon company.
Origins
By the late 1990s, Alpha had a clear reputation: it was the fastest general-purpose microprocessor available, and it was also expensive, hard to buy outside Digital's own systems, and perceived as a niche product. Digital needed volume to justify continued investment in the architecture. Samsung, which had become a manufacturing partner for Alpha chips, wanted a larger market for the parts coming out of its fabs.
Alpha Processor, Inc. was the answer both companies agreed on. Formed in 1998, API was an independent company with its own management and engineering staff, backed by Samsung and by Digital, whose interest passed to Compaq when Compaq acquired Digital that same year. Its charter was to build a merchant market for Alpha: sell processors and modules, design reference and production motherboards, and work with third parties to create a real ecosystem of Alpha-based systems.
Headquarters and team
API set up in Concord, Massachusetts, a short drive from the historic heart of Digital's engineering operations along Route 2 and the Interstate 495 corridor. That location was a deliberate choice. It let the company recruit engineers who had spent years on Alpha processors, chipsets, firmware and compilers, and it kept API close to the Digital and Compaq groups still responsible for the core architecture.
The engineering team combined board designers, signal-integrity and validation specialists, firmware developers familiar with SRM console and AlphaBIOS, and Linux kernel and toolchain contributors. Unlike a traditional systems vendor, API wanted its work to be reused by others, so reference designs, documentation and board support code were treated as products in their own right.
Mission
API's stated mission was to make Alpha the performance leader in mainstream computing rather than a curiosity at the top of the market. In practice, that meant a handful of concrete goals:
- Lower the cost of entry by using industry-standard form factors, memory and I/O wherever possible.
- Make Linux a first-class operating system on Alpha, alongside the established Tru64 UNIX and Windows NT options.
- Give integrators and OEMs a dependable supply of processors, modules and boards, with Samsung as a second source.
- Build a partner community able to deliver complete Alpha solutions, from single workstations to large clusters.
Timeline, 1998–2001
| Year | Milestone |
|---|---|
| 1998 | Alpha Processor, Inc. formed by Samsung and Digital; Compaq assumes Digital's role after its acquisition of Digital. Headquarters established in Concord, Massachusetts. |
| 1999 | UP1000 single-processor ATX motherboard for the 21264 ships, bringing the EV6 bus and Slot B processor modules to an industry-standard form factor. Strong focus on Alpha Linux and technical computing. |
| 1999–2000 | UP2000 dual-processor board introduced for servers and compute clusters; faster 21264A processors adopted across the line. |
| 2000 | API creates the API NetWorks business unit to pursue high-density servers and networking infrastructure; the company later adopts the API NetWorks name. |
| 2000–2001 | CS20, a dense rack-mount dual-Alpha server, targets clusters and service providers. |
| 2001 | API NetWorks announces support for AMD's HyperTransport technology and develops HyperTransport silicon, including an HT-to-PCI bridge. |
For the HyperTransport announcement itself, see the February 2001 press release. Other announcements are collected in the news and press archive.
Business lines
Processors and modules
API sold Alpha 21264 and 21264A processors, both as components and on processor modules that bundled the CPU with its backside cache. Customers ranged from small integrators to research labs building their own systems. The microprocessors overview summarises the chips involved.
Motherboards and platforms
The UP-series boards were API's most visible products. Single- and dual-processor designs used ATX-class layouts, standard PCI slots and commodity SDRAM, so an integrator could build an Alpha system with familiar chassis, power supplies and storage.
Linux systems and solutions
API worked closely with Linux distributions, compiler vendors and application developers to certify software on its hardware. Alpha Linux clusters became one of the most successful niches, as the 21264's floating-point performance made it attractive for scientific and engineering workloads.
Networking and HyperTransport
The API NetWorks unit extended the company into dense servers and, increasingly, into silicon for networking and communications equipment. HyperTransport bridges were a natural fit for a team with deep experience in point-to-point processor buses.
Culture and engineering
API was small by semiconductor standards, and its culture reflected that. Engineers moved between board design, firmware and customer support, and the company prized quick turnaround on problems reported by partners. Many staff came directly from Digital and brought with them a strong tradition of rigorous validation and openly published technical documentation.
We wanted a customer to be able to open the box, read the manual and have Linux booting on an Alpha the same afternoon.
An API engineer, describing the goals of the UP-series program
The company was also comfortable working in public. API staff participated in Alpha Linux mailing lists, contributed patches, and attended trade shows alongside partners rather than simply exhibiting on their own.
That outward-facing attitude shaped two of API's most important programs. The Partner Program gave integrators, resellers and software vendors roadmaps and engineering access, while the technical support organisation published firmware, memory and installation guidance that customers could use without waiting for a phone call. Both reflected the view that Alpha would only succeed if many companies, not just API, could profit from it.