Admin panels
Fast CRUD-heavy backoffice screens directly from your Java model.
Mateu
Build backoffice UIs without building a frontend. Backend-driven UI for distributed systems.
The problem
Section titled “The problem”Most business applications end up with two applications:
backend → API → frontend → duplicated model → duplicated validationThat usually means duplicated business concepts, duplicated validation, more glue code, more moving parts, and harder maintenance.
The Mateu approach
Section titled “The Mateu approach”backend (Java · Kotlin · C# · Python) → Mateu wire protocol → browser · desktop · mobileThe backend owns the UI.
Mateu lets your backend expose real business UIs directly, without turning every internal tool into a separate frontend project.
@UI("/orders")public class Orders extends AutoCrud<Order> {}
Wondering how this differs from a React SPA, Vaadin, or a CRUD generator? See Mateu vs the traditional stack →.
What you can build
Section titled “What you can build”Distributed backoffices
Let each microservice define its own UI and compose everything in one shell.
Embedded UI
Use Mateu inside React, Vue, Angular or plain HTML through a web component.
Real-world architectures
Works naturally with microservices, DDD, CQRS, and hexagonal architecture.
Works with your stack
Section titled “Works with your stack”Mateu works with Spring Boot MVC, Spring WebFlux, Micronaut, Quarkus, and any HTTP-based Java backend. You keep your architecture. Mateu becomes one more inbound adapter.
One protocol, many stacks
Section titled “One protocol, many stacks”Mateu’s UI travels as a wire protocol, not as framework code. That means:
- Polyglot servers — write your UI in Java, Kotlin, C# or Python (C# and Python are early-stage); they all emit the same UI model.
- Multi-frontend — the same backend renders on five web design systems (Vaadin, SAP UI5, Oracle Redwood, PatternFly, SLDS) and on native desktop and mobile (JavaFX, Compose Multiplatform, React Native), without touching your code.