Your ops manager wants a ticket system. Engineering quotes three sprints. Someone suggests "just use Airtable" until you hit row limits and can't wire approvals. Someone else wants Cursor to vibe-code a CRM from scratch until you realize nobody maintains the permissions layer when the intern leaves.
NocoBase sits in the middle. ~23k GitHub stars, open source, and an AI + no-code platform for building business systems — data models, pages, workflows, and permissions as production infrastructure, not generated spaghetti. WYSIWYG editing for humans. CLI and skills for Claude Code, Cursor, and Codex. AI employees that run inside the system with the same role boundaries as real users.
What it actually does
NocoBase is a data-model-driven business app platform. Define tables and relationships first — customers, tickets, orders, assets — then compose pages from blocks (tables, forms, charts) like a structured Notion. UI and data stay decoupled; change the layout without migrating schema by hand.
WYSIWYG no-code. Toggle between usage mode and configuration mode. Non-developers can build and adjust pages, fields, and workflows visually. Developers aren't locked out — it's infrastructure you extend, not a black-box generator.
Workflows and permissions. Approval flows, automations, audit logs, field-level read/write rules built in — the stuff that breaks when AI writes a CRUD app from zero. AI actions respect the same permission model as human users.
AI employees. In-system AI for analysis, document recognition, form filling, task routing — integrated with workflows, not bolted on as a chat sidebar.
Agent ecosystem. MCP, HTTP APIs, CLI (@nocobase/cli), and NocoBase Skills so external agents (OpenClaw, n8n, Dify) connect with boundaries. Initialize a project with nb init --ui, point your coding agent at the directory, and it understands your data models and plugins.
Plugin architecture. Microkernel design — features ship as plugins, WordPress-style. Official and custom plugins share the same extension model.
NocoBase vs Appsmith vs ToolJet
We've covered low-code internal tool builders:
- Appsmith — drag widgets, write JavaScript, connect existing databases and APIs into admin panels
- ToolJet — similar lane: visual front ends over data you already have
Appsmith and ToolJet assume your database already exists and you're building views on top. NocoBase assumes you're building the business system — schema, UI, workflows, permissions, and AI in one platform. Pick Appsmith for a Postgres admin console. Pick NocoBase when you're standing up a ticket desk, asset tracker, or lightweight CRM and want the data layer to live inside the product.
Why self-host?
Business data stays yours. Customer records, HR tickets, inventory — standard relational data in PostgreSQL or MySQL on your server. No multi-tenant SaaS holding your ops data in another jurisdiction.
PIPEDA and client contracts. Canadian agencies building client portals can host NocoBase on Montreal or Toronto hardware and answer "where does our data live?" without a vendor DPA maze.
AI without losing control. AI employees and coding agents operate inside permission boundaries and audit logs — not a shadow admin with god-mode API keys.
No per-seat spreadsheet tax. Self-hosted means server cost, not per-editor SaaS pricing as your team grows.
What running it takes
Docker Compose is the recommended path:
curl -fsSL https://static-docs.nocobase.com/docker-compose/en/latest-postgres.yml -o docker-compose.yml
# Set APP_KEY and DB passwords in the file
docker compose up -dUI on port 13000 (maps to container port 80). Image nocobase/nocobase:latest-full includes database clients and LibreOffice for PDF templates. PostgreSQL needs wal_level=logical in the compose command — the official file handles this.
Plan 2 GB RAM minimum, 4 GB+ for production. CPU: 2 cores recommended. Back up ./storage and the Postgres volume — that's your app data and uploads.
Put HTTPS and auth in front. This platform can hold sensitive business records — don't expose port 13000 to the internet without a reverse proxy and strong admin passwords.
Who it's for (and who should skip it)
Good fit: ops teams outgrowing spreadsheets, agencies building client business apps without a full dev sprint per feature, orgs wanting AI-assisted development on proven infrastructure instead of greenfield codegen, teams that need workflows and permissions day one.
Maybe skip it: you only need a read-only dashboard over an existing warehouse — Appsmith fits better. You want pure workflow automation without a data model — n8n. You need a public marketing site — wrong tool entirely.
Hosting it in Canada
We run NocoBase on Canadian Docker hosting — Postgres alongside the app container, TLS, backups on storage volumes, RAM sized for workflows and concurrent users.
Tell us what you're building — ticket system, CRM, asset tracker — and we'll size the box before your first workflow times out under load.
