Monetize your idle compute
Data centers, GPU clusters, and edge nodes - join LinqProtocol and earn LNQ tokens for resources you're not using. Real payments for real compute.
Compute is the new oil. You're sitting on a well.
Right now, millions of CPUs and GPUs sit idle. Data centers run at 30-50% utilization. Edge devices sleep 90% of the time. That's wasted value.
LinqProtocol creates a marketplace where that unused capacity becomes income. You provide compute. Developers pay for it. Smart contracts handle the rest.
All types of infrastructure welcome
Data Centers
Monetize excess capacity during off-peak hours. No minimum commitments - provide what you want, when you want.
GPU Clusters
AI workloads are exploding. GPU providers are in high demand for LLM inference, image generation, and ML training.
Edge Operators
Run compute closer to users. Edge locations can offer lower latency for latency-sensitive applications.
Individual Operators
Have a beefy server sitting in your basement? Put it to work. Earn while you sleep.
From idle to earning
Set Up Infrastructure
Use Linux (with or without virtualization) or Windows/macOS with virtualization enabled.
Register On-Chain
Run the LinqProtocol installer to bootstrap the system, benchmark hardware, and register on-chain.
Receive Deployments
When developers need resources matching your capacity and price, our orchestrator routes deployments to you.
Earn LNQ
Payments flow through escrow. Withdraw your earnings anytime. No invoicing, no 30-day payment terms.
The provider economics
Per-Resource Pricing
Set your own rates for vCPU (per core-hour), Memory (per GB-hour), Storage (per GB-month), GPU (per GPU-hour by class)
Competitive Market
Lower prices attract more deployments. Better uptime builds reputation. Find your optimal balance.
Instant Settlement
Earnings accrue in escrow as you serve workloads. Withdraw to your wallet anytime.
No Middlemen
Direct on-chain payments. No platform taking 30%. Just you, the developer, and the smart contract.
What you need to provide
Infrastructure
- Linux host (with or without virtualization) or Windows/macOS with virtualization enabled
- Run the LinqProtocol installer to bootstrap the full runtime
- Reliable internet connection
- Public IP or ability to run outbound tunnels
LPStack
Our default runtime bundle:
- Kubernetes runtime
- FluxCD for GitOps
- Longhorn storage
- Prometheus/Loki for observability
- Argo Tunnels for secure ingress
On-chain identity
When you register as a provider, your information is stored on-chain:
Wallet Address
Your unique identifier
Capacity
CPU, memory, storage, GPU you're offering
Pricing
Your per-unit rates
Metadata
Location, description, and other info
This registry is public. Developers can query it. Your reputation builds as you successfully complete deployments.
Learn About the RegistryProtected by design
Workload Isolation
Deployments run in isolated Kubernetes namespaces. Containers can't access your host system.
VM Isolation (Coming Soon)
Double-layer isolation with containers inside lightweight VMs for even stronger security.
Network Boundaries
Workloads can only access the network through defined ingress. No access to your local network.
You Control Capacity
Only provide what you're comfortable with. Adjust capacity and pricing anytime.
Provider program status
LinqProtocol is currently in alpha with a curated provider fleet managed by the LinqAI team. We're preparing for open provider onboarding.
What's coming:
- Self-serve provider registration
- LinqProtocol Installer for easy setup
- Provider dashboard and analytics
- Reputation and matching system
Want to be an early provider?
Apply now to join our provider waitlist. Early providers will help shape the program and get priority support.
Apply for Early AccessProvider questions
How do I get paid?
LNQ tokens are paid directly to your wallet via escrow contracts. Withdraw earnings anytime.
What if a workload crashes my server?
Workloads run in isolated containers with resource limits. They can't crash your host system.
Can I choose which workloads to accept?
During the alpha, matching is handled by the orchestrator. Future releases will include filtering options.
What if I need to go offline?
Update your capacity to 0 when you need maintenance. No penalties for planned downtime.
How is reputation calculated?
Reputation will be based on uptime, job completion rate, and developer feedback. Details coming as we finalize the system.