38 apps Kubernetes
Milvus screenshot thumbnail

Milvus

With over 45,000 GitHub stars and 100 million Docker pulls, Milvus is the most widely adopted open-source vector database, powering production AI systems at NVIDIA, Salesforce, eBay, Airbnb, and DoorDash. The distributed architecture separates compute and storage with stateless microservices on Kubernetes, horizontally scaling query nodes for read-heavy workloads and data nodes for write-heavy ingestion independently. Milvus 3.0 introduces lake-native retrieval that builds and serves indexes directly over vector data in object storage and open formats including Parquet, Lance, Iceberg, and Vortex without maintaining separate copies. Native hybrid search unifies lexical BM25 full-text retrieval and semantic vector search in a single engine with metadata filtering, eliminating the need for separate search infrastructure. Hardware-accelerated ANN indexing supports IVF, HNSW, DiskANN, and GPU-based indexes with BitQ 1-bit quantization cutting memory usage by 72 percent. SDKs for Python, Go, Node.js, and Java provide programmatic access, while Milvus Lite offers lightweight embedding for local development via pip install. Server-side aggregation, sorting, faceted search, StructArray for nested document structures, and ColBERT multi-vector scoring move ranking and result processing into the engine. The Path Index enables 100x faster JSON filtering with support for 100,000+ collections per cluster for multi-tenant deployments. Self-hosting deploys via Docker Standalone or Kubernetes with Helm charts using S3-compatible, GCS, or Azure Blob storage backends. 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
Orchard screenshot thumbnail

Orchard

With one command, Orchard turns a bare Linux server into a private deployment platform that builds your Git repositories, serves each app over HTTPS, runs managed Postgres beside it, and rolls back bad releases. Connect GitHub, GitLab, Gitea, Forgejo, Codeberg, or Bitbucket Cloud, enable auto-deploy, and every push builds from a Dockerfile or automatic language detection and starts new pods before the old ones stop. Prebuilt images, Compose files, Score files, and more than 90 ready-made templates, including n8n, Open WebUI, and Minecraft servers, cover everything else. Postgres comes with continuous backups to S3-compatible storage, restore to any moment in the last 30 days, forks for safe testing, standby failover, read replicas, and a connection pooler. Live logs, a shell inside a running container, CPU, memory, and request metrics, alert rules, and Slack, Discord, email, or webhook notifications show how each app behaves. Organizations, projects, roles, SAML and OIDC sign-in, SCIM provisioning, quotas, and audit logs let a team share one instance, while cron jobs, custom domains with self-renewing certificates, Tailscale-only private apps, and public status pages cover daily operations. The orchard CLI and a Terraform provider script deployments, an MCP server lets Claude, Cursor, or another agent deploy apps and read logs, and grafts add extras such as Greenhouse for running coding agents on cloud machines. 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
Argo CD screenshot thumbnail

Argo CD

A CNCF Graduated project with over 23,700 GitHub stars and adoption by organizations including Intuit, Adobe, Capital One, and Red Hat, Argo CD has become the industry standard for GitOps-based Kubernetes deployments since its creation at Intuit in 2018, treating Git repositories as the single source of truth for application configurations and automatically reconciling live cluster state with declared desired state. The platform supports Helm charts including Helm 4, Kustomize overlays, Jsonnet, and plain Kubernetes YAML manifests, rendering templates and applying resources through configurable sync policies with automated or manual reconciliation, pruning of orphaned resources, and self-healing that reverts unauthorized cluster changes. ApplicationSets enable templated generation of applications across multiple clusters, environments, and Git repositories using generators for pull requests, Git directories, cluster lists, and merge strategies. The web UI provides a real-time application topology view with resource health status, sync state indicators, log streaming, and a network view supporting Gateway API and Ingress visualization. Version 3.5 introduced mTLS for internal component communication, graduated user impersonation and source hydrator to beta, added native ApplicationSet management with preview applications in the UI, and delivered source integrity validation. Multi-cluster management deploys applications across development, staging, and production environments from a single Argo CD instance with RBAC, SSO via OIDC and SAML, and audit logging. 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
Coroot screenshot thumbnail

Coroot

Coroot uses eBPF to capture metrics, distributed traces, logs, and continuous CPU profiles directly from the Linux kernel, delivering full observability without any application code changes, SDKs, or sidecars. From the first minute of deployment, an automatically generated service map covers every microservice, database, message queue, and external dependency with request rate, error rate, and latency measurements. When a service breaches its SLO, AI-powered inspections analyze telemetry across all dimensions to pinpoint the root cause and send a single consolidated alert with findings, replacing the flood of fragmented notifications typical of traditional monitoring. Deployment tracking automatically discovers Kubernetes rollouts and compares each release against the previous one to detect performance regressions, resource spikes, and cost impacts without CI/CD pipeline integration. Continuous profiling captures CPU flame graphs down to the line of code with negligible overhead. Integrated cost monitoring tracks cloud spending across AWS, GCP, and Azure, attributing expenses to individual services and deployments. Coroot supports Prometheus, OpenTelemetry, and ClickHouse as data sources and works identically on Kubernetes clusters, virtual machines, and bare-metal hosts. 7,700+ GitHub stars. Apache-2.0 licensed.

Deploy
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
Apache SkyWalking screenshot thumbnail

Apache SkyWalking

An open-source application performance monitoring platform for microservices, Kubernetes, and service meshes, Apache SkyWalking draws the live service map and ties slow requests to their traces, logs, and metrics. Agents cover Java, .NET Core, PHP, Node.js, Go, Lua, Rust, C++, browser JavaScript, and Python, and OpenTelemetry, Zipkin, Prometheus, Zabbix, and Telegraf data can be ingested too. Start at the service topology map, follow a request through the trace waterfall, then drill into the instance and its API dependencies. When the cause is inside the code, trace profiling, async-profiler, Go pprof, eBPF, and network profiling render flame graphs and process graphs in the same console. The Rover eBPF agent profiles Kubernetes workloads for CPU and network problems, and Istio and Envoy service meshes, including Istio Ambient, report into the same dashboards. Alarm rules target a service, deployment, or API, and alarms and telemetry can be forwarded to third-party systems. Metric and log analysis rules hot-update at runtime without a restart, and a live debugger shows what each rule stage receives and produces. An AI assistant answers plain-language questions with charts, topology, and traces from live data, using an OpenAI-compatible or Amazon Bedrock model you configure, and an MCP connection serves your own AI client. 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
Kubewall screenshot thumbnail

Kubewall

One binary is all that stands between you and every Kubernetes cluster you own: Kubewall opens a realtime web dashboard over all of them, with no agents to install and nothing phoning home. Switch between clusters from the sidebar and browse workloads, networking, storage, configuration, and access control in tables that update live as pods start, fail, and reschedule. Open any resource to inspect its overview, edit its manifest in the built-in YAML editor with validation, watch its events, or stream logs aggregated across pods and containers with search and tail controls. A command palette jumps straight to any resource type, while faceted filters and global search cut through thousands of objects by name, namespace, label, or image. Scale deployments, restart pods, trigger rollout restarts, and apply manifests with a click, or forward a cluster service to your local machine without memorising kubectl incantations. An integrated AI assistant, connected to OpenAI, Claude, Gemini, DeepSeek, OpenRouter, Ollama, or a local model, helps troubleshoot failures and review configurations right beside the resource it concerns. 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
Cupdate screenshot thumbnail

Cupdate

Cupdate keeps a watchful eye on every container image you run, reporting which ones are outdated or vulnerable while deliberately never touching the update button itself. Point it at a Kubernetes cluster, a Docker socket, or Podman hosts (local or remote, one or several) and it inventories every image in use with no configuration to write. Each image is matched against its registry to find the newest available version, and the dashboard shows the gap between what you deployed and what you could be running, with release notes inline so the decision to upgrade takes seconds instead of a changelog hunt. Vulnerability data is layered on top from four sources: Docker Scout for Docker Hub images, Clair for participating Quay images, GitHub Advisories for images tied to repositories, and osv.dev correlation for images shipping SBOMs. A dependency graph explains why each image exists in your stack by showing which workloads pull it, which ends the "can I delete this?" guessing game. Subscribe to the RSS feed to hear about new releases passively, query the REST API to drive scripts that update compose files or kustomizations, or surface outdated and vulnerable counts in a Homepage dashboard widget. Prometheus metrics and traces are available when you want the watcher itself watched. 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
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