API Partner Program — Building Alpha Linux Solutions Together
API never intended to sell Alpha on its own. The Partner Program gave systems integrators, resellers, software vendors and hardware makers the roadmaps, documentation and engineering access they needed to build complete Alpha Linux solutions, and it was the main route by which API boards reached end customers.
Why a partner program
Alpha Processor, Inc. was a component and platform company. It designed motherboards such as the UP1000 and UP2000, sold 21264-family processors and modules, and invested heavily in Alpha Linux. What it did not do was build and support finished systems for thousands of individual buyers. That required a network of companies closer to the customer: integrators who could assemble and test systems, resellers with regional reach, software vendors whose applications made the hardware worth buying, and hardware makers whose cards, storage and chassis had to work alongside API boards.
The pitch to prospective partners was straightforward. Alpha offered a genuine performance advantage, particularly in floating-point and memory-intensive work; Linux offered a low-cost, open operating system; and API offered the glue between them. For a partner, that combination meant a differentiated product in a market otherwise crowded with commodity x86 systems.
Partner tiers
Partners were grouped by the role they played in bringing a solution to market. The categories below reflect how the program was organised in practice.
| Tier | Who | Typical role | What API provided |
|---|---|---|---|
| Systems integrators | Companies building complete workstations, servers and clusters | Design, assemble, validate and support finished Alpha systems | Boards and processors, pre-release hardware, integration guides, direct engineering contact |
| Resellers | Value-added and regional resellers | Sell and service Alpha systems to end customers | Product training, sales materials, configuration guidance, escalation path |
| ISVs | Independent software vendors, including compiler, tools and application developers | Port, tune and certify software on Alpha Linux | Development systems, porting assistance, performance tuning advice, joint certification |
| IHVs | Independent hardware vendors of cards, storage, memory and chassis | Ensure their products work reliably with API platforms | Board documentation, compatibility testing, driver support contacts |
Benefits of membership
The value of the program lay mostly in information and access rather than discounts alone. Partners could plan products around API's schedule instead of reacting to it.
- Roadmaps. Advance visibility of upcoming boards, processor speed grades and platform changes, typically shared under non-disclosure, so partners could align their own product launches.
- Documentation. Detailed board specifications, firmware notes, memory and power guidelines, and design information beyond what was published for end users.
- Engineering access. A route to API engineers for integration problems, early access to evaluation hardware, and help debugging issues that sat between hardware, firmware and the operating system.
- Co-marketing. Joint announcements, shared trade-show presence, listings in API partner directories, and opportunities to appear in case studies.
- Supply. Predictable access to processors and boards, backed by API's relationships with Samsung and Compaq.
Alpha Linux cluster and HPC partners
The most active part of the program in practice was high-performance computing. The 21264's floating-point throughput and memory bandwidth made it one of the strongest processors of its era for scientific codes, and Linux clusters, groups of commodity nodes connected by fast networks, were becoming the dominant way to build affordable supercomputers. Alpha Linux clusters appeared in university research groups, government laboratories and engineering companies.
Cluster integrators were therefore central partners. They combined API boards with high-speed interconnects, cluster management software and optimised maths libraries, and delivered systems ready for parallel workloads. ISV partners contributed compilers and numerical libraries tuned for Alpha, which often made the difference between a respectable benchmark and a leading one. IHV partners supplied the network adapters and storage needed to keep the nodes fed with data.
How the pieces fitted together
A typical cluster deal might involve API hardware, an integrator doing the build and burn-in, a software partner supplying the compiler and message-passing libraries, and a reseller or the integrator handling the customer relationship. API's role was to make sure each of those parties had the documentation and engineering support they needed, and to step in when a problem crossed boundaries.
Our partners are the ones who turn a fast chip into a working system. Everything in the program is designed to make that job easier.
An API company spokesperson
Joining the program
Becoming a partner was deliberately lightweight. A company described its business, the markets it served and the Alpha products it planned to build or support, and API matched it to the most appropriate tier. Partners who committed to specific product plans or volume could move to a closer relationship with more engineering time and earlier access to hardware.
- Submit a partner application outlining the company, its customers and its intended Alpha offering.
- Agree the partner terms and, where roadmaps were involved, a non-disclosure agreement.
- Receive evaluation or development hardware and access to partner documentation.
- Complete integration or certification work, with API engineering support as needed.
- Launch, often with a joint announcement and a listing in the partner directory.
Partners were expected to keep API informed of customer issues they could not resolve, which in turn fed back into firmware updates, documentation fixes and board revisions. Many of the fixes described on the technical support page started as reports from partners in the field.
Later directions
As API created its API NetWorks unit and moved toward dense servers and communications silicon, the partner model extended to equipment makers interested in HyperTransport. The February 2001 HyperTransport announcement shows that shift in progress. Other partner and product announcements can be found in the press archive, and the company overview places the program in the wider history of API.