Source server components and replacement hardware.

Not every requirement is a whole system. Expansion, replacement and spare-parts requests are handled the same way: send the part list, receive comparable quotations.

Describe What You Need Configure a Server

Not sure what to specify?

A part number helps, but it is not required. Share the target system, purpose, quantity, and any compatibility limits you know.

Memory expansion for an installed server

Replacement drives and caddies

NICs, accelerators, rails, or power supplies

What you can source

Memory modules, including matched population kits
SSDs and NVMe drives across endurance classes
Nearline and enterprise HDDs
GPUs and accelerator cards
NICs, SmartNICs, DPUs and HBAs
RAID and storage controllers, cables and backplanes
CPUs and processor upgrade kits
Rails, bezels, power supplies and replacement spares

Send a part list or a BOM

You can paste a list of part numbers and quantities directly into a request, or attach an existing BOM, quote or spreadsheet. Attachments are stored privately and are only used to source the requirement.

Part numbers are useful, but the target system matters just as much. Stating the server model or platform a component has to fit lets an incorrect or superseded part number be caught before it is ordered.

Compatibility details worth including

Server or chassis model the part must fit
Existing configuration the part has to match
Firmware or generation constraints already in place
Whether an equivalent or superseded part is acceptable
Quantity now, and whether spares are wanted

How 46 Systems handles component requirements

Component requests are normalized into a clear line-item list and sourced against availability and lead time. Where a part is constrained or end-of-life, equivalents can be requested explicitly rather than substituted silently.

What helps us quote accurately

Ordering memory without checking the platform's population rules
Reusing a superseded part number from an old BOM
Omitting the chassis model on drive and caddy requests
Assuming a GPU fits the power and slot budget of an older server
Leaving no spares on components with long lead times

Server SourcingRack, GPU, storage-heavy and custom server requirements.StorageCapacity and performance storage specified for quotation.NetworkingEthernet, InfiniBand, NICs, DPUs and cluster fabrics.GPU & AI InfrastructureTraining, inference and HPC systems sized around the workload.Rack & Infrastructure ProjectsMulti-system, cluster and rack-level requirements.Infrastructure SourcingHow 46 Systems turns a requirement into quotation options.

Send your part list.

Paste the list or upload a BOM, and we will source it.