Create a Lilac account
Sign up at console.getlilac.com using your email or Google account. Create an organization for your team — this is where you’ll manage clusters, API keys, and revenue.
Use the same organization for all your clusters. You can invite team members later from Settings > Members.
Submit the supplier intake form
Fill out the supplier intake form so we can understand your infrastructure and match workloads to your hardware.We’ll review your submission and follow up within one business day.
Supplier Intake Form
Tell us about your GPU fleet — hardware, location, availability, and capacity.
Book an onboarding meeting
Schedule a 30-minute onboarding call with our team. We’ll walk through the operator installation, help you configure your first GPU pool, and answer any questions.During this meeting, we’ll also upgrade your account to supplier status, which unlocks the supplier dashboard and cluster management features.
Book Onboarding Call
Pick a time that works for you.
Install the operator
After onboarding, you’ll install the Lilac GPU operator in your Kubernetes cluster. The operator handles everything — GPU discovery, workload scheduling, health monitoring, and preemption.See the full installation guide: Operator Installation.
What Happens During Onboarding
During the onboarding call, our team will:- Review your infrastructure — confirm GPU types, cluster topology, and availability windows
- Activate your supplier account — flip your organization to supplier mode, unlocking the supplier dashboard
- Walk through operator setup — help you deploy the operator and create your first GPU pool
- Configure scheduling — set up availability windows so Lilac only uses GPUs when you want
- Test the connection — verify the operator syncs with the Lilac control plane
After Onboarding
Once onboarded, your supplier dashboard shows:- Cluster status — connected, degraded, or offline
- GPU utilization — idle, tenant, and Lilac workload breakdown
- Revenue — real-time token counts and earnings
- Workload history — what ran on your hardware and when

