Skip to main content
Verify that your infrastructure meets HoneyHive’s minimum dependency versions before provisioning a self-hosted deployment.
BYOC and BYOVPC deployments: If HoneyHive is provisioning and managing your cluster, you do not need to provision these dependencies yourself, as our team handles all infrastructure setup and versioning. See HoneyHive Cloud or Dedicated Cloud for managed deployment guides. This page applies to organizations deploying and managing the HoneyHive Helm charts independently on their own Kubernetes cluster.

​
Version Compatibility Matrix

​
Dependency Details

​
PostgreSQL

HoneyHive uses PostgreSQL for relational data storage (projects, configurations, user management). The application uses Prisma 6.x as its ORM, which technically supports PostgreSQL 9.6+. However, all versions below 13 are end-of-life, and only 13+ is tested in production. SQL features used (JSONB, enums, array types) are available from PostgreSQL 9.4+. We recommend PostgreSQL 14 or later for performance improvements and long-term support alignment.
PostgreSQL is expected to be provided as a managed service, such as AWS RDS for currently supported AWS deployments. The Helm charts do not include a self-hosted PostgreSQL deployment.

​
Redis

Redis is used for caching, rate limiting, and ephemeral state. The application uses only basic operations (GET, SET, DEL, KEYS) which are available from Redis 2.6+. However, Redis 6.0 is the minimum recommended version for ACL support and security hardening. The deployment uses a master-replica topology with separate read/write endpoints. No Redis Cluster, Sentinel, Streams, or modules (RedisJSON, RediSearch) are required.

​
NATS

NATS provides the event streaming backbone for HoneyHive’s ingestion, enrichment, evaluation, and notification pipelines. JetStream (introduced in NATS 2.2.0) is a hard requirement, and all stream and consumer management uses the JetStream API. The deployment includes:
  • File-based JetStream storage with configurable retention
  • NACK (NATS Account Controller for Kubernetes) operator for Kubernetes-native stream/consumer CRD management
  • Max payload size of 8 MB

​
ClickHouse

ClickHouse is the analytical data store for all event, session, and trace data. Version 23.1 or later is required for query optimization settings used by the platform.

​
Kubernetes

We recommend Kubernetes 1.25+ to stay within active support windows of major managed Kubernetes providers.

​
Helm

All HoneyHive Helm charts use apiVersion: v2, which requires Helm 3.2.0 or later. Helm 2.x is not supported.

​
Managed Service Compatibility

If you are using managed cloud services instead of self-hosted databases, the following AWS configurations are supported today:

​
Coming Soon

The following cloud-specific configurations are planned alongside GKE and AKS support:
For managed Redis services, ensure the offering supports Redis 6.0+ and simple master-replica topology. Redis Cluster mode is not required.

​
Kubernetes Provider Compatibility

HoneyHive’s Helm charts are currently tested and supported on:

​
Coming Soon

Contact us if you need support for a different Kubernetes distribution.

​
Required Operators and CRDs

The following Kubernetes operators must be installed in your cluster before deploying HoneyHive:
If you use ArgoCD for GitOps deployments, HoneyHive’s charts include ArgoCD Application CRDs (argoproj.io/v1alpha1). This is optional and not required for non-ArgoCD deployments.

​
Next steps

Self-Hosted Setup

Deployment models, supported platforms, and getting started.

Platform Architecture

How HoneyHive’s components work together.

Security

Security posture and compliance details.