Kubernetes Runtime

Real Kubernetes. Not containers pretending to be Kubernetes.

LinqProtocol runs on the same container orchestration system that powers Google, Spotify, and Airbnb. Deploy multi-pod applications with proper scheduling, networking, and observability.

Why Kubernetes

Industry standard for a reason

Kubernetes is the most widely adopted container orchestration platform in the world. It's battle-tested at scale by virtually every major technology company.

When you deploy on LinqProtocol, you're deploying on real Kubernetes clusters - not simplified container runtimes that break when you need advanced features.

5.6M+

developers use Kubernetes

96%

of organizations have adopted or are evaluating

15+

years of production experience

Capabilities

Everything you expect from Kubernetes

Multi-Pod Deployments

Run applications with multiple containers that communicate and scale together. Web server + database + cache in a single deployment.

Persistent Volumes

Attach persistent storage to your pods. Data survives container restarts and redeployments.

Resource Limits

Set CPU and memory limits. Kubernetes enforces them and prevents noisy neighbors from affecting your workloads.

Health Checks

Liveness and readiness probes ensure your apps stay healthy. Automatic restarts on failure.

Rolling Updates

Deploy new versions without downtime. Kubernetes gradually replaces old pods with new ones.

Namespace Isolation

Each deployment runs in its own namespace. Workloads can't see or affect each other.

LPStack

Enterprise-grade tooling built in

Kubernetes

Kubernetes

Container orchestration. Pod scheduling. Service discovery. The foundation.

Flux

FluxCD

GitOps-based delivery. Helm charts for reproducible deployments.

Longhorn

Distributed block storage for Kubernetes. Persistent volumes with replication and snapshots.

Lets Encrypt

Cert-Manager

Automatic TLS certificate provisioning and renewal via Let's Encrypt.

Cloudflare Tunnels

Public ingress without opening provider-side inbound ports.

Prometheus

Metrics Pipeline

Resource time-series data surfaced in the dashboard.

Grafana

Loki

Workload logs available beside service status and diagnostics.

KubeVirt

Run virtual machines alongside containers. Full VM isolation when needed.

Istio

Istio Ingress

Routes platform hostnames to the correct deployment services.

Security

Secure by default

Namespace Separation - Every deployment gets its own Kubernetes namespace
Service Discovery - Workloads use Kubernetes DNS and service names inside the deployment
Explicit Exposure - A port becomes public when a platform route is created for it
Resource Quotas - CPU and memory limits prevent resource exhaustion
Workload Boundaries - Deployment resources run as namespace-scoped Kubernetes workloads

Future updates will add VM-level isolation via KubeVirt for even stronger security boundaries.

Comparison

How we compare to 'decentralized compute'

FeatureLinqProtocolOther DePIN Projects
Kubernetes
Real K8s clusters
Basic containers or custom runtimes
Multi-pod apps
Supported
Single container only
Persistent storage
PVCs
Ephemeral only
Service discovery
Kubernetes DNS
Varies
Observability
Dashboard metrics + Loki logs
Varies

Ready to deploy on real Kubernetes?