DEV Community: NocoBase

Weekly Updates: Improvements and Bug Fixes

NocoBase — Fri, 11 Sep 2026 09:42:33 +0000

Summarize the weekly product update logs, and the latest releases can be checked on our blog.

NocoBase is currently updated across three branches: main, next, and develop.

main: The most stable version to date, recommended for installation.
next: Beta version, contains upcoming new features and has been preliminarily tested. There might be some known or unknown issues. It is mainly used to collect feedback from test users and further optimize features. Ideal for test users who want to experience new features early and provide feedback.
develop: Alpha version, contains the latest feature code, may be incomplete or unstable, and is mainly used for internal development and rapid iteration. Suited for technical users interested in cutting-edge product capabilities, but not recommended for production use.

main

v2.2.10

Release date: 2026-09-10

🚀 Improvements

[utils] Added an option to block server-side requests and redirects to literal IP addresses (#10490) by @2013xile
[client-v2] Improve V2 form QR scanning reliability on iOS. (#10456) by @katherinehhh

🐛 Bug Fixes

[client-v2] Hide unsupported built-in date variables from workflow create and update field assignments. (#10442) by @mytharcher
[server] Fixed misleading preparing status when a subapp deployment environment is unavailable (#10485) by @2013xile
[Workflow: Delay node] Fixed delay duration variable validation and report invalid resolved values instead of waiting unexpectedly. (#10469) by @mytharcher
[App supervisor] Fixed subapp access failures after rolling updates or deployment environment changes by @2013xile

v2.2.9

Release date: 2026-09-09

🐛 Bug Fixes

[client-v2]
- Fixed the v2 Update record field settings failing after an assigned field was deleted. (#10483) by @katherinehhh
- Show the standard deleted-field warning for historical V2 field assignments. (#10484) by @katherinehhh
- Fix filter forms not collapsing on mobile (#10479) by @zhangzhonghe
- Support displaying to-many association fields as read-only subtables in client v2 forms. (#10478) by @katherinehhh
- Fix nested association fields rendering blank in V2 forms when the parent relation uses dropdown selection. (#10477) by @katherinehhh
- Fixed the inverse relationship type being editable in v2 field configuration. (#10476) by @katherinehhh
- Fix interrupted option value input for custom radio and checkbox fields in filter forms (#10480) by @zhangzhonghe
- Fix full-page reloads when opening settings pages (#10474) by @zhangzhonghe
[cli] Restrict legacy local upload URLs to signed-in users by default, with an opt-in compatibility switch for public access. (#10471) by @mytharcher
[Data source manager] Fixed the inverse-field option not remaining selected when editing a v2 relation field. (#10482) by @katherinehhh
[Flow engine] Fixed non-admin variable resolution in form linkage rules, referenced templates, and scripts. (#10467) by @gchust
[Access control] Fix role permissions so selecting a deeply nested menu also selects all parent menus (#10473) by @zhangzhonghe
[Block: Kanban] Fixed an issue where newly created records were not immediately visible in the Kanban block. (#10463) by @gaurangagar
[Workflow: Approval] Fix approval cards showing outdated content after saving an edited draft by @zhangzhonghe

v2.2.8

Release date: 2026-09-08

🚀 Improvements

[WeCom] Improved type safety and unified the notification recipient selector in the WeCom plugin. by @chenzhizdt

🐛 Bug Fixes

[server] Fixed applications unexpectedly starting in environments where they were not deployed (#10464) by @2013xile
[Notification: In-app message] Allow all workflow variable types in in-app notification titles and detail links. (#10470) by @mytharcher
[File manager] Prevent file redirects from reusing expired signed storage URLs. (#10475) by @mytharcher
[Data source manager] Added current user and current role variable selection to v2 permission data scopes (#10472) by @jiannx
[Workflow: JavaScript] Fixed an issue where a timed-out JavaScript workflow node could incorrectly abort the workflow instead of respecting "Continue when exception thrown". (#10461) by @mytharcher
[AI employees] Fixed AI employees repeatedly querying knowledge bases when the Knowledge Base Prompt omitted the retrieved-content placeholder, and added clear validation guidance when saving the configuration. (#10413) by @cgyrock
[AI: Knowledge base] Fixed PGVector connection testing, ZIP import result display, document segment-setting inheritance, and validation for chunk overlap values in AI knowledge bases. by @cgyrock
[App supervisor] Fixed exposure of sub-application authentication secrets in application management responses by @2013xile
[DingTalk] Unified the DingTalk notification recipient selector. by @chenzhizdt

v2.2.7

Release date: 2026-09-05

🎉 New Features

[AI: Knowledge base] Added an authenticated knowledge base retrieval API and a built-in provider for connecting remote NocoBase knowledge bases. by @cgyrock

🚀 Improvements

[undefined] Corrected the root package license metadata to Apache-2.0 and raised the Node.js requirement to version 22 (#10448) by @hongboji
[Notification: In-app message] Fixed frontend freezing after selecting an in-app message or email channel in workflow v2 notification nodes (#10445) by @jiannx
[DingTalk] DingTalk ActionCard button links can now be configured to open in an external browser. by @chenzhizdt

🐛 Bug Fixes

[Collection: SQL] Restricted SQL collections from querying PostgreSQL system objects or executing multiple statements (#10455) by @2013xile
[Block: Comment] Fixed the record comments block to display the commenter's nickname when using the Last modified by field (#10446) by @jiannx
[AI employees]
- Prevented Bedrock errors caused by aborted AI responses leaving tool calls without matching tool results. (#10447) by @cgyrock
- Fixed an error that prevented business analysis reports containing charts from opening. (#10440) by @cgyrock
[Collection field: Markdown(Vditor)] Fix Vditor detail fields to use HTML preview by default so Markdown images can be displayed. (#10459) by @mytharcher
[Data source manager] Fix the missing record unique key setting in the v2 collection editor. (#10453) by @katherinehhh
[Workflow] Fixed workflow user selection when a user-related collection uses its primary key as the user foreign key (#10354) by @mytharcher
[File manager] Fixed AI employee workflow nodes failing to access NocoBase permanent file URLs and unnecessarily copying internal files to AI storage. (#10408) by @cgyrock
[AI: Knowledge base] Knowledge base uploads now allow all document formats supported by the backend by @cgyrock
[Template print] Fix dynamic image rendering for stable file URLs in template printing. by @hongboji

v2.3.0-beta.9

Release date: 2026-09-10

🚀 Improvements

[utils] Added an option to block server-side requests and redirects to literal IP addresses (#10490) by @2013xile
[client-v2] Improve V2 form QR scanning reliability on iOS. (#10456) by @katherinehhh
[WeCom] Improved type safety and unified the notification recipient selector in the WeCom plugin. by @chenzhizdt

🐛 Bug Fixes

[client-v2]
- Hide unsupported built-in date variables from workflow create and update field assignments. (#10442) by @mytharcher
- Fix full-page reloads when opening settings pages (#10474) by @zhangzhonghe
- Fixed the v2 Update record field settings failing after an assigned field was deleted. (#10483) by @katherinehhh
- Show the standard deleted-field warning for historical V2 field assignments. (#10484) by @katherinehhh
- Fix interrupted option value input for custom radio and checkbox fields in filter forms (#10480) by @zhangzhonghe
- Support displaying to-many association fields as read-only subtables in client v2 forms. (#10478) by @katherinehhh
- Fix nested association fields rendering blank in V2 forms when the parent relation uses dropdown selection. (#10477) by @katherinehhh
- Fixed the inverse relationship type being editable in v2 field configuration. (#10476) by @katherinehhh
- Fix filter forms not collapsing on mobile (#10479) by @zhangzhonghe
[server] Fixed misleading preparing status when a subapp deployment environment is unavailable (#10485) by @2013xile
[cli] Restrict legacy local upload URLs to signed-in users by default, with an opt-in compatibility switch for public access. (#10471) by @mytharcher
[Workflow: Delay node] Fixed delay duration variable validation and report invalid resolved values instead of waiting unexpectedly. (#10469) by @mytharcher
[Data source manager]
- Fixed the inverse-field option not remaining selected when editing a v2 relation field. (#10482) by @katherinehhh
- Added current user and current role variable selection to v2 permission data scopes (#10472) by @jiannx
[Notification: In-app message] Allow all workflow variable types in in-app notification titles and detail links. (#10470) by @mytharcher
[Access control] Fix role permissions so selecting a deeply nested menu also selects all parent menus (#10473) by @zhangzhonghe
[Block: Kanban] Fixed an issue where newly created records were not immediately visible in the Kanban block. (#10463) by @gaurangagar
[File manager] Prevent file redirects from reusing expired signed storage URLs. (#10475) by @mytharcher
[Flow engine] Fixed non-admin variable resolution in form linkage rules, referenced templates, and scripts. (#10467) by @gchust
[Workflow: Approval] Fix approval cards showing outdated content after saving an edited draft by @zhangzhonghe
[App supervisor] Fixed subapp access failures after rolling updates or deployment environment changes by @2013xile

v2.3.0-beta.8

Release date: 2026-09-07

🎉 New Features

[AI: Knowledge base] Added an authenticated knowledge base retrieval API and a built-in provider for connecting remote NocoBase knowledge bases. by @cgyrock

🚀 Improvements

[Notification: In-app message] Fixed frontend freezing after selecting an in-app message or email channel in workflow v2 notification nodes (#10445) by @jiannx

🐛 Bug Fixes

[server] Fixed applications unexpectedly starting in environments where they were not deployed (#10464) by @2013xile
[AI employees]
- Fixed AI employees repeatedly querying knowledge bases when the Knowledge Base Prompt omitted the retrieved-content placeholder, and added clear validation guidance when saving the configuration. (#10413) by @cgyrock
- Prevented Bedrock errors caused by aborted AI responses leaving tool calls without matching tool results. (#10447) by @cgyrock
[Collection field: Markdown(Vditor)] Fix Vditor detail fields to use HTML preview by default so Markdown images can be displayed. (#10459) by @mytharcher
[Collection: SQL] Restricted SQL collections from querying PostgreSQL system objects or executing multiple statements (#10455) by @2013xile
[Block: Comment] Fixed the record comments block to display the commenter's nickname when using the Last modified by field (#10446) by @jiannx
[Workflow] Fixed workflow user selection when a user-related collection uses its primary key as the user foreign key (#10354) by @mytharcher
[Data source manager] Fix the missing record unique key setting in the v2 collection editor. (#10453) by @katherinehhh
[Workflow: JavaScript] Fixed an issue where a timed-out JavaScript workflow node could incorrectly abort the workflow instead of respecting "Continue when exception thrown". (#10461) by @mytharcher
[AI: Knowledge base]
- Knowledge base uploads now allow all document formats supported by the backend by @cgyrock
- Fixed PGVector connection testing, ZIP import result display, document segment-setting inheritance, and validation for chunk overlap values in AI knowledge bases. by @cgyrock
[Template print] Fix dynamic image rendering for stable file URLs in template printing. by @hongboji
[App supervisor] Fixed exposure of sub-application authentication secrets in application management responses by @2013xile
[DingTalk] Unified the DingTalk notification recipient selector. by @chenzhizdt

develop

v2.4.0-alpha.5

Release date: 2026-09-09

🚀 Improvements

[WeCom] Improved type safety and unified the notification recipient selector in the WeCom plugin. by @chenzhizdt

🐛 Bug Fixes

[client-v2]
- Support displaying to-many association fields as read-only subtables in client v2 forms. (#10478) by @katherinehhh
- Fixed the inverse relationship type being editable in v2 field configuration. (#10476) by @katherinehhh
- Fix nested association fields rendering blank in V2 forms when the parent relation uses dropdown selection. (#10477) by @katherinehhh
[cli] Restrict legacy local upload URLs to signed-in users by default, with an opt-in compatibility switch for public access. (#10471) by @mytharcher
[Workflow: JavaScript] Fixed an issue where a timed-out JavaScript workflow node could incorrectly abort the workflow instead of respecting "Continue when exception thrown". (#10461) by @mytharcher
[File manager] Prevent file redirects from reusing expired signed storage URLs. (#10475) by @mytharcher
[Notification: In-app message] Allow all workflow variable types in in-app notification titles and detail links. (#10470) by @mytharcher
[Data source manager] Added current user and current role variable selection to v2 permission data scopes (#10472) by @jiannx
[Block: Kanban] Fixed an issue where newly created records were not immediately visible in the Kanban block. (#10463) by @gaurangagar
[DingTalk] Unified the DingTalk notification recipient selector. by @chenzhizdt

v2.4.0-alpha.4

Release date: 2026-09-06

🎉 New Features

[AI: Knowledge base] Added an authenticated knowledge base retrieval API and a built-in provider for connecting remote NocoBase knowledge bases. by @cgyrock

🚀 Improvements

[Notification: In-app message] Fixed frontend freezing after selecting an in-app message or email channel in workflow v2 notification nodes (#10445) by @jiannx

🐛 Bug Fixes

[server] Fixed applications unexpectedly starting in environments where they were not deployed (#10464) by @2013xile
[Collection field: Markdown(Vditor)] Fix Vditor detail fields to use HTML preview by default so Markdown images can be displayed. (#10459) by @mytharcher
[AI employees]
- Fixed AI employees repeatedly querying knowledge bases when the Knowledge Base Prompt omitted the retrieved-content placeholder, and added clear validation guidance when saving the configuration. (#10413) by @cgyrock
- Prevented Bedrock errors caused by aborted AI responses leaving tool calls without matching tool results. (#10447) by @cgyrock
[Block: Comment] Fixed the record comments block to display the commenter's nickname when using the Last modified by field (#10446) by @jiannx
[Data source manager] Fix the missing record unique key setting in the v2 collection editor. (#10453) by @katherinehhh
[Workflow] Fixed workflow user selection when a user-related collection uses its primary key as the user foreign key (#10354) by @mytharcher
[Collection: SQL] Restricted SQL collections from querying PostgreSQL system objects or executing multiple statements (#10455) by @2013xile
[AI: Knowledge base]
- Fixed PGVector connection testing, ZIP import result display, document segment-setting inheritance, and validation for chunk overlap values in AI knowledge bases. by @cgyrock
- Knowledge base uploads now allow all document formats supported by the backend by @cgyrock
[Template print] Fix dynamic image rendering for stable file URLs in template printing. by @hongboji
[App supervisor] Fixed exposure of sub-application authentication secrets in application management responses by @2013xile

10 Open-Source AI Agent Platforms for Business: From Automation to Internal Apps

NocoBase — Sat, 05 Sep 2026 14:07:48 +0000

Originally published at https://www.nocobase.com/en/blog/open-source-ai-agent-platforms-for-business

TL;DR

These 10 platforms can be roughly grouped into three categories:

NocoBase, Activepieces, Kestra, and Windmill are better suited to connecting AI with enterprise data, automation, and business processes.
Coze Studio, Langflow, and Dify are better suited to visually building Agents and AI applications.
MaxKB, AnythingLLM, and RAGFlow are better suited to enterprise knowledge bases and RAG.

If a company needs to manage structured business data, permissions, and internal applications, NocoBase is worth considering first. If the main goal is to connect multiple SaaS tools and automate tasks, Activepieces is a strong option. If the focus is building Agents and AI workflows, Dify, Langflow, or Coze Studio are good starting points. If private document Q&A and complex knowledge retrieval matter most, MaxKB, AnythingLLM, or RAGFlow are more suitable.

Introduction

More companies are starting to bring AI Agents into everyday work. Customer follow-up, email organization, task reminders, and data summaries are all examples of repetitive work that can increasingly be handed over to AI.

On Reddit's r/smallbusiness, one small-business owner explained that they already use ChatGPT and want to go further by letting AI handle customer follow-up, email classification, proposal reminders, and weekly summaries. As they researched further, they came across n8n, Zapier, APIs, MCP, and various Agent-building tools. They do not have a development background and do not want to learn an entire technical stack just for a few automation workflows. What made the decision even harder was the maintenance question: if it takes several weeks to build these applications, will they then need constant upkeep and eventually become more complicated than the original way of working?

This is a common problem when businesses choose AI Agent tools. A simple search for “AI Agent” brings up very different types of products: developer frameworks such as LangChain, CrewAI, and Haystack; Agent-building platforms; automation tools; RAG platforms; and enterprise application platforms that can manage business data, pages, permissions, and workflows in the same system.

💬 Hey, you're reading the NocoBase blog. NocoBase is the most extensible AI-powered no-code/low-code development platform for building enterprise applications, internal tools, and all kinds of systems. It’s fully self-hosted, plugin-based, and developer-friendly. → Explore NocoBase on GitHub

Based on practical business use cases, this article collects 10 open-source AI Agent projects that support self-hosting and already provide visual applications, workflows, knowledge bases, or business-system capabilities. For each project, we look at the basics, notable AI Agent capabilities, business use cases, and the types of teams it is best suited for.

To keep the scope clear, the projects included here need to meet several basic criteria: the core code is public and actively maintained, self-hosting is supported, Agent, tool-calling, or AI workflow capabilities are already available, and the project provides at least one of the following: visual applications, automation, knowledge bases, or enterprise business systems. Project information and selection guidance are based mainly on official websites, GitHub repositories, and official documentation. This is not a benchmark under a unified test environment or a complete ranking.

💡 If you are more interested in development frameworks such as LangChain and CrewAI and want to compare different Agent frameworks and development platforms, see our earlier article: 8 Open-Source AI Agent Platforms for Internal Tools.

Before going through the projects one by one, you can first scan the list below to understand how their positioning, use cases, and technical requirements differ.

1. Enterprise Applications and Business Automation

1. NocoBase

Website: https://www.nocobase.com/

GitHub: https://github.com/nocobase/nocobase

GitHub Stars: 23.9K

Related documentation

AI Employees: https://docs.nocobase.com/ai-employees/quick-start

AI Builder: https://docs.nocobase.com/ai-builder

NocoBase is an open-source, self-hosted AI no-code platform for enterprise applications. It is mainly used to build CRM systems, ticketing systems, IT management systems, approval workflows, and other internal business applications. It provides the foundational capabilities required by enterprise applications, including data models, pages, permissions, and workflows, while also allowing AI to participate in both application building and later adjustments. AI Employees can also be configured inside the system so AI can combine current business data, tools, and processes to perform analysis, information processing, and task execution.

Core AI Capabilities

AI + no-code application building: Users can describe business requirements in natural language, and AI can create data tables and relationships, pages, workflows, and role permissions. NocoBase provides both a no-code portal and an AI portal. The no-code portal makes it easier for business users to continue adjusting the application visually, while the AI portal is better suited to complex interactions and highly customized pages.

👉 AI Portal Quick Start - NocoBase Documentation

AI Portal:

No-code Portal:

AI Employees and business execution: AI can participate in daily work as a specific role, handling tasks such as data analysis, email organization, and information extraction. It can also use system tools and workflows to query data, fill forms, or trigger business processes.

👉 AI Employees: Using Tools - NocoBase Documentation

Enterprise knowledge base: AI Employees can retrieve enterprise knowledge automatically or on demand, with accessible content filtered according to the current user's role. This allows customer service, sales, or internal assistants to work with the company's own knowledge.

👉 NocoBase AI Knowledge Base Documentation

Enterprise permissions and execution control: AI Employees inherit the current user's data permissions. Important operations such as modifying data can also require confirmation before execution, helping prevent an Agent from gaining access beyond the user's own permission scope.

👉 AI Employee Roles and Permissions - NocoBase Documentation

Business Use Cases

CRM: Organize communication details from customer emails or meeting notes, generate follow-up suggestions, and assist sales using customer, contact, and opportunity data.

Customer support and ticketing: Analyze submitted customer issues, determine category and priority, generate response suggestions using the knowledge base, and participate in ticket-handling workflows.

IT management: Identify IT request types, priorities, and handling suggestions from employees' natural-language descriptions, then work with asset, maintenance, approval, and related business data.

Internal business applications: Configure AI Employees for different roles in procurement, approval, project management, operations, and other systems, allowing them to use business data and workflows to complete routine tasks.

Selection Guidance

NocoBase is a good fit for teams with clearly defined business needs such as CRM, customer support ticketing, IT management, or approvals, especially when they want AI to accelerate application building without asking AI to create an entire business system from scratch. Core capabilities such as data models, permissions, and workflows are already provided by the platform. Business teams can complete most of the setup with no-code tools and AI, then extend the system further through APIs and plugins. It is especially suitable for teams building internal systems that are expected to be used and iterated over the long term.

2. Activepieces

Website: https://www.activepieces.com/

GitHub: https://github.com/activepieces/activepieces

GitHub Stars: 24.0K

Related documentation

MCP: https://www.activepieces.com/docs/mcp/overview

Product Overview

Activepieces is an open-source, self-hosted AI automation platform mainly used to connect the applications, data, and business processes a company already relies on. It brings AI Agents, automation workflows, and data into the same environment and is well suited to sales, customer support, operations, and other work that spans multiple tools.

Core AI Capabilities

Visual AI Agent creation: Users can define an Agent's task, model, and available tools, then place the Agent directly inside automation workflows. Existing workflows can also be reused as Agent tools.

Natural-language automation building: Users can describe what they want to accomplish and let AI generate an Agent or automation workflow. They can then continue editing visually by adding conditions, loops, and code execution.
Connect business tools: The platform can connect more than 700 applications, including CRM systems, email, collaboration tools, spreadsheets, and other commonly used services. Through MCP, tools and workflows built in the platform can also be exposed to other AI clients that support MCP.

Business Use Cases

Sales lead processing: Capture new leads from email or forms, let AI classify customer type and priority, update the CRM, and generate follow-up content.
Customer support workflows: Automatically read customer issues, classify and summarize them, assign tickets, and synchronize information between customer support systems and CRM.
Daily operations automation: Organize email, extract information, synchronize spreadsheets or databases, and automatically generate daily reports, weekly reports, and business notifications from data across multiple systems.

Selection Guidance

Activepieces is better suited to small and midsize teams or business departments that already use several SaaS tools but have limited development resources. Sales, marketing, customer support, and operations teams that frequently move data, send messages, and follow up across multiple systems can start with visual workflows and later add APIs or custom integrations as requirements become more complex.

3. Kestra

Website: https://kestra.io/

GitHub: https://github.com/kestra-io/kestra

GitHub Stars: 28.0K

Related documentation

AI Copilot: https://kestra.io/docs/ai-tools/ai-copilot

Product Overview

Kestra is an open-source, self-hosted workflow orchestration platform mainly used to manage automation across data, AI, and infrastructure. AI Agents can run directly as tasks inside workflows, calling tools, executing other tasks, or triggering existing flows based on their goals.

Core AI Capabilities

AI Agents working with workflows: AI Copilot can generate or modify workflows from natural-language instructions. Agents can also be placed directly inside existing workflows, where they can use models, memory, tools, and existing Kestra tasks and flows, then decide the next step based on execution results.

Visual and code-based development: Workflows can be created and adjusted through the visual interface, while more complex requirements can be extended with YAML, Python, Docker, and custom scripts.

Traceable execution: Agents and regular tasks share the same runtime system, making it possible to inspect execution status, logs, and failure records in one place for easier troubleshooting and maintenance.

Business Use Cases

Data-processing automation: Choose next steps based on data state and call existing workflows to complete cleaning, analysis, and aggregation.
IT and operations workflows: Analyze alerts or system events, then execute checks, notifications, or other follow-up tasks.
Complex business and AI workflows: Combine models, tools, approvals, data processing, and cross-system tasks to handle workflows that require multiple steps and dynamic decisions.

Selection Guidance

Kestra is better suited to teams that already have some automation foundation and have developers, data engineers, or operations specialists involved. Its orchestration capabilities become more valuable when workflows grow longer and need task dependencies, retries, execution-state tracking, and multi-step AI decisions. If a small team only wants to build a few simple business automations quickly, it may not need such a complete workflow system.

4. Windmill

Website: https://www.windmill.dev/

GitHub: https://github.com/windmill-labs/windmill

GitHub Stars: 17.7K

Related documentation

AI Agent applications: https://www.windmill.dev/use-cases/ai-agents

Product Overview

Windmill is an open-source, self-hosted development and automation platform that can run scripts, APIs, workflows, and internal applications in one environment. It supports both visual orchestration and code in Python, TypeScript, Go, SQL, and other languages, making it more suitable for teams with some technical expertise.

Core AI Capabilities

Add Agents to workflows: AI Agents can run directly as workflow steps and be combined with conditions, approvals, error handling, and other nodes to handle tasks that require AI judgment.

Use existing technical resources: Agents can use scripts, databases, APIs, and other workflows already available in Windmill. They can also connect to MCP tools, allowing teams to reuse existing code and internal services directly inside Agent workflows.

Permissions, approvals, and execution records: Teams can limit which resources an Agent can access and execute, require human confirmation before important actions, and inspect tool calls, inputs and outputs, logs, and execution status for each run.

Business Use Cases

IT and operations automation: Analyze problems based on alerts or system state, then call scripts to perform checks, remediation, and notifications.
Data processing and analysis: Query databases or run existing data scripts, let an Agent analyze the results, and trigger subsequent workflows.
Internal AI tools: Combine Agents, backend scripts, and internal app interfaces to build data assistants, operations tools, and other internal applications.

Selection Guidance

Windmill is more suitable for teams that already have developers, data specialists, or operations engineers. If a company has accumulated many scripts, databases, APIs, and internal services and wants to reuse those existing resources for Agents and automation, Windmill can be a natural fit. For teams without technical staff that mainly want to build a few simple workflows visually, its development-platform orientation may feel heavier.

2. Visual AI Agent Building Platforms

5. Coze Studio

Website: https://www.coze.cn/home

GitHub: https://github.com/coze-dev/coze-studio

GitHub Stars: 21.5K

AI Agent documentation: https://github.com/coze-dev/coze-studio/wiki/1.-What-is-Coze-Studio

Product Overview

Coze Studio is an open-source, all-in-one AI Agent development platform from ByteDance. Its main focus is visually creating, debugging, and deploying Agents. Users can combine models, knowledge, and tools directly, making it suitable for quickly building customer-service assistants, knowledge Q&A, content assistants, and other AI applications.

Core AI Capabilities

Visual Agent and workflow building: Configure models, prompts, and tools through the interface, or orchestrate multi-step workflows on a canvas with conditions, data processing, and other logic.

RAG and knowledge bases: Connect enterprise documents and knowledge data so Agents can answer questions and handle tasks based on specified content.
Plugins and external tools: Agents can call external services through plugins, bringing search, queries, data processing, and other capabilities into the execution process.

Development, debugging, and deployment: Agents can be created, tested, and deployed within the same platform, reducing the need to switch between multiple tools.

Business Use Cases

AI customer support: Use knowledge bases to answer product, service, and after-sales questions, while plugins query additional business information.
Enterprise knowledge assistants: Provide employee Q&A, document lookup, and information organization based on internal documents and knowledge bases.
Content and marketing assistants: Combine search, content generation, and workflows for research, content organization, and first-draft creation.

Selection Guidance

Coze Studio is a good fit for teams that are just starting to experiment with AI Agents and want to quickly build customer-service assistants, knowledge Q&A, or content assistants without dedicated AI developers. Product, operations, or business teams can validate ideas visually first, then add knowledge bases, plugins, and more complex workflows as needed.

6. Langflow

Website: https://www.langflow.org/

GitHub: https://github.com/langflow-ai/langflow

GitHub Stars: 153.9K

Related documentation

Agents: https://docs.langflow.org/agents

Product Overview

Langflow is an open-source visual AI application development platform mainly used to build Agents and AI workflows. It combines models, tools, data, and other Agents through modular components while retaining Python extensibility, making it suitable for AI application scenarios that require frequent experimentation and iteration.

Core AI Capabilities

Drag-and-drop building and multi-Agent composition: Configure Agents on a visual canvas and connect models, prompts, tools, and other components into complete workflows. Components and flows can also be used as Agent tools, and multiple Agents can divide work such as retrieval, analysis, and organization.
MCP support: Connect external MCP services or expose workflows built in Langflow to other AI applications that support MCP.

Models and Python extensions: Freely combine different models and data sources. When built-in components do not cover a requirement, custom Python components can connect enterprise APIs and processing logic.

Business Use Cases

Knowledge and document applications: Combine internal documents, retrieval, models, and Agents for knowledge Q&A, document analysis, and information extraction.
Multi-Agent workflows: Let different Agents handle retrieval, analysis, organization, and other tasks, then connect them into one complete process.
AI application prototypes: Quickly validate ideas such as customer support assistants, research assistants, and content-generation tools, then connect them to existing products through APIs.

Selection Guidance

Langflow is better suited to teams with some technical involvement that need to experiment frequently with different models and Agent structures. Product or data teams can first build workflows visually, while developers add more complex functionality through Python, custom components, and APIs. It is well suited to prototyping and continuous experimentation. For teams with no technical staff that only want to launch fixed business workflows quickly, later-stage maintenance may depend more heavily on developers.

7. Dify

Website: https://dify.ai/

GitHub: https://github.com/langgenius/dify

GitHub Stars: 154.0K

Related documentation

Official documentation: https://docs.dify.ai/

Dify is an open-source AI application development platform for building Agents, knowledge assistants, and more complex AI workflows. It covers the full lifecycle from application creation and debugging to publishing and ongoing runtime management, making it suitable for teams that want to develop multiple AI applications continuously within one platform.

Core AI Capabilities

Agent and workflow building: Configure Agent models, instructions, tools, and knowledge bases through the visual interface, or use the canvas to orchestrate multi-step workflows with conditions, knowledge retrieval, tool calls, and human input.

RAG and knowledge processing: Build knowledge bases from PDF, PPT, and other documents, with content cleaning, chunking, indexing, and retrieval testing.

Model and plugin extensions: Connect multiple model providers and add new tools, data sources, triggers, and Agent capabilities through plugins.
Publishing and runtime management: Publish completed applications as web apps or APIs, while monitoring logs, feedback, latency, and usage.

Business Use Cases

AI customer support and knowledge assistants: Combine enterprise knowledge bases and external tools to handle customer inquiries or internal employee knowledge searches.
Business information processing: Connect extraction, classification, analysis, generation, and tool calls into complete workflows.
Rapid AI application launch: Publish completed Agents or workflows as applications or APIs, then integrate them with existing products and business systems.

Selection Guidance

Dify is a good fit when a team has moved beyond experimenting with a single Agent and plans to keep building customer support, knowledge assistants, content-processing tools, and other AI applications. Business and product teams can complete most configuration visually, while developers can add plugins, APIs, and deeper integrations when needed. For small and midsize businesses or product teams that want to manage multiple AI projects on one platform, it can be easier than maintaining several separate tools.

3. Enterprise Knowledge and RAG Agents

8. MaxKB

Website: https://maxkb.cn/

GitHub: https://github.com/1Panel-dev/MaxKB

GitHub Stars: 22.6K

Related documentation

Official documentation: https://maxkb.cn/docs/v2/index.html

Product Overview

MaxKB is an open-source, self-hosted enterprise Agent platform that is well suited to starting with enterprise knowledge bases and knowledge Q&A. In addition to basic RAG, it provides visual workflows and tool-calling capabilities that can be extended into customer support, office assistants, and similar scenarios.

Core AI Capabilities

Enterprise knowledge bases and RAG: Upload documents or crawl online content, then perform chunking, vectorization, and knowledge retrieval for internal materials and professional Q&A.
Visual workflows and tool calling: Combine AI conversation, knowledge retrieval, conditions, forms, document extraction, and other nodes on a canvas. MCP services can also be connected so models can call external tools.
Multiple models and local deployment: Connect public models such as OpenAI, Claude, Gemini, DeepSeek, and Qwen, as well as local models through Ollama, vLLM, and similar tools.
Integration with existing systems: Completed Agents can be embedded into websites and internal applications through public links, embed code, or APIs.

Business Use Cases

AI customer support: Connect product knowledge bases, FAQs, and business materials to an Agent for handling customer inquiries.
Professional knowledge applications: Use industry materials for search, organization, and analysis in finance, education, research, and other specialized scenarios.

Selection Guidance

MaxKB is particularly suitable for teams that already have a large amount of enterprise documentation and knowledge material and want to build knowledge-focused AI Agents relatively quickly. Its visual workflows and knowledge-base capabilities have a relatively low entry barrier, while local deployment and local models make it a good fit for organizations with requirements around internal knowledge use, data control, and third-party system integration.

9. AnythingLLM

Website: https://anythingllm.com/

GitHub: https://github.com/Mintplex-Labs/anything-llm

GitHub Stars: 65.4K

Related documentation

Agent Flow: https://docs.anythingllm.com/agent-flows/overview

Product Overview

AnythingLLM is an open-source, local-first AI application mainly used to build AI assistants based on private documents and internal knowledge. It offers both desktop and self-hosted versions with a relatively complete graphical interface, so teams can start without first setting up a complex development environment.

Core AI Capabilities

Private documents and RAG: Add PDF, Word, text, and other files to separate workspaces so AI can answer questions based on selected content while preserving citations.

Agent Flow: Visually combine web scraping, API calls, model instructions, file reading and writing, and other steps into repeatable processing flows.
Multi-user and permissions: The self-hosted version supports multiple users and permission management, allowing teams to separate workspaces and knowledge access by user or group.

Business Use Cases

Internal knowledge and document assistants: Answer questions, summarize information, and extract data from company policies, product materials, training documents, contracts, and reports.
Research and document organization: Combine internal documents, web information, and tool calls to collect, organize, and analyze information.

Selection Guidance

AnythingLLM is better suited to individuals, small teams, or companies that want to pilot a private AI assistant within a department first. Even without dedicated AI developers, teams can start quickly with document Q&A and information organization. If the main goal is to let AI use internal knowledge securely rather than build complex business workflows, it is a lighter-weight option.

10. RAGFlow

Website: https://ragflow.io/

GitHub: https://github.com/infiniflow/ragflow

GitHub Stars: 89.7K

Related documentation

Agent guide: https://github.com/infiniflow/ragflow/tree/main/docs/guides/agent

Product Overview

RAGFlow is an open-source RAG and AI Agent platform focused on complex document processing and enterprise knowledge retrieval. Compared with simpler knowledge-Q&A tools, it is better suited to scenarios with complex document types, large knowledge volumes, and stronger requirements for retrieval accuracy and source traceability.

Core AI Capabilities

Complex document understanding: Process PDF, Word, PPT, spreadsheets, images, and long documents, extracting information that can be used for retrieval and analysis.
High-accuracy RAG: Combine vector retrieval, keyword search, reranking, and metadata filtering to improve retrieval accuracy and traceability.
Agent workflows: Use a visual canvas to combine retrieval, models, conditions, loops, classification, and other steps. More complex patterns such as multi-Agent workflows, planning, and reflection are also supported.

Tools and data-source integration: Agents can call external tools and support MCP. Enterprise knowledge can also be synchronized from Confluence, S3, Notion, Google Drive, and other sources.

Business Use Cases

Complex enterprise knowledge bases: Build a unified knowledge retrieval system across large collections of policies, technical manuals, reports, and professional materials.
Legal and compliance analysis: Retrieve supporting evidence from regulations, contracts, cases, and internal materials, then generate analysis with sources.
Research and decision support: Combine internal data and external materials so Agents can retrieve, analyze, and generate reports.

Selection Guidance

RAGFlow is suitable for teams with large knowledge volumes, complex documents, and some technical resources. In legal, manufacturing, technical support, research, and similar settings, it has stronger advantages when materials contain many long documents, tables, images, or specialized content and when retrieval accuracy and source evidence matter significantly.

Conclusion

Many AI Agent products are beginning to overlap in functionality. Visual workflows, knowledge bases, MCP, and tool calling are now available on more and more platforms. In practice, teams need to consider whether these capabilities can fit smoothly into existing work and how much additional operational and maintenance overhead they will introduce.

Hopefully, this article helps narrow down the options. Feel free to share it with friends or teams that are also looking for AI Agent tools.

If you want to build similar enterprise applications with AI and NocoBase, these complete examples may be useful:

👉 Build a CRM with AI + NocoBase

👉 Build an Enterprise IT Operations System with AI + NocoBase

Related reading:

Weekly Updates: Improvements and Bug Fixes

NocoBase — Fri, 04 Sep 2026 08:33:13 +0000

Summarize the weekly product update logs, and the latest releases can be checked on our blog.

NocoBase is currently updated across three branches: main, next, and develop.

main: The most stable version to date, recommended for installation.
next: Beta version, contains upcoming new features and has been preliminarily tested. There might be some known or unknown issues. It is mainly used to collect feedback from test users and further optimize features. Ideal for test users who want to experience new features early and provide feedback.
develop: Alpha version, contains the latest feature code, may be incomplete or unstable, and is mainly used for internal development and rapid iteration. Suited for technical users interested in cutting-edge product capabilities, but not recommended for production use.

main

v2.2.6

Release date: 2026-09-02

🚀 Improvements

[Migration manager] Displayed migration file sizes with readable binary units instead of raw byte counts by @hongboji

🐛 Bug Fixes

[utils] Prevent stored XSS in rich-text fields written through APIs and rendered in display or edit mode. (#10425) by @katherinehhh
[database] Fixed SQL Server string filters failing to match literal square brackets and other LIKE wildcard characters (#10436) by @hongboji
[Collection field: Markdown(Vditor)] Restore table actions in V2 Markdown Vditor fields. (#10438) by @katherinehhh
[File manager] Fixed the missing file storage selector in v2 file collection create and edit forms. (#10439) by @katherinehhh
[File storage: S3(Pro)] Fix S3 Pro multipart upload failures for backup files larger than 5 MB. by @mytharcher

v2.2.5

Release date: 2026-08-31

🐛 Bug Fixes

[Workflow]
- Improve workflow task detail handling on mobile by using a full-width Drawer and responsive task-center presentation. (#10428) by @mytharcher
- Optimized pending workflow job recovery by adding a composite index on job status and ID. (#10427) by @mytharcher
- Fix schedule workflows in static mode running one more time after endsOn (#10411) by @Tespera
[Notification manager] Fix workflow user recipient variables displaying Variable parsing failed and unify user selectors across workflow nodes. (#10432) by @mytharcher
[Workflow: Approval]
- Adapted approval task details and remote forms to narrow mobile viewports. by @mytharcher
- Fix approval assignee variables displaying Variable parsing failed and reuse the shared workflow user selector. by @mytharcher

v2.2.4

Release date: 2026-08-28

🐛 Bug Fixes

[AI: Knowledge base] Fixed AI employees incorrectly reporting no knowledge-base access for root users by @hongboji
[Workflow: Approval] Fixed the approval trigger-variable form not rendering for subflow nodes on v1 workflow pages. by @mytharcher
[DingTalk] Fixed an issue where DingTalk Stream mode synchronization sources could not be submitted in the v1 client. by @chenzhizdt

v2.3.0-beta.6

Release date: 2026-08-31

🐛 Bug Fixes

[Workflow]
- Optimized pending workflow job recovery by adding a composite index on job status and ID. (#10427) by @mytharcher
- Fix schedule workflows in static mode running one more time after endsOn (#10411) by @Tespera
- Improve workflow task detail handling on mobile by using a full-width Drawer and responsive task-center presentation. (#10428) by @mytharcher
[Notification manager] Fix workflow user recipient variables displaying Variable parsing failed and unify user selectors across workflow nodes. (#10432) by @mytharcher
[Workflow: Approval]
- Fix approval assignee variables displaying Variable parsing failed and reuse the shared workflow user selector. by @mytharcher
- Adapted approval task details and remote forms to narrow mobile viewports. by @mytharcher
[DingTalk] Fixed an issue where DingTalk Stream mode synchronization sources could not be submitted in the v1 client. by @chenzhizdt

develop

v2.4.0-alpha.3

Release date: 2026-09-02

🚀 Improvements

[AI employees] Removed the persisted AI context data source settings and selector while keeping direct data source query capabilities. (#10450) by @cgyrock

v2.4.0-alpha.2

Release date: 2026-09-02

🚀 Improvements

[undefined] Corrected the root package license metadata to Apache-2.0 and raised the Node.js requirement to version 22 (#10448) by @hongboji
[DingTalk] DingTalk ActionCard button links can now be configured to open in an external browser. by @chenzhizdt

🐛 Bug Fixes

[File manager] Fixed AI employee workflow nodes failing to access NocoBase permanent file URLs and unnecessarily copying internal files to AI storage. (#10408) by @cgyrock
[AI employees] Fixed an error that prevented business analysis reports containing charts from opening. (#10440) by @cgyrock

v2.4.0-alpha.1

Release date: 2026-09-02

🚀 Improvements

[Migration manager] Displayed migration file sizes with readable binary units instead of raw byte counts by @hongboji

🐛 Bug Fixes

[database] Fixed SQL Server string filters failing to match literal square brackets and other LIKE wildcard characters (#10436) by @hongboji
[utils] Prevent stored XSS in rich-text fields written through APIs and rendered in display or edit mode. (#10425) by @katherinehhh
[Collection field: Markdown(Vditor)] Restore table actions in V2 Markdown Vditor fields. (#10438) by @katherinehhh
[File manager] Fixed the missing file storage selector in v2 file collection create and edit forms. (#10439) by @katherinehhh
[File storage: S3(Pro)] Fix S3 Pro multipart upload failures for backup files larger than 5 MB. by @mytharcher

How to Build a Production-Ready Ticketing System with AI

NocoBase — Thu, 03 Sep 2026 07:49:25 +0000

Originally published at https://www.nocobase.com/en/blog/build-production-ready-ticketing-system-with-ai

TL;DR

AI can build a ticketing system quickly, but “the features have been generated” does not mean “the system is ready for production.”

A system that a team can actually use needs at least clear data relationships, inspectable role permissions, and workflows whose execution results can be traced. This article uses a NocoBase ticketing system as an example to show how AI can turn natural-language requirements into an application and how to verify these core business foundations.

How to Build a Production-Ready Ticketing System with AI

Building a ticketing system with AI may not seem difficult. But can it really be used in production?

On Reddit in the r/nocode community, one user described a problem their team had encountered. They tried several AI + no-code tools. The applications looked good at first, but once real business data was added, problems started appearing one after another, and it was often difficult to tell what had gone wrong.

One reply in the comments pointed to the core issue: many AI-built systems start to fail in more complex business scenarios because they do not maintain a complete internal model of the application, including who is using the system, what permissions different roles have, how work moves through the process, and what users ultimately need to accomplish.

AI can generate pages and features quickly, but for an application to run reliably over the long term, the underlying platform still needs clear data models, relationships, permissions, and workflow capabilities. Otherwise, as business complexity grows, the features generated by AI become increasingly difficult to keep working correctly.

In this article, I will use a ticketing system as an example to show how AI and NocoBase can be used together to build a system with the foundations required for production use.

In this process, NocoBase provides the underlying capabilities for data relationships, permission control, and workflows. AI is responsible for understanding business requirements, converting natural language into data structures, pages, and features, and continuing to adjust the system as requirements evolve.

Step 1: Describe the Business Requirements and Let AI Design the System

Before building anything, start from the actual work. Clarify the problems the team is facing and what the system needs to solve, then describe those requirements to AI in natural language so it can build the required ticketing system on NocoBase.

If you are not sure how to describe the requirements, start from a few angles. For a ticketing system, for example:

How customer issues enter the system: which channels they usually come from and how they are currently collected and handled;
What happens after an issue comes in: who takes ownership, how follow-up works, and when the issue is considered resolved;
Which situations require special attention: for example, urgent issues, tickets that remain unassigned for too long, or tickets that have been open for an extended period.

Once these points are clear, they can be turned directly into a natural-language requirement for AI. Below is the actual requirement we used in this build:

We are a small software company with four customer support agents. Customers mainly report issues through email and the support entry point on our website.

We currently handle these issues through a shared inbox. As the volume grows, issues are sometimes missed. People may assume someone else has already replied, only to find that no one handled the issue. Some tickets go through several rounds of communication, but it becomes unclear who currently owns them. Urgent issues can also remain unresolved for too long.

I want to build a customer support ticketing system. Each customer issue should be recorded separately and assigned to a specific support agent. Agents should be able to continuously update progress until the issue is resolved. For urgent issues, tickets that remain unassigned for too long, or tickets that are close to breaching their deadline, the system should remind the team to take action.

We also want an overview page that quickly shows how many issues are still open, which issues need priority attention, and how many issues have recently been resolved.

Please design and build this system based on these actual business requirements.

AI first breaks the requirements down into a data structure. In NocoBase, it creates tables for tickets, customers, support agents, communication records, SLA rules, and related data, then defines the relationships between them.

On top of the data model, AI continues building the pages.

In the end, AI creates a ticket list, ticket detail pages, and a support workspace, covering the basic scenarios of ticket recording, assignment, follow-up, and overview.

At this point, we have turned a business description into a working ticketing system. But “the features have been built” and “the system is ready for production” are not the same thing.

Once the whole team starts using the system, three questions still need to be verified: Are the data relationships accurate? Can different team members collaborate according to their permissions? Can assignment, reminders, SLA breaches, and escalation rules execute reliably?

Step 2: Solve Three Core Problems for Production Use

The Reddit comment mentioned earlier pointed out that many AI-built applications begin to fail once real data is added because they do not maintain a complete internal model of the application: who uses the system, what roles different members have, how the data is related, and which rules govern the flow of work.

The ticketing system now has data tables and pages, but when four support agents start working with real customer issues, we still need to validate three core areas.

1. Are the Data Relationships Accurate?

A ticket is not an isolated record.

Each ticket needs to be associated with the customer who submitted it, the current owner, historical communication records, and the applicable SLA rule. When the ticket status changes, statistics and pending items on the workspace also need to update accordingly.

If these relationships are not defined clearly, the system may still look complete while failing in actual use. After changing the owner, previous handling records may become difficult to find. A ticket may be matched to the wrong response deadline, or numbers on the overview page may no longer match reality.

In NocoBase, these relationships are not temporary pieces of logic written by AI into a specific page. They are defined directly in the data model. Using the ticket table as an example, the SLA policy, queue, ticket type, and submitter are defined as many-to-one relationships. One ticket can be linked to multiple satisfaction records, attachments, followers, and other tickets. Parent-child ticket relationships are also explicitly defined in field configuration.

These relationships become part of the NocoBase data model and are shared by pages, permissions, workflows, and reporting features. Users can inspect each field type and relationship directly in the data source interface and continue adjusting them as business requirements change.

This is different from a Vibe Coding approach that starts from generated code. In a code-generated application, data relationships usually need to be implemented across the database structure, backend models, APIs, and page queries. If a relationship is incomplete or only one layer is updated later, data inconsistencies can occur. Manual inspection also requires developers to look into both code and database structures to verify the actual implementation.

NocoBase already provides data modeling capabilities. AI only needs to translate business requirements into tables, fields, and relationships instead of building the entire data layer from scratch. After the system is generated, people can inspect and modify the model directly in the same interface.

2. Can Different Roles Collaborate According to the Rules?

When only one person uses a system, permissions are usually not a major issue. Once an entire team starts collaborating, it becomes necessary to define who can see what and who can change what.

In this ticketing system, AI can configure the corresponding roles and data permissions directly in NocoBase.

This is another important difference between building with NocoBase and using a Vibe Coding approach. In an AI-generated application, permission rules often need to be implemented separately across pages, APIs, and data queries. As the number of roles and rules increases, configuration becomes more complex. During manual review, teams often need to return to the code or test the application directly to confirm whether permissions are actually taking effect.

NocoBase already provides permission management capabilities. AI does not need to rebuild a permission system. It only needs to configure which data different roles can view and operate on according to the business requirements. The result is also clearly visible in the administration interface, where users can inspect the permission scope for each role and switch identities to validate the result.

3. Can Business Rules Execute Reliably?

Many rules in a ticketing system need to be monitored continuously and triggered automatically by the system.

In the workflow management interface, users can directly inspect how each rule is triggered, its execution mode, whether it is enabled, and how many times it has run. There is no need to enter the codebase to confirm which rules are active, what conditions trigger them, and whether they have actually executed.

Execution results can also be inspected in detail. Take the “escalate overdue urgent tickets” workflow as an example. The system iterates through tickets that meet the condition, processes their deadlines, and runs the notification node. In the execution record shown in the screenshot, the escalation notification to the current owner has completed successfully, and the node status is shown as complete.

This means business rules are no longer hidden pieces of code. AI can configure them directly using NocoBase's existing workflow capabilities, while people can inspect the workflow structure, runtime status, and individual execution records from the interface.

This is exactly what an internal application needs before being used in real operations: it is not enough to define a business process. Teams also need to know whether it was triggered, how far it progressed, and whether it ultimately completed successfully.

Step 3: Add AI Capabilities to the System

Another advantage of building on NocoBase is that AI does not only help during the application-building stage. Once the core system is ready, AI Employees and workflows can allow AI to participate directly in ticket handling.

In the current ticketing system, we use AI in two specific parts of the process.

The first is ticket creation.

Support agents do not need to fill in every ticket field manually from the start. They can simply describe the customer's issue in natural language. AI Smart Form Fill first turns that description into a ticket title and issue description. Once the basic information is filled in, AI Smart Triage can review the ticket and suggest a category and priority.

Here, AI is responsible for converting the customer's natural-language description into structured information, but it does not bypass the form and submit the ticket automatically. The support agent can still review and edit the generated content before confirming and creating the ticket.

The second part is ticket handling.

On the ticket detail page, a support agent can ask AI to draft the next customer reply based on the current ticket. AI reads the customer's issue, handling progress, and communication history, then refers to the help articles matched by the system. It summarizes the ticket situation and response strategy before generating a reply draft.

More importantly, AI does not operate outside the system's permission model. NocoBase can control which users are allowed to use which AI Employees based on role. When an AI Employee calls the built-in data query tools, the system applies the current user's data permissions and only returns data that the user is allowed to access.

This means that when a regular support agent uses AI, AI does not automatically gain access to data that only a supervisor is allowed to see. What AI can access is still constrained by the original permission boundaries of the business system.

This is also what distinguishes NocoBase's AI capabilities from temporarily calling a large language model outside the application. AI is not just an extra chat entry point. It operates inside the existing data, permission, and workflow system. It can participate in the business process without bypassing the application's existing management rules.

Conclusion

Back to the question at the beginning: can an AI-built ticketing system really be used in production?

It depends on whether the system has a clear, inspectable business structure underneath it.

In this case, we first describe the business problems and requirements to AI. AI then uses NocoBase's existing data model, permission, and workflow capabilities to turn those requirements into a working ticketing system.

That is the value of combining AI with NocoBase: AI understands the requirements and improves building efficiency, while NocoBase provides a manageable and inspectable system foundation. The final business rules and go-live results are still confirmed by people.

If you have an internal process that still depends on spreadsheets, a shared inbox, or manual reminders, start with four questions:

Who will use the system?
What business information does the system need to record?
What can different roles view and operate on?
Which rules need to be executed automatically by the system?

Once these questions are described clearly, AI has a much better starting point for building the business system.

If you want to try this approach, first connect your Coding Agent to NocoBase AI Builder, then describe your business requirements in natural language.

During initialization, you can give AI the following instruction:

Help me install the NocoBase CLI and complete initialization:
https://docs.nocobase.com/ai/ai-quick-start.md
(Please open and read the linked documentation directly.)

After initialization is complete, continue with the specific business requirements and ask AI to build on NocoBase's existing data model, permissions, workflows, and related capabilities. You can then keep modifying the same application as the requirements evolve.

Try the NocoBase + AI Demo: Request an online demo
Build it yourself: View the AI Builder documentation

Related reading:

Weekly Updates: Added DeepSeek V4 Flash with Reasoning Continuation and Web Search

NocoBase — Fri, 28 Aug 2026 15:57:41 +0000

Summarize the weekly product update logs, and the latest releases can be checked on our blog.

NocoBase is currently updated across three branches: main, next, and develop.

main: The most stable version to date, recommended for installation.
next: Beta version, contains upcoming new features and has been preliminarily tested. There might be some known or unknown issues. It is mainly used to collect feedback from test users and further optimize features. Ideal for test users who want to experience new features early and provide feedback.
develop: Alpha version, contains the latest feature code, may be incomplete or unstable, and is mainly used for internal development and rapid iteration. Suited for technical users interested in cutting-edge product capabilities, but not recommended for production use.

main

v2.2.3

Release date: 2026-08-26

🐛 Bug Fixes

[client-v2] Fix a render error when switching a v2 association field to popup record selection. (#10419) by katherinehhh
[Public forms] Fix duplicate Submit actions in V2 regular form configuration when Public Forms is enabled. (#10417) by katherinehhh
[AI LLM: GigaChat] Fixed an application startup error on iOS 15.6 and earlier when the GigaChat AI provider is enabled (#10418) by cgyrock
[WeCom] Fixed WeCom automatic login lifecycle and notification form compatibility in client-v2. by chenzhizdt

v2.2.2

Release date: 2026-08-25

🚀 Improvements

[undefined] Clarified how to use public NocoBase file URLs in Markdown, external pages, and third-party services (#10406) by mytharcher Reference: Storage engine overview

🐛 Bug Fixes

[Access control] Fixed an ACL bypass that allowed firstOrCreate or updateOrCreate to read or modify existing records without the required view or update permission. (#10403) by mytharcher
[Workflow]
- Fix option fields being unable to select configured values in v2 workflow Create record and Update record nodes. (#10414) by katherinehhh
- Fix the extra trigger at startsOn for schedule workflows repeating on a cron expression (#10410) by Tespera
- Fixed workflow task center menus so the active menu can be collapsed by clicking it again while retaining its selected highlight (#10404) by mytharcher
- Fixed collection event as sub-workflows failing when called with a record ID and no preload associations configured (#10407) by mytharcher
[UI templates] Fix the error when closing an approval task containing a referenced block (#10415) by zhangzhonghe

v2.2.1

Release date: 2026-08-24

🐛 Bug Fixes

[UI layout] Fix the issue where desktop routes may be empty after upgrading (#10405) by zhangzhonghe
[Action: Export records Pro] Fix a crash when changing and drag-sorting Pro export fields. by katherinehhh

v2.2.0

Release date: 2026-08-22

🎉 New Features

[client-v2]
- Tabs on pages, subpages and pop-ups support the configuration of linkage rules (#10099) by zhangzhonghe
- Added configurable App and Portal entry support for V2 action panels and the left-top app switcher. (#9893) by katherinehhh
- Add an environment variable to configure legacy and modern route entry modes. (#9891) by Molunerfinn
[undefined]
- Added configurable App and Portal entries for the V2 action panel and app switcher. by katherinehhh
- Add Multi-Portal plugin by zhangzhonghe
[AI employees]
- Added configurable automatic or on-demand knowledge-base retrieval for AI employees, with role-based knowledge-base access filtering. (#10362) by cgyrock
- Added DeepSeek V4 Flash and V4 Pro Responses API support with reasoning continuity, native web search, citations, and model-aware web search controls (#10337) by cgyrock
- AI employees can now be assigned skills from the employee settings page. Skills are built from plugins. (#10237) by cgyrock
- Added UI navigation for supported LLM service CLI commands, including provider preselection when creating a service. (#10210) by cgyrock
- Added an embeddable AI chat box block that supports scoped conversations, AI employee tasks, and shared chat runtime behavior. (#10125) by cgyrock
- Added frontend AI tools for JS blocks (#10121) by 2013xile
- Added RunJS APIs for triggering AI employee tasks from JS blocks. (#10061) by cgyrock
- Added structured AI usage records for usage statistics (#10004) by 2013xile
- Added an external vector store configuration form for AI knowledge bases. (#9723) by cgyrock
[WEB client] Reduced application language responses to requested resource namespaces (#10175) by 2013xile
[Public forms] In the v1 public form, support creating v2 forms and prohibit creating v1 forms (#10045) by zhangzhonghe
[Block: Comment]
- Improved comment block settings with data scope, default sorting, selectable page size, optional last-page jumping, and scalar owner field mapping. (#9954) by jiannx
- Added a comments block. (#9916) by jiannx
[Notification: Email] Migrated the workflow notification node client to v2, restored channel-specific notification forms, and kept legacy workflow route compatibility for migrated notification configuration. (#9817) by jiannx
[Workflow: mailer node] Added v2 client support for configuring the workflow mailer node. (#9825) by jiannx
[UI layout] Add support for mobile layout (#9641) by zhangzhonghe
[Workflow]
- Added workflow database transaction scope support. (#9742) by mytharcher Reference: Database Transaction
- Migrate the Workflow settings page to the v2 client and share a reusable draggable category-tabs component via @NocoBase/client-v2. (#9645) by Molunerfinn
[Multi-space]
- Added default-space configuration so newly created users automatically join the selected default space. by jiannx
- Added debounced display-name search to space switchers and space management in both v1 and v2 by jiannx
[AI: Knowledge base]
- Added UI navigation for creating and editing vector databases from CLI commands, with provider preselection for new databases. by cgyrock
- Added role-based read-only and read/write permissions for knowledge-base management, including creator ownership and read-only management views. by cgyrock
[Workflow: Database transaction node]
- Added the database transaction workflow node plugin. by mytharcher
- Added a client-v2 implementation for the workflow database transaction node while preserving the legacy client entry. by katherinehhh
[Record history] Added client v2 support for the record history plugin. by jiannx
[Workflow: Approval]
- Added usage instructions and card-style workflow selection to the approval initiation list in client v2 by mytharcher
- Added usage instructions and card-style workflow selection to the approval initiation list by mytharcher
- Add approval initiation and todo blocks for v2 pages by zhangzhonghe
[Email manager]
- Email synchronization now uses recoverable background jobs with status history and safer full-resync cleanup, including Gmail Spam and Trash. by jiannx
- Migrated the email manager client to v2. by jiannx
[Auth: LDAP] Add LDAP user synchronization configuration support for client v2. by chenzhizdt

🚀 Improvements

[undefined]
- File URLs now use stable NocoBase access URLs so permissions can be checked before redirecting to storage. (#10103) by mytharcher
- Refined Russian documentation translation for improved wording, readability, and terminology consistency. (#9942) by sembaev-a-a
- Refined Russian documentation translation for improved wording, readability, and terminology consistency. (#9816) by sembaev-a-a
- Improved AI knowledge base retrieval and documentation. (#9765) by cgyrock
- Refined Russian documentation translation for improved wording, readability, and terminology consistency. (#9754) by sembaev-a-a
[cli] nb api resource create now accepts a JSON array for --values to create multiple records in a single request. (#10325) by Molunerfinn
Reference: nb api resource create
[client-v2]
- Refactor Markdown Vditor into a unified plugin-backed Markdown engine with compatibility bridges for existing Markdown block and Vditor field plugins. (#9998) by katherinehhh
- Refactor Markdown Vditor into a unified plugin-backed Markdown engine with compatibility bridges for existing Markdown block and Vditor field plugins. (#9998) by katherinehhh
- Adjusted the v2 System settings menu order and page panel height to match the standard settings layout. (#9849) by katherinehhh
- Fixed missing Settings entries for Client V2 plugin manager cards when a plugin uses a shared or legacy settings path. (#9852) by katherinehhh
[Workflow]
- Grouped task-center items by workflow in the new client and kept workflow filters consistent across task types. (#10374) by mytharcher
- Workflow create and update nodes now support combining text with variables when assigning string and text fields (#10238) by mytharcher
- Workflow tasks can now be filtered and navigated by workflow, with per-workflow pending counts (#10173) by mytharcher
- Improved workflow pending task handling by persisting start, resume, and rerun tasks in the event queue. (#9846) by mytharcher
- Unsupported workflow v2 canvas nodes now keep the normal node card actions while showing the node type as unsupported. (#10054) by mytharcher
- Simplified workflow v2 create/update field assignment, improved selected variable display, and avoided generating unused assign-form model data. (#9887) by katherinehhh
- Exported workflow v2 canvas extension APIs for downstream workflow node plugins. (#9834) by katherinehhh
- Migrate the workflow output node configuration to v2 and align v2 workflow result viewers with the legacy display behavior for string results. (#9813) by Molunerfinn
- Migrate the workflow end node to the v2 implementation. (#9795) by Molunerfinn
[AI employees]
- Simplified AI knowledge base vector configuration (#10178) by cgyrock
- Improved AI employee reliability across validation, data permissions, record context, attachments, workflow tasks, conversation recovery, and coding editor lifecycle handling. (#10162) by cgyrock
- Fixed AI employee model settings persistence, disabled employee conversation creation, and mobile chatbox layout behavior. (#10120) by cgyrock
- Improved AI employee tool settings, data-query guardrails, relation field querying, and malformed tool call diagnostics. (#10042) by cgyrock
- Improved AI employee web search to reduce unnecessary model reasoning and better use provider-specific thinking controls. (#9996) by cgyrock
- Removed the deprecated Datasource entry from AI employee settings and context selection in the v2 UI. (#9988) by cgyrock
- Migrated the AI employee plugin to client-v2. (#9794) by cgyrock
[File manager] Added independent storage settings for returning original file URLs and allowing public access to file URLs (#10160) by mytharcher
[Workflow: Manual node] Show manual workflow tasks in the V2 task center and guide users to the legacy page for processing (#10085) by zhangzhonghe
[Flow engine]
- Support multi portals for ui build apis. (#10072) by gchust
- Open runjs browser globals. (#9841) by gchust
[Collection: SQL] Not user-facing; added client-v2 unit test coverage for migrated plugins. (#9967) by katherinehhh
[Data visualization] Improved chart event scripts so custom event handlers can clean up safely (#10034) by 2013xile
[Data source manager]
- Hide deprecated v2 main data source collection templates from the create collection menu. (#10009) by katherinehhh
- Display unsupported external data source fields in V2 Configure fields, and align backup restore form label styles. (#9983) by katherinehhh
[Block: Comment]
- Improved comment submit actions and fixed related comment/user form submission issues. (#10002) by jiannx
- Added the new comment block plugin to the NocoBase preset and marked the legacy comments plugin as deprecated. (#9936) by jiannx
[Users]
- Improve client-v2 test coverage for the users plugin. (#9975) by jiannx
- Improved the Users & Permissions v2 page layout and department tree behavior. (#9780) by jiannx
[Workflow: JavaScript]
- Aligned v2 workflow request and mailer node configuration fields with legacy layout and attachment variable behavior. (#9952) by jiannx
- Migrated the JavaScript workflow node to client-v2 (#9805) by jiannx
[UI layout] Improved the v2 mobile tab bar so crowded tabs scroll horizontally instead of overlapping. (#9949) by katherinehhh
[Workflow: Aggregate node] Improved v2 workflow field selection for update and aggregate query nodes, including safer associated collection selection in aggregate query nodes. (#9938) by katherinehhh
[Logger] Added the Logger settings page to the client v2 runtime. (#9933) by jiannx
[Form drafts] Migrate plugin form drafts to client v2. (#9910) by gchust
[Workflow: JSON calculation] Migrated the workflow JSON calculation node configuration UI to the v2 workflow canvas while preserving v1 canvas compatibility. (#9902) by mytharcher
[User data synchronization] Added modern UI support for user data synchronization settings (#9837) by 2013xile
[Public forms] Separated v1 and v2 public form lists and fixed the v2 Configure page to open a configurable form detail page. (#9851) by katherinehhh
[Backup manager]
- Improved backup manager table styling and long file name display. (#9864) by katherinehhh
- Tables whose collection dataCategory is marked as 'runtime' are now excluded from backups automatically. (#9804) by cgyrock
[Workflow: Custom action event] Migrated workflow triggers and bind-workflow settings to client-v2, including action trigger, custom action trigger, request interception trigger, and submit/update action workflow binding settings. (#9845) by mytharcher
[Workflow: HTTP request node] Migrated the workflow HTTP request node to client-v2. (#9806) by jiannx
[Locale tester] Added a client v2 settings page for the locale tester. (#9744) by jiannx
[Access control] Aligned the v2 Users & Permissions settings pages with v1 behavior, including pagination totals, department tree behavior, selected styles, and internal permissions-panel scrolling. (#9810) by jiannx
[AI: Knowledge base]
- Aligned the vector database list styling with other settings tables by cgyrock
- Vector database and embedding settings can now be configured directly for each AI knowledge base by cgyrock
- Migrated the AI knowledge base settings pages to the v2 client and fixed layout and loading issues in knowledge base and vector store pages. by cgyrock
[HTTP request encryption] Added v2 client support for HTTP request encryption so query parameters continue to be encrypted in the v2 client. by jiannx
[Workflow: Database transaction node] Improved the v2 workflow database transaction node layout so branch labels and the commit marker have better spacing. by katherinehhh
[Workflow: Subflow] Change pending queue strategy based on workflow engine refactored by mytharcher
[File storage: S3(Pro)]
- S3 Pro uploads now return the created file record with permanent file URLs. by mytharcher
- Added independent S3 Pro settings for original URLs, public file URL access, and unsigned URLs by mytharcher
[Workflow: Approval]
- Updated approval task grouping and timelines in the new client to match the legacy experience. by mytharcher
- Approval application and todo tasks can now be filtered by workflow with per-workflow pending counts by mytharcher
[Email manager]
- Moved the department-based mail viewing option to the V1 general mail settings page, prevented service credential saves from overwriting it, and placed V2 General settings before Service provider settings. by jiannx
- Moved the department-based mail viewing option to the general mail settings page. by jiannx
[App supervisor] Hid the standalone V2 Applications block while keeping its settings page available internally. by katherinehhh
[WeCom] Added modern UI support for WeCom authentication, sync, and notification settings by 2013xile
[DingTalk]
- Complete DingTalk client v2 support, including Stream synchronization, notification configuration, and automatic login improvements. by chenzhizdt
- Added modern UI support for DingTalk authentication, sync, and notification settings by 2013xile

🐛 Bug Fixes

[undefined] Fix nb plugin import failing on plugin tarballs built by yarn build --tar, and correct example code and scaffold structure in the plugin development docs. (#10351) by Molunerfinn
[client-v2]
- Fixed relationship picker labels when association form values contain only a related record ID. (#10386) by cgyrock
- Fixed a false DatePicker missing-component error in v2 table filters. (#10392) by katherinehhh
- Fixed false missing-component console errors when opening v2 table filters. (#10389) by katherinehhh
- Fixed an error that prevented filter conditions from being cleared in workflow settings. (#10388) by Molunerfinn
- Fixed missing frontend response notifications on Client V2 pages, including errors returned by pre-action workflows (#10376) by mytharcher
- Fix Chinese text appearing when searching mobile select fields in English (#10367) by zhangzhonghe
- Fixed pages under /v remaining in UI editing mode after switching to a role without page configuration permission (#10359) by jiannx
- Show a retryable localized fallback in v2 blocks when an external data source is unavailable. (#10336) by katherinehhh
- Redirect users without Settings access to the first available page (#10331) by zhangzhonghe
- Automatically redirect to an accessible Settings tab when the current tab is unavailable (#10332) by zhangzhonghe
- Fix incorrect editing and display of large decimal values in V2 fields. (#10330) by katherinehhh
- Fixed Kanban column quick create records not inheriting the selected group value (#10321) by jiannx
- Fixed automatic SSO redirect providers failing to preserve authentication order in production builds (#10100) by jiannx
- Workflow filters now preserve workflow variable expressions and show a clear parsing error when variable metadata cannot be resolved. (#10088) by Molunerfinn
- Fix an error in v2 workflow value editors when a collection field is named nodeName. (#10067) by katherinehhh
- Fixed workflow v2 variable editors to preserve saved variable pills, disabled states, and operator labels consistently across trigger, filter, and field assignment forms. (#10041) by Molunerfinn
- Fixed an issue where v2 workflow assigned fields could still be edited in read-only executed workflow versions. (#10014) by katherinehhh
- Fix the issue where opening an empty V2 Group menu item shows 404 (#9896) by zhangzhonghe
- Fix workflow execution revision navigation so creating a new version after manual execution opens the correct workflow page in both legacy and modern shells. (#9955) by Molunerfinn
- Fixed V2 admin group routes showing 404 when the group has no available child menu page. (#9932) by katherinehhh
- Fixed link actions becoming invisible on mobile embedded pages when icon-only mode is enabled but no icon is configured. (#9919) by katherinehhh
- Fixed a brief no-pages prompt flash when refreshing in UI Editor mode. (#9918) by katherinehhh
[flow-engine]
- Fix issue where RunJS resource create actions could not create associated sub-table records (#10355) by gchust
- Fix dropdown menus being cut off in short browser windows (#10379) by zhangzhonghe
- Fixed an issue where users could type extra text after selecting a variable in single-value variable inputs. (#10050) by katherinehhh
- Fix the issue where mobile popups with long content cannot scroll (#9871) by zhangzhonghe
[client] Fix incomplete long sidebar menu titles and misaligned configuration toolbars (#10380) by zhangzhonghe
[auth] Fixed occasional Invalid CSRF token errors on API requests in cross-origin deployments (#10245) by mytharcher
[server] Fixed custom portals missing when multi-application plugins are disabled (#10055) by 2013xile
[AI employees]
- Fix V2 Import drag-and-drop being blocked by the AI attachment overlay. (#10384) by katherinehhh
- Fixed AI employee chat streaming long responses causing other idle browser tabs to balloon to multiple gigabytes of memory (#10352) by cgyrock
- Fixed the untranslated Settings tab in the AI plugin's client-v2 settings pages (#10234) by cgyrock
- Fixed frontend Tools asking for confirmation in chat instead of using runtime approval (#10166) by 2013xile
- Fix unnecessary login-required requests on V2 public form pages (#10013) by zhangzhonghe
[Workflow]
- Disable workflow execution mode selection until a trigger type is selected. (#10296) by Molunerfinn
- Fixed workflow execution page titles and added a workflow-list link for missing workflows (#10360) by mytharcher
- Improved regression coverage for permanent file URLs, attachment thumbnails, preview downloads, and local storage security headers (#10148) by mytharcher
- Workflow form controls now correctly inherit the disabled state when viewing executed workflows. (#10079) by Molunerfinn
- Refresh the workflow canvas after updating trigger configuration (#10068) by zhangzhonghe
- Fixed workflow v2 condition operands to stay on one row by default and wrap correctly when selected variable paths are too long. (#10033) by Molunerfinn
- Fix display and detail loading issues in the workflow v2 task center (#10001) by zhangzhonghe
- Fix untranslated workflow result labels and oversized CC configuration dialogs (#9977) by zhangzhonghe
- Fix workflow context mismatches across bundles so branches and some variable pickers work correctly in legacy workflow pages. (#9951) by Molunerfinn
- Fix issues after migrated client to v2 (#9929) by mytharcher
- Fix the issue where in-app message content cannot be configured in v2 workflows (#9885) by zhangzhonghe
- Restored debounced remote search for workflow collection trigger manual execution and aligned the selector with the v1 200-record fetch behavior. (#9870) by Molunerfinn
- Fixed the workflow v2 add-node menu so unavailable node types are disabled according to workflow and branch rules (#9855) by mytharcher
[Notification: In-app message] Fixed the in-app message template form showing workflow canvas variables instead of the variables provided by the page. (#10180) by Molunerfinn
[Block: Map] Fixed region selection not finishing on double-click when map point data is displayed, and fixed AMap remaining in a loading state (#10373) by jiannx
[UI layout]
- Fix mobile pages appearing in the desktop navigation (#10375) by zhangzhonghe
- Hide the mobile UI Editor when the current role cannot configure the interface (#10341) by zhangzhonghe
- Fix desktop pages using mobile styles on narrow screens (#10229) by zhangzhonghe
- Fix the Mobile settings link losing the current sub-application path (#10078) by zhangzhonghe
- Fixed the Mobile settings link opening the main application from a sub-application. (#10075) by katherinehhh
[File manager]
- Fixed local storage files such as logos failing to load in sub-applications after stable URL redirects (#10358) by mytharcher
- Fixed shared attachments such as the system logo not loading for authenticated member users (#10268) by mytharcher
- Fixed 404 errors when uploading files to attachment URL fields in external data sources (#9809) by 2013xile
[Users]
- Fixed required-field validation being skipped when submitting forms in UI editor mode (#10371) by jiannx
- Show backend errors when adding a user or changing a password in V2. (#10364) by katherinehhh
[Block: Tree]
- Fixed tree filter permissions and connected tree-table expansion state, and corrected details pagination totals after filtering. (#10361) by jiannx
- Fixed Tree block searches showing placeholder nodes when no business-field records matched (#10323) by jiannx
[Action: Import records] Fixed an issue where files could not be imported by dragging them into the v2 Import dialog. (#10350) by katherinehhh
[Action: Print]
- Fix the missing print action model registration on V1 pages. (#10347) by katherinehhh
- Fixed v2 detail block printing so empty detail blocks no longer print the whole page. (#9832) by katherinehhh
[Verification] Add a refresh button to the Verification list (#10340) by zhangzhonghe
[Notification manager]
- Fixed locale tester errors when no saved locale record exists, and allowed notification channel identifiers to be customized when creating channels (#10311) by jiannx
- Fix receiver selection saving user IDs as text (#10093) by zhangzhonghe
- Fix incorrect workflow variables shown in CC configuration (#9937) by zhangzhonghe
[Block: Gantt] Fixed custom record colors not being applied to short Gantt task bars (#10322) by jiannx
[Localization] Fixed a crash when opening Localization settings with the Lina AI assistant entry. (#10293) by cgyrock
[Backup manager]
- Prevent repeated V2 backup restore submissions while a restore request is in progress. (#10262) by katherinehhh
- Improved the stability and accuracy of backup plugin frontend tests. (#10184) by cgyrock
- Fixed inconsistent bold labels on the v2 Backup manager settings page. (#9908) by katherinehhh
[Variables and secrets] Fix validation feedback for v2 environment variable bulk imports and fix Type filtering failures. (#10154) by katherinehhh
[Authentication]
- Fixed declaration generation errors in the v2 authenticator management page (#10095) by jiannx
- Fixed missing saved Authenticator settings when editing authenticators in the v2 authentication manager. (#10091) by jiannx
- Fixed incorrect redirects after SSO login in v2 sub applications (#9927) by 2013xile
[Workflow: JSON variable mapping] Fix an error when selecting loop scope variables in the JSON variable mapping workflow node. (#10094) by Molunerfinn
[Workflow: Delay node] Fix delay node duration input and prevent values below the minimum from being saved. (#10056) by Molunerfinn
[Workflow: Aggregate node] Fix validation rule to allow null filter (#10053) by mytharcher
[Public forms] Fix the issue where public forms can still be configured when UI Editor is off (#10036) by zhangzhonghe
[Embed NocoBase]
- Fixed an issue where tokens could be polluted when embedding NocoBase pages. (#9948) by gchust
- Fixed v2 embed pages losing token-based access after the URL token is removed and the page is refreshed. (#9857) by katherinehhh
[Action: Export records] Fixed a crash when dragging v2 exportable fields after selecting relation fields. (#9995) by katherinehhh
[Block: Comment] Adjusted the default action order for new Comment blocks. (#9976) by jiannx
[Flow engine] Fixed the issue where mobile page can't be created by flow surface api. (#9911) by gchust
[Workflow: mailer node] Fixed workflow v2 test failures caused by missing mocks for trigger workflow action registration. (#9863) by jiannx
[Data source manager] Added a warning and quick setup for v2 data source collections without a primary key or record unique key. (#9872) by katherinehhh
[Workflow: JavaScript] Fixed JavaScript workflow node registration failure in the legacy workflow client. (#9826) by jiannx
[Workflow: Response message] Migrated the workflow response message node to the v2 canvas and fixed unsupported workflow types being able to add it. (#9830) by jiannx
[API documentation] Fixed the API documentation package declaration build failure. (#9752) by katherinehhh
[AI: Knowledge base] Added an overwrite option for AI knowledge base workflow document creation, allowing workflows to replace existing documents with the same key. by cgyrock
[Data source: External PostgreSQL] Automatically load collections when editing an external relational data source in client v2. by katherinehhh
[plugin-service-platform]
- Restored licensed plugin downloads from the service platform. by jiannx
- Disabled the service platform plugin download endpoint. by jiannx
[Verification: TOTP authenticator] Fixed TOTP authenticator bindings so temporary setup secrets are removed and previously verified codes cannot be reused. by jiannx
[Data source: External NocoBase] Fixed file preview, permanent URL handling, and upload routing for external NocoBase file collections, including S3 Pro uploads by mytharcher
[Multi-space] Fixed authentication recovery requests being blocked by stale multi-space headers. by jiannx
[Auth: SAML 2.0] Fixed SAML automatic sign-in redirects for unauthenticated users in the modern client while preserving the original destination path by jiannx
[App SSO] Fixed incorrect App SSO redirects in v2 sub applications by 2013xile
[Workflow: Subflow] Fixed workflow title search in the subflow node configuration selector. by mytharcher
[Migration manager]
- Fixed duplicate migration creation on repeated submission and improved v2 migration log and process drawer display. by katherinehhh
- Improve v2 migration error feedback, prevent duplicate migration rule names, and fix environment check modal overflow. by katherinehhh
[Auth: OIDC] Fixed OIDC automatic login redirects in production builds and retained the original modern-client path after login by jiannx
[Workflow: Approval]
- Invalid approval workflows in the new to-do center are now disabled and display a configuration warning. by mytharcher
- Fixed related approval blocks failing to load on Client V2 record detail pages by mytharcher
- Fix workflow form action buttons responding in configuration dialogs by zhangzhonghe
- Fix Approval blocks not refreshing after withdrawal or return by zhangzhonghe
- Guide users to V1 pages when approval interfaces cannot be used in V2 by zhangzhonghe
- Fix blank approval forms and missing or incorrect action buttons by zhangzhonghe
- Allow users to view approval interfaces and cards after a workflow has been executed by zhangzhonghe
- Fixed premature applicant validation and untranslated role labels in the approval workflow manual execution dialog. by Molunerfinn
- Fix the error when configuring approval workflow conditions by zhangzhonghe
- Fix the approval workflow task title remaining editable in executed workflow configurations after production builds. by Molunerfinn
- Close the Apply new drawer when opening an approval form by zhangzhonghe
- Fix empty approval interfaces and fixed assignee IDs by zhangzhonghe
- Fix the error when opening CC node settings by zhangzhonghe
- Fix v2 approval subtables not displaying correctly in details by zhangzhonghe
- Fix approval assignee sorting and hide unsupported legacy configuration entries by zhangzhonghe
- Fix missing approval data on approval task cards by zhangzhonghe
- Fix missing processed approval details in v2 task detail popups by zhangzhonghe
- Fix approval task form and action issues in the workflow v2 task center by zhangzhonghe
- Fix issues involved by migrating to client v2 by mytharcher
- Fix display and action issues in approval initiator interfaces by zhangzhonghe
- Fix the issue where approval tables appear in the block data source list by zhangzhonghe
- Fix an error that could prevent V2 pages from opening when approval and notification plugins are enabled by zhangzhonghe
[Collection field: Signature] Fix client-v2 signature field file collection selector localization and option filtering. by katherinehhh
[Audit logs] Fixed raw translation expressions appearing in the client V2 audit log Role column. by katherinehhh
[App supervisor] Fixed app visit links losing the v2 path in sub applications by 2013xile
[WeCom]
- Fixed WeCom notification channels not saving the selected authenticator. by jiannx
- Fixed a blank flash when switching route menu items with the WeCom plugin enabled in Client V2 by 2013xile
[DingTalk] Fixed DingTalk notification channels losing the selected authenticator when saved from the v2 channel form by jiannx

v2.1.44

Release date: 2026-08-21

🎉 New Features

[Multi-space] Added search to space switchers and space management in both v1 and v2 by jiannx

🐛 Bug Fixes

[DingTalk] Fixed DingTalk internal auto-login retaining the previous user's session after switching accounts. by chenzhizdt

v2.1.43

Release date: 2026-08-19

🐛 Bug Fixes

[app] Added runtime polyfills for modern JavaScript APIs in supported older browsers (#10385) by mytharcher
[undefined] Fixed customized external database field display names being reset when selected tables are reloaded by cgyrock
[Data source manager] Fixed customized external database field display names being reset when a data source is submitted or its selected tables are changed (#10387) by cgyrock
[Workflow: Approval] Fixed approval workflows configured to return to any previous approval node only allowing the nearest upstream node by mytharcher

v2.1.42

Release date: 2026-08-18

🚀 Improvements

[undefined]
- Added LDAP and DingTalk user data synchronization guides, including permissions, event modes, synchronized fields, department owners, and troubleshooting. (#10377) by chenzhizdt Reference: DingTalk synchronization, LDAP synchronization
- Improve LDAP and DingTalk user synchronization documentation and add all supported translations. (#10382) by chenzhizdt Reference: DingTalk / LDAP

🐛 Bug Fixes

[Workflow: JavaScript] Fixed JavaScript workflow task recovery repeatedly enqueueing jobs whose executions have ended or expired. (#10366) by mytharcher
[Action: Export records Pro] Fix export errors when using complex filters with the Export Pro plugin by zhangzhonghe
[Action: Import records Pro] Fixed asynchronous imports not respecting field-level import permissions by mytharcher
[App supervisor] Fixed Kingbase connections when creating supervised applications by 2013xile

v2.3.0-beta.4

Release date: 2026-08-25

🚀 Improvements

[undefined] Clarified how to use public NocoBase file URLs in Markdown, external pages, and third-party services (#10406) by mytharcher Reference: Storage engine overview

🐛 Bug Fixes

[UI layout] Fix the issue where desktop routes may be empty after upgrading (#10405) by zhangzhonghe
[Workflow] Fixed workflow task center menus so the active menu can be collapsed by clicking it again while retaining its selected highlight (#10404) by mytharcher
[Action: Export records Pro] Fix a crash when changing and drag-sorting Pro export fields. by katherinehhh

v2.2.0-beta.18

Release date: 2026-08-20

🎉 New Features

[AI employees] Added DeepSeek V4 Flash and V4 Pro Responses API support with reasoning continuity, native web search, citations, and model-aware web search controls (#10337) by cgyrock
[Multi-space]
- Added search to space switchers and space management in both v1 and v2 by jiannx
- Added debounced display-name search to space switchers and space management in both v1 and v2 by jiannx
[Email manager] Email synchronization now uses recoverable background jobs with status history and safer full-resync cleanup, including Gmail Spam and Trash. by jiannx
[Auth: LDAP] Add LDAP user synchronization configuration support for client v2. by chenzhizdt

🚀 Improvements

[undefined]
- Improve LDAP and DingTalk user synchronization documentation and add all supported translations. (#10382) by chenzhizdt Reference: DingTalk / LDAP
- Added LDAP and DingTalk user data synchronization guides, including permissions, event modes, synchronized fields, department owners, and troubleshooting. (#10377) by chenzhizdt Reference: DingTalk synchronization, LDAP synchronization
[lock-manager] Added renewable local lock leases and ensured try-acquired locks are released safely across reuse and errors (#10368) by jiannx
[cli] nb api resource create now accepts a JSON array for --values to create multiple records in a single request. (#10325) by Molunerfinn
Reference: nb api resource create
[Workflow] Grouped task-center items by workflow in the new client and kept workflow filters consistent across task types. (#10374) by mytharcher
[Block: Tree] Tree filter blocks now support configurable default sorting. (#10339) by jiannx
[Redis lock adapter] Added renewable Redis lock leases and made reusable lock handles release safely during contention and errors by jiannx
[Workflow: Approval] Updated approval task grouping and timelines in the new client to match the legacy experience. by mytharcher
[DingTalk] Complete DingTalk client v2 support, including Stream synchronization, notification configuration, and automatic login improvements. by chenzhizdt

🐛 Bug Fixes

[client-v2]
- Fixed relationship picker labels when association form values contain only a related record ID. (#10386) by cgyrock
- Fixed a false DatePicker missing-component error in v2 table filters. (#10392) by katherinehhh
- Fixed false missing-component console errors when opening v2 table filters. (#10389) by katherinehhh
- Fixed an error that prevented filter conditions from being cleared in workflow settings. (#10388) by Molunerfinn
- Fixed missing frontend response notifications on Client V2 pages, including errors returned by pre-action workflows (#10376) by mytharcher
- Fix Chinese text appearing when searching mobile select fields in English (#10367) by zhangzhonghe
- Fix filter forms refreshing automatically in UI edit mode (#10356) by zhangzhonghe
- Use Cascader by default for tree-structured relation fields in v2 filter forms (#10357) by zhangzhonghe
- Fix JS items incorrectly appearing in form field linkage rule actions (#10363) by gchust
- Fixed pages under /v remaining in UI editing mode after switching to a role without page configuration permission (#10359) by jiannx
- Automatically redirect to an accessible Settings tab when the current tab is unavailable (#10332) by zhangzhonghe
- Fix mobile single-select relation fields not clearing when the selected record is tapped again (#10346) by zhangzhonghe
- Fix the issue where China region fields cannot be added directly to filter forms (#10333) by zhangzhonghe
- Fixed an issue where ctx.form.submit could not correctly submit form data. (#10063) by gchust
- Redirect users without Settings access to the first available page (#10331) by zhangzhonghe
- Fix incorrect editing and display of large decimal values in V2 fields. (#10330) by katherinehhh
- Show a retryable localized fallback in v2 blocks when an external data source is unavailable. (#10336) by katherinehhh
[app] Added runtime polyfills for modern JavaScript APIs in supported older browsers (#10385) by mytharcher
[flow-engine] Fix dropdown menus being cut off in short browser windows (#10379) by zhangzhonghe
[client] Fix incomplete long sidebar menu titles and misaligned configuration toolbars (#10380) by zhangzhonghe
[undefined]
- Fix nb plugin import failing on plugin tarballs built by yarn build --tar, and correct example code and scaffold structure in the plugin development docs. (#10351) by Molunerfinn
- Fixed customized external database field display names being reset when selected tables are reloaded by cgyrock
[database] Fixed prefix indexes on camel-case fields when underscored database naming is enabled (#10329) by 2013xile
[Data source manager] Fixed customized external database field display names being reset when a data source is submitted or its selected tables are changed (#10387) by cgyrock
[Workflow: JavaScript] Fixed JavaScript workflow task recovery repeatedly enqueueing jobs whose executions have ended or expired. (#10366) by mytharcher
[Workflow]
- Fixed workflow execution page titles and added a workflow-list link for missing workflows (#10360) by mytharcher
- Disable workflow execution mode selection until a trigger type is selected. (#10296) by Molunerfinn
[Notification: In-app message] Fixed the in-app message template form showing workflow canvas variables instead of the variables provided by the page. (#10180) by Molunerfinn
[Block: Map] Fixed region selection not finishing on double-click when map point data is displayed, and fixed AMap remaining in a loading state (#10373) by jiannx
[Collection field: Markdown(Vditor)] Fix Markdown HTML previews in v2 details blocks under dark themes. (#10370) by katherinehhh
[UI layout]
- Fix mobile pages appearing in the desktop navigation (#10375) by zhangzhonghe
- Hide the mobile UI Editor when the current role cannot configure the interface (#10341) by zhangzhonghe
[AI employees]
- Fix V2 Import drag-and-drop being blocked by the AI attachment overlay. (#10384) by katherinehhh
- Fixed AI employee chat streaming long responses causing other idle browser tabs to balloon to multiple gigabytes of memory (#10352) by cgyrock
[Workflow: JSON calculation] Fixed JSON Query jobs losing structured parser errors and displaying [object Object] (#10344) by mytharcher
[Users]
- Show backend errors when adding a user or changing a password in V2. (#10364) by katherinehhh
- Fixed required-field validation being skipped when submitting forms in UI editor mode (#10371) by jiannx
[File manager]
- Fix the extra submit step when selecting an existing file in a single-value field (#10372) by zhangzhonghe
- Fixed local storage files such as logos failing to load in sub-applications after stable URL redirects (#10358) by mytharcher
- Fixed video previews not updating when switching between files (#10345) by mytharcher
[Action: Import records] Fixed an issue where files could not be imported by dragging them into the v2 Import dialog. (#10350) by katherinehhh
[Action: Print] Fix the missing print action model registration on V1 pages. (#10347) by katherinehhh
[Block: Tree] Fixed tree filter permissions and connected tree-table expansion state, and corrected details pagination totals after filtering. (#10361) by jiannx
[Verification] Add a refresh button to the Verification list (#10340) by zhangzhonghe
[Block: Kanban] Fixed configured content disappearing after reopening a kanban card's detail drawer (#10334) by jiannx
[Action: Export records]
- Fix table export errors after filtering by multiple relation fields (#10342) by zhangzhonghe
- Fixed a page crash when sorting an edited relation field in Export V2. (#10335) by katherinehhh
[Notification manager] Fixed locale tester errors when no saved locale record exists, and allowed notification channel identifiers to be customized when creating channels (#10311) by jiannx
[Action: Duplicate record] Improve direct duplication failure feedback in v2 without duplicate API error messages. (#10327) by katherinehhh
[Data source: External PostgreSQL] Automatically load collections when editing an external relational data source in client v2. by katherinehhh
[Collection field: Encryption] Fixed bulk import failing with model.changed is not a function when the collection contains an encryption field by cgyrock
[Action: Export records Pro] Fix export errors when using complex filters with the Export Pro plugin by zhangzhonghe
[Action: Import records Pro]
- Fixed asynchronous imports not respecting field-level import permissions by mytharcher
- Fixed asynchronously imported records not being associated with the current space by jiannx
- Clarified import results by showing the number of newly created records separately from updated records by mytharcher
[Workflow: Webhook] Fixed a 400 error when manually executing a webhook workflow without request headers by mytharcher
[Record history] Improved record history write performance for collections with large snapshot tables by 2013xile
[Workflow: Approval]
- Fixed approval workflows configured to return to any previous approval node only allowing the nearest upstream node by mytharcher
- Add data scope filtering to Client V2 related approval blocks by zhangzhonghe
- Fix Approval blocks not refreshing after withdrawal or return by zhangzhonghe
- Invalid approval workflows in the new to-do center are now disabled and display a configuration warning. by mytharcher
- Fix inconsistent subtable column widths in approval details by zhangzhonghe
- Fixed related approval blocks failing to load on Client V2 record detail pages by mytharcher
[Audit logs] Fixed raw translation expressions appearing in the client V2 audit log Role column. by katherinehhh
[App supervisor] Fixed Kingbase connections when creating supervised applications by 2013xile

Building an Inventory Management System: Vibe Coding vs NocoBase + AI

NocoBase — Mon, 24 Aug 2026 11:37:45 +0000

Originally published at https://www.nocobase.com/en/blog/building-inventory-management-system-vibe-coding-vs-nocobase-ai

On Reddit in r/InventoryManagement, someone wanted to use AI to build an inventory management app for a restaurant.

At first, the requirements seemed simple: enter products, receive goods, and issue goods. But once the system was actually being built, more questions appeared. How should different inventory units be handled? How should quantities change after receiving and issuing goods? Requirements that can be described in just a few sentences often involve more data and business rules than expected once they are implemented in a real system. People in the comments also pointed out that inventory management is much more complex than it appears on the surface.

This is also a common issue when using AI to build business systems. Generating a few pages is becoming increasingly fast, but the data relationships behind those pages, inventory movements, permissions, workflows, and whether the system can still be maintained when requirements change all need to be checked carefully.

If we use exactly the same inventory management requirements, what is the difference between letting AI generate an application from scratch and letting AI build the same system on NocoBase?

We built two versions:

Starting from a blank project, AI directly generated an independent inventory management application.
AI built the same system on top of NocoBase's data models, permissions, and workflows.

Next, we compare the two approaches across purchasing, receiving, inventory movement records, inventory counting, and later requirement changes, focusing on concrete differences in data relationships, business rules, permissions, and maintenance.

1. What Can the Same Prompt Generate?

The requirements we gave AI covered a relatively complete inventory management workflow:

Build an inventory management system for an auto-parts sales company to centrally manage products, categories, suppliers, purchase orders, and inventory; record receipts, issues, damage, and inventory adjustments; view inventory movement records; identify stockouts, low stock, overstock, and products with no outbound movement for a long time; support inventory counting, discrepancy review, and inventory adjustments; and provide a management workspace with interconnected demo data.

The requirements mainly contain five parts:

Products and suppliers → Purchasing → Inventory movements → Inventory risks → Inventory counting and adjustments

A purchase order may contain multiple products. After products are received, inventory quantities need to change, while the corresponding receipt record must also be preserved. If an inventory count finds a discrepancy, the system should not simply overwrite an inventory figure; it also needs to record the discrepancy, adjustment reason, and confirmation result.

The full prompt is below. Both systems in the rest of this article were generated from this same requirement.

I am responsible for inventory management at an auto-parts sales company. We currently manage products, suppliers, purchasing, and inventory mainly with spreadsheets. As the number of products grows, we frequently encounter inaccurate inventory quantities, delayed discovery of stockouts, long-term overstock of some products, and inventory count discrepancies that are difficult to trace.

I want to build an inventory management system that centrally manages products, categories, suppliers, purchase orders, and inventory data. The system should record every receipt, issue, damage event, and inventory adjustment so that I can view current inventory at any time and understand why inventory quantities changed.

I want the system to automatically identify stockouts, low-stock items, overstock, and products with no outbound movement for a long time. Based on recent sales and inventory conditions, it should provide replenishment suggestions to help purchasing staff decide which products to buy, how much to buy, and which supplier to use.

The system also needs to support inventory counting. Staff can enter the actual quantity, and the system should automatically calculate inventory gains or losses. After review is completed, inventory should be adjusted according to the discrepancy, with a complete record retained.

Managers need an intuitive workspace showing total inventory, inventory value, recent receipts and issues, inventory risks, and pending items. The overall design should be clear and easy to use, allowing inventory staff to handle daily operations efficiently while helping managers quickly identify problems.

Based on the actual business requirements above, please design a reasonable functional structure, data relationships, and page interactions, and prepare some interconnected sample data so the system can directly demonstrate a complete inventory management process.

First-Round Results

We built the system in two ways: with Vibe Coding and with NocoBase + AI.

From the pages alone, both versions already cover the main functions, including products, purchasing, receipts and issues, inventory counting, and data overview. Once we actually tested the systems, however, the difference in completeness became much clearer.

In this generated result, NocoBase + AI had already created operational data tables, pages, and basic business relationships. Product, supplier, and purchase-order data could be entered and linked normally. After the first round, the system was already relatively close to something that could be used in practice, and the next step was mainly to refine rules and operation details around the real business.

The Vibe Coding version was still closer to a frontend prototype. Although the pages already presented products, purchasing, receipts and issues, and inventory counting, the data was not yet truly interactive, and some buttons and actions could not complete actual business operations. To reach the same usage state, it would still need data persistence, APIs, business logic, permissions, and other pieces.

This difference comes from the starting point of the two approaches.

Vibe Coding starts from a blank project. The database, APIs, pages, and business logic all need to be generated by AI step by step according to the current requirements.

NocoBase + AI builds inside an existing application framework. When AI creates products, purchase orders, and inventory records, it can directly use existing capabilities for data relationships, pages, permissions, and workflows.

2. Comparing the Two Inventory Management Systems in Real Business Workflows

We selected a common inventory management workflow:

Create products and suppliers → Create purchase order → Receive goods → Generate an inventory movement record → Identify low stock → Start an inventory count → Review discrepancy → Adjust inventory

Start with Products and Purchase Orders

Start with the most basic data: products, suppliers, and purchase orders.

Suppose the company purchases three types of auto parts from Supplier A. One purchase order contains:

100 sets of brake pads
200 air filters
300 spark plugs

This order involves at least four types of records: supplier, purchase order, purchase order lines, and products. One order can contain multiple line items, and each line records a product, quantity, and unit price.

NocoBase + AI

Vibe Coding

When checking an inventory management system, seeing a “Supplier” page and a “Purchase Order” page is not enough.

Can these records reference one another and continue to be used during later receiving operations?

For example, can you view related products and purchase records from the supplier detail page? When opening a purchase order, can you see every product line? When receiving goods later, can the system still reference the data from this purchase order?

NocoBase + AI

Vibe Coding

Based on the current generated results, both systems already provide pages for these business objects. In NocoBase + AI, these business objects are built on a unified data model; in the Vibe Coding version, those relationships need to be maintained by the generated database structure and program logic.

Purchase Receiving and Inventory Movement Records

After the purchase order is created, the next step is receiving.

Suppose the brake pads already have 20 units in inventory and another 100 are received from this purchase order. After receiving, current inventory should become 120, and a new receipt record should be created and linked to the corresponding purchase order.

The record also needs to retain the receiving time, operator, and other information. Later issues, damage, returns, or inventory-count adjustments should continue generating new inventory movement records.

So we focus on three things: whether inventory is updated correctly, whether a corresponding record is preserved, and whether that record can be traced back to the original purchase order.

NocoBase + AI

Vibe Coding

An inventory management system cannot store only the latest inventory figure. Receipts, issues, damage, and adjustments all need their own movement records so the source of the current inventory can be traced later.

Low Stock and Replenishment Decisions

After inventory changes, managers also need to quickly identify which products have fallen below safety stock.

For example, if a product has current inventory of 20 and safety stock of 50, the system should classify it as low stock. If safety stock is later changed to 30, the risk result should update accordingly.

Both first versions already generated inventory-risk or similar management pages.

But the source of the data still matters. Are these results directly derived from the inventory data created earlier?

If the system also generates replenishment suggestions, it needs to calculate suggested quantities using current inventory, safety stock, target stock levels, and potentially historical outbound movements, while also retrieving the corresponding supplier information.

NocoBase + AI

Inventory risk is not standalone data. It comes from existing information such as current inventory, safety stock, products, and suppliers.

Inventory Count Discrepancies, Review, and Inventory Adjustments

Suppose the system shows 100 units of a part, but warehouse staff physically count only 96.

The counting staff first enter the actual quantity, and the system calculates a discrepancy of -4. But inventory should not immediately be changed to 96.

The reason for those four missing units needs to be confirmed first. It may be an unrecorded issue, loss, an input error, or another cause. If counting staff can directly overwrite the original inventory figure after entering a count, it becomes difficult to determine later how the change occurred.

So we added a more specific rule:

Counting staff can enter the actual quantity and discrepancy reason, but only after a reviewer confirms the result can the system formally adjust inventory.

The processing flow for one inventory-count discrepancy is:

Enter actual quantity → Calculate discrepancy -4 → Submit for review → Confirm adjustment → Inventory becomes 96 → Save adjustment record

At this point, there is much more to check:

Is the discrepancy calculated automatically and moved into the correct status?
Can users without review permission adjust inventory?
After review, is inventory updated and an inventory movement record generated at the same time?
Are the operator, time, and reason recorded?
Are historical inventory-count results preserved?

This kind of requirement is difficult to solve simply by “generating an inventory count page.”

In the Vibe Coding version, the system needs additional program logic to connect count status, review permissions, inventory updates, and adjustment records. For example, once a review is approved, the program must update inventory and create an adjustment record at the same time. Accounts without review permission must not be able to perform that operation.

The NocoBase + AI version uses existing data relationships, role permissions, and workflows to handle the same set of rules. After an inventory-count record is submitted, it enters a pending-review status. A reviewer confirms it, then inventory is updated and the corresponding adjustment record is preserved.

3. Vibe Coding or NocoBase + AI: Which Should You Choose?

After comparing purchasing, receiving, inventory risks, inventory counting, and the resulting features, the difference between the two approaches becomes more visible.

Comparison	Vibe Coding	NocoBase + AI
First-Round Results	In this test, it was closer to a frontend prototype and still required additional data and business logic.	In this test, it was already able to enter, link, and operate business data.
Data Model	Database structures, APIs, and data relationships need to be implemented within the project.	Relationships between products, purchasing, inventory, and other business objects are built directly on a unified data model.
Permissions & Data Scope	Permission logic needs to be developed and tested according to business rules.	Roles, operation permissions, and data scopes can be configured directly.
Business Processes	Status transitions, approvals, and automation require further development.	Can be configured and adjusted directly through workflows.
Requirement Changes	Changes may affect databases, APIs, pages, validation logic, and testing at the same time.	Changes mainly focus on data models, pages, permissions, and workflows.
Extension Approach	Extend and modify the system directly through code.	Can be extended through configuration, while still supporting JS, plugins, and custom code when needed.
Future Maintenance	More dependent on developers and a complete codebase.	Many business adjustments can continue to be handled through configuration, while complex requirements can move into the code layer.

When Is NocoBase + AI a Better Fit?

If you are building an internal business system for inventory management, procurement, CRM, or IT management, NocoBase + AI is generally a better fit.

Its advantages mainly appear in four areas.

1. AI generates more than pages

Products, suppliers, purchase orders, inventory movement records, inventory-count records, permissions, and workflows created by AI become business objects inside NocoBase that can continue to be used and modified.

2. Common back-office capabilities do not need to be rebuilt

Data relationships, permissions, forms, workflows, and similar capabilities are already provided by NocoBase. Teams can spend more time on specific business rules such as how inventory should be calculated, who can see which warehouses, and how transfers should work.

3. Later changes cost less

When adding fields, adjusting pages, changing permissions, or adding workflows, many changes can be configured directly on the existing data model rather than repeatedly modifying frontend code, APIs, and database code.

4. The scope of AI changes is clearer

AI mainly operates on explicit objects such as data models, fields, pages, permissions, and workflows. As the system becomes more complex, it is easier to inspect which parts were affected by a change.

When Is Vibe Coding a Better Fit?

Vibe Coding's main advantages are speed and flexibility. It can be a better choice when your project is focused on the following:

1. The project is still in an early validation stage. The current goal is simply to build a demo, MVP, or disposable prototype quickly, without needing to consider complex data relationships, permissions, or long-term maintenance.

2. You already have an existing codebase and want AI to continue developing within that technical stack. For example, your team already has its own frontend and backend projects and only wants AI to add pages, APIs, or business logic.

How Can You Let AI Build on NocoBase?

If you want to reproduce the NocoBase + AI approach above, first let your Coding Agent enter the NocoBase AI Builder environment, then submit the specific business requirements. During initialization, you can use the following instruction:

Please follow the official NocoBase documentation to help me install the NocoBase CLI and complete initialization:
https://docs.nocobase.com/ai-builder

All subsequent applications must be built with NocoBase AI Builder and NocoBase Skills. Do not create a standalone React, Vue, or Next.js project.

After initialization is complete, submit the inventory management requirements from earlier and ask AI to prioritize NocoBase's data models, pages, permissions, and workflows. This keeps later generation and modification within the same application structure.

If this article was helpful, feel free to share it with others who are exploring how to use AI to build business systems.

If you also want to see what a system built with NocoBase + AI looks like in practice, you can request an online demo. If you want to try building one yourself, you can start with the AI Builder documentation.

Try the NocoBase + AI Demo: Request an online demo
Build it yourself: View the AI Builder documentation

Related reading:

Announcing NocoBase 2.2

NocoBase — Mon, 24 Aug 2026 09:37:16 +0000

Originally published at https://www.nocobase.com/en/blog/2.2.0

NocoBase 2.2 further completes the end-to-end V2 experience. With the independent /v/ frontend entry and the new mobile experience now available, V2 is no longer just a redesigned page experience—it is becoming a more independent and lightweight frontend runtime. This release also upgrades the file access mechanism and continues to improve the comment block, AI knowledge base, workflows, and V2 compatibility across core plugins.

If your application already relies primarily on V2 pages, 2.2 provides a more complete and lightweight V2 experience. If your application still mainly uses V1 pages, we recommend migrating your pages and plugins before switching to the new /v/ entry.

New features

New independent `/v/` frontend entry

/v/ is a new, independently built frontend entry. NocoBase 2.0 introduced a major frontend refactor while retaining compatibility with V1 modules and pages. The /v/ build removes this legacy V1 compatibility: it can no longer create or render V1 pages and blocks and includes only V2 capabilities. It also delivers significant performance improvements and will become the primary target for future NocoBase development.

If your production application already consists entirely of V2 pages, you can consider adopting the /v/ entry.

If your application mainly uses V2 pages but still contains a small number of V1 pages, migrate those pages to V2 first.

If your application still mainly uses V1 pages, we do not recommend switching directly to /v/. Migrate the pages and related plugins first.

In most cases, you can enter the new frontend by adding the /v/ prefix to an existing path:

# Original path
https://nocobase.example.com/admin/1xl0epqn6q3

# Independent V2 entry
https://nocobase.example.com/v/admin/1xl0epqn6q3

Set the default application entry

Use the APP_CLIENT_ENTRY_MODE environment variable to control the application entry mode:

legacy-default: both / and /v/ are available; / is the default entry
modern-default: both / and /v/ are available; /v/ is the default entry
modern-only: only /v/ is available

Current status of `/v/`

The /v/ entry is being introduced progressively. It has several notable differences:

Pages created with Page V1 are no longer displayed under /v/. Pages created with Page V2 continue to work normally.
Plugins adapted only for client-v1 are not loaded under /v/. The /v/ entry loads only plugins adapted for client-v2. See the client plugin development documentation for details.

Most built-in NocoBase plugins have been adapted and migrated to client-v2 in this release, so most features are ready to use. A small number of plugins have not yet been migrated and will be handled progressively. Some plugin capabilities will receive future updates only under /v/. Current differences include:

The plugin list no longer shows deprecated plugins or plugins that support only NocoBase 1.x
New Page V1 pages can no longer be created
Public forms distinguish between V1 and V2, and V1 public forms are not displayed under /v/
Approval workflows require their related UI to be reconfigured before they can be used under /v/
The new mobile experience is available only under /v/
The “AI employees / Data sources” tab has been removed
Comment, calendar, expression, and external data collections have been removed
Workflow manual nodes are not yet supported under /v/
Badge counts cannot yet be added to menus

Plan the migration to /v/ according to your production environment and current use of V1 and V2 features.

Related documentation:

Client plugin development

File access upgrade: stable URLs, permission checks, and deployment changes

NocoBase 2.2 introduces an important upgrade to the access mechanism for NocoBase-managed files. By default, attachments and files no longer expose local storage paths, object storage URLs, or presigned URLs as their business URLs. Instead, they use stable NocoBase URLs:

/files/<app>/<dataSource>/<collection>/<id><extname>

For example:

/files/main/main/attachments/42.pdf

If APP_PUBLIC_PATH=/nocobase is configured, the corresponding subpath is added automatically:

/nocobase/files/main/main/attachments/42.pdf

When a stable URL is accessed, the request first goes to NocoBase. NocoBase checks the current user, role, view permission, and data scope for the target attachment or file collection. Once the check succeeds, NocoBase responds with a 302 redirect to the actual URL generated by the storage engine.

Stable URL → NocoBase identity and permission checks → 302 → Local or object storage URL

This separates business content from physical storage addresses. If you change a bucket, CDN domain, signing strategy, or thumbnail rule, stable URLs already stored in business fields usually do not need to be updated. The everyday workflows for uploading attachments, displaying images, previewing files, and downloading files remain essentially unchanged.

Configure file URLs and public access independently

For file storage engines, NocoBase URL is the recommended default so that file access follows NocoBase role and data permissions. NocoBase 2.2 also provides separate options for scenarios that require direct storage URLs or public access:

Original URL: returns the storage engine URL directly, without NocoBase permission checks
Allow public access: continues to return a NocoBase URL but skips file-record permission checks when the URL is accessed

Both Original URL and Allow public access expand the scope from which files can be accessed, so configure them carefully for your use case. After the settings are saved, the API response behavior changes for both existing and new files under the same storage engine, but no files are moved or uploaded again.

Check deployment configuration before upgrading

/files/ is an authenticated NocoBase application route. It must not be handled as a static directory or fall through to the frontend SPA's index.html fallback. Nginx and Caddy configurations generated by the current NocoBase CLI include the required rules automatically. If you maintain your reverse proxy manually, verify that:

/files/ is forwarded to NocoBase and evaluated before the SPA fallback rule
When APP_PUBLIC_PATH is configured, the corresponding subpath /files/ route is also forwarded, while the root /files/ route remains available for compatibility
The 302 Location returned by a stable URL is not cached
When a page accesses the API cross-origin, its origin is included in CORS_ORIGIN_WHITELIST
All cluster nodes and replicas are upgraded together so that /files/ requests cannot reach an older node
When using an external NocoBase data source, the consuming instance and its related plugins are upgraded before the source instance

Note: Existing /storage/uploads/..., CDN, and object storage URLs stored in historical Markdown, rich text, or business fields are not rewritten automatically. Once the new version is running, newly uploaded files and newly edited content may contain /files/... URLs, which older versions do not recognize. Environments with strict rollback requirements should retain a database snapshot before reopening write access and verify the reverse proxy configuration in advance.

Security boundaries

Stable URLs provide a permission check before access, but NocoBase does not continuously proxy the file content. After permission checks succeed, the browser can still see the final storage URL. If that URL points to a public bucket, a public CDN, or an openly accessible local static directory, anyone who obtains it may still bypass NocoBase.

For sensitive files such as contracts, identity documents, and internal materials, use storage-side controls such as private storage, short-lived signed URLs, or CDN authentication. For online Office previews, NocoBase issues a short-lived URL bound to the current file after the user's permissions are validated. This URL is valid for 10 minutes by default and must not be stored or distributed as a long-term sharing link.

Related documentation:

New mobile experience (`/v/` only)

The new mobile experience provides a /v/mobile entry with a dedicated mobile layout.

Mobile and desktop layouts share the same data sources and business data, while their menus, routes, and page content can be configured independently. This makes it possible to reorganize pages around mobile usage patterns and use a bottom tab bar as the primary navigation, which is better suited to mobile devices.

NocoBase 2.2 further improves interactions such as mobile tab bars, scrolling in half-screen panels, embedded pages, and permission controls, making data entry, queries, approvals, and task processing more reliable.

Related documentation:

Mobile layout

New comment block

The new comment block is no longer limited to the comments collection in the main data source and no longer needs to be used as a relationship block. You can add it to a record detail page or popup for tasks, articles, tickets, customers, and other records, allowing users to view, reply to, and add comments in the context of the current record.

Related documentation:

Comment block

AI knowledge base enhancements

The AI knowledge base has been migrated to client-v2 and now offers improved knowledge base and vector storage configuration:

When a workflow creates a knowledge base document, it can overwrite an existing document with the same document key
Vector databases can be configured and managed
Configuration entries are available for external knowledge bases and external vector storage extensions, allowing developers to use plugins to integrate vector databases or third-party retrieval services that NocoBase does not yet support out of the box

Related documentation:

Workflow: Database transaction node

The new database transaction node runs a group of database operations within the same transaction. It is designed for scenarios in which multiple data-processing steps must either all succeed or all roll back—for example, creating an order, reducing inventory, writing order line items, and updating the order status.

Related documentation:

Database transaction node

V2 compatibility and experience improvements

In addition to the new features above, NocoBase 2.2 continues to migrate and improve the V2 interfaces and interactions of commonly used features:

User, department, and permission settings
User data synchronization
DingTalk authentication, synchronization, and notification settings
WeCom authentication, synchronization, and notification settings
Email management
Form drafts
Public forms
Backup management
Data source management
Translation testing tools

This release also fixes a range of issues affecting mobile devices, embedded pages, sub-application SSO, printing, and exporting, further improving the stability and consistency of the V2 entry.

Related documentation:

Plugins that no longer support V2 (deprecated but not yet removed)

Some plugins were deprecated in earlier releases. A number of them can still be used for now, but they will be removed entirely in NocoBase 3.

Plugin	Replacement	Notes
`@nocobase/plugin-audit-logs`	`@nocobase/plugin-audit-logger`	Deprecated since 1.0
`@nocobase/plugin-backup-restore`	`@nocobase/plugin-backups`	Deprecated since 1.0
`@nocobase/plugin-block-multi-step-form`	JS Block	Deprecated since 2.0
`@nocobase/plugin-charts`	`@nocobase/plugin-data-visualization`	Deprecated since 2.0
`@nocobase/plugin-collection-fdw`	Database synchronization	Deprecated since 2.2
`@nocobase/plugin-comments`	`@nocobase/plugin-block-comment`	Deprecated since 2.2
`@nocobase/plugin-custom-variables`	Event flow	Deprecated since 2.2
`@nocobase/plugin-data-visualization-echarts`	`@nocobase/plugin-data-visualization`	Deprecated since 2.0
`@nocobase/plugin-disable-pm-add`	None	Deprecated since 2.2
`@nocobase/plugin-field-component-mask`	RunJS	Deprecated since 2.0
`@nocobase/plugin-graph-collection-manager`	None	Deprecated since 2.2
`@nocobase/plugin-mobile-client`	`@nocobase/plugin-ui-layout`	Deprecated since 2.0
`@nocobase/plugin-mobile`	`@nocobase/plugin-ui-layout`	Deprecated since 2.0
`@nocobase/plugin-mock-collections`	AI-powered app building	Deprecated since 2.0
`@nocobase/plugin-multi-app-manager`	`@nocobase/plugin-app-supervisor`	Deprecated since 2.0
`@nocobase/plugin-multi-app-share-collection`	None	Deprecated since 1.0
`@nocobase/plugin-notifications`	`@nocobase/plugin-notification-manager`	Deprecated since 1.0
`@nocobase/plugin-snapshot-field`	None	Deprecated since 1.0

How to Build a Production-Ready IT Operations System with AI and NocoBase

NocoBase — Tue, 18 Aug 2026 07:50:34 +0000

Originally published at https://www.nocobase.com/en/blog/build-it-operations-system-with-ai-nocobase

Introduction

A recent post in Reddit's r/sysadmin described how one user built an ITSM system with AI over a weekend, covering both ticketing and asset management. In actual use, they found it more convenient than many products they had used before.

The comments also raised a different view: AI can quickly generate a Help Desk that looks mature, but that does not mean it already has the data structure, permissions, security, and extensibility required for production use.

In our previous article, Enterprise IT Asset Management System Guide: From Requirements to Implementation, we introduced a way to design an IT asset management system: let AI understand and break down business requirements, let NocoBase provide the data, permissions, and automation capabilities, and then have people review and adjust the system against real business rules. This combines AI's efficiency in understanding requirements and generating systems with the data, permissions, security, workflows, and other foundations that enterprise applications actually need.

This time, we will take that approach further and focus more on efficiency. In about two hours, we will use AI and NocoBase to build a more complete IT operations system from scratch. It will cover IT asset inventory, device assignment and return, service catalog and service requests, device approval and delivery, maintenance management, software license management, an AI IT assistant, an operations knowledge base, and dashboards. We will also improve permissions, workflows, and data synchronization so the system can be used in production and continue evolving with business needs.

🚀 Try applications built with NocoBase + AI online and see what AI-assisted application building looks like in practice: https://demo.nocobase.com/new

All screenshots in this article come from the NocoBase online Demo. The entire system, from design to implementation, was completed by an AI Coding Agent.

1. Start by Designing Around the Core Business Process

You are the IT administrator at a mid-sized company. The company has both office-based and remote employees and needs to manage laptops, monitors, phones, printers, servers, network devices, and other office peripherals.

Employees regularly request new laptops, monitors, software licenses, VPN or remote-access permissions, and they also report password, MFA, device, and other IT issues. These requirements can eventually involve asset management, service requests, approvals, maintenance, software licenses, a knowledge base, permissions, and dashboards.

But there is no need to put every scenario into the first version. We will start with one of the most common workflows:

Employee requests a laptop → Manager approves → IT selects a device and completes delivery

Let AI Understand the Requirements First

Once the business scenario and first-stage scope are clear, give the requirements to AI so it can understand the company's IT work and design the first version around laptop requests and delivery.

You can use the following prompt:

Please help me build an internal IT operations system in NocoBase.

The company has both office-based and remote employees and needs to manage laptops,
monitors, phones, printers, servers, network equipment, and other office peripherals.

Common IT requests include new laptop requests, monitor or peripheral requests,
software license requests, VPN / remote access, password or MFA issues,
and meeting-room equipment support.

Devices may go through registration, inventory, available for assignment, assigned to an employee,
in use, under maintenance, returned, reassigned, or retired. Employee requests may require
manager approval before IT completes delivery.

For the first stage, only build:
- Employees;
- Asset inventory;
- Device assignment and return records;
- Service catalog;
- Service requests;
- Laptop request and delivery workflow.

Maintenance, software licenses, operations manuals, reminders, and operational reporting
will be added later. Keep room for them, but do not create them yet.

Regular employees can submit and view their own requests; managers handle requests
that require approval; IT administrators maintain assets and complete device delivery.

Please return first:
1. The core data needed in the first stage;
2. How the data should be related;
3. How a laptop request should move through delivery;
4. Which pages and workflows you plan to create;
5. Which business rules still need confirmation.

Do not create anything yet. Wait for my confirmation before building.

Check AI's Understanding of the Business Rules

Before AI starts creating the system, confirm that it has correctly understood these five key rules:

One employee can be associated with multiple devices;
One device has a clear current user;
The asset's current status and historical assignment records are stored separately;
After a service request is approved, the actual device still needs to be delivered;
When the device is delivered, the asset information and assignment record are updated together.

The rule most likely to be missed is:

An approved service request does not mean the device has already been delivered.

For a new laptop request, approval only means the request has been accepted. IT still needs to select an actual device, assign it, update the asset status, and save the assignment record.

If AI treats “request approved” as the end of the workflow, ask it to add the IT processing and device delivery steps before creating the system.

For guidance on collaborating more effectively with an AI Agent, see: https://docs.nocobase.com/ai-builder/ai-portal/agent-workflow

2. Build and Check the Core Workflow

After confirming the business rules above, let AI create the first-stage system based on the agreed design. Once it is generated, start from the laptop request workflow and verify step by step that assets, assignment records, service requests, and device delivery work together correctly.

Check the Asset Inventory

When an employee is preparing to request a laptop, IT first needs to know what devices exist and which ones are currently available. Start by checking the asset inventory.

The asset inventory should at minimum record asset ID, serial number, device category, device name, model, location, current user, warranty expiration date, and current status.

You can verify asset status against the following flow:

In inventory → Available → Assigned → In use → Under maintenance / Retired

Here, “Assigned” means IT has selected and allocated the device, but the employee has not formally started using it yet. After delivery is completed, the status changes to “In use.”

The asset inventory mainly answers three questions: what is this device, who is using it and where, and can it still be assigned?

Check the following points carefully:

Asset IDs must be unique to prevent duplicate registration;
Devices under maintenance or retired must not appear in the available-device list;
Assigned or in-use devices must have a clear current user so the same device is not assigned twice.

Also verify the employee-device relationship. One employee may use multiple devices at the same time, such as a laptop, monitor, and phone, while one device should have only one current user at a given time. The employee detail page should directly show all devices assigned to that employee.

After the first-stage system is generated, enter three test devices: one “Available,” one “In use,” and one “Under maintenance.” Then filter for “Available” devices. Only the first device should appear, confirming that the status and filtering rules work.

Record Every Device Assignment and Return

The asset inventory records who currently uses a device, but past assignments and returns need to be stored separately. Therefore, the system also needs a dedicated device assignment and return record linked to both the device and the employee.

Each record should at minimum include the device, assigned employee, assignment time, return time, return condition, operator, and notes.

These two data types serve different purposes: the asset inventory stores the current state of the device, while assignment and return records preserve the history of each device movement.

Next, simulate a complete device lifecycle:

Assign to Employee A → Employee A returns it → Reassign to Employee B

Afterward, check that:

The current user on the asset detail page is Employee B;
Employee A's original assignment and return history is still preserved;
The device no longer appears in Employee A's current-device list, but does appear in Employee B's list.

3. Extend IT Operations Capabilities on Top of the Core Workflow

Once the laptop request and delivery workflow works end to end, the system already has the basic data for assets, service requests, approvals, and device movement. Next, give the follow-up requirements—device maintenance, software licenses, AI assistance, and operations manuals—to AI and let it extend the existing system. Afterward, test each new capability against a real business scenario.

NocoBase AI Builder lets AI design, build, and continue adjusting enterprise applications from natural-language requirements: https://docs.nocobase.com/ai-builder

A Device Breaks — Add Maintenance Management

Devices can fail after delivery. Once maintenance management is added, IT can create a maintenance record for the original device and save the problem description, date sent for repair, service provider, repair cost, maintenance status, and result.

When a device enters maintenance, the asset status must change as well:

In use → Under maintenance → In use / Available / Retired

If the repaired device goes back to the same employee, restore its status to “In use.” If it returns to inventory, set it to “Available.” If it can no longer be used, set it to “Retired.”

After creating a test maintenance record, first verify that the linked asset automatically changes to “Under maintenance” and disappears from the available-device list so it cannot be assigned again while being repaired.

When maintenance is complete, separately test the three outcomes—“return to original employee,” “return to inventory,” and “retire device”—and confirm that the asset status matches the maintenance result.

More Software Requests — Manage Software Licenses

As the number and variety of software products grow, IT needs to know how many seats have been purchased, how many are already in use, when each license renews, and the annual cost. The system therefore also needs software license management.

Each software record should store the vendor, total seats, used seats, renewal date, annual cost, and current status. When handling a software request, first check whether seats remain available, then update the used-seat count after activation is completed.

These rules can also be handed to AI and automated through NocoBase Workflow. For example, notify the owner and create a renewal task when a license is about to expire; if used seats exceed total seats, trigger an overage alert and let AI assist in deciding whether to expand capacity or reclaim accounts.

Employees Cannot Explain the Problem Clearly — Let AI Structure the Request

Employees do not always know which service to choose, and they may not describe an issue in the format IT prefers. For example:

After resetting my password, I cannot connect to VPN and need access before today's customer call.

Employees can describe the issue in natural language and let AI turn it into a request title, service type, priority, and problem description. The employee can review or edit the result before formally submitting the request.

Use the example above as a test and confirm that the service type, priority, and description produced by AI can still be edited and submitted normally. This way, employees can describe issues in their own words while IT still receives a structured request that can be categorized and processed.

Repeated Problems — Build an Operations Knowledge Base

Issues involving VPN, MFA, new-laptop setup, and printer failures occur repeatedly. Verified solutions can be organized into operations manuals that record purpose, prerequisites, procedures, validation steps, and exception handling.

As the knowledge base grows, AI can also help IT find the relevant procedure based on the content of a request.

4. Validate the System with a Complete Workflow

Check Whether Everything Stays in Sync

By this point, the system contains asset, service request, assignment, maintenance, and software-license data. The operations dashboard can summarize available devices, devices in use, pending requests, devices under maintenance, license utilization, licenses approaching renewal, and software costs.

The dashboard data comes directly from the asset, service request, maintenance, and license records built earlier.

Change a device status, complete a service request, or add a maintenance record, then confirm that the related dashboard metrics update accordingly. Clicking a metric should also allow users to view the matching details.

Validate the Full Process from Request to Return

Finally, return to the employee used in the earlier tests and run through the whole process again:

Request laptop → AI-assisted form filling → Manager approval → IT selects device → Create assignment record → Employee starts using device → Maintenance / Return → Asset status updates → Operations dashboard updates

After completing the process, verify these points:

Are the current user and asset status accurate?
Are assignment, return, and maintenance histories fully preserved?
Can the service request be traced back to the actual delivered device?
Do employee, manager, and IT viewing and operation permissions match the design?
Do status updates, reminders, and other automations execute correctly?
Can AI-structured requests be edited and submitted normally?
Do the related dashboard metrics update with business-state changes?

Once these data and workflow behaviors match the business rules defined earlier, the system can first be released to a small group of users and then adjusted based on real feedback.

Conclusion

If you already have a clear business scenario, start with the workflow your team knows best. Describe the real requirements, team roles, and handling process directly to AI, then let NocoBase provide the data, permissions, and other enterprise application foundations. Build, check, and adjust as you go. Get the core business process working first, then expand the system gradually based on actual use.

If this article was useful, feel free to share it with others who are exploring how to use AI to build internal enterprise systems.

Related reading:

Weekly Updates: Added Default Space Settings with Automatic User Assignment

NocoBase — Mon, 17 Aug 2026 09:27:16 +0000

Summarize the weekly product update logs, and the latest releases can be checked on our blog.

NocoBase is currently updated across three branches: main, next, and develop.

main: The most stable version to date, recommended for installation.
next: Beta version, contains upcoming new features and has been preliminarily tested. There might be some known or unknown issues. It is mainly used to collect feedback from test users and further optimize features. Ideal for test users who want to experience new features early and provide feedback.
develop: Alpha version, contains the latest feature code, may be incomplete or unstable, and is mainly used for internal development and rapid iteration. Suited for technical users interested in cutting-edge product capabilities, but not recommended for production use.

main

v2.1.41

Release date: 2026-08-16

🚀 Improvements

[lock-manager] Added renewable local lock leases and ensured try-acquired locks are released safely across reuse and errors (#10368) by jiannx
[Redis lock adapter] Added renewable Redis lock leases and made reusable lock handles release safely during contention and errors by jiannx

🐛 Bug Fixes

[File manager] Fix the extra submit step when selecting an existing file in a single-value field (#10372) by zhangzhonghe
[Collection field: Markdown(Vditor)] Fix Markdown HTML previews in v2 details blocks under dark themes. (#10370) by katherinehhh
[Collection field: Encryption] Fixed bulk import failing with model.changed is not a function when the collection contains an encryption field by cgyrock
[Workflow: Webhook] Fixed a 400 error when manually executing a webhook workflow without request headers by mytharcher

v2.1.40

Release date: 2026-08-14

🚀 Improvements

[Block: Tree] Tree filter blocks now support configurable default sorting. (#10339) by jiannx

🐛 Bug Fixes

[client-v2]
- Fix filter forms refreshing automatically in UI edit mode (#10356) by zhangzhonghe
- Use Cascader by default for tree-structured relation fields in v2 filter forms (#10357) by zhangzhonghe
- Fix mobile single-select relation fields not clearing when the selected record is tapped again (#10346) by zhangzhonghe
- Fix the issue where China region fields cannot be added directly to filter forms (#10333) by zhangzhonghe
- Fix JS items incorrectly appearing in form field linkage rule actions (#10363) by gchust
[Workflow: JSON calculation] Fixed JSON Query jobs losing structured parser errors and displaying [object Object] (#10344) by mytharcher
[Action: Export records]
- Fixed a page crash when sorting an edited relation field in Export V2. (#10335) by katherinehhh
- Fix table export errors after filtering by multiple relation fields (#10342) by zhangzhonghe
[Block: Kanban] Fixed configured content disappearing after reopening a kanban card's detail drawer (#10334) by jiannx
[File manager] Fixed video previews not updating when switching between files (#10345) by mytharcher
[Action: Import records Pro]
- Fixed asynchronously imported records not being associated with the current space by jiannx
- Clarified import results by showing the number of newly created records separately from updated records by mytharcher
[Workflow: Approval]
- Fix inconsistent subtable column widths in approval details by zhangzhonghe
- Add data scope filtering to Client V2 related approval blocks by zhangzhonghe

v2.1.39

Release date: 2026-08-11

🐛 Bug Fixes

[client-v2] Fixed an issue where ctx.form.submit could not correctly submit form data. (#10063) by gchust
[database] Fixed prefix indexes on camel-case fields when underscored database naming is enabled (#10329) by 2013xile
[Action: Duplicate record] Improve direct duplication failure feedback in v2 without duplicate API error messages. (#10327) by katherinehhh
[Record history] Improved record history write performance for collections with large snapshot tables by 2013xile
[Workflow: Approval] Fix the issue where removed one-to-many relation records cannot be selected again in approval forms by zhangzhonghe

v2.1.38

Release date: 2026-08-10

🚀 Improvements

[undefined] Clarified the default JavaScript Worker concurrency behavior and when to configure a concurrency limit (#10317) by mytharcher Reference: JavaScript node
[Workflow: JavaScript] JavaScript workflow nodes now queue asynchronous Worker execution and limit per-process Worker concurrency to reduce resource spikes. (#10280) by mytharcher

🐛 Bug Fixes

[Flow engine]
- Fixed popup record variables and association blocks for custom non-Sequelize data sources (#10272) by gchust
- Fixed incorrect variable resolution for form field values (#10319) by gchust
[File manager] Fixed file downloads failing after previewing cross-origin images when browser cache entries lack CORS response headers (#10313) by mytharcher
Reference: File Preview / Aliyun OSS

v2.2.0-beta.17

Release date: 2026-08-10

🎉 New Features

[client-v2] Add Date variables and optional formatted output to V2 field-value editors. (#10289) by katherinehhh
[AI employees]
- AI employees can now be assigned skills from the employee settings page. Skills are built from plugins. (#10237) by cgyrock
- Added UI navigation for supported LLM service CLI commands, including provider preselection when creating a service. (#10210) by cgyrock
[Multi-space] Added default-space configuration so newly created users automatically join the selected default space. by jiannx
[AI: Knowledge base] Added UI navigation for creating and editing vector databases from CLI commands, with provider preselection for new databases. by cgyrock

🚀 Improvements

[undefined] Clarified the default JavaScript Worker concurrency behavior and when to configure a concurrency limit (#10317) by mytharcher Reference: JavaScript node
[Workflow: JavaScript] JavaScript workflow nodes now queue asynchronous Worker execution and limit per-process Worker concurrency to reduce resource spikes. (#10280) by mytharcher
[Action: Export records] Add field search to v2 import and export action settings. (#10261) by katherinehhh
[Action: Batch update] Support configurable after-success behavior for v2 Update record and Bulk update actions. (#10278) by katherinehhh
[Workflow: HTTP request node] Fix unstable test cases (#10246) by mytharcher
[Workflow] Workflow create and update nodes now support combining text with variables when assigning string and text fields (#10238) by mytharcher
[Action: Export records Pro] Add field search to v2 Import Pro and Export Pro action settings. by katherinehhh
[AI: Knowledge base] Aligned the vector database list styling with other settings tables by cgyrock

🐛 Bug Fixes

[client-v2]
- Fixed Kanban column quick create records not inheriting the selected group value (#10321) by jiannx
- Fix missing and incorrectly resolved Current popup parent record variables in v2 popup-subtable add-new and edit dialogs. (#10292) by katherinehhh
- Fixed parent item variables resolving to the wrong level when assigning association field values in sub-tables. (#10249) by gchust
- Fix the cancel button language in mobile selection lists (#10297) by zhangzhonghe
- Fix missing Current record variables in v2 JS column event-flow conditions. (#10279) by katherinehhh
[database]
- Fixed migration packages omitting many-to-many through-table data after an application restart (#10306) by cgyrock
- Fixed MSSQL queries failing when filtering to-many relations with pagination and sorting by a root collection field (#10224) by cgyrock
[data-source-manager]
- Fixed formula fields being converted to number fields after synchronizing fields from the database (#10303) by 2013xile
- Fixed external data source table synchronization leaving removed collections registered in the database manager (#10209) by cgyrock
[auth] Fixed occasional Invalid CSRF token errors on API requests in cross-origin deployments (#10245) by mytharcher
[Block: Tree] Fixed Tree block searches showing placeholder nodes when no business-field records matched (#10323) by jiannx
[Block: Gantt] Fixed custom record colors not being applied to short Gantt task bars (#10322) by jiannx
[Flow engine]
- Fixed incorrect variable resolution for form field values (#10319) by gchust
- Fixed popup record variables and association blocks for custom non-Sequelize data sources (#10272) by gchust
[Backup manager]
- Prevent repeated V2 backup restore submissions while a restore request is in progress. (#10262) by katherinehhh
- Fix duplicate backups from async exports (#10300) by gchust
[Data source manager] Prevented clearing a field interface directly from the Configure fields table. (#10288) by hongboji
[File manager]
- Fixed file downloads failing after previewing cross-origin images when browser cache entries lack CORS response headers (#10313) by mytharcher Reference: File Preview / Aliyun OSS
- Fixed shared attachments such as the system logo not loading for authenticated member users (#10268) by mytharcher
[Collection field: Sequence] Fixed duplicate automatic sequence values after migration when multiple records share the latest creation time (#10239) by mytharcher
[AI employees]
- Fixed the untranslated Settings tab in the AI plugin's client-v2 settings pages (#10234) by cgyrock
- AI employee actions now support linkage rules for conditional visibility in v2 forms. (#10298) by jiannx
[UI templates] Fix the issue where table blocks load data after returning to a page with empty filters (#9890) by zhangzhonghe
[Localization] Fixed a crash when opening Localization settings with the Lina AI assistant entry. (#10293) by cgyrock
[Workflow] Fixed an issue where manually executing a workflow with autoRevision=0 could still create a new revision. (#10243) by mytharcher
[Workflow: JavaScript] Fixed JavaScript workflow Workers not exiting after scripts returned or asynchronous workflows timed out (#10241) by mytharcher
[Data source: External NocoBase] Fixed external NocoBase files and attachment fields failing to load in AI workflows by 2013xile
[Data source: External SQL Server] N/A — regression test coverage only by cgyrock
[Data source: External MySQL] Fixed previously selected external database tables disappearing after adding new tables. by cgyrock
[AI: Knowledge base] Fixed PGVector knowledge base searches consuming unused PostgreSQL pool connections and creating duplicate pools for different vector tables. by cgyrock
[Migration manager] Fixed many-to-many through-table migration data after application restarts and classified migration rules as system data by cgyrock
[Template print]
- Fixed unwanted spacing between Latin and East Asian text in PDF files generated from DOCX templates. by jiannx
[Workflow: Approval]
- Fix missing external data source fields in approval views by zhangzhonghe
- Fix missing field values in approval sub-tables by zhangzhonghe
- Fix approval comment default values when using RunJS by zhangzhonghe
- Fix the issue where removed one-to-many relation records cannot be selected again in approval forms by zhangzhonghe
- Allow approval comments to use configurable default values by zhangzhonghe
[App supervisor] Prevented app creation with database identifiers that do not start with an English letter or contain unsupported characters. by hongboji
[DingTalk] Fixed DingTalk notification channels losing the selected authenticator when saved from the v2 channel form by jiannx
[Auth: LDAP] Fixed LDAP login when a user DN mixes UTF-8 escapes with escaped syntax characters such as commas. by hongboji

develop

v3.0.0-alpha.9

Release date: 2026-08-11

🚀 Improvements

[cli] nb api resource create now accepts a JSON array for --values to create multiple records in a single request. (#10325) by Molunerfinn Reference: nb api resource create

🐛 Bug Fixes

[client-v2]
- Fix incorrect editing and display of large decimal values in V2 fields. (#10330) by katherinehhh
- Fixed an issue where ctx.form.submit could not correctly submit form data. (#10063) by gchust
- Automatically redirect to an accessible Settings tab when the current tab is unavailable (#10332) by zhangzhonghe
- Fixed Kanban column quick create records not inheriting the selected group value (#10321) by jiannx
- Redirect users without Settings access to the first available page (#10331) by zhangzhonghe
[database] Fixed prefix indexes on camel-case fields when underscored database naming is enabled (#10329) by 2013xile
[Block: Gantt] Fixed custom record colors not being applied to short Gantt task bars (#10322) by jiannx
[Block: Tree] Fixed Tree block searches showing placeholder nodes when no business-field records matched (#10323) by jiannx
[Action: Duplicate record] Improve direct duplication failure feedback in v2 without duplicate API error messages. (#10327) by katherinehhh
[Record history] Improved record history write performance for collections with large snapshot tables by 2013xile
[Workflow: Approval]
- Fix missing return scope options in Client V2 approval forms by zhangzhonghe
- Fix the issue where removed one-to-many relation records cannot be selected again in approval forms by zhangzhonghe
[DingTalk] Fixed DingTalk notification channels losing the selected authenticator when saved from the v2 channel form by jiannx

v3.0.0-alpha.8

Release date: 2026-08-10

🎉 New Features

[client-v2] Add Date variables and optional formatted output to V2 field-value editors. (#10289) by katherinehhh
[Portal manager] Show an access denied message when users do not have permission to access a Portal (#10275) by zhangzhonghe
[Connect coding agent] Copy a ready-to-paste prompt from an AI Portal card to connect a coding agent to the instance by Albert-mah

🚀 Improvements

[undefined]
- Clarified the default JavaScript Worker concurrency behavior and when to configure a concurrency limit (#10317) by mytharcher Reference: JavaScript node
- Add a model selection guide with evaluation dimensions and a color-coded model comparison table. (#10295) by Charls-Wu
[cli] fix: incorrect author identity in nb portal push commits (#10315) by gchust
[Portal manager]
- Improve Portal access check efficiency (#10302) by zhangzhonghe
- Show a concise placeholder when Portal access cannot be configured directly (#10301) by zhangzhonghe
[Workflow: JavaScript] JavaScript workflow nodes now queue asynchronous Worker execution and limit per-process Worker concurrency to reduce resource spikes. (#10280) by mytharcher
[Verification] Add a refresh button to the Verification settings list (#10299) by zhangzhonghe

🐛 Bug Fixes

[client-v2]
- Show loading feedback when enabling or disabling plugins (#10310) by zhangzhonghe
- Hide the retry button while the app is running a command (#10290) by zhangzhonghe
- Fix the cancel button language in mobile selection lists (#10297) by zhangzhonghe
- Fixed parent item variables resolving to the wrong level when assigning association field values in sub-tables. (#10249) by gchust
- Fix missing and incorrectly resolved Current popup parent record variables in v2 popup-subtable add-new and edit dialogs. (#10292) by katherinehhh
[database] Fixed migration packages omitting many-to-many through-table data after an application restart (#10306) by cgyrock
[data-source-manager] Fixed formula fields being converted to number fields after synchronizing fields from the database (#10303) by 2013xile
[undefined] fix the issue unable to create portal from local (#10304) by gchust
[Flow engine]
- Fixed incorrect variable resolution for form field values (#10319) by gchust
- Fixed popup record variables and association blocks for custom non-Sequelize data sources (#10272) by gchust
[AI employees]
- Fixed the AI employee chat entry briefly appearing while a page is loading or redirecting. (#10309) by cgyrock
- AI employee actions now support linkage rules for conditional visibility in v2 forms. (#10298) by jiannx
[File manager] Fixed file downloads failing after previewing cross-origin images when browser cache entries lack CORS response headers (#10313) by mytharcher
Reference: File Preview / Aliyun OSS
[Action: Batch edit] Corrected built-in plugin documentation to show that these plugins are enabled by default (#10314) by hongboji
[Portal manager]
- Fix compatibility issues when older AI Portals check access permissions (#10307) by zhangzhonghe
- Fix incorrect Portal URLs when the name is x or v (#10305) by zhangzhonghe
- Keep Portal titles unchanged in role permissions (#10291) by zhangzhonghe
[Backup manager] Fix duplicate backups from async exports (#10300) by gchust
[Workflow] Disable workflow execution mode selection until a trigger type is selected. (#10296) by Molunerfinn
[Data source: External NocoBase] Fixed external NocoBase files and attachment fields failing to load in AI workflows by 2013xile
[Migration manager] Fixed many-to-many through-table migration data after application restarts and classified migration rules as system data by cgyrock
[Workflow: Approval]
- Fix approval application cards not showing submitted content immediately by zhangzhonghe
- Align the V2 approval message template page with the V1 layout and actions by zhangzhonghe

NocoBase vs Baserow: Flexible Databases vs Enterprise Systems

NocoBase — Wed, 12 Aug 2026 11:47:35 +0000

Originally published at https://www.nocobase.com/en/blog/nocobase-vs-baserow

Introduction

If you are looking for an open-source, self-hosted platform to manage data, build internal applications, or automate business processes, NocoBase and Baserow are likely to appear on the same shortlist.

Both products provide visual data management and application-building capabilities, and both let teams extend the platform around their own needs. But judging only by these shared labels can make them look more similar than they really are.

In practice, Baserow and NocoBase represent two different product directions.

Baserow represents the spreadsheet-style no-code approach. Its first priority is helping teams organize, manage, and collaborate on structured data in a more flexible and intuitive way.

NocoBase starts from business-system development. It combines data models, pages, role-based permissions, workflows, and automation to help teams build enterprise applications that can run for the long term and continue evolving.

As AI Agents move into real business scenarios, these capabilities are also becoming infrastructure for AI to access enterprise data, invoke business processes, and perform tasks within defined permission boundaries.

This article therefore looks at the products from the perspective of actual usage and answers a practical question: when is a spreadsheet-style no-code platform such as Baserow the better fit, and when should you choose NocoBase instead?

Baserow: A Spreadsheet-Style No-Code Platform

Baserow was started by Bram Wiepjes as a personal project in 2019. Its first version was released in 2020, when the team also began to take shape. Today, its GitHub repository has around 5.3k Stars.

Baserow first gained attention as an open-source Airtable alternative. Its most recognizable experience still starts from a familiar model: create and manage structured data as easily as working in a spreadsheet.

Products in this category are often described as multidimensional spreadsheets, online databases, or spreadsheet-database tools. Besides Baserow, Airtable, NocoDB, Grist, SeaTable, and Feishu Bitable follow a similar approach.

NocoBase: Business-System Infrastructure for the AI Era

The NocoBase GitHub repository has now surpassed 23k Stars. NocoBase is an open-source AI + no-code platform for rapidly building business systems, but its role goes beyond visual application building. It provides infrastructure for people and AI Agents to build, run, and continuously extend business systems together.

In NocoBase, the data model is the foundation, but the final product is not simply a set of tables for users to maintain directly. It is a complete business system that can include:

Business pages designed for different roles
Data scopes and actions available to different users
Forms, detail pages, and business operations
Approvals, state transitions, and automated workflows
Operation records and audit logs
AI Employees that participate in business processing inside the system
APIs, MCP, CLI, and Skills for external AI Agents
Plugins and integrations that continue to grow with enterprise requirements

These capabilities support not only traditional business applications but also the context and execution boundaries AI needs in enterprise environments. AI Coding Agents can participate in data modeling, page configuration, permission setup, workflow orchestration, and plugin development. AI Employees inside the system and external Agents can query data, trigger workflows, and execute tasks within predefined permissions, while their operations remain subject to access control and auditing.

Ordinary users typically work through configured pages, forms, and actions instead of interacting directly with underlying tables. System builders can continue changing data models, pages, permissions, and workflows, while AI Agents can participate in building and iteration on top of the same architecture.

Core Difference 1: Creating a Database or Building a Business System

Both Baserow and NocoBase are based on data models, and both let users visually create fields, relationships, and application pages.

But they start from different places in actual use.

Baserow: start by creating a database and manage data collaboratively in a more flexible way.
NocoBase: start by identifying business objects, roles, and processes, then combine them into a complete business system.

Both products can create tables, relationships, and application pages, but their most natural end results are different.

With Baserow, a team will typically end up with a table-centered collaborative workspace:

Clear data structures
Direct editing
Flexible views
Easy bulk maintenance
Fast adaptation to changing needs

With NocoBase, a team will more naturally end up with an application system centered on business roles and processes:

Users work through dedicated business pages
Different roles have different permissions
Data changes are governed by operation rules
State changes can trigger approvals and workflows
New modules can be added as the business grows

In Baserow, the database itself is often the team's primary workspace.

In NocoBase, the database is more often the underlying foundation of a business system, while ordinary users interact with data through pages, forms, buttons, and workflows.

Core Difference 2: Editing Data or Completing Business Operations

Baserow and NocoBase both support tables, forms, and application pages, but ordinary users interact with data differently.

Baserow: users typically enter a table view to view, filter, and bulk-edit records. Grid View remains its most representative data-management interface.
NocoBase: users typically complete work through business pages, forms, and action buttons. Buttons can also trigger workflows that control subsequent data processing and business steps.

For example, consider updating a customer record.

In Baserow, users can click a cell and change the value directly. This is efficient for quick maintenance and bulk editing.

In NocoBase, once the data model is defined, the frontend can be organized much more freely. Teams can build pages around different roles and business scenarios, and AI can also help configure those pages.

For the same customer-status change, a team could use an action button on the customer detail page, or organize customers in a Kanban board and move cards between statuses. Each record can still open into a detail page for full information and editing.

This means the same underlying data and business rules can be presented through different pages and interactions depending on how the work is actually performed.

The two approaches fit different situations:

Spreadsheet-style tools emphasize directness, speed, and flexibility.
Business systems emphasize explicit operation entry points, validation, and process control.

When users are changing a content plan or a task note, direct editing is often more efficient.

But when they are changing an order amount, inventory quantity, contract status, or approval result, enterprises often need users to complete an explicit business operation rather than directly change underlying data.

For collaborative data tools, saving one click can improve efficiency. For formal business systems, adding one confirmation step may reduce the cost of mistakes.

Core Difference 3: Small-Team Collaboration or Enterprise Multi-Role Use

Baserow and NocoBase both support multi-user collaboration and permission management, but their typical collaboration models differ.

Baserow: better suited to teams collaborating around the same set of data through different views, filters, and record editing.

NocoBase: better suited to multiple departments and roles working in the same system, with different pages, data scopes, and operation permissions for each type of user.

For example, in a sales-management application:

Sales representatives can only view and edit customers assigned to them.
Sales managers can view the entire team's data and approve discounts.
Finance users can only access contracts, invoicing, and payment information.
Management can view aggregated data without directly editing business records.

In NocoBase, data permissions can also be controlled down to the row level for finer-grained access management.

Building the Same Business Scenario with Baserow and NocoBase

Consider the same CRM scenario in both products.

Assume the system needs to manage customers, contacts, sales opportunities, and follow-up records while supporting sales-stage management, owner assignment, and sales reporting.

Both products can build this CRM, but the resulting usage model will differ.

Baserow more naturally starts from data tables and views, then gradually adds application pages, automation, and permissions.

NocoBase starts from the data model, then builds pages, permissions, workflows, and AI capabilities around the same underlying data, eventually forming a business system designed for different roles.

AI makes the comparison even more interesting. Baserow has already integrated AI deeply into database and application building. Its AI assistant Kuma can create and modify databases, formulas, views, and application pages through natural language.

NocoBase also supports AI-assisted system building, but AI reaches further across the complete business-system structure. AI Agents can participate in data modeling, page building, permission configuration, workflow orchestration, plugin management, and system deployment. After the system is built, AI Employees can work directly inside CRM pages using current customer data, sales opportunities, and user permissions.

Both products can therefore use AI to build applications and process data. The clearer difference is that NocoBase can directly connect Coding Agents and treat AI as a participant in the business system: AI not only helps users build the CRM, but can continue participating in daily business execution after the CRM is in use.

Enterprise Capability Comparison

As applications spread across more teams, factors beyond data management and page building—permissions, security, deployment, and long-term operations—also become part of the selection process.

Baserow has expanded from an open-source database product into application building, automation, and AI, while adding increasingly complete enterprise capabilities.

NocoBase's enterprise capabilities are organized around complete business systems. Data models, pages, workflows, permissions, security, multi-environment management, cluster deployment, and AI Agents all operate within the same system architecture.

Conclusion: How to Choose Between Baserow and NocoBase

Baserow and NocoBase are both open-source and self-hostable, and both now offer application building, automation, and AI capabilities. But the problems they are best suited to solve are still different.

If your core requirement is to organize data quickly, replace spreadsheets, and let a team collaborate around that data, Baserow is simpler. It keeps a spreadsheet-like experience while allowing you to add views, applications, automation, and AI.

If your requirements already involve multiple business objects, different roles, complex permissions, approvals, and workflows—or if you want AI Agents to operate inside an enterprise system under established permissions and business rules—NocoBase is better suited to building that kind of long-running business system.

In simple terms:

Baserow is a good fit when you want to start from straightforward data management and collaboration.
NocoBase is a better fit when you want to start from a business system and provide AI Agents with an executable enterprise environment.

We are also seeing more users who originally chose spreadsheets or multidimensional-table products for business management move to NocoBase as their needs grow. As business complexity increases, table-centered management often begins to run into limitations around role permissions, workflows, data relationships, and system extensibility. At that point, the requirement starts shifting from “a better spreadsheet” to a real business system.

Related reading:

How to Build a Production-Ready CRM with AI and NocoBase

NocoBase — Tue, 11 Aug 2026 12:29:28 +0000

Originally published at https://www.nocobase.com/en/blog/build-production-ready-crm-with-ai-and-nocobase

TL;DR

AI can build a CRM that is genuinely ready for production. With NocoBase providing the enterprise application foundations—data models, role-based permissions, security auditing, workflows, and more—AI can build a CRM from business requirements and then continue adding automation and AI Employees so the team can use it reliably in real operations over the long term.

Background

A recent Reddit discussion raised an interesting question: now that AI development tools are so capable, do teams still need to buy Salesforce or HubSpot, or can they simply Vibe Code an internal CRM?

One user who had actually built a CRM this way noted that AI can quickly create basic features such as customer management and dashboards. But once the system needs to support a real team over time, issues such as permissions, data isolation, security, and ongoing maintenance still have to be solved.

He made the point that you can absolutely Vibe Code a CRM, but you cannot simply Vibe Code an enterprise CRM that remains reliable once it is exposed to real users, real data, and real business processes. Coding is the easy part; everything behind it is harder.

AI can build the basic framework of a CRM very quickly, but there is still a gap between that and a system that is truly ready for enterprise use.

Today, however, there is another approach. Instead of asking AI to recreate enterprise application fundamentals from scratch—permissions, security, auditing, data models, and so on—we can give it an application foundation that already provides those capabilities, then let AI focus on building and iterating the actual business system.

In this guide, we will show how to combine AI with NocoBase's enterprise application capabilities to build a production-ready CRM from natural-language requirements in about an hour.

🚀 You can also try applications built with NocoBase + AI online and see what AI-assisted application building looks like in practice: https://demo.nocobase.com/new

All screenshots in this article come from the NocoBase online demo. The entire system, from design to implementation, was completed by an AI Coding Agent.

1. Start with Real Business Requirements

This article uses a small B2B office furniture company as the example.

The company mainly supplies office furniture and commercial-space solutions to businesses, design firms, architecture studios, hotels, coworking spaces, and educational institutions. A small sales team handles customer acquisition, project follow-up, quotations, and deal closing.

A typical project might begin when a design firm requests an office renovation. A salesperson needs to create the company account and contacts, open an opportunity, continuously record meetings and email communication, select products such as conference tables, office chairs, workstations, and acoustic partitions based on the project requirements, generate a quotation, and then move the deal through several rounds of communication and negotiation until it closes.

The main sales process is:

Lead → Company account → Opportunity → Quotation → Ongoing follow-up → Closed deal

For this sales team, the CRM needs to manage company accounts and contacts, leads, opportunities, products and quotations, communication records, and follow-up tasks in one place. It should also support sales dashboards, team permissions, business automation, and AI-assisted work.

Describe the Business in Natural Language

Describe the company's business, customer types, team roles, and sales process directly to AI. The key is to explain what the company sells, which customers it serves, how salespeople develop accounts and move projects forward, how a project progresses from initial contact to closing, and what data and daily work the CRM needs to manage. You can also include team roles, sales rules that should run automatically, and the work you want AI Employees to handle so AI first understands the team and business the CRM is supposed to support.

NocoBase can connect to different large language models for application building, including GPT, Opus, Qwen, and DeepSeek. Different models may vary in how they understand requirements, how quickly they generate results, and how the final application is presented, so you can choose based on actual results and your own preferences.

Which model should you choose? NocoBase model comparison: https://docs.nocobase.com/ai-builder/ai-portal/model-selection/

You can give the business requirements to AI like this:

I run a small B2B office furniture company. We mainly provide office furniture and commercial-space solutions to businesses, design firms, architecture studios, hotels, and coworking spaces.

Please use NocoBase to help me build a CRM that manages the full sales process from lead to closed deal, including company accounts and contacts, opportunities, products and quotations, customer communications, follow-up activities, and sales dashboards.

Our opportunities usually move through these stages:
Initial contact → Quotation → Business negotiation → Closed deal.

The team includes sales representatives, sales managers, and read-only users. We will also need corresponding data permissions, post-deal automation, reminders for opportunities that have not been followed up for a long time, and AI Employees that can organize customer emails and meeting notes.

First, summarize the CRM's main modules, data relationships, sales process, and user roles based on these requirements. After I confirm the design, begin building it in NocoBase.

Permissions, automation, and AI Employees do not all need to be configured in one pass. First confirm that AI correctly understands the core business objects—accounts, contacts, opportunities, products, and quotations—then continue improving the existing CRM.

Confirm AI's Understanding of the Business

Before building, ask AI to produce a concise CRM structure based on the requirements. Confirm that it includes accounts and contacts, leads, opportunities, products and quotations, communications and follow-ups, sales dashboards, user roles, and business rules.

Also verify that the main data relationships and sales stages are correct. For example, one company account can have multiple contacts, opportunities, and communication records, while each quotation should be linked to the customer, the opportunity, and the specific products being quoted.

Use the following sales stages consistently:

Initial contact → Quotation → Business negotiation → Closed deal

Once AI clearly understands the business, let it start building the CRM from this design.

2. Let AI Build the CRM, Then Check the Core Business Logic

After the CRM is generated, first verify the basic business relationships instead of immediately adding permissions, automation, or more pages. Focus on whether accounts, contacts, opportunities, products, quotations, and communication records are correctly connected and whether the full process matches how sales actually works.

Check Accounts and Contacts

Each company account should centrally connect company information, contacts, account owner, related opportunities, communication records, and follow-up items.

When a salesperson opens an account detail page, they should be able to immediately see who the contacts are, which projects are currently active, what the latest communication was, and what needs to happen next.

Also check that one customer can be linked to multiple contacts, opportunities, and communication records instead of having this information generated as unrelated standalone pages.

Check Opportunity Progression

All active projects should be managed through opportunities and progress through these stages:

Initial contact → Quotation → Business negotiation → Closed deal

Each opportunity should record the associated customer, opportunity owner, expected value, expected close date, and current stage, and users should be able to view and update opportunities from a pipeline board.

Check Products and Quotations

The product catalog should centrally maintain product code, product name, category, sales price, and availability status.

A quotation should be linked to the company account, the specific opportunity, quoted products, quotation amount, validity period, and current status, so salespeople can open quotations from an opportunity and also view related quotations from the customer detail page.

If the relationships between customers, opportunities, products, and quotations do not match the real business, describe the specific issue directly to AI and have it adjust the existing CRM. Once the core business is correct, continue adding the capabilities needed for team use.

For guidance on collaborating more effectively with an AI Agent during application building, see: https://docs.nocobase.com/ai-builder/ai-portal/agent-workflow

3. Turn the Basic CRM into a System the Team Can Actually Use

Once the core workflows around customers, opportunities, and quotations work correctly, continue giving AI the team's roles and sales rules. AI can then add permissions and automation to the existing CRM so it supports collaboration and daily operations.

Configure Permissions Around Team Responsibilities

First tell AI which roles exist and what each role is allowed to view and do:

Sales representatives can only view and manage the customers, opportunities, and follow-up items assigned to them; sales managers can view the entire team's data, reassign owners, and review sales progress; read-only users can view relevant information but cannot create, edit, or delete business data.

AI can create these roles directly in the existing CRM and configure data scopes and operation permissions. After configuration, enter the system as each role and confirm that the visible data and available actions match the actual division of responsibilities. If the permission scope is inaccurate, tell AI which role, data, or operation needs adjustment, or modify the permissions directly in the interface.

Turn Repetitive Sales Rules into Workflows

Repeated business actions in the sales process can also be expressed as clear trigger conditions and expected outcomes, then handed to AI to configure as automation in the existing CRM.

For example, when an opportunity reaches the Closed stage, the system can automatically update the customer status, create follow-up tasks, and assign them to the appropriate owner. If an opportunity has no new communication record for seven consecutive days, the system can automatically remind the salesperson to follow up.

After the rules are configured, test real scenarios by changing opportunity stages or simulating a long period without follow-up. Confirm that the automation triggers as expected and correctly updates data, creates tasks, or sends reminders.

Configure AI Employees for Sales Work

You can also configure AI Employees for sales scenarios and let them participate directly in everyday work.

For example, after a customer meeting, a salesperson can give the meeting notes or customer email to an AI Employee. The AI Employee can organize the communication, extract key points and next actions, generate a customer activity record, and provide follow-up suggestions.

The same approach can be used to organize customer background information, summarize historical communications, and prepare follow-up content, allowing AI Employees to continuously take over repetitive information-processing work.

Keep Adjusting the CRM Based on Real Use

Once the CRM is in actual use, a sales manager may want the dashboard to add current pipeline value, expected near-term closing value, closed revenue, customers requiring follow-up, and sales target completion.

Sales representatives may also want the opportunity board to add customer filters, owner filters, expected close dates, and more complete opportunity information so they can quickly identify the projects that need attention first.

Continue giving this feedback to AI so it can adjust page layouts, information density, status presentation, card content, key data placement, and the overall visual style. All changes can be made directly on the existing CRM without rebuilding the system.

NocoBase AI Builder lets AI design, build, and continue adjusting enterprise applications from natural-language requirements: https://docs.nocobase.com/ai-builder

4. Run Through a Complete Real Sales Process

Once the system is basically complete, run through the full process in the same order a salesperson would use it:

Create company account → Add contact → Create opportunity → Move opportunity through stages → Record customer meeting → Create follow-up task → Select products and generate quotation → Enter business negotiation → Close opportunity → Automatically run post-deal workflows → Update sales dashboard

Check four areas throughout the process:

Is the business data connected correctly? Are customers, contacts, opportunities, quotations, communication records, and follow-up tasks linked correctly?

Are team permissions correct? Do sales representatives, sales managers, and read-only users see the right data and have the right actions?

Does automation run correctly? Do closed opportunities, long periods without follow-up, and other configured scenarios trigger correctly and update data or create tasks as expected?

Are AI Employees genuinely useful? Can meeting notes and customer emails be organized correctly, and can key information, next actions, and follow-up suggestions become part of the real sales workflow?

After completing this end-to-end sales process, you can confirm that the CRM is capable of supporting a small B2B sales team across customer management, opportunity progression, product quotations, ongoing follow-up, team collaboration, and daily sales operations.

Conclusion

Vibe Coding has significantly lowered the barrier to taking an application from zero to one. A new division of responsibilities is emerging between AI and enterprise application platforms: AI understands the business, generates the application, and keeps iterating as requirements change; enterprise application platforms such as NocoBase provide the data management, permissions, workflows, auditing, and other foundations required for a system to run reliably over the long term.

If you already have a clear business requirement, start by describing it. Tell AI about your business, team, and processes, then combine it with NocoBase to build the CRM you actually need step by step. Going from requirements to a usable business system may now be simpler than you expect.

Ready to get started? Build your enterprise AI CRM with AI + NocoBase.

Related reading:

Weekly Updates: Assign Plugin Skills to AI Employees

NocoBase — Mon, 10 Aug 2026 07:22:18 +0000

Summarize the weekly product update logs, and the latest releases can be checked on our blog.

NocoBase is currently updated across three branches: main, next, and develop.

main: The most stable version to date, recommended for installation.
next: Beta version, contains upcoming new features and has been preliminarily tested. There might be some known or unknown issues. It is mainly used to collect feedback from test users and further optimize features. Ideal for test users who want to experience new features early and provide feedback.
develop: Alpha version, contains the latest feature code, may be incomplete or unstable, and is mainly used for internal development and rapid iteration. Suited for technical users interested in cutting-edge product capabilities, but not recommended for production use.

main

v2.1.37

Release date: 2026-08-08

🎉 New Features

[client-v2] Add Date variables and optional formatted output to V2 field-value editors. (#10289) by @katherinehhh

🐛 Bug Fixes

[client-v2]
- Fix missing and incorrectly resolved Current popup parent record variables in v2 popup-subtable add-new and edit dialogs. (#10292) by @katherinehhh
- Fixed parent item variables resolving to the wrong level when assigning association field values in sub-tables. (#10249) by @gchust
- Fix the cancel button language in mobile selection lists (#10297) by @zhangzhonghe
[data-source-manager] Fixed formula fields being converted to number fields after synchronizing fields from the database (#10303) by @2013xile
[database] Fixed migration packages omitting many-to-many through-table data after an application restart (#10306) by @cgyrock
[Backup manager] Fix duplicate backups from async exports (#10300) by @gchust
[AI employees] AI employee actions now support linkage rules for conditional visibility in v2 forms. (#10298) by @jiannx
[Data source: External NocoBase] Fixed external NocoBase files and attachment fields failing to load in AI workflows by @2013xile
[Migration manager] Fixed many-to-many through-table migration data after application restarts and classified migration rules as system data by @cgyrock
[Workflow: Approval] Fix approval comment default values when using RunJS by @zhangzhonghe
[App supervisor] Prevented app creation with database identifiers that do not start with an English letter or contain unsupported characters. by @hongboji

v2.1.36

Release date: 2026-08-05

🐛 Bug Fixes

[Data source manager] Prevented clearing a field interface directly from the Configure fields table. (#10288) by @hongboji
[Auth: LDAP] Fixed LDAP login when a user DN mixes UTF-8 escapes with escaped syntax characters such as commas. by @hongboji

v2.1.35

Release date: 2026-08-05

🚀 Improvements

[Workflow: HTTP request node] Fix unstable test cases (#10246) by @mytharcher
[Action: Batch update] Support configurable after-success behavior for v2 Update record and Bulk update actions. (#10278) by @katherinehhh
[Action: Export records] Add field search to v2 import and export action settings. (#10261) by @katherinehhh
[Action: Export records Pro] Add field search to v2 Import Pro and Export Pro action settings. by @katherinehhh

🐛 Bug Fixes

[client-v2] Fix missing Current record variables in v2 JS column event-flow conditions. (#10279) by @katherinehhh
[database] Fixed MSSQL queries failing when filtering to-many relations with pagination and sorting by a root collection field (#10224) by @cgyrock
[data-source-manager] Fixed external data source table synchronization leaving removed collections registered in the database manager (#10209) by @cgyrock
[Workflow: JavaScript] Fixed JavaScript workflow Workers not exiting after scripts returned or asynchronous workflows timed out (#10241) by @mytharcher
[Collection field: Sequence] Fixed duplicate automatic sequence values after migration when multiple records share the latest creation time (#10239) by @mytharcher
[Data source: External SQL Server] N/A — regression test coverage only by @cgyrock
[AI: Knowledge base] Fixed PGVector knowledge base searches consuming unused PostgreSQL pool connections and creating duplicate pools for different vector tables. by @cgyrock
[Data source: External MySQL] Fixed previously selected external database tables disappearing after adding new tables. by @cgyrock
[Workflow: Approval]
- Fix missing field values in approval sub-tables by @zhangzhonghe
- Allow approval comments to use configurable default values by @zhangzhonghe

develop

v3.0.0-alpha.7

Release date: 2026-08-06

🎉 New Features

[client-v2] Support using the standalone Settings application as the default app entry. (#10267) by @katherinehhh
[AI employees]
- AI employees can now be assigned skills from the employee settings page. Skills are built from plugins. (#10237) by @cgyrock
- Added Portal-scoped AI conversations and unread counts. (#10266) by @cgyrock
[Portal manager] Updated init defaults so non-latest installs use the modern client entry and seed the default AI, admin, and mobile portals; the CLI can now save and update the client entry mode. (#10281) by @chenos

🚀 Improvements

[Action: Batch update] Support configurable after-success behavior for v2 Update record and Bulk update actions. (#10278) by @katherinehhh
[Action: Export records] Add field search to v2 import and export action settings. (#10261) by @katherinehhh
[Action: Export records Pro] Add field search to v2 Import Pro and Export Pro action settings. by @katherinehhh

🐛 Bug Fixes

[client-v2]
- Fix missing spacing in workflow approval configuration dialogs (#10276) by @zhangzhonghe
- Fix missing Current record variables in v2 JS column event-flow conditions. (#10279) by @katherinehhh
- Hide the maintenance dialog and retry button while the application is upgrading (#10250) by @zhangzhonghe
- Prevent long table content from widening columns and wrap it automatically (#10259) by @zhangzhonghe
[database] Fixed MSSQL queries failing when filtering to-many relations with pagination and sorting by a root collection field (#10224) by @cgyrock
[data-source-manager] Fixed external data source table synchronization leaving removed collections registered in the database manager (#10209) by @cgyrock
[Localization] Fixed a crash when opening Localization settings with the Lina AI assistant entry. (#10293) by @cgyrock
[Data source manager] Prevented clearing a field interface directly from the Configure fields table. (#10288) by @hongboji
[Backup manager] Prevent repeated V2 backup restore submissions while a restore request is in progress. (#10262) by @katherinehhh
[File manager] Fixed shared attachments such as the system logo not loading for authenticated member users (#10268) by @mytharcher
[AI employees] Fixed the AI employee entry not appearing in non-default portals. (#10260) by @cgyrock
[Data source: External MySQL] Fixed previously selected external database tables disappearing after adding new tables. by @cgyrock
[AI: Knowledge base] Fixed PGVector knowledge base searches consuming unused PostgreSQL pool connections and creating duplicate pools for different vector tables. by @cgyrock
[Data source: External SQL Server] N/A — regression test coverage only by @cgyrock
[Workflow: Approval]
- Fix missing field values in approval sub-tables by @zhangzhonghe
- Fix approval comment default values when using RunJS by @zhangzhonghe
- Allow approval comments to use configurable default values by @zhangzhonghe
[App supervisor] Prevented app creation with database identifiers that do not start with an English letter or contain unsupported characters. by @hongboji
[Auth: LDAP] Fixed LDAP login when a user DN mixes UTF-8 escapes with escaped syntax characters such as commas. by @hongboji

v3.0.0-alpha.6

Release date: 2026-08-03

🚀 Improvements

[Workflow: HTTP request node] Fix unstable test cases (#10246) by @mytharcher

🐛 Bug Fixes

[auth] Fixed occasional Invalid CSRF token errors on API requests in cross-origin deployments (#10245) by @mytharcher
[Portal manager] Fix device icon and long title display on Portal cards (#10248) by @zhangzhonghe
[Collection field: Sequence] Fixed duplicate automatic sequence values after migration when multiple records share the latest creation time (#10239) by @mytharcher
[Workflow: JavaScript] Fixed JavaScript workflow Workers not exiting after scripts returned or asynchronous workflows timed out (#10241) by @mytharcher