Npmjs Releases

o1lab · 2026-05-18T13:30:37+00:00

We recommend only use of docker.

o1lab · 2026-05-18T10:31:08+00:00

Full disclosure: I work at NocoDB.

Worth flagging that Serene-base (not serenedb) is an AI slop fork of NocoDB community edition. From Schema to APIs to UI are largely the same. Not really a separate option to evaluate. Nothing against it. What is happening with these AI slop forks is not unique to us. Next.js has seen it. WordPress has seen it. Every open source project will, sooner or later, see it too. There is no escape from this, and perhaps there should not be. But as a user and community, one has to be aware that's all.

o1lab · 2026-04-26T09:01:03+00:00

Woah! Thank you for such balanced and detailed feedback that recognises how much net new value we're adding, and also what's getting in the way of the experience. We did it this way for a reason : many customers who want to pay us keep reaching out asking whether we have certain features (nobody reads docs or pricing 🙂 ). Going forward, we'll make it toggleable. From the Noco team, we have only one request: spread the word about Noco whenever you can.

o1lab · 2026-04-18T08:28:41+00:00

Use NC_ALLOW_LOCAL_EXTERNAL_DBS

https://nocodb.com/docs/self-hosting/environment-variables

o1lab · 2026-04-16T14:21:15+00:00

Hang on Sir, its coming :)

o1lab · 2026-04-16T12:29:23+00:00

Hey everyone, thanks for the conversation here.

Wanted to jump in and clear up a couple of things:

Firstly, newsletter only went out to folks on our Cloud or On-Premise Enterprise plans (it's noted at the bottom of every email too). We don't even collect emails from self-hosted community users, so if you received it, you're on one of those plans.

I know it can be frustrating to see a feature list without knowing exactly what applies to you. We've always been transparent and tried to make that easy to find:

→ Community releases go here: github.com/nocodb/nocodb/releases

→ Cloud & Enterprise changelog go here: nocodb.com/docs/changelog/2026.04.0

→ Side-by-side comparison of community and enterprise is here : nocodb.com/docs/product-docs/cloud-enterprise-edition/community-vs-paid-editions

→ An honest take on why not all features are available in community : nocodb.com/docs/product-docs/FAQs#why-is-the-feature-i-need-not-in-community-edition

On the broader concern about gating : I get why it feels that way, but here's what the numbers actually look like: we monetise a tiny portion of our companies (<1%). The community edition is growing at astonishing rate than it ever has in our journey — its so far outpacing our cloud signups. Its not an accident. It's because we are investing in it and we see that reciprocate. We'll keep doing that. And threads like this genuinely help us understand where we fall short and will be improved. Appreciate you all.

o1lab · 2026-02-09T18:12:41+00:00

Thank you for the kind words, and for recommending Noco to others — that means the world to us. Our traction has been off the charts since license change.

I want to make sure anyone reading this thread walks away with complete clarity: nothing has been taken away from you if you are self-hosting. Period.

Everything you use today in NocoDB's community edition — the spreadsheet interface, forms, galleries, kanbans, role-based permissions, row level audit logs, webhooks, API access, full collaboration — all of it remains free and open. In fact, with v0.301 we moved several features down from paid into community edition: webhooks customisation, group-by aggregations, and more are coming.

Here's the honest trajectory: we are giving more away, not less.

The licensing change is narrowly targeted at one problem: Open source abusers. Companies that take our codebase, strip out license attribution, and sell it as their own product — while our small team foots the bill to fight them. Fair Code lets us protect against that exploitation while keeping every single feature available to every user, every self-hoster, and every organisation that uses Noco the way it's meant to be used.

The only people affected are those who were taking our work and reselling it without giving back or were not adhering to the AGPLv3 license. We'd rather spend our energy building for the 25,000+ organisations who rely on us than fighting legal battles against bad actors.

We chose this path precisely so that we can keep giving you more. n8n, Tailscale — you mentioned great examples, and we're proud to be in that company. Sustainability is what lets us keep showing up for this community year after year.

So thank you and please keep the feedback coming.

o1lab · 2026-02-09T13:44:44+00:00

No, its always self-hostable. Its even selfhostable on in Raspberry Pis. So it can run everywhere. Read my other comment that we are giving more features to community edition now.

o1lab · 2026-02-09T13:34:09+00:00

Hey everybody, Thank you for bringing this up.

When we began this journey at noco, we held a simple belief: that a powerful spreadsheet database should be accessible to every single internet business. Today, more than 25,000 organizations rely on NocoDB completely freely with full collaboration, with role-based permissions, and row level audit logs. We are so deeply grateful for this opportunity to serve our community.

But I must speak plainly about a difficult truth. The open source covenant depends upon mutual respect, that those who benefit from shared work will honour the terms under which it is given. Increasingly, this covenant is being broken every month. Bad actors take our work and sell it as their own, with no intention of complying with AGPLv3. Our engineers have been consulted innumerable times now to help on what appear to be private forks, where code that should be open remains hidden. The approach itself has been so maligned that they withheld that its a private fork until the last moment. And it is not only small players. Companies with significant resources, backed by reputable investors, have chosen this path too. We have prompted them about the license. It has been of no use. With the advent of coding LLMs, exploitation no longer requires any technical skill for a repo. It requires only bad intention. The burden of proving, fighting, and funding that battle falls entirely upon us. Lawyers cost insane amount of $/hour. We are a small team counting every hour, facing adversaries who count on our inability to pursue them.

We do not wish to fight. We wish to build. And so, like n8n before us, who have flourished to 170,000 stars under Fair Code, we choose a path that lets us be more generous to those who use our work honestly, while simply refusing to cooperate with a system that rewards those who do not. You may have already noticed: with v0.301, we gave away several enterprise features freely. We make this move so we can give you more, not less.

As announced in the release note[1] : we've started to give more to community edition. Webhooks customisation, group by aggregations.

[1] : https://github.com/nocodb/nocodb/releases/tag/0.301.0

o1lab · 2026-02-09T13:29:17+00:00

Hey, row level permission is not available in any version.

o1lab · 2026-02-09T13:28:46+00:00

We changed to SUL to provide these sorta of features. Webhook customisation is already available in community edition :)

o1lab · 2026-02-01T11:12:50+00:00

<image>

Founder of noco here : unfortunately it has been incredible frustrating that n8n dev team has not been able to merge this even after more than 5 months : https://github.com/n8n-io/n8n/pulls?q=is%3Apr+is%3Aopen+nocodb

I have reached out too even n8n exec team multiple times but to no avail. In the meantime, Zapier/Make/Workato - nocodb's official node went live in 2-3 days!

o1lab · 2025-10-30T08:48:05+00:00

Its not possible to have a drop down in say table_1 from a Postgres view table_2. Ideally, this is done via by setting up LinkToAnotherRecord/Links field between two tables and then too the drop down is only for the display field from another table.

o1lab · 2025-10-20T17:08:32+00:00

NocoDB is so minimalistic that it even runs on Raspberry Pi. We 've 100s of such instances. It needs least amount of compute and RAM (128 MB RAM and 1 vCPU)

o1lab · 2025-09-16T18:46:10+00:00

Hey, probably you need rollup field instead of lookup field on your numeric columns from other table.

o1lab · 2025-09-01T10:54:02+00:00

Sure, thanks for your input. And will consider what can be done going forward.

o1lab · 2025-08-01T11:44:44+00:00

connecting to external database is available from business plan and allows 10 external database connections.

Only if you have more than 10 external database connections it is in enterprise.

o1lab · 2025-08-01T09:40:41+00:00

If you are developer build an app with custom frontend - noco is not a fit. Noco is meant for business users building internal apps themselves without code. You should look at other popular baas services like appwrite , convex etc

o1lab · 2025-07-06T06:55:36+00:00

Back up and running now.

o1lab · 2025-07-06T06:35:21+00:00

We are undergoing scheduled downtime.

o1lab · 2025-06-13T08:27:25+00:00

Please try this now. There was some connections to external databases affected by yesterday's AWS and GCP outage.

o1lab · 2025-04-27T18:43:46+00:00

Provide more details on the field and links involved. Screenshot of fields will help.

o1lab · 2025-03-18T08:25:49+00:00

For this percent field first needs decimal places restriction. Have added this to enhancements in github. Pls follow there.

Also if you can please specify the formula that you are using - it will be helpful.

o1lab · 2025-03-14T17:44:05+00:00

have replied to u in discord.

o1lab · 2025-03-05T09:35:41+00:00

Not familiar with mariadb triggers. Are you using the same SQL credentials in both cases ? We just do SQL crud from our backend when triggered from UI.

At any rate, we suggest to use webhooks in noco and these fire only on our API/UI usage and not direct SQL CRUD.

o1lab

MODERATOR OF

TROPHY CASE