Comparison

How Wardn compares to the established GitOps tools. We built Wardn because we believe you shouldn't need a dedicated platform team to run ArgoCD.

Feature Matrix

Feature	Wardn	ArgoCD	Flux
Git sync	✅	✅	✅
Raw YAML	✅	✅	✅
Kustomize	✅	✅	✅
Helm	�	✅	✅
Image-source deploys	✅ (distinctive)	❌	❌
Server-side apply	✅	✅	✅
Pruning	✅	✅	✅
Self-heal	📋 (field only)	✅	✅
Health checks	🚧 (5 kinds)	✅	✅ (limited)
Multi-cluster	✅	✅	✅
Approval gates	✅ (`requiresApproval`)	❌	❌
Freeze	✅ (`spec.freeze`)	✅ (suspend)	✅ (suspend)
Sync waves	📋	✅	✅ (dependsOn)
Hooks	📋	✅	🚧
Rollback	✅	✅	❌
Diff view	❌	✅	❌
Web UI	✅	✅	❌ (3rd party)
Built-in auth	✅ (Better Auth + orgs)	❌ (needs Dex)	❌
RBAC	✅ (org + scoped bindings)	✅ (complex)	❌
Audit log	✅	✅	❌
SOPS	🚧 (store; no decrypt)	✅	✅
ESO integration	✅	🚧	✅
Vault direct	� (image env only)	❌	❌
Notifications	🚧 (Slack only)	✅	✅
Webhooks	🚧 (GitHub, unsigned)	✅	✅
CLI	🚧 (clusters/can-i/mcp)	✅	✅
API	✅	✅ (gRPC/REST)	❌
MCP/agent access	✅	❌	❌

✅ Available · 🚧 Partial · 📋 Planned · ❌ Not available

Tool	Components
Wardn	3 — server, operator, frontend (+ Postgres, Redis)
ArgoCD	5+ — server, repo-server, application-controller, dex, redis, notifications-controller
Flux	3+ — source-controller + kustomize-controller + helm-controller operators

Fewer components means simpler installation, less to monitor, smaller attack surface, and easier troubleshooting.

Auth — ArgoCD needs Dex/OIDC for SSO; Wardn embeds Better Auth (email + social + org/team memberships).
RBAC — ArgoCD uses Casbin policies in a ConfigMap; Wardn's is org-role + scoped-binding, UI-managed.
Sources — Wardn adds an Image source type (registry-driven deploys — no git repo needed) on top of git paths.
Agents — Wardn exposes an MCP endpoint; ArgoCD has no agent surface.
Gaps — ArgoCD is ahead on self-heal, diff view, sync waves/hooks, Helm, and app-of-apps.

Choose ArgoCD if you need its mature ecosystem, ApplicationSets, or proven self-heal/diff today.

UI — Flux has none; Wardn ships the platform app.
Auth — Flux has none; Wardn has orgs, teams, scoped roles.
Rollback — Flux reverts in git; Wardn has POST /rollback.
Gaps — Flux is ahead on source maturity (OCI/Helm repos) and SOPS decrypt-at-apply.

Choose Flux if you want minimal composable operators and build the platform layer yourself.

You want GitOps without the platform-team overhead
You need a UI with built-in auth, orgs, and scoped RBAC out of the box
Image-source deploys fit your workflow (no git repo required per app)
You want an MCP/agent-access surface — proposals gated by human approval
You value operational simplicity over feature maximalism, and accept the gaps above

ArgoCD → Wardn migration tooling is on the roadmap. The App spec maps mechanically from ArgoCD's Application:

ArgoCD `Application`	Wardn `App`
`spec.source.repoURL`	`spec.source.git.repoURL`
`spec.source.targetRevision`	`spec.source.git.branch`
`spec.source.path`	`spec.source.git.path`
`spec.syncPolicy.automated`	`spec.syncPolicy.automated`
`spec.syncPolicy.automated.prune`	`spec.syncPolicy.prune`
`spec.syncPolicy.automated.selfHeal`	`spec.syncPolicy.selfHeal` 📋 unwired
`spec.destination.server`	`spec.destination.cluster` (registered name)
`spec.destination.namespace`	`spec.destination.namespace`
`spec.sources[].helm.valueFiles`	`spec.source.git.helm.valuesFile` 📋 unwired