WeWeb vs Kubernetes
Side-by-side trajectory, velocity, and editorial themes.
From front-end no-code builder to full-stack AI app generator.
WeWeb has crossed from a front-end no-code builder into a full-stack platform. In April it launched a native backend (database, APIs, auth, storage, server logic inside the editor) and rebuilt the editor around three tabs (Interface, Data & API, Settings). May releases are extending WeWeb AI from single-page generation to multi-page apps with more consistent handling of complex native elements.
The combined backend launch, editor redesign, and multi-page AI generation point at deliberate competition with Bolt, Lovable, and Cursor's app-builder products — the bet is on full-stack code-free generation, not template-based site building. Release cadence is high (multiple per week, occasionally same-day duplicates in the feed), mixing substantive features with rolled-up "improvements and fixes" bundles.
Expect WeWeb AI to gain backend-aware generation — schema, endpoints, auth flows in one prompt — and a GitHub or code-export story to neutralize the "real code" pitch that Bolt and Lovable lean on.
Kubernetes 1.36 leans into AI/ML scheduling and control-plane scaling.
The 1.36 cycle is graduation-heavy, with PSI metrics, declarative validation, and volume group snapshots all promoted to GA. Alongside that, the project is making architectural moves around workload scheduling (a new PodGroup API), API-server safety (Mixed Version Proxy on by default), and very-large-cluster scaling (server-side sharded list and watch in alpha). Etcd 3.7 has hit beta in parallel.
Kubernetes is repositioning the control plane for two pressures at once: AI/ML batch workloads, where gang scheduling and DRA are becoming first-class concerns, and very-large clusters, where the control plane itself needs to shard. The pattern across this cycle is consolidation — old experimental scaffolding is reaching GA or being removed (ExternalIPs), while new APIs land with explicit separation of static template from runtime state. Less feature sprawl, more API hygiene.
Expect 1.37 to push server-side sharded watch toward beta and to keep extending DRA's reach into native resources like memory and networking. Workload-aware scheduling will likely accumulate scheduler-plugin-level coordination patterns next, with downstream batch frameworks starting to converge on the PodGroup shape.
See more alternatives to WeWeb →
See more alternatives to Kubernetes →