Borg App Hub replaces Heroku

Your infrastructure. Your rules.

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

Servers on Borg
  • No per-seat costNo seat count, no seat price.
  • Unlimited usageNo video, record, or activity caps.
  • Pay only for the AI and compute you useMetered, not per-head.

Workflows to explore

Plan your deployment workflow on Borg

Feature by feature

Server workflows: feature coverage

Separate deployment sync from the infrastructure that runs your app. Review the cluster, build, registry and data-service dependencies below.

App deployments

Partly covered

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.

Managed compute

Planned

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.

Container registry

Planned

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.

Release controls

Partly covered

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.

Add-ons and data

Planned

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

Borg and Heroku: compare the costs

Heroku per dyno per month; add-ons billed separately

PlanPriceLimits
Eco$5/moShared Eco dyno hours for personal accounts; sleeps after 30 minutes idle.
Basic$7/dyno/mo0.5 GB RAM; always on.
Standard-1X$25/dyno/mo0.5 GB RAM; 1 dyno unit per month.
Standard-2X$50/dyno/mo1 GB RAM; 2 dyno units per month.
  • Eco sleeps after 30 minutes of inactivity.
  • Basic and Standard-1X each have 0.5 GB RAM per dyno.
  • Databases and add-ons cost extra.

Public pricing checked 2026-10-07. Source

Argo CD on Borg App Hub

$0 per seat

  • Unlimited usage, no caps
  • Metered AI + compute, billed to actual use
  • Runs inside a workspace you control

For comparison: Compute, not seats, drives Heroku pricing: two Standard-1X dynos cost $600/year before add-ons.

Questions

Questions about servers on Borg

Is Argo CD a drop-in Heroku replacement?

No. Argo CD deploys to Kubernetes; you must bring a cluster, image registry, and build pipeline.

Does Argo CD host my app?

No. Your Kubernetes cluster hosts the app; Argo CD keeps deployments in sync with Git.

Can Argo CD build container images?

No. Use a separate build tool to create and publish images before deployment.

Do I still need a database?

Yes. Argo CD does not include Heroku-style managed database add-ons.

Is there an open-source or free alternative to Heroku?

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.

How does Borg App Hub pricing work?

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.

Explore your deployment workflow with Borg.

One App Hub, every tool your team already reaches for. No per-seat cost.

Early access for Search Atlas Mastermind and Enterprise.