This applies to self-hosted (BYOC/BYOVPC) deployments only. If you’re using HoneyHive Cloud or Dedicated Cloud, infrastructure is managed for you.
Version Compatibility Matrix
| Dependency | Minimum Version | Recommended Version | Notes |
|---|---|---|---|
| PostgreSQL | 13 | 14+ | Prisma 6.x supports 9.6+, but only 13+ is tested and supported |
| Redis | 6.0 | 7.0+ | Security baseline; core features require only 2.6+ |
| NATS | 2.2.0 | 2.10+ | JetStream API requires 2.2.0 |
| ClickHouse | 23.1 | 24.x+ | Required for query optimization settings |
| Kubernetes | 1.23 | 1.25+ | 1.25+ recommended for active support windows |
| Helm | 3.2.0 | 3.12+ | All charts use apiVersion: v2 |
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.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 useapiVersion: 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 configurations are supported:| Service | AWS | GCP | Azure |
|---|---|---|---|
| PostgreSQL | RDS for PostgreSQL (13+) | Cloud SQL for PostgreSQL | Azure Database for PostgreSQL |
| Redis | ElastiCache for Redis, MemoryDB | Memorystore for Redis | Azure Cache for Redis |
| NATS | Self-hosted on EKS (no managed offering) | Self-hosted on GKE | Self-hosted on AKS |
| ClickHouse | Self-hosted on EKS, or ClickHouse Cloud | Self-hosted on GKE, or ClickHouse Cloud | Self-hosted on AKS, or ClickHouse Cloud |
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 tested and supported on:| Provider | Service | Notes |
|---|---|---|
| AWS | EKS | Primary deployment target |
| GCP | GKE | Fully supported |
| Azure | AKS | Fully supported |
| Rancher | RKE/RKE2 | Supported for on-premise |
| Red Hat | OpenShift | Supported for on-premise |
Required Operators and CRDs
The following Kubernetes operators must be installed in your cluster before deploying HoneyHive:| Operator | Minimum Version | CRD API Group | Purpose |
|---|---|---|---|
| Altinity ClickHouse Operator | 0.25.x | clickhouse.altinity.com/v1 | ClickHouse cluster lifecycle management |
| NACK (NATS Account Controller for Kubernetes) | 0.20.0+ | jetstream.nats.io/v1beta2 | Kubernetes-native JetStream stream and consumer management |
| External Secrets Operator | 0.9+ | external-secrets.io/v1 | Syncs secrets from your cloud provider’s secret manager (e.g., AWS Secrets Manager) |
| OpenTelemetry Operator | 0.90+ | opentelemetry.io/v1beta1 | Deploys and manages OpenTelemetry collectors |
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.