Skip to main content

How Goldline works

Goldline has two halves. The control plane is hosted and operated by Goldline at goldline.tech. Everything that runs your applications, including your Kubernetes clusters and your container registry, stays in your own cloud account on AWS, Azure or Google Cloud. A small Goldline Agent in each cluster connects the two.

How Goldline worksEngineering teams, AI coding agents and CI pipelines reach the hosted Goldline control plane through its secure front door, and Goldline imports services from your GitHub org. The control plane holds the application catalog, release and promotion, environments, insights, orchestration and a registry gateway. In your own AWS, Azure or Google Cloud account, the Goldline Agent runs in your Kubernetes clusters alongside Argo CD, Argo Rollouts, Istio and OpenTelemetry. The agent connects outward to orchestration over TLS, with no inbound ports. The registry gateway pushes images to your container registry, and your clusters pull from it.WHO SHIPSEngineering teamsWeb portal and CLIAI coding agentsClaude Code, Codex and moreCI pipelinesGitHub Actions, service accountsYour GitHub orgEvery repo scanned for servicesGoldline control planeHOSTED SAAS · GOLDLINE.TECHSecure front doorSingle sign-on, role-based policy on every call, audit trailApplication catalogServices, versions andAI-drafted manifestsRelease & promotionDev → QA → Prod withwaves and canariesEnvironmentsClusters, namespaces andpreview environmentsInsightsHealth, DORA metrics anddeployment patternsOrchestrationEvery change is a tracked job, sent to the right clusterRegistry gatewayOne Goldline login to push images to your registryYour cloudYOUR AWS, AZURE OR GCP ACCOUNTKubernetesYour clusters on EKS, AKS or GKEGoldline AgentOne Helm install, connects outwardArgo CDGitOps: every change reconciledArgo RolloutsCanary releases, gated by healthIstio service meshIngress, friendly URLs, previewsOpenTelemetryMetrics, logs, traces collected in-clusterYour container registryImages never leave your accountpullimportimage pushOutboundTLS only.No inboundports.
Hosted and operated by GoldlineRuns in your accountGoldline component inside your clusterAgent connection: deploy jobs out, status and telemetry back

Who ships​

Changes reach Goldline from three places, all through the same secure front door:

  • Engineering teams, using the web portal and the CLI.
  • AI coding agents, such as Claude Code and Codex.
  • CI pipelines, such as GitHub Actions, using service accounts.

Goldline also scans every repository in your GitHub org for services and imports them into the application catalog.

Your cloud​

Your applications run in your own AWS, Azure or Google Cloud account. Goldline doesn't host your workloads or store your images.

Kubernetes​

Your applications run on your own Kubernetes clusters, on Amazon Elastic Kubernetes Service (EKS), Azure Kubernetes Service (AKS) or Google Kubernetes Engine (GKE). Each cluster runs the Goldline Agent, installed with a single Helm chart, alongside the open-source tooling Goldline drives.

How the agent connects​

The Goldline Agent connects outward to the control plane. Deploy jobs come down that connection, and status and telemetry go back up it.

  • The connection is outbound TLS only.
  • Your cluster needs no inbound ports open for Goldline.

Your container registry​

Application images are pushed to your own container registry through Goldline's registry gateway, and your clusters pull them from there. Images never leave your account.

Open source underneath​

Inside your clusters, Goldline drives standard CNCF tooling, so your platform team already knows how it works.

ProjectWhat it does in Goldline
GitHubWhere your code lives. Goldline scans your repositories for services.
KubernetesRuns your applications, on EKS, AKS or GKE.
HelmInstalls the Goldline Agent.
Argo CDReconciles every change to your clusters the GitOps way.
Argo RolloutsRuns canary releases, gated by health.
IstioProvides ingress, friendly URLs and preview environments.
OpenTelemetryCollects metrics, logs and traces in the cluster.