Step 1
Idle node detected
Finds unused GPU capacity.
Install Lilac once, keep full control of your cluster, and earn from idle capacity.
$ kubectl apply -f lilac-provider.yaml
→ Installing Lilac operator...
→ Detecting idle GPUs...
→ Applying your preemption and payout policy...
✓ Idle GPU nodes ready for paid workloads
Auto-Preempts
GPUs return the moment you need them
One Command
kubectl apply and done
Full Control
Your cluster, your rules
Clear Payouts
Usage-based revenue reporting
Revenue potential
Research shows the average data center runs at just 50% GPU utilization. Enterprise on-prem clusters average as low as 10%. That's thousands of GPU-hours wasted every month.
Small cluster
$4K–9K
est. monthly revenue
8 GPUs · ~50% idle
2,880 GPU-hours wasted
Mid-size cluster
$17K–35K
est. monthly revenue
32 GPUs · ~50% idle
11,520 GPU-hours wasted
Large fleet
$69K–138K
est. monthly revenue
128+ GPUs · ~50% idle
46,080+ GPU-hours wasted
Utilization data from LBNL, CRS, and ACM PEARC 2025. Revenue based on $1.50–3/GPU-hr through optimized model hosting and inference routing.
Features
Enterprise-grade infrastructure with zero operational overhead.
Your workloads always come first. The moment internal demand returns, GPUs are reclaimed instantly — no manual intervention, no downtime, no risk to your production jobs.
kubectl apply and you are live. No agents to manage, no sidecars to configure, no complex onboarding. Lilac runs as a lightweight operator inside your existing Kubernetes cluster.
Your cluster, your rules. Define exactly which pools to monetize and when.
Usage-based revenue with transparent metering and detailed reporting.
Track GPU utilization, earnings, and workload status from one dashboard.
End-to-end encryption with isolated workloads and compliance-ready architecture.
Why Lilac
Purpose-built for GPU operators who want revenue without complexity.
No migration needed. Lilac runs inside your Kubernetes cluster — your GPUs never leave your infrastructure.
Skip months of engineering. Preemption, billing, workload isolation, and demand routing ship out of the box.
Idle GPUs cost money around the clock. Even partial monetization significantly offsets infrastructure spend.
Capacity lifecycle
Your GPUs cycle between your workloads and monetized capacity.
Full control
Lilac only uses capacity you explicitly expose. Reclaim GPUs immediately when internal demand returns.
Onboard once, set policy, and generate supplier revenue from capacity you're already paying for.
No commitment required.