Pertisk.

Open infrastructure for Kubernetes.

Immutable node OS, native cluster ops, self-hosted Git with CI and registry, and an HTTP/3 edge proxy — open source from pertisktech.

Open source

Four projects. One stack story.

From the node OS and desktop ops, through self-hosted Git + CI + registry, to the edge proxy that fronts your services — each with GitHub, docs, and (where available) a live demo.

  1. Pertisk KOS management dashboard with cluster resource cards
    01Lab · HA ready

    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, and Nutanix AHV.

    • Rust
    • containerd
    • kubelet
    • gRPC
  2. PTKublet desktop dashboard showing cluster health and resource charts
    02Desktop · open source

    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
  3. Pertisk Proxy Admin sites list with HTTPS upstreams
    03Edge · open source

    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
  4. Pertisk Gits repository code browser for pertisk-kos
    04Platform · open source

    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, standalone ESXi, or Nutanix AHV — 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.

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.