Backend-Only Knowledge Base

GeneXus Next supports the creation of Backend-Only Knowledge Bases for projects that do not require a user interface (UI) or that implement the UI using other technologies.

A Backend-Only Knowledge Base is a KB focused exclusively on backend functionality (including APIs, Procedures, Data Providers, and Business Logic), without any UI/frontend-related components.

Since UI-related objects and functionality are not generated, the resulting Knowledge Base is more lightweight, improving efficiency during generation, compilation, and related processes.

How to create a Backend-Only KB

Backend-Only KBs can be created from three different entry points.

In each case, both the way to configure a KB as Backend-Only and the default value are different.

1. GeneXus MCP Server

In this case, the KB is Backend-Only by default. Therefore, when you write the Knowledge Base creation prompt in the Agentic CLI (for example, CODA CLI), explicitly specify if the Knowledge Base should include both backend and frontend objects.

When the create_knowledge_base tool is invoked in the GeneXus MCP Server without specifying the backendOnly parameter, the KB is created as Backend-Only.

Example #1 — Backend-Only KB (default behavior; the backendOnly parameter is not required):

{
  "request": {
    "knowledgeBaseName": "MyKB",
    "environment": ".NET"
  }
}

Example #2 — Standard KB with UI (the backendOnly parameter must be explicitly set to false):

{
  "request": {
    "knowledgeBaseName": "MyKB",
    "environment": ".NET",
    "backendOnly": false
  }
}

2. MSBuild

In this case, the KB is not Backend-Only by default. Instead, it is created as a standard KB with UI. The CreateKnowledgeBase MSBuild task includes a new BackendOnly property that is set to false by default. To create a Backend-Only KB, pass the parameter explicitly.

Example # 1 — Standard KB with UI (default behavior; the BackendOnly property does not need to be set):

<CreateKnowledgeBase
    Directory="C:\work\KBs\MyKB"
    Template=".NET" />

Example # 2 — Backend-Only KB (the BackendOnly property must be explicitly set to true):

<CreateKnowledgeBase
    Directory="C:\work\KBs\MyKB"
    Template=".NET"
    BackendOnly="true" />

3. GeneXus Next Desktop IDE (through the New Knowledge Base dialog)

In this case, the KB type depends on the frontend checkboxes selected in the dialog.

In the New Knowledge Base dialog, the Backend-Only mode is determined automatically based on the selected frontend checkboxes:

• If no frontend is selected (Web, Android, Apple, and Angular are all unselected), the KB is created as Backend-Only.
• If at least one frontend is selected, the KB is created as a standard KB with UI.

By default, the Web (.NET) checkbox is selected. This means the dialog defaults to a standard KB with UI.

To create a Backend-Only KB from the GeneXus Next Desktop IDE, open the New Knowledge Base dialog, clear all frontend checkboxes, and select Create.

What changes when a KB is Backend-Only?

During KB creation

When a KB is created as Backend-Only, the following steps are skipped:

• Built-in Themes are neither imported nor updated. The default Theme is not assigned to the model.
• The User Controls manager is not initialized.
• UI-related pattern resources are not imported.
• Built-in objects of type Theme are not created (Language objects are still created).
• The default Style (GeneXusUnanimo) and the General.UI module (Web Master Panels, UI Data Providers, images, etc.) are not imported. The Design System is not generated either.
• When GAM is enabled, any GAM content related to the UI is not imported into the KB.

The following components are still created normally in a Backend-Only KB:

• The KB itself, including its database structure.
• Built-in objects of type Language.
• The General and GlobalEvents modules.
• The GeneXus module.
• All other standard creation artifacts (models, environments, etc.).

In the IDE

When a Backend-Only KB is opened in the IDE:

• Hidden Categories in New Object — The User Interface, Super App, and Reporting categories are not displayed in the object creation dialog.
• Preferences Tree — The Frontend node is not displayed under the Environment node.
• Model Explorer — The Platforms node is not displayed under Customization.
• Web Layout Tab — The Web Layout tab is not displayed when opening Transactions or other objects that normally include it.
• UI-Related Properties — All UI-related properties are hidden from the model's Properties grid (including properties in the Web Interface group and other frontend-related properties).

During Generation / Build

• Generate Prompt Programs — The default value is No; prompt programs are not generated automatically.
• messages.*.js Files — JavaScript translation message files are not generated. Only the .txt files required by the backend runtime are generated.
• Theme CSS Styles — Theme and Design System CSS files are not generated in the web directory.
• Smart Devices Metadata — The gxmetadata folder and its JSON files (used for Android/iOS images) are not generated.
• Transactions — Only Transactions marked as Business Components are generated. Transactions that are not Business Components are not generated.

Availability

Since GeneXus Next 2026.01