Deployment Documents ← All white papers

Deploy GrandLine on your own cluster

Audience: anyone with basic cloud experience who wants to stand up a production-ready self-hosted GrandLine install on AWS, Azure, or GCP.

Pick the guide that matches where you want to run GrandLine. Each one walks you through the full install in the same order: prerequisites, DNS, dependency provisioning, configuration, DNS wiring, Helm install, and TLS. Every command is copy-paste and every placeholder is clearly marked.

AWS · EKS

Deploy on AWS EKS

VPC, EKS 1.30, RDS Aurora Postgres, ElastiCache Redis, S3 with KMS, IRSA, ALB + ACM wildcard cert. ~25 minutes.

Read the guide →

Azure · AKS

Deploy on Azure AKS

VNet, AKS 1.30, Flexible Server Postgres 16, Azure Cache for Redis, Blob storage, Workload Identity, Application Gateway. ~20 minutes.

Read the guide →

GCP · GKE

Deploy on GCP GKE

VPC, GKE 1.30 Autopilot-compatible, Cloud SQL Postgres 16, Memorystore Redis, GCS, Workload Identity, GCLB + managed certs. ~15 minutes.

Read the guide →


What all three guides have in common

Every GrandLine install. regardless of which cloud it runs on. produces the same thing: an API, a BullMQ worker, a Next.js dashboard, backed by Postgres 16, Redis 7, and an S3-compatible object store, fronted by an ingress with a real TLS certificate on a domain you own.

The three install paths differ only in which cloud primitives back the data services and which pod identity mechanism gives the worker credentials to scan your accounts. The Helm chart, the images, the bootstrap flow, and the first-login experience are identical.

Cross-cloud discovery works from any install. A customer on EKS can connect AWS, Azure, and GCP accounts through the dashboard after install. Where GrandLine runs and which clouds it discovers are independent decisions.

Before you pick a guide

You'll need, on your laptop: terraform >= 1.6, helm >= 3.14, kubectl, and the cloud CLI for your target (aws, az, or gcloud) authenticated to the account you'll be deploying into.

You'll need, on the cloud side: an empty account / subscription / project you can deploy into, a domain you control, and a few hundred USD/month of budget (see each guide's cost section).

Related references

Self-hosted product page · Security white paper · Operations & reliability · All docs

Revision 2026-Q2. If anything here is wrong, missing, or unclear, email [email protected] and we'll correct it.