GitHub Trending: Today — n8n, Playwright, NocoDB, CasaOS, Docker Compose

Today's list has no debut. Every repo on it is years old, the youngest from 2021, and not one is a fresh AI launch. Here is the lay of the land before the analysis:

The day GitHub Trending was about owning your stack

Four of these five exist to keep your data and your automations on hardware you control: n8n for the workflows, NocoDB for the database UI, CasaOS for the dashboard that runs the apps, and Docker Compose for the file that wires them together on one machine. Playwright is the outlier, and even it has quietly changed jobs. None of this is new code chasing a hype cycle. It is the boring middle of the self-hosting stack, all trending on the same quiet Wednesday, which is itself the signal: the "run it yourself" toolkit has matured to the point where the interesting questions are no longer "does it work" but "who is allowed to use it" and "what happens when it breaks".

n8n-io/n8n — the automation platform that isn't quite open source

+149 stars today · 194k total · TypeScript

It targets ops and growth teams who want Zapier-style automation without per-task cloud bills: a visual builder you wire by hand, an escape hatch into custom code, and a growing shelf of AI-agent and MCP nodes. The friction is the license. n8n ships under the Sustainable Use License, which lets you self-host and modify freely but forbids reselling it as a service. The Open Source Initiative's definition bars exactly that kind of use restriction, so n8n does not call itself open source; it calls itself "fair-code". That distinction is not new marketing copy. It crystallised out of a years-old fight, issue #40, bluntly titled "n8n is not open source and your project is gaslighting its users", which keeps getting reposted to Hacker News.

"Founder of n8n here. It actually resulted in the creation of fair-code and later the Sustainable Use License." — n8n's founder, replying in the thread

The licence decides whether you can build a business on it. A bug decides whether you keep the business. In January, n8n disclosed CVE-2026-21858, a CVSS 10.0 unauthenticated remote-code-execution flaw in its Form Webhook handling that let an unauthenticated attacker take over a self-hosted instance, with an estimated 100,000 boxes exposed and no fix but upgrading. The patch landed in 1.121.0. That is the whole self-hosting bargain in one repo: you hold the keys, and you also hold the pager.

IceWhaleTech/CasaOS — a home server born from a crowdfunded board

+174 stars today · 34k total · Go

This is for the person turning a Raspberry Pi, an Intel NUC, or a retired laptop into a NAS without ever opening a terminal. CasaOS is not a full OS; it is an app layer that drops on top of an existing Linux box and gives it a friendly dashboard plus a one-click Docker app store. It started life as the pre-installed system for the crowdfunded ZimaBoard, and the same team now ships ZimaOS as the heavier successor, which colours how skeptics read it.

"Icewhale is doing a custom dev board, zimaboard, and this is their sideproject as best as I can tell. Think they may have gotten bored halfway through." — an early HN commenter who traced it to the ZimaBoard hardware

The issue tracker reads like a stability ledger rather than a feature wishlist. The most-discussed open threads are not requests but breakage reports: "Failed to load apps, please refresh later" and "Can't get apps to load or update" each drew dozens of "me too" replies, and a long-running request to enforce authentication on SMB shares hints that the friendly defaults skip a step a NAS should not. The polish is real; so is the rough edge under it.

nocodb/nocodb — an Airtable you host, with the paywall lifted

+31 stars today · 64k total · TypeScript

NocoDB is aimed at teams priced out of Airtable's per-seat plans who already run a Postgres, MySQL, or SQLite database. It is not a database; it is a spreadsheet-and-forms UI bolted onto the one you have, with the smoothest Airtable importer in its class (links, attachments, and views come across intact). The news this period is generosity: a recent release handed self-hosters features that used to sit behind the paid tier, including advanced access control. It also made the same licensing move as n8n, dropping its old AGPL-3.0 for the Sustainable Use License, so the second self-hosted app on today's list is "fair-code" rather than open source. The honest caveat is concurrency: without a real-time sync layer, two people editing the same table is still a refresh-and-pray affair.

docker/compose — the glue every other repo here runs on

+25 stars today · 38k total · Go

Compose is the least glamorous and most load-bearing thing on the list: the single YAML file that actually stands up an n8n, a NocoDB, or a CasaOS app on one server. Its trending is a debate, not a release. The freshest thread, "Should I run plain Docker Compose in production in 2026?", pulled 413 points and nearly 300 comments, and the rough consensus is "yes, if you do the homework": add healthchecks, restart: always, and resource limits, accept that you get no multi-node scheduling, zero-downtime rolling deploys, or autoscaling, and it will hold a single-box service at high uptime. Others reach for an escape hatch above it.

"Nowadays podman can pretend to be a kubernetes cluster and launch pod and deployment definitions. That of course is way close to the 'production' in 'production ready'." — a reply in the production-readiness thread

The open issues sharpen the warning: a networking regression in 2.40.3 reminds everyone that "boring and stable" still ships breaking changes.

microsoft/playwright — the one tool here built to be driven by a robot

+83 stars today · 92k total · TypeScript

Playwright is the outlier: not something you self-host, but the framework QA engineers use to drive Chromium, Firefox, and WebKit from one API. What changed its job is Playwright MCP, a Model Context Protocol server that hands the same browser control to an LLM. Instead of feeding a model screenshots, it drives pages through the accessibility tree as structured text, so an agent in Claude Desktop, Cursor, or VS Code can click and type without a vision model. The testing tool quietly became the standard pair of hands for agentic web automation, which is why it keeps surfacing alongside infra repos. Underneath, it is still winning the old fight on merit.

"I have a fairly large test suite and Selenium produces constant false positive errors, typically due to various timeouts that seem fundamentally unsolvable when running it from .NET." — an engineer running a large Selenium suite from .NET

What a boring trending day actually tells you

The story of today is that self-hosting graduated. When these tools were weekend toys, "fair-code" was a footnote and an unpatched RCE was someone else's problem. Now a single CasaOS box can hold a household's photos and a single n8n instance can run a company's billing, and the stakes invert: the source-available licence quietly determines whether you are allowed to build on the thing, and the next CVSS 10.0 determines whether "I self-host" meant control or just a server you forgot to patch. The maturity is the warning. A stack worth running yourself is a stack worth reading the licence and the changelog for.