Skip to main content
Configure isolation for your Honeycomb Private Cloud deployment. Honeycomb Private Cloud can be configured as single-tenant or multi-tenant to match your organizational structure and isolation requirements. Both Honeycomb-managed and self-managed deployment models support either tenancy option.

Single-Tenant

A single-tenant deployment gives you a dedicated Honeycomb environment with complete isolation from other tenants. Single-tenant deployments work well for organizations that need to:
  • Maximize isolation: Get complete separation at the infrastructure level with no shared resources.
  • Meet strict compliance requirements: Satisfy regulatory mandates that require dedicated infrastructure.
  • Guarantee data privacy: Ensure telemetry data has no possibility of cross-tenant exposure.
  • Isolate performance: Guarantee that your workload performance is unaffected by other tenants.
  • Customize resource allocation: Configure infrastructure specifically for your telemetry patterns and volume.
Single-tenant configurations are common in financial services with strict regulatory requirements, healthcare organizations subject to HIPAA or other health data protection regulations, government agencies requiring FedRAMP or other government compliance certifications, and high-volume enterprises with massive telemetry volumes that require dedicated, optimized infrastructure.

Architecture

In a single-tenant deployment:
  • All infrastructure components serve only your organization
  • No resources are shared with other Honeycomb customers
  • Your data stays completely isolated from other tenants
  • Infrastructure can be sized and optimized specifically for your workload

Multi-Tenant

A multi-tenant deployment provides logical separation within shared infrastructure between teams or business units. Multiple groups maintain autonomy while benefiting from operational efficiency. Multi-tenant deployments work well for organizations that need to:
  • Separate by organization: Create distinct Honeycomb environments for different business units, regions, or teams.
  • Improve operational efficiency: Share infrastructure management across multiple groups.
  • Optimize costs: Distribute infrastructure costs across multiple teams or business units.
  • Enable team autonomy: Give each group their own Honeycomb environment with independent user management and configuration.
Multi-tenant configurations are common in large enterprises with multiple business units that need separate observability environments.

Architecture

In a multi-tenant deployment:
  • Multiple Honeycomb environments run within shared infrastructure
  • Each tenant has logical isolation with independent:
    • User authentication and authorization
    • Data storage and access controls
    • Configuration and settings
    • API keys and integrations
  • Infrastructure resources are shared across tenants for efficiency
  • Each tenant maintains operational independence

Comparing Tenancy Options

AspectSingle-TenantMulti-Tenant
Infrastructure isolationCompleteLogical
Data isolationPhysical and logicalLogical only
Compliance suitabilityHighestsuitable for most enterprise needs
Performance isolationGuaranteedShared
Administrative overheadSingle environmentMultiple environments
Cost efficiencyHigherLower through sharing
ScalabilityDedicatedShared
Best forMaximum isolation and complianceOrganizational separation with operational efficiency

Combining Tenancy and Deployment Models

You can combine tenancy options with deployment models to match your specific needs:
  • Single-tenant, Honeycomb-managed: Maximum isolation with minimal operational overhead
  • Single-tenant, self-managed: Complete control and isolation for highly regulated or air-gapped environments
  • Multi-tenant, Honeycomb-managed: Efficient support for multiple teams with Honeycomb handling operations
  • Multi-tenant, self-managed: Organizational flexibility with complete infrastructure control