konfidence

README

Konfidence

Description

Konfidence is a cloud-native deployment orchestration platform that enables safe and traceable delivery of multi-component applications to your target platforms. Modern applications often consist of multiple interconnected services that need to be deployed, tested and published as cohesive units while managing complex dependencies and configurations. Konfidence addresses these challenges by treating application deployments as immutable vectors that can be safely deployed across multiple environments.

At its core, Konfidence solves the problem of coordinating multi-service deployments with confidence. Traditional deployment tools focus on individual components, but Konfidence allows you to define complete application configurations as vectors—versioned, immutable deployment units that reference all required artifacts, configuration and orchestration tasks. This approach enables teams to deploy the same application configuration consistently across development, staging and production environments.

This repository contains the core Konfidence operators, the Konfidence API server and the Konfidence CLI. For comprehensive documentation, architecture details, and getting started guides, visit konfidence.cloud.

Warning: This project is in early development. The APIs and features are subject to change. We do not give any guarantees regarding compatibility or stability at this stage. Please reach out to us if you are interested in early adoption or collaboration.

Installation

Konfidence runs on a Kubernetes cluster and consists of two main components:

• Konfidence operator: Orchestrates delivery flows across stages and manages vector lifecycles
• Kubernetes landscape orchestrator: Reference deployer implementation for Kubernetes deployments

You can quickly set up a local test environment using kind or install Konfidence on an existing Kubernetes cluster using Helm charts.

For a step-by-step guide including cluster setup, component installation, and your first vector deployment, see the Quickstart Guide.

For detailed installation instructions and production deployment considerations, see the Installation Guide.

Dashboard Development

The production dashboard lives in apps/konfidence-ui. Activate Hermit and install the workspace dependencies before starting it:

source ./bin/activate-hermit
pnpm install
pnpm ui:dev

The development server proxies /api/v1 requests to the API at http://127.0.0.1:8090. Run the API separately with make run-kden-api when developing API-backed features.

Install Chromium once before running browser-based tests:

pnpm --filter konfidence-ui exec playwright install chromium

Run the static checks and each test layer with repository commands:

pnpm ui:check
pnpm ui:check:svelte
pnpm ui:lint
pnpm ui:fmt:check
pnpm ui:test:unit
pnpm ui:test:browser
pnpm ui:test:e2e

pnpm ui:verify runs all static checks, while pnpm ui:test runs every test layer. pnpm ui:all runs both groups.

Build and preview the static SPA with:

pnpm ui:build
pnpm ui:start

The preview server is intended for checking the root page. To exercise production SPA fallback behavior, serve the build through the API with go run ./cmd/api --ui-asset-path=apps/konfidence-ui/build.

Production releases include the static SPA in the API image. The API serves the dashboard and /api/v1 from the same origin; set API_UI_ASSET_PATH when running an API binary with an external dashboard build directory.

Support, Feedback, Contributing

This project is open to feature requests/suggestions, bug reports etc. via GitHub issues. Contribution and feedback are encouraged and always welcome. For more information about how to contribute see our Contribution Guidelines.

Security / Disclosure

If you find any bug that may be a security problem, please follow our instructions at in our security policy on how to report it. Please do not create GitHub issues for security-related doubts or problems.

Code of Conduct

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone. By participating in this project, you agree to abide by its Code of Conduct at all times.

Licensing

Copyright 2026 SAP SE or an SAP affiliate company and konfidence-project contributors. Please see our LICENSES for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool.