Vaadin 25.3: AI you can audit, and observability without the Java agent
Vaadin 25.3 is the third feature release in the 25.x line. Three of its larger additions answer the same question in different places: what just happened? You can see which form fields the AI filled and how confident it was, what your application is doing in production, and whether a coding agent's last edit reached the running app.
- ▪Vaadin 25.3 is the third feature release in the 25.x line.
- ▪Three of its larger additions answer the same question in different places: what just happened?
- ▪You can see which form fields the AI filled and how confident it was, what your application is doing in production, and whether a coding agent's last edit reached the running app.
Hacker News (AI / LLM) files mainly under ai. We currently carry 7,145 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Vaadin |
| Canonical URL | https://vaadin.com/blog/vaadin-25-3-release |
| Publication time | Thu, 01 Oct 2026 12:30:57 +0000 |
| Retrieval time | 2026-10-01T12:32:34.005Z |
| Last seen | 2026-10-01T12:32:34.005Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | hdgohhUerpsD · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Vaadin 25.3 is the third feature release in the 25.x line. Three of its larger additions answer the same question in different places: what just happened? You can see which form fields the AI filled and how confident it was, what your application is doing in production, and whether a coding agent's last edit reached the running app. Around them is the usual release work, and there is a fair amount of it: a Switch component, a Table family for HTML tables, date constraints, upload validation and chat style variants for Message List. Under the hood, Flow's browser-side engine is now TypeScript instead of Java compiled to JavaScript with GWT. And three kits are on their way out: SSO Kit, Collaboration Kit and AppSec Kit are deprecated and will not be in Vaadin 26.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Vaadin.
Discussion
0 commentsMore from Vaadin
