Free Vaadin 8 support is over. What happens next?

Mikael Sukoinen
Mikael Sukoinen
On Mar 24, 2022 4:29:29 PM
In Product


After 5 years of free support, Vaadin 8 has reached its end of life. While applications developed with the unsupported framework will keep running, they will no longer receive security updates, compatibility patches and bug fixes. We recommend all projects to upgrade to the latest version, Vaadin 23. You can purchase extended maintenance for your Vaadin 8 application if you need more time to upgrade.

What are the improvements in Vaadin 23 compared to Vaadin 8? 

Vaadin 8 is of the previous generation of our Java web framework, which used GWT to implement client-side components. Parts of the component set originated from Vaadin 6, which was originally launched in 2009. In Vaadin 10, the component set was replaced for a more sustainable foundation with the open W3C Web Components standard. 

There are also numerous other improvements in the latest Vaadin version compared to Vaadin 8. New features and a simplified developer experience is only the surface of all the progress our technology has made between the releases:

  • Better and more components: Developers benefit from the openness of Web Components by being able to integrate more reusable components in their applications and running them on the latest browsers.
  • Theming: The latest W3C specifications for theming are available out-of-the-box. The Lumo theme uses CSS Custom Properties instead of SCSS, simplifying application building by eliminating the need for preprocessing for most browsers.
  • Accessibility: We test our components for compatibility with assistive technologies, such as screen readers, with help from external evaluators. This makes our library a good foundation to build modern, accessible UIs that comply with the latest accessibility requirements.
  • Real-time collaboration: Collaboration Engine provides real-time collaboration features to help users stay productive wherever they work.
  • New release model: Our simpler release model makes it easier for you to always stay on the latest Vaadin version and have access to the most feature-rich and up-to-date version of Vaadin.

What to do if you're still on Vaadin 8

We recommend all users to upgrade and stay on the latest Vaadin version. To help you to do this, we’re focusing on making the upgrades between releases smoother with a new release model.

An upgrade consumes less effort and resources than a rewrite on a comparable platform, as you can reuse your architecture, concepts, development model, backend and data binding. 

We’re also providing a range of modernization products and services to help you get from Vaadin 8 to Vaadin 23:

  • You can try the Classic Components that are native equivalents of your favorite Vaadin 8 components.
  • Prime and Enterprise subscribers may opt to purchase Extended Maintenance for Vaadin 8, if they wish to extend the lifespan of their Vaadin 8 applications. 
  • Use Multiplatfrom Runtime, which enables you to run portions of your Vaadin 8 app within Vaadin 23 for a gradual upgrade.
  • Contact us for a Modernization Assessment or Proof of Concept to ensure your upgrade is done with minimal downtime and within budget.

If you want to learn more about modernization, I recommend watching the on-demand webinar on the topic, featuring Ben Wilson. He also answered your common questions about upgrading from Vaadin 8 in a recorded live stream last year.

If you’re ready to give Vaadin 23 a go right now, configure and download a project from!

We can help 

We have guided many companies from older Vaadin versions or other technologies to the latest Vaadin version. If you’re still unsure about the best course of action, start by booking a free consultation with us.

Any questions? Ask away by commenting on this post or read our Vaadin 8 page for more information!

Mikael Sukoinen
Mikael Sukoinen
Mikael has a passion for writing text, code and music. He’s currently utilising his skills to explain difficult concepts in plain language at Vaadin Ltd.
Other posts by Mikael Sukoinen