Documentation versions (currently viewingVaadin 14)

This tutorial is for an old Vaadin version. Read the same tutorial for the latest Vaadin version.

Deploying a Vaadin Flow Application on Heroku

Learn how to prepare a Vaadin app for production and how to deploy it on Heroku.
This tutorial is for Vaadin 14.
If this is your first time trying out Vaadin, you should read the same tutorial for the latest Vaadin version instead.

In this final chapter in the series, you learn how to deploy a Spring Boot application on Heroku.

This chapter covers:

  • Vaadin production builds.

  • Configuring PostgreSQL for production.

  • Creating a Heroku account.

  • Installing the Heroku CLI.

  • Creating and deploying a Heroku app.

Vaadin can be deployed on any cloud provider

You can also deploy your application onto other cloud platforms. Read the Cloud Deployment tutorials for more options.

Preparing the Application for Production

It’s important to build a separate, production-optimized version of the application before deploying it. In development mode, Vaadin has a live-reload widget, debug logging, and uses a quick, but unoptimized, frontend build that includes source maps for easy debugging. Unoptimized frontend bundles can contain several megabytes of JavaScript.

The pom.xml build includes a production profile configuration that prepares an optimized build which is ready for production.

Using a PostgreSQL Database in Production

During development, the application uses an in-memory H2 database. This is convenient and works well for a single user. In production, it is better to use something more robust and persistent. Heroku’s free tier supports PostgreSQL, so you can configure your application to use that.

First, add the PostgreSQL dependency in the production profile of pom.xml:

 <!-- Omitted -->

Next, configure how JPA should handle schema generation. Add the following two properties to the end of

Avoid data loss

This setup recreates the database on every deployment. If you are working with real data, you should use ddl-auto=none and instead use a database migration tool like Liquibase or Flyway so you can evolve the database schema without losing data.

Building a Production-Optimized JAR

Build the application with the production profile:

mvn clean package -Pproduction

This builds a production-optimized JAR file in the target folder.

Creating a Heroku Account and Installing the Heroku CLI

Complete the following steps to create a Heroku account and install the Heroku CLI.

  1. Go to, create a new account, and verify your email.

  2. Go to and follow the instructions for installing the CLI on your operating system.

Deploying a Vaadin Application to Heroku

Use the Heroku CLI to create and deploy your application.

  1. Log in:

    heroku login
  2. Install the Heroku Java plugin:

    heroku plugins:install java
  3. Create a new app. Replace APPNAME with a name of your choice. APPNAME is part of the URL, like, so choose a name that’s unique and easy to remember.

    heroku create APPNAME
  4. Enable the PostgreSQL plugin for the newly created app:

    heroku addons:create heroku-postgresql -a APPNAME
  5. Deploy the production-optimized JAR file you created in the previous section.

    heroku deploy:jar target/flowcrmtutorial-1.0-SNAPSHOT.jar -a APPNAME
  6. Open the application in your browser.

    heroku open
  7. In the event that something goes wrong, view the application logs.

    heroku logs --tail

Conclusion and Next Steps

Congratulations, you have now built a full-stack PWA and deployed it to Heroku.

Did you like the tutorial? Did you find anything that didn’t seem right? Reach out to me on Twitter @marcushellberg or Vaadin’s Discord chat server.

Now that you have a running application, you can use it to experiment further or use it as a foundation for your next idea.

Happy hacking, and ping us @vaadin on Twitter to show off the cool stuff you’ve built!

migration assistance

Download free e-book.
The complete guide is also available in an easy-to-follow PDF format.

Open in a
new tab
export class RenderBanner extends HTMLElement {
  connectedCallback() {

  renderBanner() {
    let bannerWrapper = document.getElementById('tocBanner');

    if (bannerWrapper) {

    let tocEl = document.getElementById('toc');

    // Add an empty ToC div in case page doesn't have one.
    if (!tocEl) {
      const pageTitle = document.querySelector(
        'main > article > header[class^=PageHeader-module--pageHeader]'
      tocEl = document.createElement('div');

      pageTitle?.insertAdjacentElement('afterend', tocEl);

    // Prepare banner container
    bannerWrapper = document.createElement('div'); = 'tocBanner';

    // Banner elements
    const text = document.querySelector('.toc-banner-source-text')?.innerHTML;
    const link = document.querySelector('.toc-banner-source-link')?.textContent;

    const bannerHtml = `<div class='toc-banner'>
          <a href='${link}'>
            <div class="toc-banner--img"></div>
            <div class='toc-banner--content'>${text}</div>

    bannerWrapper.innerHTML = bannerHtml;

    // Add banner image
    const imgSource = document.querySelector('.toc-banner-source .image');
    const imgTarget = bannerWrapper.querySelector('.toc-banner--img');

    if (imgSource && imgTarget) {