Why Codumentor
Six things a real organization AI must get right
Any assistant can generate code. Codumentor is built for regulated enterprises, where the data must stay home, every step must be visible, and nothing runs without permission.
01
Automatically evolving organization memory
The knowledge base writes and corrects itself. Curator agents run after every exchange, learning from your user interactions, documents and git repositories — naming conventions, historical decisions, undocumented workarounds — then dedupe and refine what they find. Relevant insight is surfaced as a Rapid Direction Cue before anyone goes down the wrong path.
curator agents · vector search · self-correcting
02
Data sovereignty
Nothing sensitive ever leaves the house. The whole system runs entirely on-premise, or on your own company IAAS. Your code, conversations and documents stay on your infrastructure. Use the EU-hosted model from ARDINSYS, or bring any OpenAI-compatible LLM you already trust — self-hosted included.
on-prem · your IAAS · bring-your-own-LLM
03
Full transparency
Follow every step Codumentor takes. Each tool call, file change and agent decision is written into the conversation timeline as it happens. Nothing runs silently, so every answer stays auditable — down to the exact file and line it relied on.
live timeline · full audit trail
04
Full control
Any tool usage asks for your permission first. Every file write, shell command and external API call pauses for your approval. Define reusable approval rules so routine, safe operations pass through and only the risky ones stop for a human.
explicit approvals · approval rules
05
Premium security sandbox
Every tool runs inside a bwrap sandbox. Codumentor's actions are isolated from the host at the kernel level, so a command can only ever touch what you have explicitly granted it. No ambient access, no surprises reaching your wider systems.
bubblewrap · kernel-level isolation
06
Ultra-fast workspace isolation
Each session gets its own workspace in a flash. Fresh, disposable workspaces spin up instantly and are never shared between sessions — containing the blast radius of any single task and layering a second boundary on top of the sandbox for defense in depth.
per-session workspace · instant · defense-in-depth