Joget

What it is

Joget DX is a low-code application platform whose knowledge base opens with a one-line description: "Joget DX 8 is an open source platform to easily build enterprise web apps for cloud and mobile." It is aimed at teams that need business applications such as CRM, HR or healthcare systems and want to assemble them from forms, lists and workflow rather than write them from scratch. The product comes in a Community Edition and in Professional and Enterprise editions. Its documentation lives in a knowledge base run by Joget Inc., which explains in detail how apps are built.

That makes Joget a builder for process-driven business apps: data entry forms, lists, approvals and the screens around them. It is not a website or store builder.

What you build and how

The build model. The knowledge base lists the core ideas in a short list: build full-fledged apps such as CRM, HR and healthcare; drag and drop forms, lists and UI; add workflow to automate processes; extend via plugins; apps are mobile optimized and cloud ready. You can also download ready-made apps from the Joget Marketplace.

The workspace. The Form Grid tutorial shows the working loop. You start the Joget Server, open the App Center, log in as admin and click the pencil icon on a built-in app (the example is Expenses Claims) to open Design App. Forms appear in a column of the designer, and you create or edit a form there.

Forms and the Form Grid. The Form Grid is a form element that shows rows of records from another form, so one screen can hold a parent record and its line items. The guide builds an expense claim entry form and mimics an existing form in the app. Properties you set include the element ID, where declaring an ID of "entries" creates a database column c_entries, the label, the target form, and the columns to display. Each column takes a field ID from the target form, a label, a format type and a width. The documented format types are text, HTML, multiple-line text, decimal, date, file, image and options. A date column takes an original and a new format, for example M/d/y to y/M/d, and the page refers you to Java SimpleDateFormat. A file column shows a link to the attachment, and an image column shows a thumbnail.

Grid behavior. Options include sorting rows by a field ID that stores row sequence, popup dialog height and width, labels for the submit button in normal and read-only mode, a read-only setting, switches to disable adding or deleting rows, a delete confirmation message, row numbering and a paging size. A "Display field as Label when readonly" setting shows values as plain text when an element is read-only.

Validation. The page lets you attach a Validator plugin and states when validation runs: whenever a form is submitted, except when it is submitted as "Save as Draft". For a grid you can set a minimum and a maximum number of rows with an error message, and name a unique column to identify the record.

Data layer. The grid uses load and save binders. If you leave the binder empty, the grid rows are saved as JSON in the parent form and its database table. The recommended choice is the Multirow Form Binder, which saves each row into a child database table through a subform definition and writes the parent ID into each child record as a foreign key. The page also has settings for deleting associated grid data, child form data and files, and warns that these options traverse the whole form tree. The tutorial offers demo apps to download as .jwa files, one of them built with the JDBC Form Binder.

Workflow. The knowledge base's own line is "Add workflow to automate processes". The recent-updates list on the home page includes topics near process work, such as data cleansing in the Process Data Collector Table and a Governance Health Check. The Form Grid page shows how forms and processes connect: when a grid row is deleted, an "Abort Related Running Processes" option stops any process instances tied to that row, so data and running workflow stay in step.

Userviews and extension. The recent-updates list also refers to making popups draggable and resizable in the Joget Userview, a plugin properties options topic, and a Security Enhanced Directory Manager. Plugins are the stated extension route, and the Form Grid page shows it in practice: validation is done by attaching a Validator plugin, and data loading and saving by choosing from a list of available Form Binders.

For developers. The knowledge base sends developers to a page on getting the Joget community source code, and points new users to a getting-started guide, a Questions section and video tutorials.

What the company's pages state

Open source and editions. The platform is described as open source. The knowledge base says "some of the examples are for the Enterprise Edition, but the basic concepts are similar for the Community Edition", and the Form Grid page states that the Form Grid "is only available on Professional and Enterprise Edition". That is a concrete example of where the Community Edition stops.

Pricing. The knowledge base publishes no prices for the editions.

Documentation. Separate knowledge bases exist for Joget DX 8, Joget DX 7 and the Marketplace. A notice says this Confluence site is now read-only and will no longer be updated, and points to a new knowledge base at kb.joget.org. The most recent updates listed date from July and August 2025, including a Product Roadmap update on Aug 27, 2025.

Who it suits and who it does not

Joget suits an operations or IT team that needs data-driven business apps with forms, validation and approval flows, for example an expense claim with line items, and wants to build them visually while keeping the option to code a plugin. The parent and child record handling suits internal tools where one record owns many rows. A developer who wants to read the community source will find that route documented, and a team that wants ready-made starting points can look in the marketplace.

It is less suited to a founder who wants a public marketing site, a store or a native mobile app, since the pages describe web apps that are mobile optimized rather than app store builds. The docs show a form designer with many properties, such as binders, field IDs and date format strings, so a non-technical builder should expect a learning curve. Some features, such as the Form Grid, require a paid edition, so check which edition covers what your app needs. The Confluence documentation covers DX 7 and DX 8, and the vendor now points readers to its new knowledge base for current material.