7 apps GitOps
Flipt screenshot thumbnail

Flipt

Backed by 4,800+ GitHub stars and trusted by teams replacing LaunchDarkly and Split with a self-hosted solution, Flipt v2 delivers the first truly Git-native feature management platform that treats feature flags as code stored in your own repositories. The architecture eliminates all database dependencies by building immutable in-memory snapshots from YAML flag definitions on every Git commit, delivering sub-millisecond evaluation latency with zero external runtime dependencies beyond the single Go binary. Multi-environment support maps directly to Git abstractions — separate repositories per environment, different directories within the same repository, or different branches — enabling teams to use their existing branching strategy, pull request workflows, and code review processes for flag changes. The evaluation engine supports boolean flags, multivariate string and numeric variants, segment-based targeting with constraint rules, percentage rollouts, and namespace isolation. Native SCM integration with GitHub, GitLab, BitBucket, Azure DevOps, and Gitea creates merge proposals directly from the UI with GPG-signed commits. Flipt implements the OpenFeature Remote Evaluation Protocol with official providers for Go, Node.js, Python, Java, C#, Ruby, and Web SDKs, enabling vendor-agnostic flag evaluation across all services. The gRPC API with REST HTTP gateway exposes flag management, evaluation, and analytics endpoints. Offline mode continues serving flags when the source repository is temporarily unavailable. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Fair Core License (server) / MIT (client SDKs).

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
OpenRun screenshot thumbnail

OpenRun

OpenRun replaces the patchwork of CI/CD pipelines, reverse proxies, and identity providers that teams typically assemble when deploying internal tools, offering declarative GitOps-based deployment of web applications to Docker, Podman, or Kubernetes from a single self-hosted Go binary. Point it at a Git repository and it builds containers from AppSpec templates, routes requests by domain or URL path, provisions TLS certificates automatically, and scales idle applications to zero when unused. Blue-green staged deployments promote new versions through development, staging, and production environments with atomic rollback across multiple apps simultaneously. Every deployed application inherits SSO authentication through OAuth, OpenID Connect, or SAML providers alongside role-based access control, all configured once at the platform level rather than per app. Service bindings provision isolated PostgreSQL, MySQL, SQLite, or Redis credentials for each application, while Litestream integration replicates SQLite databases to S3 for automatic disaster recovery. The management console provides a web interface for monitoring containers, reviewing audit logs, configuring syncs, and managing server operations. AppSpec templates handle Streamlit, Gradio, FastAPI, Flask, and FastHTML projects out of the box, deploying existing Python applications without requiring custom Dockerfiles. 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 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
Atlantis screenshot thumbnail

Atlantis

Every Terraform change becomes a pull request with Atlantis, which runs the plan on your server, posts the output for review, and applies only the exact change reviewers approved. Open a pull request that touches Terraform code and Atlantis automatically runs terraform plan, posting the full output as a comment and a commit status your reviewers can inspect line by line. When the change looks right, a teammate comments atlantis apply and Atlantis executes the exact plan that was reviewed, then reports the result back on the same pull request. Each directory and workspace is locked while a pull request is open, preventing two changes from applying out of order, and locks can be inspected or discarded from the web interface. Apply requirements let you demand an approved review or a mergeable branch before anything runs, and optional policy checks evaluate plans against your rules before they can proceed. Repositories describe their projects, workspaces, and custom workflows in an atlantis.yaml file, including pinned Terraform versions, execution order groups, and parallel planning or applying across projects. Because Atlantis runs inside your infrastructure, cloud credentials never leave your network, and every plan, approval, and apply is preserved on the pull request as an audit trail. 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
Single Server screenshot thumbnail

Single Server

Point it at your GitHub repos and every push goes live in under five seconds: one Linux box becomes the deployment platform for every app you have ever shipped, with no build queue, no per-app bills, and no pile of YAML. An interactive installer wires the box up once, creating a GitHub App for limited, revocable repo access, Cloudflare DNS records and a tunnel so visitors get TLS and CDN at the edge while your server IP stays hidden, and Tailscale access so you SSH in without exposing SSH to the public internet. From then on you just push: the daemon receives the webhook through a Tailscale Funnel, verifies its signature, fetches the commit, builds the image on the server from your Dockerfile or a generated one, and swaps traffic only after the new container passes its health check, so a failed deploy leaves the previous version serving. Each app runs in its own container with its own environment variables and persistent storage, and one CLI on the box handles the rest: add or remove apps, attach a domain in one command, roll back to an earlier commit, stream logs, check status, take backups, or run doctor to diagnose every layer from daemon to DNS. 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