Hilla apps can be built for delivery in production using the production build. They can be packaged as a Fat JAR, WAR file or as a native image.

There are some exciting new functions in the pipeline for the Hilla framework. Three of these improvements are presented in this blog post.

n:m relationships between entities can be implemented productively and flexibly in business web apps made with Hilla and the AutoGrid and AutoForm components.

Hilla apps can be built as a native image with an integrated server using GraalVM. They can be deployed this way. In conjunction with a Dockerfile, an individual Docker image can be created, and the application can be deployed as a Docker container, e.g. at fly.io.

Hilla apps can be built as a JAR file with an integrated server. They can be deployed with a suitable Java runtime environment. In conjunction with a Dockerfile, an individual Docker image can be created, and the application can be deployed as a Docker container, e.g. at fly.io.

Authentication and role-based authorization for Hilla web apps can be easily implemented, for example in conjunction with Keycloak and the Resource Owner Password Flow of OAuth 2.0.