Jmix is an open-source Java platform for enterprise software development with local and public AI models. It combines a Spring Boot–based full-stack framework, IntelliJ IDEA tooling, reusable enterprise capabilities, and AI-assisted workflows while preserving source-code ownership and architectural control.
Jmix supports application delivery through four connected stages: Plan → Develop → Configure → Run. Plan provides a low-friction entrance to a project before the organization installs the complete development toolchain. It helps IT leaders, analysts, architects, and developers evaluate an idea in terms of solution design, likely effort, relevant Jmix architectural concepts, and important trade-offs.
Once the direction is clear, software engineers continue in Develop, using Jmix to build and evolve the application. Authorized non-technical specialists work in Configure, adapting the capabilities intentionally exposed for runtime configuration. In Run, users, integrations, and AI agents access the application under shared security and governance.
Once the application is running, new requirements follow the appropriate delivery route. Changes that fit the application's runtime configuration boundaries move to Configure; changes requiring software engineering return to Develop. Teams revisit Plan when the underlying problem, solution design, or architectural direction needs to be reconsidered.
Jmix is designed primarily for data-centric and process-centric enterprise applications with substantial data models, business logic, security requirements, reporting, and integrations. For process-centric systems, Jmix provides BPMN 2.0 modelling and execution on a Flowable-based process runtime, with capabilities for designing, monitoring, and managing business processes.
Processes operate within the same application architecture as business data, services, user interfaces, and access control. Teams can connect user tasks, application logic, integrations, and automated activities into executable end-to-end processes. Developers retain source-code access and familiar Java engineering practices while Jmix supplies standardized architecture and reusable enterprise capabilities.
Jmix is not a visual-only environment for citizen developers. Professional developers remain responsible for the engineered application, while the Jmix delivery workflow brings analysts and integrators into productive collaboration through dedicated non-IDE tools. They can contribute structured inputs during Plan and adapt permitted application behaviour during Configure without taking over unrestricted source-code development. This gives organizations higher productivity without sacrificing architectural control or application ownership. Explore the Jmix overview.
Jmix Definition and Core Idea
Jmix follows a less-code approach: it reduces repetitive development work through conventions, code generation, visual designers, integrated platform services, and reusable add-ons. Developers still design the application, write and review code, integrate external systems, test changes, and control deployment.
This distinguishes Jmix from no-code tools that aim to let non-programmers assemble applications and from proprietary low-code platforms that place more of the application inside a vendor-specific development and runtime model. With Jmix, the source code remains the normal engineering artifact, and teams can use the broader Spring ecosystem when a requirement goes beyond the platform's built-in capabilities.
This approach makes Jmix a reliable foundation for enterprise-grade software products. Development teams can scale application scope and delivery while retaining control of source code, architecture, integrations, infrastructure, and deployment — without vendor-imposed runtime or customization limits.
What Does Jmix Include?
Jmix brings together an open application framework, professional developer tooling, and an ecosystem of reusable add-ons. AI support spans both software development and applications created with the platform.
Jmix Framework — Open-Source Application Foundation
Jmix Framework is an open-source, Spring Boot–based full-stack framework for enterprise web applications. It provides a consistent foundation for data access, security, business logic, and server-side web UI development. Because it is based on Spring Boot and mainstream Java technologies, teams can use established libraries and frameworks alongside Jmix.
The framework is distributed under the Apache 2.0 license. Application source code remains accessible and can be maintained using standard Java engineering, Git-based workflows, testing, and established delivery practices. View the Jmix source repository on GitHub.
Jmix Studio — Developer Tooling in IntelliJ IDEA
Jmix Studio is a plugin for IntelliJ IDEA. It assists with project setup, project configuration, data modelling, database migrations, CRUD UI scaffolding, and visual screen design. It also adds Jmix-aware navigation, code completion, inspections, and migration assistance.
Studio's visual designers, code generators, navigation, and inspections use deterministic algorithms and work without AI. They operate alongside direct access to the application source code, giving teams repeatable assistance for routine development tasks. AI-assisted tools can complement this workflow when the team chooses to use them. Studio supports IntelliJ IDEA Community Edition, while some Studio capabilities require a commercial subscription.
Jmix Add-ons — Reusable Enterprise Capabilities
The Jmix Marketplace provides add-ons for common application requirements, including auditing, email, reporting, notifications, maps, and business process management. Many are produced by the Jmix team, while others come from the community.
A Jmix add-on can include application logic, data model elements, and user interface components — not just a standalone code library. Add-ons can be browsed and installed from Studio. Developers can also create their own add-ons to package business-specific functionality for reuse across applications and teams. Licensing varies: 50+ marketplace add-ons are open source, while some require a commercial Jmix subscription.
Jmix AI Capabilities — Three Different Jobs
Jmix currently provides distinct AI capabilities rather than one generic "AI layer":
- Jmix AI Assistant is a Jmix-focused question-and-answer assistant available in the browser and in Jmix Studio. It uses official Jmix materials to answer development questions. Project code is included only when the developer explicitly attaches it.
- Jmix Agentic Toolkit equips supported general-purpose coding agents with Jmix architecture guidance, development rules, skills, and recommended tools for working with Jmix projects.
- AI Tools add-on brings an LLM-powered assistant into an application built with Jmix. It includes an embeddable chat interface, predefined and custom application tools, and a programmatic API built on Spring AI. The application team selects and configures the model provider.
Learn about AI-assisted development · Read the AI Tools documentation · Open Jmix AI Assistant
Together, these capabilities support AI across the Jmix development lifecycle: from getting Jmix-specific guidance and working with coding agents to integrating AI into enterprise applications. Teams can work with local and public AI models while keeping AI within the application's architecture, security, and engineering practices.
What Is Jmix Used For?
Jmix is most useful when an application has a meaningful domain model and must remain secure, maintainable, and adaptable as requirements evolve.
- Enterprise software development. Build employee- and partner-facing business systems with complex data, permissions, workflows, and integrations.
- Legacy application modernization. Replace an application or modernize it incrementally while moving toward a Spring Boot–based architecture.
- ERP extensions and modules. Build purpose-specific applications around an ERP rather than forcing every requirement into the ERP core.
- Admin panels. Create secure operational interfaces for managing business data, users, access, reports, and related processes.
- Data applications. Build systems centred on interconnected business entities, forms, tables, filtering, validation, and role-based access.
- Business process automation. Combine BPMN processes, user tasks, application services, business data, and external systems within one application.
Key Advantages of Jmix
For Developers and Architects
- Familiar stack. Build on Java or Kotlin, Spring Boot, Vaadin, and IntelliJ IDEA rather than learning a closed application language and proprietary engineering model.
- Reusable enterprise foundation. Use integrated data access, security, UI patterns, and optional business add-ons instead of assembling the same foundation independently for each project.
- Source-code control. Visual tooling accelerates routine work, while developers retain direct access to application code and can extend it with the Spring ecosystem.
- Consistent architecture. Shared conventions and platform services reduce unnecessary variation between applications and make onboarding and long-term maintenance more predictable.
- AI optionality. Teams can use deterministic Studio tools, AI-assisted development, or both. AI augments the engineering process; it does not replace developer review and accountability.
For Organizations
- Application ownership. Organizations retain their application source code, data, infrastructure, and deployment choices.
- No runtime or end-user fees for built applications. Jmix commercial plans charge for developer access to premium tools and add-ons rather than for the number of application users or deployments.
- Lower repeated platform work. Standard architecture and reusable capabilities let engineering teams concentrate more of their effort on business-specific functionality.
- Controlled adaptability. Depending on the add-ons selected, authorized users can manage roles and permissions, reports, business processes, notifications, and selected domain-model extensions at runtime without turning the application into an unrestricted no-code environment.
Explore the Jmix ROI calculator.
When Should You Not Use Jmix?
Jmix requires professional software-development capability. It is not intended for business users who want to create complete applications without developers. It is also not designed primarily for static websites, content publishing, or simple pages with little domain logic, security, workflow, or expected evolution.
A small application can still be a good fit if it has complex data, permissions, integrations, or a long operational life. Conversely, an application may be a poor fit regardless of size when its main challenge is a highly customized consumer front end rather than enterprise data and business logic. See whether Jmix fits your project.
Not having an established internal development team is not automatically a reason to reject Jmix. The Jmix Services team can help a new team establish its delivery capability through training, infrastructure setup and guidance, mentoring, and experienced specialists during the early project phases. The engagement can be planned around a gradual handover as the internal team becomes ready to own development and operations.
| Approach | Primary model | Engineering control | Important trade-off |
|---|---|---|---|
| Jmix | Open-source enterprise application platform for Java teams | Application source code, architecture, infrastructure, data, and deployment remain under the team's control | Requires Java/JVM development skills |
| Proprietary low-code | Visual modelling and vendor-specific platform services; target users vary by product | Customization, deployment, source access, and runtime terms vary by vendor | Can accelerate supported scenarios, but teams must evaluate platform dependency and licensing |
| Traditional Java/Spring development | Team selects and integrates frameworks, libraries, architecture, and tools | Full engineering control | Maximum choice, with more responsibility for assembling and maintaining the application foundation |
| Generic AI coding tools | Generate or modify code from instructions and project context | Depends on the project architecture, development workflow, and controls supplied by the team | Code generation can increase speed, but does not itself provide a standardized enterprise platform |
Jmix combines platform acceleration with source-code ownership and standard engineering practices. It should be compared with specific products using current evidence rather than assuming that every low-code or AI tool has the same capabilities. See Jmix vs. OutSystems and Jmix vs. Mendix for product-specific comparisons.
How to Get Started with Jmix
For Developers
- Choose the working mode. Install IntelliJ IDEA and Jmix Studio for the richest deterministic visual and code-generation experience. For terminal-based or non-IDE work, use Jmix CLI to access project setup and application bootstrapping from the command line.
- Learn the platform with guided assistance. Complete the Jmix Tutorial to build a full-stack application covering data modelling, UI, and access control. Use Jmix AI Assistant in the browser or Studio to clarify concepts, architectural choices, and tutorial steps as you progress.
- Enable agentic development. Install the Jmix Agentic Toolkit to give a supported coding agent Jmix architecture guidance, development rules, specialized skills, and recommended tools. Combine it with Jmix CLI when the agent needs to work from an existing command-line or agentic surface.
- Study working applications. Review demo applications and their source code to evaluate architecture and development patterns.
- Open community. Exchange practical knowledge through the free Jmix Community Forum and extend applications with community-contributed add-ons available through the Jmix Marketplace.
For Product and IT Leaders
- Plan the solution. Use the Plan stage to examine the business idea, likely effort, Jmix architecture, and key trade-offs before committing to the complete development toolchain.
- Evaluate the fit and evidence. Check the application profile against Is Jmix Right for My Project?, then review relevant customer stories, demo applications, and the ROI calculator.
- Request a demo. Meet with the Jmix team for a technical demonstration of the platform, discuss your project requirements, and see how Jmix can support your specific application and delivery setup.
- Choose the delivery setup. Decide how developers, analysts, and integrators will participate across Develop and Configure. If the internal team is still being established, discuss training, infrastructure, mentoring, temporary specialist capacity, and a planned handover with Jmix Services.
- Start the delivery loop. Use the Develop – Configure – Run cycle to release the first usable application, observe how it supports business work, and collect feedback from users and stakeholders. Proceed with configuration-level improvements in Configure and engineering changes in Develop, so the application continues to deliver more value after launch.
Frequently Asked Questions
Is Jmix open source?
Yes. Jmix Framework is open source under the Apache 2.0 license, and most framework add-ons use the same license. Jmix also offers premium Studio features and commercial add-ons under separate terms. The official GitHub repository provides the Jmix Framework source code and contribution information.
What programming languages and technologies does Jmix use?
Jmix applications use Java or Kotlin on the JVM and are based on Spring Boot. The web UI uses Vaadin's server-side model together with declarative view definitions. Projects use familiar tools such as IntelliJ IDEA and Git, together with standard Java testing and deployment practices.
Is Jmix a low-code platform?
Jmix is better described as a less-code platform for professional developers. It reduces repetitive work with conventions, visual designers, generation, and reusable components, but developers still own and engineer the application's source code. It is not a visual-only environment intended to replace software developers.
Who develops Jmix?
Jmix is developed by the Jmix team at Haulmont Technology Limited, the company that previously created CUBA Platform. The framework and many add-ons are developed in public repositories, and the add-on ecosystem also includes community contributions.
Is Jmix free to use?
The Jmix Framework is free and open source, and Jmix provides free Studio functionality and open-source add-ons. Premium Studio features and some add-ons require a commercial subscription. Applications built with Jmix do not incur runtime, deployment, or per-user Jmix fees. Check the current pricing page for exact plan boundaries.