Overview
This guide deploys Hivel on Azure infrastructure you provision and manage: one Azure Virtual Machine running Hivel's Docker containers, plus Azure Database for PostgreSQL (Flexible Server) as the managed application database. Your source code, commit data, and metrics remain in your Azure environment.
Important naming note: The database and one backend service are named "insightly". This is Hivel's original internal product name, retained in the platform. It is not a typo and does not indicate a separate product.
How data flows: Integration traffic (Jira/GitHub/GitLab webhooks or polling) → API Gateway → the relevant Service → Azure Database for PostgreSQL. The UI communicates with the API Gateway; the API Gateway validates sessions through the Auth Service. Redis is used internally by backend services on the VM and is never exposed publicly.
Important: Hivel's images and packages come from AWS. Even though your infrastructure runs on Azure, Hivel's Docker container images are distributed via Amazon ECR and the deployment package via Amazon S3: both on AWS. You will need both Azure CLI and AWS CLI, plus credentials for both Azure and AWS, to complete this guide. Your VM and database are Azure resources; the images and installer package you pull from are AWS resources. See Network Requirements for traffic destinations.
Make these three decisions before you start:
You will make three independent choices as you move through this guide. Use the table below to plan; detailed instructions appear at each relevant step.
Decision
Standard Path
Alternative Path
How to deploy services (see Deployment Methods)
Use deploy.sh script. Automates ECR authentication, image pulls, health checks, and log access.
Use Docker Compose directly. Only for manual control over container startup order or custom orchestration.
Which container registry to use (see ECR Access Configuration)
Use Hivel's ECR. Default option for most customers.
Use your own ECR. Only when your organization requires hosting images in your AWS account. Requires additional configuration.
How to expose the UI over HTTPS (see DNS Setup)
Use domain + Let's Encrypt. Choose when you have a domain you control; certificates are automatic.
Use self-signed certificate. Testing only; never for production.
Next step: Go to Azure Infrastructure Setup and CLI Configuration.
Last updated