NocoBase says the free edition builds "unlimited applications" — here's what that actually means

#nocobase #opensource #lowcode #selfhosted

If you're evaluating NocoBase, you hit this question early: how far does the free Community edition actually go?

The pricing page says the Community edition lets you:

Build unlimited applications with no limits on users or data

Sounds generous. Then you open the docs, look up anything multi-app related, and every page carries a paid-edition badge. So can you build "unlimited applications" for free or not?

It turns out someone asked the official forum exactly this, and a staff member settled it. This post maps the Community/paid boundary using only primary sources — the pricing page and official staff answers on the forum (several of them in the Chinese-language category, which is by far the most active and where a lot of these answers live).

Everything below reflects the pricing page and forum answers as of July 2026. Editions and prices change; check the pricing page before making a purchase decision.

What "unlimited applications" actually means

The forum question (t/13365, July 2026, Chinese) was word-for-word the confusion above: the pricing page says unlimited apps, the multi-app docs all say paid edition — which is it?

The staff answer (translated):

The Community edition lets you deploy and develop multiple mutually independent application instances. But "multi-app" refers to the feature of creating and managing multiple isolated applications inside a single NocoBase. Using that feature in a newly installed environment requires the Professional edition.

So:

"Unlimited applications" = you can stand up as many NocoBase instances as you want. Ten Docker containers running ten systems is fine — it's open source, after all.
The multi-app feature — managing multiple isolated apps inside one NocoBase — is paid.

If you read "build unlimited applications" and expected the multi-app feature, you'd be disappointed — and judging by the forum, plenty of people read it exactly that way. I'd argue that's on the wording, not the readers.

One more wrinkle worth knowing: the pricing page lists multi-application architecture under Enterprise, while the forum answer above says Professional. If multi-app is the reason you're buying, confirm the required edition with the team directly before you pay.

The "wait, that's paid?" list

Pulling from the edition comparison on the pricing page, here's where the boundary actually sits. These are the ones most likely to surprise you:

Feature	Edition
Rebranding (logo / product name)	Standard
External database connections (supported DBs vary by edition — see below)	Standard and up
Bulk Excel import/export	Standard
Approval workflows	Professional
Subflows	Professional
Webhook trigger	Professional
SSO / record edit history	Professional
Audit log (user action logging)	Enterprise
Multi-app / multi-space	Enterprise (forum says Professional — see above)
Cluster deployment	Enterprise

Three of these bite hardest in practice:

Approval workflows. Request-then-approve is the bread and butter of internal tools, and the Approval plugin is Professional. To be precise: the Community edition does have a generic Manual Handling node (pause until a human acts). What's paid is Approval — the dedicated plugin with request lists, approval screens, and the rest of the purpose-built UI.
Webhook trigger. The official path for receiving data from external systems sits on the paid side. There's a solid workaround, though — next section.
External databases. Layering NocoBase on top of an existing business DB starts at Standard ($800), and the supported engines depend on the edition: MySQL / PostgreSQL / MariaDB at Standard, MSSQL and REST API data sources at Professional, Oracle / ClickHouse / Doris at Enterprise.

No webhooks? You can still receive data

In another thread (t/13337, July 2026), someone needed to receive pushed data from an external service. After a reply pointed out that webhooks require Professional, a practitioner shared what they run in production (translated):

Create an API key, and give it a role whose write permission is restricted to just the table you're storing into. The external service writes directly through the REST API. This is how we currently receive pushed data from a bank.

Every NocoBase collection automatically gets a REST API, so "receive via webhook" becomes "have the sender write via REST" — fully within the Community edition. The key detail is the locked-down role: API keys inherit the role's permissions, so a key scoped to one table limits the blast radius if it ever leaks.

(If you needed the webhook specifically to trigger a workflow on arrival, bind a collection event to the target table instead — with the caveat that collection events have their own quirks, like not firing on bulk operations.)

You can't buy plugins individually anymore

One more boundary fact that trips up budgeting. There was a period when commercial plugins could be purchased one by one. Asked about buying just the report-printing and subflow plugins (t/12377, May 2026), staff answered (translated):

That's no longer supported. You need to purchase a license, and the license includes the corresponding plugins.

So the current model is: buy an edition license, get that edition's plugin set. If the one feature you need lives in Professional, your unit of purchase is Professional ($8,000, one-time) — there's no à-la-carte option. Plan budgets around editions, not features.

To be fair: the free side has been growing

Lest this read as "the free edition is bait" — the movement in 2026 has been in the other direction. In February, the core license changed from AGPL-3.0 to Apache-2.0, and 16 previously-commercial plugins were open-sourced in the same move.

The realistic summary: a single internal business system, without approval flows, is entirely buildable on the Community edition. The paid line is drawn around approvals, the official external-integration path, unified multi-app management, and enterprise operations (clustering, audit logging).

Evaluation checklist

"Unlimited apps" means unlimited instances. Managing multiple apps inside one NocoBase is paid — and the required edition (Professional vs Enterprise) is stated inconsistently, so confirm before buying.
Ask "do we need approval workflows?" first. It's the most common late surprise. If yes, budget for Professional from day one.
No webhooks needed for inbound data — a write-scoped API key plus the auto-generated REST API covers it.
No per-plugin purchases. Find which edition contains your must-have feature and price that edition.
Editions and prices move; re-check the pricing page (and ask the team directly for edge cases) before deciding.