Buyer's Guide_
GPU Deployment Providers: Compare Scope and Evidence_
Start by defining the result you need from the provider. Mounting customer-supplied servers, installing a cable package and handing over physical records are different work from facility electrical or cooling installation, OEM bring-up and workload acceptance. Put the required tasks and accepting parties in the scope before comparing bids. A useful proposal identifies what is included, what remains with others, which inputs must be ready and what evidence the receiving team will get. The questions below help you review that proposal without assuming a GPU product name, a large rack count or a broad deployment label proves the provider can perform every part of the project.
How to evaluate a provider_
A defined work package
Ask each bidder to identify the result it is pricing: mounted equipment, a physical cable installation, defined verification records or a separately commissioned system. Compare the included tasks, exclusions and accepting party line by line. A quote for mounting and labeling cannot establish the same deliverable as a complete system-acceptance package. The buyer needs an explicit work boundary before comparing price or schedule.
The actual system and installation authority
Provide the complete OEM system model, configuration and applicable document revisions. Ask which work the provider is authorized to perform and how it interfaces with the designated OEM or specialist teams. A GPU family name or a vendor logo is insufficient evidence of installation authority, supported configuration or experience. The named-product example below shows why this question matters.
People and project evidence
Ask who is proposed for the work, who supervises it and what availability has actually been confirmed. Request relevant references or redacted evidence with publication or disclosure permission. Distinguish work delivered by the bidding company from an individual team member's earlier experience. A generic rack total does not explain what that party did, which configuration was involved or what the customer accepted.
Checks and acceptance ownership
Specify what the handoff must demonstrate and who accepts it. Visual inspection, equipment identification and cable-label records differ from instrument certification, fabric validation and workload testing. If formal tests are requested, ask for the confirmed personnel, instruments, method, acceptance criteria and report coverage. Identify the qualified owner of work outside the physical installation package rather than assuming one installer performs every test.
Inputs, dependencies and change decisions
Confirm who supplies equipment and materials, approves drawings, obtains site permissions and resolves missing or changed inputs. Ask which dependencies must be released for the quoted work and who can authorize a change. A scheduled delivery or an access badge does not establish that the workfront is ready. Keep facility, handling, OEM and installation responsibilities visible in the proposed package.
A reviewable schedule and handoff
Ask what assumptions support the proposed work window, which resources are confirmed and how changed access or missing inputs affect it. Agree the required asset locations, endpoint records, drawing revisions, defect list and accepting contact before work starts. Review promises against the actual proposal; this guide supplies no universal crew size, deployment duration, response time or production-ready guarantee.
Match the provider to the work_
Leviathan Systems
Leviathan Systems is a Miami, Florida-based infrastructure services company operated by Leviathan Systems Group LLC, a Delaware limited liability company. It supports US and European projects subject to scope, site requirements and team availability. Leviathan offers equipment receiving and preparation, rack assembly, cabling, hardware burn-in, physical deployment, relocation and scheduled physical support. Identify the appointed equipment/material supplier, approved configuration, quantities and delivery responsibilities before agreeing the physical work. Liquid-side work, facility trades and licensed engineering remain outside the physical IT scope. BIOS, firmware, IP configuration, OS imaging and complete software commissioning are not standard services. Burn-in procedures, duration, available conditions, qualified personnel, records and acceptance are defined for the engagement. Handling, transport, any permitted cord task and planning outputs need their own confirmed requirements.
OEM installation and specialist teams
Confirm the installation and service rules for the system being supplied. For example, NVIDIA's DGX B200 installation guidance requires NVIDIA partner network personnel or NVIDIA field service engineers. That statement applies to the named product; it does not establish Leviathan's authorization or prescribe the rules for every OEM server. Ask the supplier which party owns restricted installation, system bring-up and subsequent acceptance, and how the agreed physical work is handed to that party.
Facility and handling parties
Identify who receives the shipment, controls site access, approves equipment movement and owns facility interfaces. Equinix's published IBX inbound shipment process, for example, assigns delivery-vehicle-to-loading-dock movement to the carrier rather than IBX personnel. This is one operator's boundary, not a universal shipping rule or acceptance of a particular heavy shipment. Obtain the actual facility arrangement and qualified handling plan. A physical installation quotation should not silently absorb freight, lifting, floor approval, electrical or cooling responsibilities that belong elsewhere.
The manufacturer and operator examples above were checked on October 15, 2026. Confirm the applicable instructions and operator approval for the actual system and site; neither example qualifies a proposed crew or releases its work.
Verify the claim at the level it names
A credential, an employer relationship, a completed project and permission to install a particular product are different claims. Start with the statement the bidder is asking you to rely on. Identify the person or legal entity, the credential or work asserted, its issuer or evidence owner, and the task for which it is offered. A genuine record can still be irrelevant to the proposed work. Do not turn a verified individual credential into a company-wide certification or treat a former employee's project as the bidding company's delivery history.
Use an issuer's verification channel for a claimed credential when one is available. BICSI, for example, provides a credential-holder directory and credential verification to check an individual's certification status. That is a concrete way to check a claimed BICSI credential; it does not make a BICSI credential mandatory for every project or establish a particular company's certification, availability or authority to install an OEM system. Request the holder's accurate credential identity and permitted verification information. If the available record is inconclusive, ask the holder or issuer for a resolution rather than asserting that the person has no credential. [B1]
Then check applicability and delivery responsibility separately. Does the verified credential concern the proposed task, and is that person actually proposed for it? Who employs or engages the person for this work, who supervises the work, and what availability has been confirmed? For a company reference, ask what that company delivered, under which configuration and scope, what the recipient reviewed and what the evidence leaves out. Redaction should preserve enough context to answer those questions while respecting the owner's disclosure limits. No private credential, customer or personnel record is requested for publication by this guide.
Fictional EX-QP161 compares three evidence returns for three different claims. The first supports an individual credential's stipulated status only. The second supports a person's stated earlier participation but not the current bidder's company delivery claim. The third names an OEM relationship without returning its product or task scope. These are one limited credential agreement, one attribution mismatch and one unresolved authorization claim, not three qualified contractors or three failed applicants.
Keep the conclusion as narrow as the evidence. A training attendance record is not automatically an exam certification; a certification is not automatically the installation authorization required for the purchased system; a verified role is not confirmation that the person or tools are available for this visit. Ask for the missing proposition, not another copy of a logo. For sovereign-cloud work, identify the actual project and jurisdiction-specific eligibility, access, personnel, information-handling and subcontracting requirements and their accepting authorities. General credential evidence does not resolve those requirements, and this guide supplies no sovereign-cloud eligibility decision.
| Fictional claim and return | What the stipulated evidence supports | What remains to be established |
|---|---|---|
| QP-1: Person A is claimed to hold Credential C; the stipulated issuer response confirms A's current C status. | One individual credential-status agreement. The example does not perform an actual directory search or verify a real person. | Relevance to the task, actual assignment and availability, employer or engagement relationship, supervision and any separate OEM or site requirement. |
| QP-2: Bidder B claims company delivery experience; its permitted reference describes Person A's work while employed by Company D. | The supplied reference concerns A's earlier participation. It does not establish that B delivered that project. | An accurately attributed company reference, or an explicitly individual-experience claim with the actual role and limits retained. |
| QP-3: Bidder B displays an OEM partner statement but supplies no applicable product, activity or performing-party scope. | The submitted statement does not settle whether the proposed task is within the asserted relationship. | The supplier or OEM's applicable requirement and evidence identifying the permitted product, tasks and performing party. No authorization is inferred from the logo. |
Original fictional three-claim comparison. One limited agreement, one attribution mismatch and one unresolved claim. No actual credential search, personnel judgment, company qualification, certification requirement or installation permission.
Evaluate Rubin and AMD bids against the supplied system
Product-specific due diligence starts with the supplied system and the proposed activity, not with an accelerator brand. Ask for the complete model and configuration, delivery state, applicable document edition, requested physical work and handoff. Compare the bidder's evidence with that combination. A relevant earlier project can explain experience while still leaving a different generation, OEM chassis, cooling interface or restricted service task unproven. The older named B200 example above remains a B200 example; it is not an installation rule for Rubin or AMD equipment.
NVIDIA's October 2026 DGX Vera Rubin hardware guide describes a rack-scale assembly containing compute trays, NVLink switch trays, a passive copper cable backplane, power shelves, a bus bar and liquid-cooling manifolds. That is a useful boundary for a Rubin contractor discussion: external IT cabling, an internal rack component service task and a liquid-side connection are different proposed activities, even when one bid calls them all rack installation. Require the supplier's actual division of work and the applicable product instructions for each activity. The hardware description alone does not identify an authorized contractor or a field method. [R1]
For an AMD example, Supermicro's AS-4126GS-NMR-LCC product page describes a liquid-cooled MI355X system and states an onsite-service requirement for liquid cooling. Its MNL-2801 family manual is addressed to professional system integrators and PC technicians and limits installation and maintenance to certified service technicians. These are requirements and descriptions for the named offering and manual, not proof that a general AMD-related credential, an air-cooled server reference or any particular company satisfies them. Obtain the applicable supplier interpretation and performing-party evidence for the ordered configuration. Do not infer which certification the manufacturer accepts from the generic word certified. [S1, S2]
Fictional EX-OQ162 applies those distinctions to three bid returns. R-A uses a B200 project reference to support an unqualified Rubin rack-installation line; its actual Rubin tasks and authority remain unresolved. A-A identifies the named Supermicro system and separates physical IT work from liquid-side work, but returns no applicable service-party qualification evidence. A-B supplies an air-cooled server reference under a different model and treats it as qualification for the liquid-cooled request. The comparison has one named model association, two evidence-applicability gaps and no contractor approved for execution. The named association is useful evidence without being an award decision.
Ask the bidder to revise the specific unsupported claim or work line. A Rubin scope can be returned as separately defined external connections, supplier-held internal tasks and facility or cooling interfaces, each with its own inputs and receiving owner. An AMD scope can identify the purchased OEM server, the applicable manual and the party proposed for each installation or service activity. The buyer then compares like tasks and the evidence actually returned, rather than treating all GPU deployments as interchangeable. Leviathan's existing physical service description and exclusions on this page remain the basis for a scope discussion; the examples add no OEM affiliation, certified personnel, liquid-side service or resources to that offer.
| Fictional bid return | Comparison supported by the return | Specific unresolved decision |
|---|---|---|
| R-A: a DGX B200 project reference accompanies a line for DGX Vera Rubin rack installation. | The evidence names a different system. No Rubin activity split, applicable instructions or performing-party authority has been returned. | Define the Rubin tasks and evidence required for them. Do not transfer the B200 installation condition to Rubin or infer authority from the earlier project. |
| A-A: the request and bid both identify AS-4126GS-NMR-LCC, with physical IT tasks and liquid-side tasks assigned to separate proposed parties. | One named model association and an explicit task boundary. The model match does not verify either proposed party's qualification or availability. | Obtain the supplier's applicable service requirements and the evidence for each actual performing party, along with the site/interface prerequisites. |
| A-B: an air-cooled server reference under another OEM model is offered as sufficient qualification for the same liquid-cooled request. | The evidence does not establish the claimed model and activity applicability. It may describe experience without answering this service requirement. | Return a task-relevant reference and the applicable qualification evidence, or narrow the claim. No rejection of the person's other skills or instruction to perform liquid work follows. |
Original fictional comparison only: three returns, one limited named-model association, two applicability gaps and zero execution approvals. No actual bidder, quotation, delivered system, supported configuration, credential or service availability has been verified.
Primary references for the added evidence comparisons
- B1: BICSI: Certification Holder Directory — Public description of individual credential-status verification only. No individual search, private credential data, certification requirement, company qualification, assurance of performance or standards clause adopted. New reference checked 20 October 2026.
- R1: NVIDIA DGX Vera Rubin: Hardware — October7,2026 hardware page, complete rack component kinds in the opening paragraph only. No operating, power, cooling, handling, geometry, performance, service method or contractor-authorization rule transferred. New reference checked 20 October 2026.
- S1: Supermicro AS-4126GS-NMR-LCC: named system and liquid-cooling service dependency — Product heading and introductory MI355X liquid-cooled system/onsite-service statement only. No dimensional, weight, electrical, operating, catalog availability, supplied-resource, actual eligibility or field method claim adopted. New reference checked 20 October 2026.
- S2: Supermicro MNL-2801: Preface and intended personnel — Dated August2025 manual preface only: named model family, audience and certified-service-technician requirement. No certification scheme inferred, no actual person's eligibility verified, no installation chapter, procedure or warranty interpretation adopted. New reference checked 20 October 2026.
Questions_
Which GPU deployment provider is best for my project?
Choose against the exact delivered system, permitted work, required evidence, site conditions and availability. Ask each provider to define its scope and show relevant company or individual experience accurately. This guide does not rank providers or verify a particular contractor's credentials, references or current projects. A provider is a fit only for the work it is actually qualified and contracted to perform.
Does Leviathan provide complete GPU cluster commissioning?
Leviathan offers equipment receiving and preparation, rack assembly, cabling, agreed hardware burn-in, physical deployment, relocation and scheduled physical support. Each engagement identifies the purchased stages, inputs and handoff records. Identify the appointed equipment/material supplier, approved configuration, quantities and delivery responsibilities before agreeing the physical work. Liquid-side work and facility electrical or structural work remain excluded. BIOS, firmware, IP configuration, OS imaging and complete software commissioning are not standard services. Burn-in requires the exact equipment, customer/OEM-approved procedure, agreed duration, suitable conditions, qualified personnel, authorized tools, recorded observations, exception handling and acceptance criteria. Any permitted cord task requires its own confirmed scope. Physical completion is handed to the nominated customer/OEM/platform owners.
What should I verify before choosing an installation contractor?
Verify the complete equipment configuration, included tasks and exclusions, applicable OEM and site requirements, proposed personnel and availability, customer-provided inputs, named acceptance owner and agreed handoff. Request the actual evidence needed for any specialist method or capability. The due-diligence questions above are evidence to seek from the bidder, not claims that Leviathan already has every resource or credential.
What should I send Leviathan for an initial scope discussion?
Send the site location, complete system models and quantities, proposed work window, physical tasks, available approved drawings or endpoint records, access/handling constraints and requested handoff. State who supplies equipment and materials and who owns facility, cooling, OEM and platform acceptance. Tell us about your project, and our team will follow up to discuss the scope, requirements and availability.
Discuss Your Infrastructure Project_
Tell us about your project, and our team will follow up to discuss the scope, requirements and availability.
Discuss a ProjectEmail Project Scope