> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getlilac.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Bare-metal partnerships

> Work with Lilac to connect current or planned bare-metal GPU capacity with suitable customer demand.

If you operate current or planned bare-metal GPU capacity, Lilac can be another route to customers with real infrastructure requirements. We find potential demand, assess whether each opportunity fits the capacity, and provide the software and VM layer between the customer and the machines.

This is a direct capacity relationship. It is separate from the [Kubernetes operator program](/suppliers/operator/overview), which contributes idle cluster capacity to Lilac's shared inference network.

## What Lilac brings

* **Demand discovery.** We look for potential customers through the YC community and our broader AI network.
* **Contextual assessment.** Available company, funding, and workload context helps us assess technical fit and the risk profile of potential demand.
* **Software and VM layer.** We provide the layer that turns compatible bare-metal capacity into an environment a customer can use.
* **Coordination.** We help move a suitable opportunity through technical scoping, commercial alignment, deployment, and support.

<Info>
  Our assessment is contextual diligence, not a formal credit rating. It does not guarantee placement, customer performance, or payment, and it does not eliminate counterparty risk.
</Info>

## How responsibilities divide

| Capacity partner                                    | Lilac                                                 |
| --------------------------------------------------- | ----------------------------------------------------- |
| Operates the hardware and network                   | Finds and evaluates potential demand                  |
| Shares capacity, access, and commercial constraints | Assesses technical fit and available customer context |
| Provides hardware operations and escalation         | Provides the software and VM layer                    |
| Defines remote-hands and support coverage           | Coordinates the technical and support path            |

The technical scope, commercial terms, and support responsibilities are agreed before a deployment moves forward.

## From capacity to deployment

<Steps>
  <Step title="Describe the capacity">
    Share the hardware, topology, volume, region, lead time, and access model.
  </Step>

  <Step title="Find suitable demand">
    Lilac compares the capacity with opportunities coming through its network.
  </Step>

  <Step title="Assess the match">
    We review technical requirements, commercial fit, and available customer context with the capacity partner.
  </Step>

  <Step title="Agree and deploy">
    If the opportunity works for everyone involved, the parties agree the scope and terms before the software layer is deployed.
  </Step>
</Steps>

## What we consider

* Hardware, topology, and volume
* Region, interconnect, and access model
* Lead time, term, and deployment workflow
* Support coverage, remote hands, and escalation
* Customer background, funding context, and workload profile

These inputs help both sides decide whether an opportunity is a good fit. They are not a fixed qualification checklist.

## Talk to us

<Card title="Discuss a bare-metal partnership" icon="calendar" href="https://calendly.com/d/ctcf-c4b-cvv/lilac-chat">
  Share your fleet and timeline. We will start with the capacity you actually have and the customers it could serve well.
</Card>

Or email [contact@getlilac.com](mailto:contact@getlilac.com).

## Related

* [Supplier program overview](/suppliers/overview)
* [Dedicated GPUs for customers](/dedicated-gpus/overview)
* [Suppliers marketing page](https://getlilac.com/suppliers)