Prometheus vs WeWeb
Side-by-side trajectory, velocity, and editorial themes.
Prometheus ships 3.13 LTS while hardening the 3.5 line against a steady drip of CVEs
Prometheus is running two supported tracks at once: the long-lived 3.5 LTS, which now takes near-monthly security-only patches, and the new 3.13 LTS, which lands a large batch of PromQL, service-discovery, and TSDB work. The bulk of recent releases are security maintenance and incremental engine improvements rather than new user-facing surface.
The center of gravity is experimental PromQL (start-timestamp-aware rate/increase, smoothed/anchored rate over native histograms, new scalar and search functions) and native-histogram maturation across TSDB and scrape. Alongside that runs a disciplined security cadence — sanitize-html bumps, credential-forwarding fixes on redirects, snappy-decode limits — backported across both LTS lines.
Expect 3.13.x to stabilize out of RC and continue the native-histogram and start-timestamp buildout behind feature flags, with the 3.5 LTS line receiving security-only patches as new CVEs surface.
WeWeb is going AI-native, letting external tools build in your project
WeWeb is pushing its visual web builder toward AI-native development. It shipped MCP support so external AI tools can understand and build directly in a WeWeb project, then followed with in-app WeWeb AI gaining planning and task tracking plus MCP quality-of-life fixes. Underneath, the core keeps getting refined — a redesigned Supabase Select, formula columns in table views, and steady editor, navigation, and publishing polish.
The arc is toward a builder where AI is a first-class way to construct apps, whether through the in-app assistant or an external tool driving the project over MCP. Recent releases pair that agentic surface with data-layer depth (Supabase, formula columns) and deployment ergonomics, suggesting WeWeb wants AI-assisted building to sit on top of a solid, data-connected foundation rather than replace it. The messaging around 'AI, visual, or both' signals a deliberately hybrid workflow.
Expect WeWeb AI and MCP to keep maturing together — richer planning, more reliable agent edits — alongside continued Supabase and data-source depth, given how these two threads dominate the recent cadence.
See more alternatives to Prometheus →
See more alternatives to WeWeb →