Technology
Built on Converge Cloud, Crossplane, and ArgoCD
Every environment you design in Cloud Build runs on infrastructure managed the same way, end to end: declared as code, provisioned through Crossplane, and kept in sync by ArgoCD.
Converge Cloud
The cloud platform itself. Every workload runs in the Luzon region, on a shared foundation network across public and private subnets — every instance, load balancer, and database Cloud Build composes is provisioned directly here.
Crossplane ↗
The infrastructure-as-code control plane behind every design. Cloud Build's Compose stage turns your architecture into Kubernetes-native, declarative Crossplane manifests — provider-convergecloud speaks natively to Converge Cloud's own resource model.
ArgoCD ↗
Continuous delivery, the GitOps way. Once your manifests are reviewed and merged, ArgoCD keeps the running environment in sync with exactly what's declared in Git — no manual apply, no drift.
How It Works
The Cloud Operations Loop
Every workload on Converge Cloud moves through the same loop: find or build it, ship it, keep it running well, and feed what you learn back into the next design.
1
Discover or Build
Launch a ready app from the Marketplace, or plan and compose your own with Nora in Cloud Build.
2
Deploy
Compose ships it as validated infrastructure, running directly on Converge Cloud.
3
Operate
Cloud Operations monitors, secures, and meters what's running — three views of the same environment.
4
Improve
What Operations learns routes back into the next Plan — the loop, not a one-way pipeline.
The Loop — Step 1 of 4
Discover or Build
Every workload starts one of two ways: pick something ready-made, or describe what you need and let Nora design it. Neither path touches a console by hand.
Discover — the Marketplace ↗
Six ready-to-deploy apps today, one click each.
📊 Grafana + Prometheus⚡ n8n🐬 MySQL🦊 GitLab CE🍵 Gitea📝 WordPress
Build — Cloud Build's Plan stage ↗
No app fits? Describe it in plain language.
"I need a Postgres database and two app servers behind a load balancer, sized for staging."
Nora's Role — The Architect
Nora is the agent that composes the infrastructure code behind every Marketplace app — and the same skill designs the custom cloud environments in Cloud Build. She prices each part of that environment as she builds it, so designing infrastructure is one holistic process, not a handoff between separate tools.
The Loop — Step 2 of 4
Deploy
Cloud Build's Compose stage turns the plan into declarative, Kubernetes-native Crossplane manifests, and provisions them directly on Converge Cloud's shared foundation network.
Plan
Composed with Nora
Git
Pushed under the hood
ArgoCD
Picks up the change
Crossplane
Deploys the manifests
Converge Cloud
Running, no manual apply
Why declarative, not manual
Reproducible. The same manifest produces the same environment every time — a manual deploy depends on whoever ran the commands, and in what order, that day.
Auditable. Every change is a commit in Git, with a reviewer and a diff — not an undocumented click in a console that nobody can trace back later.
Self-correcting. ArgoCD continuously reconciles what's running against what's declared, so drift gets caught and corrected instead of quietly piling up until something breaks.
Nora's Role — The Composer
Nora composes the infrastructure code into Crossplane manifests, and validates them against the existing documents to make sure what's designed is actually deployable.
The Loop — Step 3 of 4
Operate
Cloud Operations gives you three views of the same running environment — nothing runs unwatched between deploys.
Monitor
Health and uptime, watched continuously.
Secure
Posture and access, kept in view.
Meter
What it's costing you, before the bill.
Nora's Role — The Diagnostician
Nora has access to your logs and metering data. When an alert or anomaly is detected, she reads the logs herself to identify the problem.
The Loop — Step 4 of 4
Improve
What Operations surfaces — a cost spike, a security finding, a capacity ceiling — feeds straight back into your next Plan. The loop closes on itself; it's not a one-way pipeline from build to forgotten.
A finding from Operate becomes an input to the next Plan
Describe the fix the same way you described the original build — Nora carries it through Compose and Operate again.
Nora's Role — The Advisor
Based on the data gathered in Operate, Nora recommends a set of changes — and waits for your approval before carrying any of them through Plan again.