Jmix is built primarily for backend-heavy developers. But software engineers still working with an outdated technology stack or newcomers with basic Java knowledge can adopt Jmix and be productive! Jmix defines application architecture and guides you in easily rolling out the app to the web.

Assuming you know Java, it usually takes 1-2 weeks. If not – 1-2 months. We recommend starting with Jmix Quickstart and Video tutorials for faster onboarding.

Yes, we have a set of training courses listed here. If you want to learn Jmix individually, contact the training center to connect to a Group Training. If you have a complete developer’s team to start learning Jmix, please contact the community manager to book the Team Training.

We provide both free and paid support listed below.

FREE for everyone:

Tutorial. A 9-step tutorial which covers essentials of Jmix development.

Videos. Short videos on basic topics.

Live demo. Live demo of Jmix applications and UI Samples where you can explore UI components and learn how to use them in your project.

Documentation. The platform team provides full technical documentation with code examples.

Community forum. Visit the free Community Forum to find answers on popular topics or publish a new one and receive help from the community members and the platform team.

AI Assistant. Whether you have a general question, need help with code, or seek advice on building your application, Jmix AI Assistant is here to offer help. All Jmix users get 100 requests per month, and if you need more, feel free to contact us.

COMMERCIAL:

Consulting. You can purchase consulting hours and get support directly from Jmix team. Commercial consulting requests receive priority over forum questions.

The Community plan is free forever and includes everything needed to build fully functional applications with Jmix. However, it doesn't include high-productivity features for large projects and advanced add-ons of commercial tiers. Thus, we recommend using the Community plan in three cases.

1. You’re exploring the technology and want to start with an experimental project or a Proof of Concept.
2. You finished active development, and the project is at the support stage with occasional changes.
3. You are a seasoned Java developer ready to spend time on learning a new full-stack Spring Boot-based framework.

The commercial Sprint plan is free for small projects. You can find details here.

You can find a detailed comparison of all Jmix subscription plans here.

Yes, you can use the Jmix Sprint plan, including all visual designers and data migration tools, for projects containing up to 10 entities and 10 roles.

In the context of Jmix, an 'entity' refers to a Java class that represents a table in a database, not a record within a table. The '10 entities' limitation for the Jmix Sprint free plan means that you can use the advanced features of Jmix Studio for projects with up to 10 Java classes that represent tables (JPA entities) or up to 10 simple Java objects (DTO entities). This limitation is not about the number of records in the database or the UI views - they do not have any limits in the application.

Jmix license is named. It is connected to a certain developer profile.

Yes. You can work with the Jmix Studio from multiple workstations using your named license, but not in parallel.

If you have monthly or annual subscription auto-renewal enabled, we will:

1. Automatically send you an email before the expiration date.
2. Try to charge for the next subscription period according to your Jmix subscription payment terms.
3. If the payment succeeds, automatically renew the active subscription.

Yes, you can run your application which was built when the subscription was active. However, you are not allowed to develop your application with commercial add-ons included. You need an active Enterprise or BPM subscription to do so.

We hope that you take the decision about the purchase carefully. That’s why we provide a trial period. The license fee is not refundable, so buy the subscription when you are sure you need it and will definitely use it. If you are not sure yet, you can always ask the community manager to prolong your trial period.

Each developer needs a named license, so you would need to use as many license keys as many developers you want to involve.

Yes, it's allowed for your team to have different subscriptions for projects with commercial add-ons, but each developer’s subscription must match the specific set of commercial add-ons used in the project they are working on.

Yes. You can add additional developer seats to your active subscription in your personal account by clicking the “Manage” button.

Yes, you can switch to a different plan on your subscription page.

Yes. We provide free Academic licenses to official educational organizations and their students. Follow the link to submit a request for an Academic license.

You can find the License Agreement on our website.

No. You pay only for developer seats, using Jmix paid subscription plans. We charge for visual tools, templates and add-ons that make your development team more productive and give the ability to deliver digital products faster. Instead of user-based pricing (runtime pricing) and usage-based pricing (connected to business value), we offer a per-developer subscription pricing model. This guarantees you the freedom to use your Jmix applications freely without restrictions.

We support card payments and wire transfer. You can perform the payment using the Store. If you would like to get a pro-forma invoice before payment, please choose “Offline payment” option.

A Company license is the standard licensing option for commercial and non-profit organizations. Company purchases licenses to be used by any single person within this organization.

An Individual license is an option for private individuals who purchase a license with their own funds and solely for their own use. Individual licenses are not to be purchased, refunded or in any way financed by companies. Please consider that we will regularly check the usage conditions to prevent fraud.

Yes, we provide volume discounts for every commercial subscription plan if you want to purchase more than 3 developer seats. The volume discount depends on the total number of developer seats purchased—the larger your team, the less you pay per developer.

Please contact our sales team for a special price offer.

Yes, you can purchase a monthly subscription for Jmix Sprint plan. For the Jmix Enterprise and Jmix BPM plan, annual subscription is the only option.

You can develop a broad spectrum of line-of-business web applications. Please check Is Jmix right for my project? to find details.

Development teams vary in skillsets, project scope, and deployment practices. That’s why Jmix offers multiple subscription tiers tailored to different development profiles:

• Community – Ideal for backend developers building data-centric applications with Java. Great for teams working on internal tools, prototypes, or supporting the finished project.
• Sprint – Designed for fast-moving teams who need to accelerate development with model-driven tools, instant UI generation, and quick cloud deployment.
• Enterprise – Adds enterprise-grade features such as advanced security, document handling, geospatial tools, and enhanced end-user collaboration tools — perfect for scalable business applications.
• BPM – Provides everything in Enterprise, plus powerful tools for process-driven development: visual BPMN modeling, task assignment, form customization, and system orchestration.

All plans support distributed development teams and integrate tightly with IntelliJ IDEA for seamless team collaboration.
Refer to the Jmix plans comparison table for full details on included features.

Sure. Anytime you meet the demand for features available on the higher subscription plans, you should change your plan or add users to your subscription at the profile. Please consider that we will charge only the difference in the price between subscription plans.

There are several options. You can store the data in your self-hosted environment or a public cloud infrastructure. Check the technical documentation for details.

Some skeptics claim that open source is less secure than proprietary software. But it’s just a theoretical assumption. The key benefit of the open-source code is its potential to be revised by far greater “number of eyes” than a closed effort of a product team. Full access to the application code can prevent sudden failure by deep code inspection as there is nothing hidden in the “black box”.

Since 2016 the CUBA Platform is being developed as an open-source project. The platform team has continuously published a transparent product roadmap and regularly managed issue tracking on the public GitHub repository. Jmix platform, as the successor of the CUBA Platform, represents a mature open-source project based on a future-proof technology stack.

The platform maturity doesn’t exclude all security risks, so governance procedures are mandatory. But a strong community with over 25K members and more than 1000 projects done with the platform assure a strong basis for building secure applications.

Yes. There are several options. In addition to the standard user-password authentication, you can connect Jmix application to the enterprise LDAP directory and synchronize end-user accounts. For secure external connections via API endpoint, Jmix provides OAuth 2.0 authentication service.

No. You completely own the applications built with Jmix and can use them at any scale without any charges.

Yes. As Jmix is distributed under the Apache 2.0 license, it does not imply any substantial limitations on applications. Jmix Studio is only used at development time and is not required to run your application.

All libraries we are using are distributed under open source, non-restrictive licenses - like MIT, Apache 2.0, EPL, LGPL. We do not use libraries with ‘copyleft’ licenses like GPL.

Note: Add-ons provide integration with some products, which may have commercial license - like Google Maps or amCharts. It is your responsibility to make sure you use them properly.

All forks of third-party libraries, used in Jmix, Add-ons and Studio are distributed under the same license terms as the corresponding library.