Deployment
HirzHub is designed from the beginning as a customer-owned enterprise installation — not a SaaS product later adapted for private deployment. Choose an infrastructure model based on your security, operational and jurisdiction requirements.
Models
Whether the platform runs in a managed environment or inside customer infrastructure.
On-Premise
On-Premise deployment is designed for organizations requiring direct operational control.
Sovereign
Dedicated deployment provides an isolated HirzHub environment aligned to organizational and jurisdiction requirements. Identity, messaging data, secrets and application databases can remain isolated from unrelated customer environments.
Managed
Organizations that do not require self-operation can use a managed HirzHub environment while retaining the same core platform architecture and product model.
Runtimes
VM
Organizations should not be forced to adopt Kubernetes merely to run HirzHub. HirzHub supports a VM-oriented deployment model suitable for conventional Linux infrastructure.
Kubernetes
HirzHub also supports Kubernetes-based deployment for organizations that already operate container platforms. The architecture avoids unnecessary dependency on one Kubernetes distribution or public cloud provider.
Continuity
Air-gap
HirzHub's deployment model is designed to support controlled offline environments through:
HirzHub is designed around supported, versioned upgrades.
Upgrade an existing customer installation without rebuilding it, creating customer-specific branches or requiring data export and re-import.
Customer-owned HirzHub installations are designed so core communication does not stop because a vendor control plane becomes unavailable. Licensing, deployment and operational mechanisms are designed with offline and customer-controlled environments in mind.
Next step
Discuss infrastructure, networking, identity, storage, high availability, air-gap and operational requirements.
