BeeCRM
Read docs

Phase 1 · in developmentNo general availability yet

Your business app, defined as data.

BeeCRM stores fields, relations, views, permissions, and workflow as metadata. One shared runtime interprets it, so your own admins extend the system without an engineering project.

Join early access Read the docs
Object, field, and permission definitions flow through one shared runtime to list, detail, form, kanban, and REST API surfaces. Object, field, and permission definitions flow through one shared runtime to list, detail, form, kanban, and REST API surfaces.
Definitions as data → one runtime → every product surface

Extension should not mean rebuilding.

Fixed schemas and string-EAV custom fields turn each new field, relation, or view into a small engineering project. BeeCRM makes those changes configuration while preserving one rendering and authorization model.

How it works

One definition. Every surface.

Object and field definitions enter one metadata engine. The same definitions shape the interface, enforce permissions, and expose equivalent operations over REST.

Diagram showing object and field definitions entering a shared runtime that produces list, detail, form, kanban, permission, and API surfaces. Diagram showing object and field definitions entering a shared runtime that produces list, detail, form, kanban, permission, and API surfaces.
  • Definitions
  • Shared runtime
  • Rendered surfaces

The API can do what the UI can do.

UI operations—including metadata and admin operations—have public REST equivalents. API tokens are attenuated sub-principals of a real user, so automation inherits the user’s bounds instead of escaping them.

An agent never outranks its human.

POST /api/v1/objects/{type}/fields 
POST /api/v1/objects/lead/fields
Authorization: Bearer <user-token>
Content-Type: application/json

{
  "key": "service_region",
  "label": "Service region",
  "type": "select",
  "required": false
}

Leads become customers. Work stays visible.

Leads, customers, contacts, and tasks share custom fields, role × object permissions, audit, bulk operations, and metadata-defined views in the Phase 1 CRM spine.

BeeCRM Leads kanban view in light theme BeeCRM Leads kanban view in dark theme
Leads pipelineMetadata-defined stages and bulk-aware movement.
BeeCRM customer detail view in light theme BeeCRM customer detail view in dark theme
Customer detailRelations, activity, tasks, and facts in one record.
BeeCRM Tasks kanban view in light theme BeeCRM Tasks kanban view in dark theme
Tasks boardOwner, due state, and permission-aware work queues.

Roadmap · no dates

A core that admits more modules.

CRM establishes the shared runtime. Sales documents, engagement, and the bee CLI follow in Phase 2; projects and billing are Phase 3 roadmap items.

Roadmap diagram: CRM in active development; sales documents, engagement and bee CLI in Phase 2; projects and billing in Phase 3. Roadmap diagram: CRM in active development; sales documents, engagement and bee CLI in Phase 2; projects and billing in Phase 3.

Portable by design. Permission-first by default.

BeeCRM is edge-native, portable to a conventional server runtime, and designed to remain operable by a small team.

Follow the build. Join when it is ready.

BeeCRM is in active development. Leave one email address and we will only use it to contact you about early access.