Proactive agents that never forget.
Build autonomous agents that take action and stay reachable from any chat or AI client.
Companies
3 records · Market memory
Structured company memory your agents can recall and update.
Turn data into shared, structured memory.
Tell one agent something and the rest already know. Lobu Memory gives every agent the same typed entities and event history, recalled through MCP when it matters.
Read the memory guideGive your agent new capabilities.
A skill bundles everything an agent needs to do something: instructions, tools, and access, all in one folder. No glue code, no IT ticket. Drop it in and the agent picks it up.
Explore skills--- name: github-triage network: allow: [api.github.com] nixPackages: [gh] mcp: - github --- # Triage every new issue - Pull recent issues - Cross-reference owners - Comment with the next step
Turn schedules into agents that act on their own.
A watcher wakes on a schedule, reads recent activity, filters with a prompt you wrote, and writes the signal (not the noise) into entity memory. The agent isn't online, but the memory is moving.
How watchers workTalk to your agents from any chat or AI client.
Lobu agents live where your team already works: Slack, Telegram, Discord, Teams, WhatsApp, Google Chat. Or pull them into ChatGPT, Claude, Cursor, and any MCP-capable client over the same protocol.
Connect via MCPYou own your data.
Run open-source Lobu on your own servers for full control over your data and credentials, or use our managed runtime. With per-second billing you only pay for the time your agents are awake.
Self-host guide- ✓Open-source code
- ✓Run on your servers
- ✓Your data, your keys
- ✓We run the infra
- ✓Scale to zero when idle
- ✓Per-second billing
One gateway, isolated workers, no leaked secrets.
Lobu receives messages at the gateway, starts sandboxed worker processes on demand, and proxies tools, memory, and credentials so agents stay isolated from your real keys.
- Link users across platforms with single sign-on
- Approval flows, rich cards, buttons, and more
- Workers never see secrets
- HTTP proxy with domain allowlist
- MCP proxy with per-user OAuth
- BYO provider keys (Anthropic etc.)
- One sandbox per user and channel
- Subprocess isolation with just-bash virtual filesystems
- systemd-run hardening on Linux production hosts
- No direct internet access (gateway proxy only)
- Nix reproducible environments
- OpenTelemetry for observability
One memory schema, every record type.
Members, assets, topics. Extend the schema with your own objects and define how they relate. Lobu Memory routes events, embeddings, and watchers along those edges automatically.
- Identity
- Preferences
- Decisions
- 5 more attributes
- Valuation
- Transaction
- Source
- 3 more attributes
- Summary
- Watchers
- Linked records
- 2 more attributes
- Identity
- Preferences
- Decisions
- 5 more attributes
- Valuation
- Transaction
- Source
- 3 more attributes
- Summary
- Watchers
- Linked records
- 2 more attributes
Start with the
free open-source build.
Latest blog posts
Filesystem vs Database for Agent Memory
Agents need a workspace to think in and a warehouse to remember in. The filesystem is for ephemeral work. The memory layer is for durable organizational knowledge.
MCP Is Overengineered, Skills Are Too Primitive
MCP HTTP is great for external services. MCP stdio is redundant. And most skill systems are just prompt text with no reproducibility. Here's what we built instead.
Introducing Lobu
From a Slack bot to multi-tenant OpenClaw infrastructure — the story behind Lobu.