Codumentor logo Codumentor Enterprise

Community vs Enterprise

Community is for your own work. Enterprise adds the workflows and shared
knowledge of an organization. Both editions include the core assistant;
Enterprise is not a prerequisite for using your own models, tools or scheduled
runs.

The highlights

CommunityEnterprise
Core assistantChat, code and document understanding, file tools, shell commands and approvalsThe same core assistant
Personal toolsYour models and keys, Google Workspace, tool servers, voice, Telegram, goals and scheduled runsThese capabilities are included too
MemoryLocal knowledge base and search of your earlier conversationsAlso organizational memory, curated and surfaced across the organization
Workspaces and source controlWork in your chosen local folder or repositoryAlso isolated per-conversation workspaces on Linux, branch switching and the Push workflow
Team integrationsPersonal integrations and your own pluginsAlso Redmine, Gitea pull-request review, Slack and Subversion
OperationsRun your own assistant; connect to your own machines over SSHAlso operator-managed remote execution, port forwards and log-collection workflows

These are build capabilities, not a promise that every feature is enabled
on your instance. Configuration, credentials and your access permissions still
apply. The details and platform limits are below.

Find your edition

The edition chip beside Codumentor in the conversation-list header opens
this comparison in a new tab. You can also check Settings → About, the
documentation header, or run codumentor build-info. The chip is informational:
clicking it does not switch editions or change your instance.

How editions are packaged

Codumentor is built in two editions. The edition is fixed when the program is
built: what an edition leaves out is not switched off, it is not in the program
at all, so no setting can turn it on. A configuration that names a feature the
build does not contain is refused at startup, by name.

Who each edition is for

CommunityEnterprise
Made forOne person: your own machine, your own code, your own accountsAn organization: shared instances, many users, an operations team
Who runs itYou — you are the user and the administratorAn administrator or operator runs it for the users
Operating systemsAny machine you ownA server whose operating system the operator chooses
Running it with no commandStarts the server and opens the browserOpens the terminal UI

What both editions have

Everything that is not an add-on is in both editions — which is most of the
product:

What Community adds for one person

The Community edition ships the extensions that make a personal assistant
complete on day one, among them:

These capabilities are in the Enterprise edition too. Enabling an integration
still requires its configuration and credentials.

What only Enterprise has

Enterprise adds built-in extensions for organizational workflows. The key
differences from Community are:

AreaWhat it is
Organizational memoryKnowledge curated for the whole organization and offered before someone repeats a known mistake
SandboxEach conversation runs in an isolated workspace (Linux only); access profiles that limit a user to some repositories rely on it
Team systemsRedmine issues, Gitea pull-request review, Slack, links to the source host
Source-control workflowA branch per conversation, the Push button, Subversion, file-share sync, GitHub sign-in
OperationsOperator-managed remote execution over SSH, port forwards, log-collection conversations; personal SSH tools are available in both editions
Browser foldersAttaching a folder from the user's own machine in the browser

On safety without the per-conversation sandbox. That sandbox needs a
Linux kernel feature, and the Community edition runs on any machine, so it
does not rely on one. What holds everywhere holds there: every shell command
and outbound call goes through the approval gate, and approving or denying
each action is your decision. The Community edition adds the lighter
light sandbox below that gate: shell
commands are confined to your working folder, offline, without your
credentials (Linux and Windows; on Windows, Credential Manager is hidden
from them too, and only DPAPI stays open; macOS planned). In the Enterprise edition the per-conversation sandbox is an extra, best-effort layer on top of
the same gate.