Introduction
What Longbridge GitOps is — a fully managed Argo CD you never have to run — who it's for, and where it is today.
Early access. GitOps is rolling out behind an organization flag. Instance-hours are metered but not yet billed.
Longbridge GitOps is a fully managed Argo CD. You create an instance, connect
your git repositories, and link the clusters you deploy to — Longbridge runs,
patches, backs up, and secures the Argo CD itself. You get the genuine Argo CD UI,
API, and argocd CLI at your own hostname; there is nothing to re-learn.
Why it exists
GitOps has a chicken-and-egg problem: the Argo CD that manages your clusters has to live somewhere, and running a management cluster to hold it is exactly the undifferentiated work you would rather not own. GitOps is the answer to “where does Argo CD live” — a management plane you don’t run.
- Link a Longbridge cluster in one click. A tenant cluster’s control plane is already hosted on the same shard, so the link needs no networking on your side: the platform mints a dedicated, revocable credential and points Argo CD at the in-shard apiserver.
- Manage any cluster. Reachable clusters link with the credentials you supply; Longbridge clusters are the one-click case, not the only case.
- Sign in through Longbridge. Your org members sign in to Argo CD with their platform identity — no local Argo accounts to hand out or forget, and removing a member removes their Argo access.
- Cheap and uncapped. Priced per instance by tier and hour — never per application, linked cluster, or user. Unlimited apps, clusters, and users at every tier is the point, not an upsell.
Where it is today
GitOps is in early access behind an org flag. Instances, cluster links, versioned upgrades, and daily backups are built; the browser sign-in flow and pricing are being finalized. See the implementation plan for current status.