> For the complete documentation index, see [llms.txt](https://docs.hivel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hivel.ai/archive/generic/hivel-on-premises-deployment-guide-generic/1.-overview.md).

# 1. Overview

On-Prem Deployment Guide (Generic)

## Overview

This guide walks through deploying Hivel on infrastructure that you provision and manage, independent of which cloud provider (or on-premises data center) you use. Wherever a step is generic - provisioning servers, databases, load balancers, DNS, and firewall rules - it is written in cloud-agnostic terms with the equivalent AWS, Azure, and GCP concepts called out for reference.

***Note on naming:*** the database and one of the backend services above are named "insightly" throughout this guide and in configuration files. This is Hivel's original internal product name, retained for historical reasons - it is not a typo and does not refer to a separate product.

**Data flow:** integration traffic (Jira/GitHub/GitLab webhooks or polling) flows into the API Gateway, which routes it to the relevant backend service, which reads and writes PostgreSQL. The UI talks to the API Gateway; the API Gateway talks to the Auth Service to validate sessions. No application traffic leaves your network except outbound calls to your connected engineering tools and to Hivel's AWS-hosted ECR/S3 during setup and updates (see the note below and Network Requirements).

**Important:** Hivel's Docker images and the docker-onprem-installer package are distributed from Hivel's own AWS-hosted Elastic Container Registry (ECR) and S3 bucket, regardless of which cloud or data center you deploy into. The steps that reference AWS CLI, ECR login, and S3 download are about pulling Hivel's artifacts, not about where your infrastructure runs - these steps remain the same for every client.

### Choose This Guide If

Choose this guide if you're deploying on infrastructure that isn't AWS, or if you'd simply prefer cloud-agnostic instructions that work equally well on AWS. It covers Azure, GCP, and bare-metal/private data center deployments, with AWS equivalents called out for reference throughout.

* If you're specifically on AWS and want AWS-native instructions (EC2, RDS, and ALB terminology throughout), use the [AWS VPC](/self-managed-hivel-deployment/virtual-private-cloud/aws.md) guide instead.
* If you're specifically on Azure, use the [Azure VPC](/self-managed-hivel-deployment/virtual-private-cloud/azure.md) guide for Azure-native terminology.
* If you're on any infrastructure but want to run your own PostgreSQL instead of a managed database service, the self-hosted guide covers that variant - every other step is identical to this one.

Every guide deploys the identical set of Hivel services shown above - only the infrastructure-provisioning commands and terminology differ.

**Next step:** Prerequisites - confirm you have the access, tooling, and infrastructure this guide assumes before provisioning anything.

## <br>

{% columns %}
{% column %} <a href="/archive/generic/hivel-on-premises-deployment-guide-generic.md" class="button primary" data-icon="backward">Hivel On-Premises Deployment Guide (Generic)</a>
{% endcolumn %}

{% column %}

{% endcolumn %}

{% column %} <a href="/archive/generic/hivel-on-premises-deployment-guide-generic/2.-prerequisites-and-vm-server-requirements.md" class="button primary" data-icon="forward">Prerequisites & VM Server Requirements</a>
{% endcolumn %}
{% endcolumns %}