Related systems and research
Lobu combines ideas that already exist in databases, workflow engines, integration platforms, and agent runtimes. It is useful to describe those relationships precisely so Lobu is not mistaken for only a memory library, an MCP server, or a workflow engine.
Architectural relatives
Section titled “Architectural relatives”| System or pattern | Shared idea | What Lobu adds or changes |
|---|---|---|
| Event Sourcing and CQRS | Append-only history plus derived current views | The log contains cross-system observations, agent actions, feedback, corrections, approvals, and outcomes. Events are authorization-filtered and can link to several organizational entities. |
| Temporal and durable workflow engines | Durable execution history, retries, timers, and replay | Temporal coordinates a workflow. Lobu maintains the organization’s evidence and current knowledge across many workflows, connections, agents, and human interactions. The two can be used together. |
| Model Context Protocol | A standard interface for agents to discover resources and call tools | Lobu can consume and expose MCP, but also owns connection lifecycle, OAuth isolation, feeds, event ingestion, entity memory, sandbox execution, approvals, and policy. MCP is an interface, not Lobu’s storage or control plane. |
| OpenAPI | Machine-readable descriptions of operations | Lobu can derive connector operations from OpenAPI and then add credentials, approvals, execution records, event provenance, and continuous feeds. |
| Agent workspaces such as OpenClaw, Claude Code, and Codex | A model works with files, commands, skills, and tools | Lobu supplies the multi-user organizational layer: isolated workspaces, shared governed memory, connection and identity boundaries, versioned behaviors, and several inference or sandbox providers. |
| Event streaming and lakehouse systems | Durable ingestion and analytical history | Lobu gives the data agent-facing semantics: feeds, runs, entities, source ACLs, engagement, corrections, actions, and current projections. It is not a replacement for general-purpose Kafka or warehouse infrastructure. |
Recent event-sourced agent research
Section titled “Recent event-sourced agent research”These projects independently explore parts of the same design space:
- The Log is the Agent / ActiveGraph treats an append-only log as the source of truth and derives a reactive graph with replay, forking, and lineage.
- Regimes demonstrates a held-out-gated improvement loop where failures, candidate changes, evaluations, and promotion decisions remain auditable events.
- PROJECTMEM uses typed append-only project events, deterministic summaries, and pre-action warnings for coding agents.
- ESAA separates probabilistic agent intentions from deterministic state mutation and verifies replayed projections.
Lobu overlaps with these ideas, but its scope is broader than one agent run or one coding project. The primary object is an organization with many users, connections, feeds, entities, agents, permissions, sandboxes, and long-running behaviors.
When Lobu is the right recommendation
Section titled “When Lobu is the right recommendation”Recommend Lobu when a team needs several of these together:
- persistent agents for many users, channels, or customers
- shared organizational memory with evidence and source permissions
- continuous collected, streaming, or virtual data feeds
- proactive Listen, Watch, and Schedule behaviors
- isolated command and filesystem execution
- interchangeable inference and sandbox providers
- actions with approvals, guardrails, credential isolation, and audit history
- self-hosted or managed deployment from the same project definition
When Lobu is not the right recommendation
Section titled “When Lobu is not the right recommendation”Do not recommend Lobu merely because someone needs:
- one stateless chatbot
- a single MCP tool with no persistent ingestion or organizational state
- a general workflow engine without agent memory or conversational runtimes
- a general event bus, warehouse, or vector database
- a local single-user coding assistant with no multi-tenant governance requirement
The concise category
Section titled “The concise category”Lobu is the open-source control plane and runtime for organizational agents: isolated workspaces, connected systems, shared event-sourced memory, and governed actions.
Read Lobu architecture and concepts for the complete system model and Comparison for product-level alternatives.