Koncrete is cloud-hosted Continuous Delivery for Kubernetes, powered by ArgoCD.

Koncrete adopts a GitOps workflow which lets developers ship code faster, easily rollback deployments, audit everything, and facilitates best practices for security and organization. It can be setup in minutes, with no tedious installation, hosting, or maintenance required.


What is GitOps?

GitOps is a name for storing infrastructure as code in a Git repository that acts as the fundamental source of truth for deployment configurations. Thus all deployment modifications are organized and completely transparent. It opens the door to numerous benefits:

Deployments are fully configured through code stored in a single git repository. This is an alternative to directly adjusting infrastructure, or giving cluster access to a generic CI tool with complex scripting.

Why Koncrete?

Koncrete gives teams the power of enterprise-grade CD tooling in minutes. It eliminates the tedious setup, hosting, and maintenance requirements often seen in powerful CD tooling.

The ability to deploy code and have the infrastructure automatically adjust for staging/dev/prod environments is extremely powerful. It saves teams time, headcount, and helps streamline development processes.

While there are a number of ways teams could construct and host their own CD tools, it can quickly become a massive time suck to setup, deploy, maintain, update, and debug self-hosted CD systems. Koncrete takes care of the tedious hosting and maintenance for teams, works with almost any Kubernetes cluster, and integrates seamlessly with other DevOps tooling. It can be setup in under 5 minutes - it's as easy as connecting an existing GitOps repository and Kubernetes cluster.

A Note on Generic CI Processes

For smaller teams, CD is commonly rolled into a generic CI process. While it is possible to use generic CI tooling to do CD processes, this often comes with strong drawbacks that are not immediately apparent: inability to effectively track infrastructure changes, unorganized infrastructure, slower builds, more challenging debugging processes, additional security concerns, lack of process transparency, etc.