From deployment
to settlement
LinqProtocol combines the simplicity of modern cloud platforms with the trust guarantees of blockchain. Here's how it all works.
The big picture
LinqProtocol is a marketplace that connects developers (requestors) with compute providers. Smart contracts handle payments and trust. An orchestration layer handles deployment and management.
Choose what to deploy
Template Marketplace
Browse 50+ production-ready templates - LLM interfaces, databases, monitoring tools. Click to deploy.
Aura Code
Use AI-powered development environments to build and deploy from your browser.
Virtual Machines
Deploy full VMs with SSH access for workloads that need a complete OS.
Custom Containers
Deploy your own Docker images with custom configurations. Coming soon.
Configure your deployment
Environment Variables
Set configuration values your application needs - ports, feature flags, external URLs.
Secrets
Provide API keys and database passwords. Encrypted and only injected at runtime.
Resource Plan
Choose CPU, memory, and storage. Plans from Starter to Pro.
YAML Review
Advanced users can review and edit the Kubernetes YAML directly.
Fund your escrow
Here's where blockchain comes in. When you're ready to deploy:
- 1Connect wallet via WalletConnect (MetaMask, Rainbow)
- 2Review cost based on your plan and duration
- 3Sign transaction to create and fund the escrow
- 4Funds lock in the escrow contract
What the escrow does:
- ✓Holds your LNQ until work is complete
- ✓Tracks escrow balance on-chain
- ✓Ensures provider gets paid only for work delivered
- ✓Returns unused funds when escrow expires
The escrow is a smart contract. Anyone can verify deposits, assignments, and earnings on-chain.
Match with a provider
Once your escrow is funded, the orchestrator finds a provider by querying the on-chain registry, matching requirements, and assigning the best fit.
Your workload runs
With a provider assigned, the orchestrator sends deployment instructions, and the provider spins up your containers in an isolated namespace.
What you get:
- •Public endpoint to access your app
- •Logs and metrics in the dashboard
- •SSH access (for VMs)
What the provider runs:
- • Kubernetes cluster with LPStack
- • Your containers in isolated namespaces
- • Observability stack (Prometheus, Loki)
- • Networking stack (Argo Tunnels, Istio)
Monitor your deployment
Dashboard
Status, resource usage, endpoints, funding
Logs
Real-time log streaming. Search and filter.
Metrics
CPU, memory, request rates via Prometheus
Issues
Surface problems automatically
Earn and settle
Provider Earns
As your deployment runs, the provider accrues earnings in the escrow. They can withdraw at any time.
Balance Decreases
Your escrow balance decreases based on resource consumption over time.
Finalization
When escrow ends, provider withdraws earnings, unused funds return to you automatically.
How the layers work together
Dashboard
Web interface where developers browse templates, configure deployments, and monitor apps.
Orchestrator
Control plane that receives requests, matches providers, and manages deployment lifecycles.
Provider Cluster
Kubernetes cluster running the LPStack that executes workloads.
Smart Contracts
On-chain escrow and provider registry that handle payments and identity.
Why this matters
Trust-Minimized
You don't have to trust the provider. The escrow enforces payment rules.
Transparent
All provider info and payments are on-chain. Verify everything.
Portable
Standard Kubernetes. Your workloads can move anywhere.
Cost-Effective
Decentralized providers have lower overhead. Savings pass to you.