NocoBase for CRM: An Honest Review

NocoBase is one of the most interesting tools to emerge from the open-source no-code space in the last two years. It describes itself as "an extensibility-first, open-source no-code development platform." In practice, it's a self-hosted tool for building data-driven internal apps — databases, forms, workflows, and dashboards — without writing code.

Many teams use it for CRM. This review answers: does it actually work as a CRM, what are the real limitations, and who should consider it?

What Is NocoBase?#

NocoBase (github: nocobase/nocobase, 15,000+ stars) is a self-hosted platform built on Node.js + React with a PostgreSQL backend. You install it, and you get a blank canvas: define your data tables (they call them "collections"), create forms to enter data, build views to visualize it, set up workflows to automate actions.

Everything is driven through their UI — you don't write SQL or code (unless you want to extend the plugin system). You can create a basic CRM by:

1. Creating a "Contacts" collection with your desired fields
2. Creating a "Companies" collection
3. Adding a relation field linking contacts to companies
4. Building a form view for data entry
5. Building a table view for browsing
6. Adding a kanban view for pipeline management

On paper, this is exactly what a CRM is. And NocoBase can deliver it — with significant caveats.

Setting Up a CRM in NocoBase#

Installation#

NocoBase installs via Docker or npm. The Docker installation is the recommended path:

# Docker Compose setup
git clone https://github.com/nocobase/nocobase.git
cd nocobase
cp .env.example .env
# Edit .env with your database credentials
docker-compose up -d

First-time setup takes 15–30 minutes, including database initialization. The setup is well-documented, and the Docker Compose configuration is straightforward for developers.

For non-developers, this is immediately a barrier. NocoBase requires Docker knowledge, a server to run on, and basic command-line comfort. It's not a "sign up and start" experience.

Building Your Data Model#

Once installed, you access the admin UI and start building. The collection builder is intuitive:

• Create a collection ("Contacts")
• Add fields: text, email, phone, date, select, relation, etc.
• NocoBase handles the database table creation automatically

Supported field types are comprehensive: text, email, phone, URL, number, datetime, checkbox, select (single/multi), relation (one-to-one, one-to-many, many-to-many), file upload, JSON, formula fields, and more.

The relation system is solid. Creating a many-to-many relationship between Contacts and Companies is a few clicks. Junction tables are created automatically.

Building CRM Views#

NocoBase's view building is where the tool shines — and where it shows its database-builder DNA rather than CRM lineage.

Table view: Clean, sortable, filterable. Column visibility is configurable. Works well for browsing records.

Kanban view: Available and functional. You select a "groupBy" field (typically a status or stage enum), and records appear as cards in columns. Moving cards updates the field value. This is your pipeline board.

Calendar view: Available for collections with date fields. Useful for task/activity tracking.

Form view: For data entry. Clean forms with field-level validation, conditional display logic, and good mobile handling.

Gantt view: Available via plugin for project timeline tracking.

The challenge: building these views requires configuration time. A purpose-built CRM like HubSpot or Twenty gives you a pre-configured Contact view, Company view, and Deal pipeline. In NocoBase, you build each from scratch. This is the inherent trade-off of a database builder vs. a CRM.

The Real CRM Experience#

After setup, here's what using NocoBase as a CRM feels like day-to-day:

What Works Well#

Contact records are flexible. Add any fields you want — LinkedIn profile, custom tags, lead score, custom notes — without being constrained by a vendor's data model. This is NocoBase's biggest advantage: you own the schema.

Relationship tracking works correctly. A contact linked to a company shows the company details inline. You can navigate between related records without losing context.

Forms for data entry are genuinely good. If you're capturing leads via form (NocoBase can expose forms publicly), the form builder is solid and the data lands cleanly in your collection.

API access is excellent. NocoBase automatically generates a REST API for all your collections. Every record you create is immediately accessible via API. This makes NocoBase a decent backend for custom applications.

Access control is more granular than most open-source options. Role-based permissions can restrict access to specific collections, specific records (row-level security), and specific fields. For teams where not all members should see all data, this matters.

What Falls Short#

No built-in email integration: NocoBase doesn't sync with Gmail or Outlook. You can create a "emails" collection and manually log emails, but there's no automatic activity capture. Coming from HubSpot, this feels like a major regression.

No email sequences or outreach tools: NocoBase is a data platform, not a sales engagement tool. There's no "send a sequence of emails" functionality. You'd need to integrate an external tool (Mailchimp, Instantly, Lemlist) via the API or webhooks.

Workflow automation is functional but basic: NocoBase's workflow plugin handles triggers and actions, but it's less sophisticated than Zapier, n8n, or HubSpot's workflow builder. Complex multi-step workflows with branching logic require the workflow plugin to be extended.

Reporting is limited: The built-in reporting capabilities are basic aggregation and chart blocks. For a sales manager who needs pipeline velocity, rep performance, win rate by lead source, and forecast accuracy — NocoBase's reporting doesn't get there without significant custom development.

Mobile experience: The web interface is somewhat mobile-responsive but not optimized for mobile sales workflows. There's no dedicated native mobile app.

Learning curve for non-technical users: Building and maintaining a NocoBase CRM requires someone who understands data modeling. Non-technical sales reps can use it, but they can't configure it. Every schema change needs someone comfortable with database concepts.

NocoBase vs Purpose-Built Open Source CRMs#

Who Should Use NocoBase for CRM#

Good fit:

• Development teams that want maximum data model control and plan to extend with custom code
• Organizations that need a self-hosted internal tool platform that can also serve CRM use cases
• Teams building multiple internal apps — NocoBase's strength is building several different tools (CRM, inventory, project management) on one platform
• Companies with unusual data models that purpose-built CRMs can't accommodate
• Teams that already use NocoBase for other internal tools and want to add CRM

Poor fit:

• Sales teams that need automatic email sync and activity capture
• Outbound teams that need integrated sequencing
• Non-technical teams that need a plug-and-play CRM experience
• Teams that need strong mobile support
• Organizations requiring sophisticated pipeline reporting and forecasting

The No-Code vs AI-Native Tradeoff#

NocoBase represents a particular philosophy: give non-developers a GUI to build the internal tools they need. This is valuable, and NocoBase executes it well.

But in 2026, there's an alternative philosophy: don't make people configure UI at all — let an AI agent interpret requests and act on a structured database directly.

DenchClaw is built on this second philosophy. Rather than clicking through a collection builder to define your CRM schema, you tell the AI what you need: "Create a CRM for a sales team with contacts, companies, deals, and a pipeline with stages: Prospecting, Qualified, Proposal, Closed Won, Closed Lost." The agent writes the schema, configures the views, and creates the object.yaml — no clicks required.

Both approaches have merit. NocoBase's GUI works for teams that want visual control. DenchClaw's conversational approach works for teams that want to describe what they need and have it built.

Getting the Most from NocoBase as a CRM#

If you decide to use NocoBase, these practices improve the CRM experience:

1. Use n8n or Zapier for workflow automation — NocoBase's native workflows aren't powerful enough for real sales automation. n8n (also open source) pairs well.

2. Build a Gmail integration via API — Since NocoBase has a full REST API, you can use Zapier or a custom script to push Gmail labels/tags to NocoBase as email activity records.

3. Add formula fields for deal scoring — NocoBase's formula fields can calculate lead scores, deal age, or time-since-last-contact dynamically.

4. Create aggregate views for management — NocoBase's chart blocks can show pipeline value by stage, contact count by source, and other simple metrics even without dedicated reporting.

5. Expose forms for inbound lead capture — NocoBase's public forms are genuinely good. Using them to capture inbound leads directly into your CRM is one of the best use cases.

Frequently Asked Questions#

Is NocoBase free?#

Yes. NocoBase is AGPL-3.0 licensed and completely free to self-host. The commercial version (NocoBase Commercial) adds enterprise features (SSO, advanced permissions, commercial support), but the core platform is free and fully functional.

What database does NocoBase use?#

NocoBase uses PostgreSQL as its primary database. MySQL is also supported. The database is yours — you can query it directly with any PostgreSQL client.

Can NocoBase handle large datasets?#

For CRM use cases (tens of thousands of contacts and companies), NocoBase performs well on modest hardware. Very large datasets (millions of records) may require performance tuning and appropriate hardware.

Does NocoBase support multi-tenancy?#

Not natively in the standard version. Each NocoBase installation is a single workspace. Multi-tenant deployments require custom development or multiple separate installations.

How does NocoBase compare to Airtable?#

Airtable is cloud-hosted, polished, and easy for non-technical users. NocoBase is self-hosted, more flexible at the backend, and has better API access and access controls. For teams with data residency requirements or strong data ownership preferences, NocoBase is the better choice despite the higher setup complexity.

Ready to try DenchClaw? Install in one command: npx denchclaw. Full setup guide →