n8n, NocoDB, Appsmith and Retool in one week: where low-code ends and your own code begins

This week four builders that small companies use shipped releases, and two platform comparisons came out. Read them back to back and the same things keep showing up: a table of “what's in the free version,” a feature that got switched off, and access permissions that had to move from the app into the data. For an owner, this answers the question of where a builder stops being cheap and when it's time to order your own code.

What came out this week

On October 23, n8n released patch 2.45.3 with a single fix: text contrast in the editor's light theme. Patches come often, and if you run n8n on your own server, updating becomes a regular chore.

A few days earlier, on October 20, n8n explained why it changed its logo, font and colors at the In The Loop conference on October 14. Two lines in the post matter to me: Community Edition stays, and the choice of model stays. The rest is about the brand.

Before that, on October 16, n8n published a comparison of 12 automation platforms for large companies. The criteria are the useful part: where the data lives, whether there's SSO, RBAC and an audit log, what agents can do, and how pricing works, per user or per task. About itself, n8n writes that the code is source-available, it can be installed on your own server, it has more than 1,000 integrations, and there's a Code node for cases that aren't covered. The others get short descriptions that lean in n8n's favor.

On October 23, NocoDB released 2026.10.0. Workload tracking in Timeline View, where overloaded people are highlighted in red, is in paid plans only. Step-by-step replay of a past workflow run is in every version, Community included. Triggering an automation with a button is free in the cloud and missing from Community. The availability table in the release is honest, and it's the first thing worth reading.

On October 21, Appsmith released 2.5.1, and the main point there is a reminder: the built-in Appsmith AI was shut down on September 30, 2026, old queries to it stopped working regardless of version, and you have to move to a direct connection to OpenAI, Anthropic or Google.

On October 20, Workato published a comparison with Boomi based on a GigaOm report from September 27: 29 tests with a final score of 1363 to 1058; six of those tests cover agents and MCP, where the score is 370 to 220. Workato commissioned the report itself, and the text says so. Boomi comes out ahead on error handling and user management.

On October 22, Retool introduced Data Access Enforcement: permissions on tables, columns and rows are set once on the data source and apply to every app, workflow and agent. By default everything is closed to everyone, admins included, and a query without a user identity is blocked. The public beta is Enterprise only and Postgres only. This is an important line: once permissions had to move out of the apps and into the data, the builder stopped being a case of “draw it and it works.”

Example: a service company on a builder

Take a service company. Requests from the website go through n8n into a table, the table is shown in Appsmith, and managers work from there. For six months everything is fine. Then the accountant must not see the discount column, and a contractor must see only his own requests. The owner asks to “just hide the column.” You can hide it in the interface, but through the table's API the column is still visible. From there it's either permissions rebuilt in every app, or what Retool did: rules at the data level.

A builder's limit is where rules about data have to apply outside the screen. The sooner you notice it, the cheaper the move.

My line: 2015, 2017 and AppSheet

In 2015 I opened a marketing agency and built its CRM and automations on no-code. I started programming in 2017, when my companies needed systems that didn't exist off the shelf. I have nothing against builders: that's where my path started.

At a PDR company in the US I watched the same line get crossed. In 2021 the data lived in Google Sheets, a second developer built apps on top of them in AppSheet, and the spreadsheets slowed processes down. In 2023 I proposed moving to an SQL database for speed and a single data format, the idea was supported, and after the switch to MariaDB we connected new services one after another. Now the React Native super app we're building with the company's developers is taking over from AppSheet: the office, the sales team and the owner already use it. AppSheet is still there, though: the second developer maintains it and has built many apps in it.

From 2021 to 2025, tasks around Google Sheets came to me through Upwork. The rule there is the same: a script in a spreadsheet does the job while the process lives in Google Sheets and it's too early to move it into a separate system. Once data volume, the number of users or permission requirements grow, it's time to talk about a database.

What I would do

Before choosing a builder, read the availability table in the release notes and the list of features removed over the past year. Appsmith's built-in AI didn't last long.

Check where permissions are enforced: on the screen or in the data. If it's on the screen, count how many screens you'll have to edit the first time a rule changes.

Keep the logic that's valuable to the company on your own server. For a manufacturing company I moved the entire calculation to Node.js so the program couldn't be copied along with the interface.

I described when spreadsheets stop coping in the article When a business needs a system instead of spreadsheets. Earlier I wrote about where the logic of your process begins once you use a ready-made connector and when you need an internal system instead of running things in chats. On the same topic: Gemini in Google Sheets and catalogs of skills and MCP. Services: process automation and the business as one system. Projects: technical partnership with a PDR company and Google Sheets and Apps Script on Upwork. If your builder has hit a wall on permissions or volume, tell me what's built in it now. Discuss your task.