37 apps Kubernetes
Harbor screenshot thumbnail

Harbor

The first container registry to reach CNCF graduated status with over 29,000 GitHub stars since VMware open-sourced it in 2016, Harbor transforms the basic Docker Distribution into a hardened enterprise registry with vulnerability scanning, supply chain signing, multi-datacenter replication, and project-level access control out of the box. Trivy scans every pushed image against the NVD, GitHub Advisory Database, and distribution-specific vulnerability feeds, with scan-on-push policies that block deployment of images exceeding configurable severity thresholds. Artifact signing through Cosign keyless signatures and Notation enforces content trust policies ensuring only cryptographically verified images reach production clusters. Policy-based replication synchronizes images and Helm charts between Harbor instances across multiple datacenters using repository, tag, and label filters with automatic retry and bandwidth throttling — enabling hybrid-cloud and disaster-recovery topologies. The RBAC model isolates projects with per-project quotas, robot accounts for CI/CD automation, webhook notifications, and audit logging that tracks every pull, push, delete, and configuration change. LDAP, Active Directory, and OIDC authentication integrate with existing identity providers, while the proxy cache transparently caches images from Docker Hub, Quay, and other upstream registries to reduce pull latency and rate-limit exposure. The RESTful API with embedded Swagger UI, tag retention policies, garbage collection scheduling, and immutable artifact rules complete the lifecycle management. Deploy via Docker Compose or Helm Chart on Kubernetes. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

Deploy
Kite screenshot thumbnail

Kite

With nearly 3,000 GitHub stars and 14 releases since its June 2025 launch, Kite delivers a lightweight Kubernetes dashboard that replaces the fragmented workflow of switching between kubectl, Lens, and separate monitoring tools with a unified multi-cluster management platform. The dashboard automatically discovers clusters from kubeconfig files and supports independent Prometheus configurations per cluster, providing real-time CPU, memory, and network charts alongside live pod log streaming with filtering and search. A built-in web terminal opens shells directly into pods and nodes without kubectl port-forward, while the Monaco-based YAML editor offers syntax highlighting and validation for in-place resource editing. The integrated AI agent, powered by OpenAI or Anthropic models via native Go SDK integrations, translates natural language into precise client-go API calls — querying cluster health, analyzing pod logs, scaling deployments, patching resources, and cleaning up failed jobs — all operating strictly within the logged-in user's RBAC permissions. Enterprise governance includes OAuth 2.0 single sign-on, multi-factor authentication, FIDO2 passkeys, granular role-based access control with per-namespace permissions, and comprehensive audit logging. Helm chart management enables browsing, installing, and upgrading releases directly from the UI, while the Docker registry integration provides quick image tag selection. Deploy via a single Docker container with SQLite or use the official OCI Helm chart with PostgreSQL or MySQL for production. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

Deploy
Compartment screenshot thumbnail

Compartment

Compartment gives the small internal tools, private apps, and AI-built utilities your team keeps creating a proper place to live: your own Kubernetes, with one-command deploys, stable URLs, and sign-in handled for you. Install it into a cluster you already run, or let the guided installer provision a managed single-node Kubernetes host after showing you exactly what it will change. Each app is described by one small compartment.yml file naming its services, and from there deployment is a single command from your checkout, or a branch-driven flow when you connect the Git repository and let pushes roll out on their own. If an app can build into a container image with Docker or Railpack, it fits the model, and every deploy lands behind the edge ingress with its own URL and HTTPS from the first release. The browser Console becomes your operations surface for projects, deployment history, logs, and runtime variables, while SSO, role-based access, and audit logs replace the informal permission paths that grow around shared tools. Workloads stay isolated and can sit close to the private services, data stores, and internal APIs they need, without turning steady traffic into managed-platform spend. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy
Versus Incident screenshot thumbnail

Versus Incident

Versus Incident is a self-hosted AI SRE agent and incident manager that learns what normal looks like in your logs, metrics, traces, and Kubernetes clusters, then opens a triaged incident the moment something genuinely new appears. Detection earns trust gradually. Training mode only observes and catalogs patterns; shadow mode records what it would have alerted so you can judge its instincts; detect mode creates real incidents with an AI-written summary, a severity, and suggested next steps attached. Existing alerting does not have to move: Alertmanager, Grafana, Sentry, CloudWatch, Fluent Bit, and custom scripts post to the same webhook endpoint, and every incident, however it arrived, is rendered with your Go templates. Delivery fans out to Slack, Microsoft Teams, Telegram, Viber, email, and Lark. Silence has a deadline, because unacknowledged incidents escalate to on-call through PagerDuty, AWS Incident Manager, Opsgenie, incident.io, or ServiceNow. The Kubernetes dashboard gathers cluster health and capacity, workloads, resource relationships, recent changes, Helm releases, and GitOps status, and a DevOps chat agent in the web UI answers questions against the connected systems while responders work. The admin dashboard reviews learned patterns, shadow events, and raised incidents, so the agent's judgment stays inspectable. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
KubeSphere screenshot thumbnail

KubeSphere

Managing Kubernetes shouldn't require every developer to become a Kubernetes expert — KubeSphere wraps cluster operations, CI/CD, service mesh, and observability into guided web workflows that operations teams configure once and developers consume without kubectl. The LuBan extensible architecture treats each capability as an independently installable extension plugging into a lightweight microkernel: enable DevOps without service mesh, add monitoring without the app store, compose exactly what your organization needs. Multi-cluster management provides a centralized control plane for provisioning and operating clusters across cloud providers, data centers, and edge locations with unified identity and resource quotas. The DevOps extension integrates Jenkins for graphical pipeline creation with S2I and B2I workflows, while Argo CD powers GitOps continuous deployment with real-time sync status. Istio-based service mesh provides traffic management, canary deployments, circuit breaking, and distributed tracing through the console without CLI knowledge. Prometheus monitoring with custom dashboards, Fluentd log collection with multi-tenant search, and alerting via Slack and email complete the observability stack. Multi-tenant workspace hierarchy enforces resource quotas and fine-grained RBAC roles across teams. A built-in Helm-based app store handles lifecycle management across clusters. KubeKey deploys production-grade clusters on bare metal or VMs with air-gapped support. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy
Pyrra screenshot thumbnail

Pyrra

Define a service level objective in a few lines of YAML and Pyrra writes the Prometheus recording rules and multi-window burn rate alerts for it, then tracks the remaining error budget in a web interface. An objective can be an error ratio or a latency target, declared as a Kubernetes custom resource or as a plain file read from disk when running under Docker or as binaries. Grouping labels fan one definition out into an objective per route or handler. The objectives page lists each SLO with its window, target, availability, and remaining budget, sorted so the worst offenders sit on top; columns can be sorted or hidden, and a search box or a click on any label filters the list. Opening an objective highlights availability and error budget, plots the budget over time, and charts requests, errors, and duration with a time range picker and absolute or relative scales. Below the charts, a table shows the four generated alerts with their severities. Generated alerts carry a link back to the objective's page, and severities can be overridden in the spec. Queries go to Prometheus, Thanos, or Mimir, with basic auth, bearer tokens, or tenant IDs, and ready-made Grafana dashboards chart the same objectives. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy
OptScale screenshot thumbnail

OptScale

Idle instances, forgotten snapshots, and unattached volumes quietly inflate cloud bills, and OptScale hunts them down across AWS, Azure, Google Cloud, Alibaba Cloud, and Kubernetes from one self-hosted FinOps console. Cloud accounts connect with read-only rights, and the Recommendations page turns billing exports and monitoring data into savings cards for abandoned and underutilized instances, obsolete snapshots, detached volumes, abandoned load balancers, inactive IAM users, public S3 buckets, and Reserved Instance, Savings Plan, and Spot opportunities, each priced in monthly dollars. Cost Explorer breaks daily, weekly, or monthly spend down by data source, pool, owner, or geography, and the Cost Map plots it by region on a world map. Pools mirror your organization with limits, owners, and forecasts, while quotas and budgets, anomaly detection, tagging policies, TTL rules, and VM power schedules flag or contain overspending. Shared Environments let engineers book test stands on a calendar and see which Jira tickets and software builds each one carries. Kubernetes costs are split by namespace, workload, and label, K8s rightsizing compares CPU and memory use with requests, and Databricks cost analytics shows cluster usage and idle time. A cost comparison page lines up VM sizes and prices across providers. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy
Argo Workflows screenshot thumbnail

Argo Workflows

Container-native and declarative, Argo Workflows is a workflow engine that runs multi-step jobs in parallel on Kubernetes, each step in its own container. Workflows are written in YAML as ordered steps or as directed acyclic graphs, so dependencies stay explicit and independent branches start at the same moment. The web console lists every run with its phase, progress, and duration, then opens any workflow as a live graph that marks each node as pending, running, failed, or finished. Selecting a node reveals its logs, inputs, and outputs, and retry or resubmit sends a failed run back through the pipeline. Loops fan a pipeline out over a list of items, conditionals skip steps that do not apply, and retry strategies, timeouts, and exit handlers decide what happens when a step misbehaves. Reusable WorkflowTemplates live in the cluster and accept parameters from the console, the argo CLI, or the REST API; CronWorkflows launch the same pipelines on a schedule. Artifacts travel between steps and out to S3, Google Cloud Storage, Azure Blob Storage, or Git, and the archive keeps finished runs in a SQL database for later review. Suspend steps hold a pipeline until someone approves it, and OAuth2 or OIDC single sign-on signs operators in to the console. Machine learning pipelines, batch data processing, infrastructure automation, and CI/CD jobs all fit the same model. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy
Eclipse Che screenshot thumbnail

Eclipse Che

Eclipse Che spins up complete development environments on Kubernetes from a Devfile in the project repository, so new developers click a factory link and open a browser IDE with dependencies, runtimes, and debugging already configured instead of spending their first day installing toolchains. Each workspace runs as a DevWorkspace custom resource in the user's namespace, making environments API-manageable with kubectl and GitOps tooling alike. Developers choose their editor per workspace, from Visual Studio Code Open Source to JetBrains IDEs via Projector, and the 7.124 release adds Orca, an agent development environment for working alongside AI coding agents. Workspaces carry their own containers for build and run, so code executes in a production-like environment with direct Kubernetes API access from the IDE. Teams standardize stacks as Devfile templates, onboard contributors in minutes, and open a fresh workspace per branch or pull request in a new browser tab. The 7.124 release also builds workspace lifecycle commands into chectl, including SSH connections with port forwarding to desktop editors, and DevWorkspace Operator 1.0 adds optional per-workspace NetworkPolicy isolation. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. EPL-2.0 licensed.

Deploy
Grafana Loki screenshot thumbnail

Grafana Loki

With over 28,600 GitHub stars and 450 contributors, Grafana Loki is the log aggregation system that takes the Prometheus approach to logging — indexing only metadata labels instead of full log content, making it dramatically cheaper and simpler to operate than traditional log management platforms. The label-based indexing strategy groups log streams using the same labels already applied to Prometheus metrics, enabling seamless switching between metrics and logs in Grafana dashboards without maintaining separate indexing infrastructure. Grafana Alloy, the telemetry collector replacing Promtail, scrapes and pushes logs with Prometheus-style service discovery, automatic Kubernetes Pod label extraction, and pipeline stages for parsing, filtering, and relabeling before ingestion. LogQL, the query language, combines label matchers for stream selection with regex line filters and aggregation functions, supporting rate calculations, pattern parsing, and metric generation from log data for alerting and dashboard panels. The storage architecture writes compressed log chunks and TSDB indexes to S3, GCS, Azure Blob Storage, or MinIO-compatible object stores, with configurable retention and compaction policies. Deployment modes scale from a single binary for development through monolithic high-availability mode with multiple replicas to full microservices decomposition with separate ingester, distributor, querier, query-frontend, compactor, and ruler components on Kubernetes via Helm charts. Multi-tenancy isolates data and query paths per tenant through header-based tenant ID assignment. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Deploy
RocketplaneIO screenshot thumbnail

RocketplaneIO

RocketplaneIO is a self-hosted AI SRE platform that gives Kubernetes clusters zero-instrumentation eBPF observability plus a copilot capable of safely diagnosing and fixing issues without your telemetry ever leaving your infrastructure. Point it at any cluster, and an eBPF DaemonSet starts capturing HTTP, gRPC, SQL, Redis, and Kafka spans across every service, including compiled binaries, with cross-service context propagation and no code changes required. The live service map draws itself from actual network traffic, matching technology logos from container images and coloring each node's health from RED metrics. Every log line sits two clicks from its parent distributed trace, and a PromQL query engine, embedded from the real Prometheus evaluator, runs over ClickHouse for long-term metric retention. The complete Kubernetes inventory (Services, Ingress, ConfigMaps, network policies, persistent volumes, CRDs) syncs continuously and is searchable alongside traces and logs. When the copilot identifies a problem, it picks from a catalog of roughly 30 risk-classified safe actions; each action verifies its preconditions, captures a before-state snapshot, executes, checks the result, and rolls back automatically on failure. Disruptive operations pause for explicit human approval before proceeding. An MCP endpoint exposes the identical guardrailed toolbox to external AI agents, so Claude Code or Cursor can operate the cluster through the same safety boundary the browser copilot uses. Complex remediations compose as searchable, forkable Starlark workflows that compile deterministically at save. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy
Zeabur screenshot thumbnail

Zeabur

Zeabur is a self-hosted web platform that deploys and runs your services on your own Kubernetes cluster, presenting the cluster as simple projects and services instead of raw manifests. Every change starts as a readable plan listing the exact fields it will write and who owns them today, and nothing is applied until you confirm it. When something breaks, Zeabur says so in plain words and points at the fix: a worker that restarted fourteen times gets a button straight to the logs from the run before the restart. You deploy from Git repositories, from an uploaded folder or ZIP archive, or directly in the dashboard, then follow live logs, open a terminal inside a container, and watch CPU and memory move over time. Projects are namespaces and all state lives in Kubernetes objects, so there is no Zeabur database to back up, and uninstalling the platform leaves your Deployments, Services, and Ingresses running untouched. Companion pieces add passkey sign-in for kubectl with tokens that expire in minutes, image builds from Git through a BuildKit operator, and a catalog of cluster components and app templates. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy
OpenChoreo screenshot thumbnail

OpenChoreo

OpenChoreo gives developers a complete open-source internal developer platform for Kubernetes: a self-service portal to build, deploy, and run applications without wrestling raw cluster YAML. In the portal you create a component from source code or a container image, expose it through endpoints, and promote it across environments with a few clicks. Platform engineers define the golden paths behind that simplicity: component types, traits, and workflows set the rules for how workloads are built, secured, and connected. The control plane translates each declaration into the Kubernetes resources it needs, then keeps the portal in sync with what is actually running. Built-in CI builds from source with Buildpacks and Argo Workflows, and GitOps delivery keeps every environment reconciled with the declared state. Metrics, logs, and traces surface in the same portal, organized by component and environment instead of pod names and namespaces. Role-based access control, project isolation, and traffic policies draw the boundaries between teams, and platform analytics show how the platform itself is being used. Existing Backstage portals can adopt OpenChoreo as plugins, and developers can also work through the CLI, GitOps files, or AI agents. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy
Rancher screenshot thumbnail

Rancher

Used by over 30,000 teams and 650+ enterprise customers managing more than 5.2 million containers, Rancher has earned recognition as a Leader in the Gartner Magic Quadrant for Container Management and the Forrester Wave for Multicloud Container Platforms. The platform provides a single pane of glass for provisioning, upgrading, and securing Kubernetes clusters across Amazon EKS, Google GKE, Microsoft AKS, RKE2, K3s, and any CNCF-conformant distribution. Multi-Cluster Management enables centralized authentication via Active Directory, LDAP, SAML, GitHub, and OpenID Connect with granular role-based access control at the cluster, project, and namespace levels. Fleet, the built-in GitOps engine, delivers continuous deployment across hundreds of clusters simultaneously using Helm charts, Kustomize, or raw YAML manifests from any Git repository. The integrated app catalog provides one-click deployment of Prometheus monitoring, Grafana dashboards, Longhorn persistent storage, Istio service mesh, and hundreds of community Helm charts. Rancher supports air-gapped installations for disconnected environments, CIS benchmark scanning for security compliance, and automated backup and restoration of cluster configurations. The dashboard offers real-time workload monitoring, log aggregation, pod shell access, and namespace-scoped resource quotas. Cluster templates enforce organizational standards through Helm-based provisioning policies that ensure consistent configurations across environments. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

Deploy
Inference Gateway screenshot thumbnail

Inference Gateway

Inference Gateway puts a single OpenAI-compatible API endpoint in front of OpenAI, Anthropic, Groq, Cohere, Ollama, DeepSeek, Google, Mistral, MiniMax, Moonshot, Nvidia, and llama.cpp, so your application code never changes when you switch models or providers. The Go binary starts on port 8080 and normalizes authentication, streaming protocols, and response formats across all backends transparently. Native Model Context Protocol support auto-discovers tools from connected MCP servers and injects them into LLM requests without client-side management, enabling server-side tool execution across any provider that supports function calling. Agent-to-Agent protocol integration allows distributed agent communication through a declarative Agent Definition Language that generates production-ready Go or Rust servers from a single YAML manifest. The dedicated Kubernetes Operator manages Gateway, Agent, MCP, and Orchestrator custom resources with automatic HPA scaling, OIDC authentication, and service discovery that rebuilds MCP configurations when the discovered server set changes. Prometheus metrics and OpenTelemetry tracing provide full request-level observability across the entire inference pipeline. Middleware controls enable per-request provider selection, model routing, and fallback strategies. Official SDKs in Go, Python, TypeScript, and Rust provide typed client interfaces with streaming support. Docker Compose deployment requires only environment variables for API keys. A CNCF Sandbox applicant. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

Deploy
TelltaleDNS screenshot thumbnail

TelltaleDNS

Every connection your devices make starts with a DNS lookup, and TelltaleDNS is the resolver that answers it, filters it per device, and explains exactly why it answered that way. The query log ties each question to a named device, using names from your router's leases, mDNS, or the UI, times every stage, and a Why panel shows the list and rule behind each block. Groups per network or VLAN carry their own blocklists, schedules, safe search, blocked services, and rewrites, and a new rule can be previewed against yesterday's real traffic before you save it. Serve devices over DoT, DoH, or DoQ, give each one a client ID that follows it onto mobile data, forward to encrypted upstreams, validate DNSSEC, or resolve recursively from the root servers. The dashboard adds a traffic map, a heatmap of when your network asks, a flow diagram from groups to answers, and anomaly alerts, with Prometheus metrics, OpenTelemetry, and dnstap for your SIEM. A Raspberry Pi and Kubernetes nodes can share one configuration, with canary rollouts, automatic failover, and failover drills. It answers queries only from private and Tailscale address ranges unless you widen that, and it imports Pi-hole and Technitium setups. A REST API, command line, and MCP tools with approval serve scripts and agents. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 or MIT licensed.

Deploy
Kubero screenshot thumbnail

Kubero

With over 4,300 GitHub stars and a v3 release adding built-in user management, team views, and multi-language support, Kubero has established itself as the most feature-complete open-source Heroku alternative running natively on Kubernetes. The platform operates as a Kubernetes operator with two containers — kubero-ui and the operator — storing all state in etcd without an external database. Developers push code via Git integration with GitHub, GitLab, Bitea, or Gitea, and Kubero automatically builds using Buildpacks, Nixpacks, Runpacks, or Dockerfiles, then deploys to the configured domain with SSL via cert-manager. CI/CD pipelines support up to four staging environments — review, test, staging, and production — with per-stage environment variable isolation and ephemeral review apps that spin up on pull request open and tear down on close. The template catalog includes over 170 pre-configured applications like WordPress, Grafana, and PostgreSQL deployable in one click, while managed add-ons provide highly available PostgreSQL, Redis, MySQL, Kafka, CouchDB, Elasticsearch, and MongoDB alongside your applications. Security features include Trivy vulnerability scanning, GitHub and OAuth2 single sign-on, basic auth, and a role-based permission system with API tokens. The NestJS backend with Vue.js and Vuetify frontend provides application metrics, real-time logs, a built-in web console for container access, scheduled cronjob management, and deployment notifications via Discord, Slack, or webhooks. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.

Deploy
Prowler screenshot thumbnail

Prowler

Point it at your cloud accounts and it returns a ranked list of what is misconfigured, mapped to the standards auditors ask about. Connect providers like AWS, Azure, Google Cloud, Kubernetes, Microsoft 365, and GitHub, launch a scan or schedule recurring ones, and read the results on an overview with a ThreatScore gauge, severity bars, and a resource inventory by category. The Findings page groups failed checks, expands each group into the affected resources, and lets teams mute noise, triage status, send groups to Jira, and create alerts that email or message people after each scan. Compliance pages score every framework from CIS and NIST to PCI DSS, SOC 2, HIPAA, GDPR, and ISO 27001, with a watchlist for the ones you care about and downloadable reports. Attack Paths draws a graph from IAM roles and policies to outcomes like code execution, using a Neo4j graph database filled by AWS scans. A built-in AI assistant answers questions about critical findings and compliance gaps with the model provider you configure. Organizations, roles, and API keys keep access tidy. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy