nocobase

nocobase/nocobase

NocoBase is an open-source AI + no-code platform for building business systems fast. Instead of generating everything from scratch, AI works on top of production-proven infrastructure and a WYSIWYG no-code interface, so you get both speed and reliability.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 16, 2026
today
Ship score
96/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 23,961 → 24,555 (Sep 1 – Oct 13, 2026)
+354 stars in the 28 days to 2026-10-13

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
24.6K
Forks
2.9K
Open issues
356
Watchers
172
Primary language
TypeScript
License
Other
Created
Oct 24, 2020
Owner
nocobase · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. License unknown — GitHub’s own license field, not legal advice. 211 startups in the directory ship primarily in TypeScript.

Topics

#admin-dashboard#ai-agent#ai-agents#ai-assistant#ai-tools#crm#crud#dsh-plugin#erp#internal-tool#internal-tools#low-code#lowcode#no-code#nocode#project-management#salesforce#self-hosted#workflows

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 99%, self-hostable 74%, hosted offering 71%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-16This is the badge for nocobase/nocobase, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/nocobase/nocobase.svg)](https://ossean.com/nocobase/nocobase)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.