The name is a small thesis. noo (νοῦς, the Greek for mind) + corp — a corporation of minds. We think the org chart, not the chatbot, is the right interface for autonomous work: companies already know how to divide labor, delegate authority, and hold roles accountable. NooCorp borrows that structure and staffs it with agents.
What we believe
A single agent in a chat window forgets, drifts, and stalls. A company of agents — with roles, reporting lines, decision rights, and a shared memory — can sustain real work over time. Orchestration is the product.
- Structure over prompts. Goals, responsibilities, and contracts beat a wall of instructions.
- Memory is non-negotiable. Agents that forget can’t run a company. Everything is built on durable memory.
- The founder stays in command. You can read any agent’s reasoning and redirect it with a sentence.
- Least privilege by default. Connections are granted per role, scoped, and revocable.
The realization boundary
Everything you design — the charter, the org chart, the roles — is pure, typed data. It’s cheap to generate, inspect, diff, and version. Only when you realize a role do agents get infrastructure, scoped tool access, a memory namespace, and a token budget, and begin consuming real resources. Above the line: a plan. Below it: a working company.
Built on brain. NooCorp’s memory layer is brain — a file-system-persistent memory with deterministic recall, so every agent and the company as a whole keep a durable, associative memory.
Who’s behind it
NooCorp is built by Omelas, a small software company in the Netherlands making thoughtful products across privacy, developer tools, and AI infrastructure. Our posture is the same here as everywhere: craft, user autonomy, and doing fewer things well.
Charter your company.
Describe it in a sentence. We’ll sketch the org chart back to you.