Appwrite vs Argo CD
Side-by-side trajectory, velocity, and editorial themes.
Appwrite hardens auth and broadens its framework and runtime surface as a Firebase alternative.
Appwrite is an open-source backend-as-a-service competing with Firebase and Supabase across auth, functions, storage, realtime, and hosted Sites. The recent cadence is broad and infrastructure-heavy: auth hardening (password strength, email policies), new realtime primitives (Presences), storage speedups, more build runtimes (Bun, Deno, Dart, Flutter), and a first-class React library. It also tightened free-tier economics by deleting long-paused free projects.
The platform is investing on two fronts at once — developer experience (React hooks, monorepo-aware Git build triggers, a Claude Code plugin) and backend breadth (presence, auth policies, faster uploads). The pattern is filling parity gaps with Firebase and Supabase while courting framework-native and agent-assisted workflows. Free-tier cleanup suggests attention to cloud cost discipline alongside feature growth.
Expect the React library to grow past auth into data and realtime hooks, and continued runtime and framework additions for Sites and Functions.
Argo CD's 3.5 line is in release-candidate hardening after a feature-heavy rc1 (Helm 4, supply-chain, Gateway API).
Argo CD shipped 3.4.0 to GA and has moved the 3.5 line into release candidates. The 3.5.0-rc1 carried a large feature set: Helm 3-to-4 migration, opt-in source-integrity verification for the hydrator, Gateway API support in the network view, mTLS in the repo-server, server-operation impersonation, and ApplicationSet UI work, while rc2 is bug-fix stabilization. The project keeps a strong supply-chain posture with cosign-signed images and SLSA Level 3 provenance.
Argo CD is converging 3.5 toward GA, so expect further rc bug-fix rounds until it stabilizes. The 3.5 theme blends supply-chain security (source integrity, provenance, mTLS), ecosystem currency (Helm 4, Gateway API), and ApplicationSet and UI maturation. After GA, the rolling stable tag advances and the 3.4 line drops to maintenance cherry-picks.
Expect one or more further 3.5.0 release candidates with bug-fix cherry-picks, then a 3.5.0 GA that moves the rolling stable tag forward.
See more alternatives to Appwrite →
See more alternatives to Argo CD →