Overview

You can deploy Sifflet on your own infrastructure. This is called a "self-hosted deployment" (also referred to as "in-VPC", "self-managed" or "on-premises").

Sifflet only recommends this solution for customers with strict compliance requirements, as it puts the burden of installation and maintenance on your organization. Instead, most customers should either deploy the Sifflet Agent, or a custom networking setup.

With this deployment type, all data resides inside your own infrastructure. Unlike some other solutions, self-hosted installations operate without exchanging any data with Sifflet, and do not even require Internet access (this is not a "hybrid" model).

You can optionally send logs from these installations to Sifflet to help Sifflet investigate issues with your deployment. You have full access to the contents of these logs and can turn them off at any moment.

A Sifflet installation complies with security requirements from most organizations. For instance, Sifflet always keeps the provided software up to date so it does not trigger vulnerability alerts from security scanners, you can run container images with arbitrary user IDs, and so on.

Supported Environments

With a self-hosted deployment, you are responsible for managing the infrastructure that runs the Sifflet instance. You must provide a Kubernetes cluster, a database, and a secrets manager.

You can deploy a Sifflet instance to all the major cloud providers (AWS, GCP, Azure), as well as most Kubernetes clusters (such as OpenShift clusters running on-premises).

You can deploy Sifflet in environments without any Internet access.

Detailed Documentation

Sifflet can share detailed documentation about how to install and maintain a self-hosted Sifflet instance under NDA (non-disclosure agreement).