This documentation is for an older Keptn release. Please consider the newest one when working with the latest Keptn.


Explore the functionalities of Keptn based on examples.

Onboarding a Service

Shows you how to onboard the carts service including its database to a Keptn-managed project. Besides, this tutorial shows how to deploy a new version of carts via Keptn.

Deployments with Quality Gates

Describes how Keptn allows deploying an artifact using automatic quality gates and blue/green deployments.

Quality Gates for external Deployments

Describes how Keptn allows using quality gates without delivery and testing capabilities of Keptn.


Provides details about self-healing using upscalling and feature toggle.

Argo CD for Deploying and Keptn for Testing, Evaluating, and Promoting

Describes how Argo CD can be used for deploying and Keptn for testing, evaluating, and promoting

Runbook Automation

Gives an overview of how to leverage the power of runbook automation to build self-healing applications. Therefore, you will use automation tools for executing and managing the runbooks.

Write your Keptn-service

Explains to you how to implement your Keptn-service that listens to Keptn events and extends your Keptn with certain functionality.

The above list of tutorials helps you to explore the functionalities of Keptn based on examples.

Application and environment

In these tutorials, a very simple application is used that provides the functionalities for an online shopping cart. This application is composed of a stateless Java service that implements the business logic and a MongoDB that stores items added to the cart by an end-user. The following image show the architecture of the application:

Example application

In context of the tutorials, this application will be maintained as part of the project sockshop. Besides, the application will be deployed in three stages:

  • Dev stage: A developer can test the implementation of a new feature in this stage.
  • Staging stage: Performance test are conducted to verify the stability of the application.
  • Production stage: An end-user of the application will access the version deployed in this stage.