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
| Community | Enterprise | |
|---|---|---|
| Core assistant | Chat, code and document understanding, file tools, shell commands and approvals | The same core assistant |
| Personal tools | Your models and keys, Google Workspace, tool servers, voice, Telegram, goals and scheduled runs | These capabilities are included too |
| Memory | Local knowledge base and search of your earlier conversations | Also organizational memory, curated and surfaced across the organization |
| Workspaces and source control | Work in your chosen local folder or repository | Also isolated per-conversation workspaces on Linux, branch switching and the Push workflow |
| Team integrations | Personal integrations and your own plugins | Also Redmine, Gitea pull-request review, Slack and Subversion |
| Operations | Run your own assistant; connect to your own machines over SSH | Also 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
| Community | Enterprise | |
|---|---|---|
| Made for | One person: your own machine, your own code, your own accounts | An organization: shared instances, many users, an operations team |
| Who runs it | You — you are the user and the administrator | An administrator or operator runs it for the users |
| Operating systems | Any machine you own | A server whose operating system the operator chooses |
| Running it with no command | Starts the server and opens the browser | Opens the terminal UI |
What both editions have
Everything that is not an add-on is in both editions — which is most of the
product:
- Ways in — the web UI, the terminal UI (
codumentor tui), the one-shot command line (codumentor -p "…") and an OpenAI-compatible HTTP API. - Understanding your code — indexing of Git repositories and plain folders, reading of Markdown, PDF, Word, Excel and PowerPoint files, a local knowledge base, @-mentions and attachments.
- The assistant — reading, writing and searching files, running shell commands, delegating to subagents, background tasks.
- Approvals — every write, shell command and outbound call can ask for your approval first. See Permissions.
- Security basics — login, roles and permissions, encrypted stored tokens and secrets, rate limiting and audit logging.
- Your own extensions — plugins you write yourself and put in
~/.codumentor/plugins/work in either edition.
What Community adds for one person
The Community edition ships the extensions that make a personal assistant
complete on day one, among them:
- Your own tool servers through MCP, and your own Google account through Google Workspace.
- Your own models and keys, chosen per conversation, including signing in with a ChatGPT subscription.
- Reaching the assistant through Telegram or voice.
- Scheduled runs, goals, and searching your own earlier conversations.
- A configuration assistant that edits your instance's settings from a chat — because nobody else administers it for you.
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:
| Area | What it is |
|---|---|
| Organizational memory | Knowledge curated for the whole organization and offered before someone repeats a known mistake |
| Sandbox | Each conversation runs in an isolated workspace (Linux only); access profiles that limit a user to some repositories rely on it |
| Team systems | Redmine issues, Gitea pull-request review, Slack, links to the source host |
| Source-control workflow | A branch per conversation, the Push button, Subversion, file-share sync, GitHub sign-in |
| Operations | Operator-managed remote execution over SSH, port forwards, log-collection conversations; personal SSH tools are available in both editions |
| Browser folders | Attaching 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.