Self-Hosting Overview

HoneyHive offers self-hosted deployments for organizations with strict privacy, security, or compliance requirements. Both the Control Plane and Data Plane are deployed in your environment, giving you full control over all infrastructure and data.

Self-hosted deployments are managed by HoneyHive. Contact us to get started.

Deployment models

We support two deployment models:

Model	Description
BYOC (Bring Your Own Cloud)	We deploy HoneyHive’s Kubernetes cluster in a dedicated AWS account you provision.
BYOVPC (Bring Your Own VPC)	We deploy HoneyHive’s Kubernetes cluster within an AWS VPC you manage, aligned with your existing network controls.

Both models give you full network isolation and control over data residency.

Supported platforms

Cloud Provider	Kubernetes	Deployment
AWS	EKS	Terraform + Helm

Need a different platform? Contact us to discuss availability and requirements.

What’s included

During setup, we work with your security and infrastructure teams to:

Review network architecture and data flow against your policies
Configure Terraform modules and Helm charts to meet your requirements
Deploy the cluster and validate the installation
Set up private connectivity, such as AWS PrivateLink where needed
Integrate SAML/SSO with your identity provider

See Platform Architecture for details on how these components work together. For data classification, flow boundaries, and retention controls, see Data Flow & Residency. For security controls, access policies, and compliance scope specific to self-hosted deployments, see Self-Hosted Security. For the general security posture and certifications, see Security.

SDK Configuration

In federated deployments, the Control Plane and Data Plane run at different URLs. The Python SDK talks only to the Data Plane, so point HH_API_URL at your data plane host. Control plane operations (projects, alerts, workspaces) go through the TypeScript control-plane SDK or the CLI, which take the control plane host in HH_CONTROL_PLANE_URL.

Environment Variables

# Data Plane URL - used for span/event ingestion and the Python SDK (required)
export HH_API_URL="https://dp.your-company.honeyhive.ai"

export HH_API_KEY="your-api-key"

# Control Plane URL - for the control-plane SDK and the CLI's control plane commands
export HH_CONTROL_PLANE_URL="https://cp.your-company.honeyhive.ai"

SDK Parameters

You can also pass the URL directly when initializing the SDK client:

from honeyhive import HoneyHive
import os

client = HoneyHive(
    api_key=os.getenv("HH_API_KEY"),
    base_url="https://dp.your-company.honeyhive.ai",
)

For the tracer, use server_url:

from honeyhive import HoneyHiveTracer
import os

tracer = HoneyHiveTracer.init(
    api_key=os.getenv("HH_API_KEY"),
    server_url="https://dp.your-company.honeyhive.ai",
)

Resolution Order

Each client resolves its URL in this order (first match wins):

Client	Resolution order
Python SDK (Data Plane)	`base_url` or `server_url` parameter → `HH_API_URL` env var → `https://api.dp1.us.honeyhive.ai`
Control-plane SDK and CLI (Control Plane)	`controlPlaneUrl` option or `--control-plane-url` flag → `HH_CONTROL_PLANE_URL` env var → `https://api.cp.us.honeyhive.ai`

For cloud-hosted HoneyHive (default), you don’t need to set any URL. Separate URLs are only needed for self-hosted federated deployments where the CP and DP run on different hosts.

Maintenance and Support

Self-hosted deployments include:

Dedicated implementation - Setup and deployment led by our forward-deployed engineering team
Guided upgrade process with versioned changelogs - Versioned releases with migration guides and patch diffs provided for your team to review and apply
Custom support packages - Tailored support availability and incident response policies to meet your organization’s requirements

For Day 2 operational procedures including upgrades, monitoring, backup, scaling, and incident response, see the Operations Guide.

Get started

Infrastructure Requirements

Supported dependency versions and required operators.

Security

Access controls, encryption, network policies, and compliance scope.

Data Flow & Residency

Data classification, flow boundaries, and retention controls.

Operations Guide

Day 2 procedures: upgrades, monitoring, backup, and incident response.

Contact us

Reach out to discuss your deployment requirements.

Getting Started

Observability

Evaluation

Prompt Management

Administration

Learn More

Deployment models

Supported platforms

What’s included

SDK Configuration

Environment Variables

SDK Parameters

Resolution Order

Maintenance and Support

Get started

Infrastructure Requirements

Security

Data Flow & Residency

Operations Guide

Contact us

​Deployment models

​Supported platforms

​What’s included

​SDK Configuration

​Environment Variables

​SDK Parameters

​Resolution Order

​Maintenance and Support

​Get started

Infrastructure Requirements

Security

Data Flow & Residency

Operations Guide

Contact us

Deployment models

Supported platforms

What’s included

SDK Configuration

Environment Variables

SDK Parameters

Resolution Order

Maintenance and Support

Get started