Appwrite vs Kubernetes
Side-by-side trajectory, velocity, and editorial themes.
Appwrite broadens from Firebase alternative to full app platform, adding realtime primitives and agent tooling.
Appwrite is shipping across its whole surface at once: a new first-class Presences API for realtime status, runtime breadth (Dart, Flutter, Bun, Deno), Git deployment triggers with branch and path filters, faster parallel Storage uploads, Auth email policies, and an Appwrite plugin now in the official Claude marketplace. Database work is maturing too, with relationships hitting GA and BigInt columns added.
The platform is filling in primitives that push it past a backend-as-a-service toolkit toward an application platform. Presences targets multiplayer and live-collaboration apps; runtime and deployment controls court serious teams and monorepos; the Claude marketplace listing plants a flag in agent-native development. The throughline is reducing the reasons a team would reach outside Appwrite.
Expect continued realtime and collaboration primitives building on Presences, plus deeper agent/MCP tooling now that the plugin is in the official marketplace.
Kubernetes 1.36 leans into workload-aware scheduling while clearing legacy security debt.
Kubernetes is mid-release cycle around v1.36, with multiple long-running features graduating to Beta or GA — Mixed Version Proxy, PSI metrics, volume group snapshots, and DRA maturation. The project is simultaneously deprecating Service.externalIPs over a six-year-old CVE class and archiving the official Dashboard in favor of Headlamp. The cadence is steady upstream release-train work, weighted toward AI/ML workload primitives this quarter.
The center of gravity is shifting toward batch and AI/ML workloads — the new PodGroup API, gang scheduling, DRA expansion, and workload-aware scheduling primitives all point that way. Security and ecosystem hygiene (CVE record correction, ExternalIPs removal, Dashboard sunset) are getting equal weight, suggesting the project is using v1.36 to clear inherited liabilities. etcd 3.7 entering beta means storage-layer changes are queued for the next release.
Expect v1.37 to make workload-aware scheduling defaults-on for batch workloads and graduate at least one DRA sub-feature to GA. The ExternalIPs removal will likely land as default-disabled in the same release.
See more alternatives to Appwrite →
See more alternatives to Kubernetes →