Pertisk.
Open infrastructure for Kubernetes.
Immutable node OS, QEMU/KVM control plane, native cluster ops, self-hosted Git with CI and registry, and an HTTP/3 edge proxy — open source from pertisktech.
Open source
Five projects. One stack story.
From the hypervisor and node OS, through desktop ops and self-hosted Git + CI + registry, to the edge proxy that fronts your services — each with GitHub, docs, and (where available) a live demo.

Pertisk KOS
Immutable Kubernetes OS, API-only.
An immutable, API-only Kubernetes node OS written in Rust — plus a management plane for HA clusters on Proxmox, ESXi, Nutanix AHV, and Pertisk VMs.
- Rust
- containerd
- kubelet
- gRPC

Pertisk VMs
QEMU/KVM control plane — API, CLI, and UI.
A Rust virtualization stack: pertiskd runs guests on QEMU or Cloud Hypervisor, with clustered HA, replica storage, live metrics, and Terraform export. KOS uses it as provider kind pertisk-vms.
- Rust
- QEMU / OVMF
- Cloud Hypervisor
- Axum

PTKublet
Native desktop for live Kubernetes work.
A Tauri 2 desktop app with a Rust sidecar and React UI — dashboards, YAML, logs, exec, and WebSocket watches in one place.
- Tauri 2
- Rust / Axum
- React
- kube-rs

Pertisk Proxy
Reverse proxy and Ingress on Pingora + HTTP/3.
Two binaries, one data plane: standalone reverse proxy or Kubernetes Ingress controller — Admin UI for sites, TLS, tunnels, GeoIP, and WAF.
- Rust
- Pingora
- Quiche / HTTP/3
- Kubernetes Ingress

Pertisk Gits
Git hosting, CI/CD, and OCI registry.
A Rust Git platform with Smart HTTP/SSH, pipelines and runners, and an org-scoped container registry — Pingora gateway optional HTTP/3.
- Rust
- Pingora
- React
- PostgreSQL
Use cases
Where Pertisk fits.
Homelab & lab HA
Spin HA Kubernetes on Proxmox, ESXi, Nutanix AHV, or Pertisk VMs — immutable nodes, no SSH on the guest.
Day-2 cluster ops
PTKublet keeps watches, YAML, logs, exec, and backups in one native desktop workspace.
Git, CI/CD & registry
Host repos, run pipelines on your runners, and push OCI images — one platform instead of bolting Gitea + Jenkins + Harbor together.
HTTP/3 edge
Front services with Pingora + Quiche: standalone proxy or Ingress, with GeoIP, WAF, and captcha when you need them.
Why Pertisk
Infrastructure you can read, run, and fork.
Each project is Rust-first where it matters for performance and control planes, with clear binaries, docs, and GitHub repos underpertisktech. Use one tool or the whole path from node to edge.
Community
Built in the open.
Issues, pull requests, and GitHub Discussions are the main channels. Email works when a private note is better.
Roadmap
Where this is headed.
- Now
Lab / HA-ready KOS, open-source Proxy + PTKublet + Gits, live demos, and public docs.
- Next
Deeper Cluster API (CAPx) path, tighter scaler + mgmt loops, and install polish.
- Later
Broader provider coverage and production hardening beyond the lab profile.