Skip to main content
All posts
Comparison· by Nikhil Jathar

ERPNext AI in 2026: NextAI, ChatNext, ChangAI Compared

ERPNext core ships no native AI in 2026. The third-party Frappe app ecosystem has filled the gap with NextAI, ChatNext, ChangAI, Aerele Chatbot, and an MCP bridge. Here is the map.

ERPNext by Frappe Technologies is one of the most-installed open-source ERPs on the planet. Roughly 100,000 production installs, fifteen years of community, a respectable global reseller network. When ERPNext users ask “how do I add AI to my install in 2026?”, the honest answer is that the core does not ship native AI and the ecosystem has filled the gap with a handful of third-party Frappe apps, each solving a different slice of the problem.

This post is a map. It walks through the five most-installed AI options in the Frappe ecosystem in 2026, what each one does, what license each ships under, and where the tradeoffs are sharpest. At the end I will be honest about where ERPClaw sits in the same picture.

ERPNext core in 2026 does not ship native AI

The architecture story explains why. ERPNext is built on the Frappe Framework, which is a forms-and-workflow toolkit. A DocType defines a form, a workflow defines the state transitions, and the UI is generated from the schema. MariaDB stores the data, Redis handles caching and the queue, Node.js renders the front end, Nginx fronts everything. It is a clean architecture, fifteen years polished, and it was designed for a world where the primary interaction model is a human filling out a form.

AI was not in scope when the architecture was set. There is no native chat copilot in ERPNext 15 (the current line in 2026). There is no agent runtime, no embedded LLM, no document-OCR pipeline shipped with the core. What the ecosystem has done instead is build add-on Frappe apps that you install separately into your ERPNext bench. Each app brings its own AI surface.

NextAI

NextAI is the most-installed AI app in the Frappe ecosystem in 2026. The angle is content generation. NextAI adds AI-assisted writing across ERPNext records: drafting product descriptions, polishing email replies, generating customer-facing copy, fixing grammar, suggesting contextual improvements.

It plugs OpenAI as the default model provider. Some forks support Anthropic and local models via Ollama, but the main branch defaults to OpenAI and expects you to bring your own API key. The Frappe app is free, but the model calls are billable to the OpenAI account you wire in.

What NextAI is good at is taking the writing tax off founders and operations staff. What it does not do is operate ERPNext for you. You still log in to Desk, go to the right DocType, and use NextAI to improve the text in a single field. It is a writing assistant inside ERPNext, not an agent that runs ERPNext.

ChatNext

ChatNext (listed as “NextAI” on the Frappe Marketplace) is a sibling project from the same team and the naming is admittedly confusing. ChatNext is the conversational layer. The pitch is that a user can open a chat window and ask questions about ERPNext data in natural language: “what is the AR aging for Acme?”, “show open POs from last month over $5,000”, “which items are below reorder point?”.

Under the hood, ChatNext translates the question into a Frappe report query, runs it, and returns a formatted answer. It is essentially a natural-language query interface over the Frappe ORM, with an LLM doing the translation step.

This is more useful day to day than NextAI for an operations team because it cuts out the click-through-screens cost of finding data. It is still a query interface, though, not an action interface. ChatNext can read your data; it cannot, by default, create a sales invoice or post a journal entry for you. The latest builds have started adding write actions for a small set of common operations, but the coverage is narrow and uneven.

ChangAI

ChangAI from ERPGulf is a broader AI integration for the Frappe stack. The scope is larger than NextAI or ChatNext on paper. ChangAI bundles a chat sidebar, document OCR for invoice and receipt processing, a forecasting helper for sales and inventory, and a hooks-based system that lets you wire AI into custom server scripts.

The breadth is appealing if you want one app instead of five. The tradeoff is that depth in each area is shallower than the focused single-purpose apps. ChangAI’s OCR is fine for clean invoices; for messy scans it lags the purpose-built OCR vendors. ChangAI’s chat is functional but the query coverage is narrower than ChatNext.

Licensing on ChangAI is GPL v3 like the Frappe core, which is helpful because it means there is no license-mixing concern when you install it next to ERPNext. Several of the other apps in this space use MIT or proprietary licenses, and the mix matters if you are publishing your own derived work.

Aerele Chatbot

Aerele Chatbot takes a different angle. Instead of putting the AI interface inside the Frappe Desk, it puts ERPNext behind Telegram, WhatsApp, and Slack. You message a bot, the bot relays to ERPNext, and ERPNext does the work.

For sales teams that live in WhatsApp Business this is a real productivity win. The founder can type “invoice Globex $3,000 for May retainer” into Telegram and Aerele Chatbot will create the sales invoice, attach the PDF, and reply with a confirmation. That is a real action-layer use case, and Aerele is one of the few Frappe apps that actually closes the loop on actions rather than just reads.

The limits show up in coverage. Aerele Chatbot supports a curated list of actions out of the box; anything outside that list requires custom Frappe code and a Frappe developer who knows the chatbot’s request format. The integration is also model-agnostic but defaults to OpenAI, with the same bring-your-own-API-key story as NextAI.

MCP integration via Composio

The newest entry in 2026 is the Composio ERPNext toolkit, which exposes ERPNext as a Model Context Protocol (MCP) server. The implication is that any MCP-aware AI client (Claude Desktop, Cursor, the new wave of agentic frameworks) can connect to ERPNext and call its operations as tools.

This is structurally different from the other four apps. NextAI and ChatNext live inside ERPNext and bring their own UI. Composio’s MCP bridge inverts the relationship: ERPNext becomes a service that external AI agents talk to. If you are an ERPNext user who wants to use Claude or another agentic platform as your primary interface and have it operate ERPNext as one of many tools, Composio is the right path.

The trade is that you are now running an MCP bridge service alongside ERPNext, configuring auth between the bridge and your ERPNext instance, and depending on Composio’s hosted infrastructure (or self-hosting their stack). It is more moving parts than the in-Desk apps.

The tradeoffs of the third-party-app model

What this map shows, when you step back from it, is the cost of being AI-decorated instead of AI-native. To get a reasonably full AI footprint on ERPNext in 2026 you typically install:

  • NextAI for content generation.
  • ChatNext for natural-language queries.
  • ChangAI or a similar app for document OCR.
  • Aerele Chatbot for messaging-channel actions.
  • Composio MCP for agent platform integration.

Five separate apps, each with its own:

  • Install and upgrade path. Each app version-pins independently of ERPNext. When ERPNext 16 ships, you will wait for each app’s maintainer to catch up.
  • License. GPL v3, MIT, AGPL, and proprietary all appear in the mix. License compatibility matters if you are deploying internally with strict policy or if you are reselling.
  • Model provider. Each app picks its default LLM. You will end up with API keys for OpenAI, Anthropic, and possibly Google in the same install, each billed separately.
  • Support story. Frappe support is for ERPNext; each app’s support is for that app. When something breaks at the boundary, the back-and-forth between vendors is yours to coordinate.
  • Data flow. Each app sends a different subset of your ERPNext data to a different external model. Mapping out who-sees-what is its own audit.

This is not a knock on the Frappe community. It is what an AI-decorated architecture forces. Because the AI surface is bolted on, the integration overhead is real and falls on the user. For an established ERPNext shop with a Frappe consultant on retainer, this is manageable. For a founder doing it themselves, it is a lot.

ERPClaw as a different shape of answer

ERPClaw is built the other way. Honest disclosure, I am the builder. AI is the primary interface from the first commit, not a sidebar added later. That changes a few things in the install footprint:

  • One install, one license. GPL v3, free forever, self-hosted on your own infrastructure. No per-user fee, no Enterprise tier, no add-on apps to license separately.
  • The action layer is the AI’s interface. Every operation an AI agent might want to take, create a customer, post a journal entry, submit an invoice, reconcile a Stripe payout, is exposed as a versioned action with a typed contract. The same actions power the CLI, the chat clients, the MCP bridge, and the web UI.
  • Audit-grade accounting under the hood. Money is stored as exact decimals (not floats). Every GL posting passes a 12-step validation. Submitted entries are immutable; corrections are reversals, not edits.
  • Cryptographic verification of every release. Each install resolves against a signed module manifest, so the code you got is provably the code we shipped.
  • 5-minute install. One command pulls the foundation and the verticals you need. Auto-detection picks the right industry pack.

The honest comparison against ERPNext, including the places where ERPNext is genuinely ahead (community size, localization breadth, certified-consultant network), lives in ERPNext vs ERPClaw: An Honest AI-Native Open-Source ERP Comparison. The head-to-head pricing and feature snapshot is at /compare/erpnext/.

Two related reads on competitor AI stories in 2026:

The summary

ERPNext in 2026 is a strong open-source ERP with no native AI in the core and a healthy third-party Frappe app ecosystem that has filled the gap. NextAI handles content generation. ChatNext handles natural-language queries. ChangAI bundles a broader feature set. Aerele Chatbot bridges messaging channels. Composio MCP exposes ERPNext to agentic AI platforms. Together they cover most of what an AI surface for an ERP looks like in 2026, at the cost of running five apps with five maintainers and five licenses.

If that integration tax fits your team’s profile, ERPNext plus the ecosystem is a workable AI-decorated path. If you would rather start from a stack that put AI in the core from line one, ERPClaw is one of a small group of alternatives worth a serious look.

Compare ERPClaw and ERPNext side by side.

Tagserpnextfrappeai-erpcomparisonopen-source-erp