App deployments
Partly coveredRelease new app versions.
Why it matters. Teams can ship changes without manual server steps.
On Borg. Push a Git change and Argo CD syncs your Kubernetes manifests automatically, though it never builds your code.
Borg App Hub replaces Heroku
Explore Git-based deployments with Argo CD. You need a Kubernetes cluster, build pipeline and image registry; this workflow does not provide managed hosting.
Early access for Search Atlas Mastermind and Enterprise.
The Borg collective Engineering
Workflows to explore
Sync Git-defined deployments to a Kubernetes cluster you provide
Build and publish container images through your own pipeline and registry
Review sync history and plan rollbacks through Git
Connect databases and other data services separately
Feature by feature
Separate deployment sync from the infrastructure that runs your app. Review the cluster, build, registry and data-service dependencies below.
Release new app versions.
Why it matters. Teams can ship changes without manual server steps.
On Borg. Push a Git change and Argo CD syncs your Kubernetes manifests automatically, though it never builds your code.
Run app and worker processes on dynos.
Why it matters. Apps need a place to stay online.
On Borg. Deploy app and worker processes to your own Kubernetes cluster, which you provide and operate yourself.
Store deployable container images.
Why it matters. Deployments need a versioned artifact.
On Borg. Pull versioned images from an external registry since Argo CD doesn't host one itself.
Review releases and roll back when needed.
Why it matters. Teams can recover from a bad change.
On Borg. Review sync history and drift at a glance, then roll back by reverting the commit in Git.
Attach managed data services and extensions.
Why it matters. Apps often need a database or queue.
On Borg. Deploy a database or queue as a Kubernetes resource, though there's no managed add-on marketplace like Heroku's.
Some upstream apps gate certain features behind their own licenses; the coverage chips above say where.
The math
Heroku per dyno per month; add-ons billed separately
| Plan | Price | Limits |
|---|---|---|
| Eco | $5/mo | Shared Eco dyno hours for personal accounts; sleeps after 30 minutes idle. |
| Basic | $7/dyno/mo | 0.5 GB RAM; always on. |
| Standard-1X | $25/dyno/mo | 0.5 GB RAM; 1 dyno unit per month. |
| Standard-2X | $50/dyno/mo | 1 GB RAM; 2 dyno units per month. |
Public pricing checked 2026-10-07. Source
Argo CD on Borg App Hub
$0 per seat
For comparison: Compute, not seats, drives Heroku pricing: two Standard-1X dynos cost $600/year before add-ons.
Questions
No. Argo CD deploys to Kubernetes; you must bring a cluster, image registry, and build pipeline.
No. Your Kubernetes cluster hosts the app; Argo CD keeps deployments in sync with Git.
No. Use a separate build tool to create and publish images before deployment.
Yes. Argo CD does not include Heroku-style managed database add-ons.
Yes. Argo CD is open source and free; Coolify and Dokku are other self-hosted options. You still pay for the cluster, registry, storage, and operations to run it yourself.
There's no per-seat cost and no usage caps. You pay only for the AI and compute Argo CD uses, as part of your existing Borg subscription.
Weighing options? See the full Heroku alternatives comparison.
One App Hub, every tool your team already reaches for. No per-seat cost.
Early access for Search Atlas Mastermind and Enterprise.