Open source. Self-host or use Lobu Cloud.

Give every agent the context of your company.

Bring ChatGPT, Claude, Codex, OpenClaw, or any agent. Give each one durable company context, scoped access, human approvals, and a complete audit trail.

Try Lobu
app.lobu.ai/acme/activity
AAcmeRecent
Search…Agent scoutApproval: PendingFilters Sort: Newest first4,545 events
nowCreate renewal-risk issueon GitHub (App install)Requested by scout · approval requiredTitle *Acme renewal at risk · moved to Jun 30Labels Add items...ConfirmReject
append-only1 awaiting approval
Open Lobu and start building →
#revenueTony · Acme
TS
Tony@slackbot is Acme at risk?
sb
slackbot APPRenewal moved to Jun 30, P1 #482 reopened, and ACME-214 was escalated.
Add to Slack →
app.tsservice · Acme
import { searchMemory } from "@lobu/client"
 
const { data } = await searchMemory({
  path: { orgSlug: "acme" },
  body: { query: "renewals at risk" },
})
 
data.entity?.name
// "Acme Corp"
data.content?.[0]?.title
// "P1 #482 reopened"
data.content?.[1]?.title
// "ACME-214 escalated"
Client SDK docs →
claude code
> Which customers are at risk this quarter?
lobu · mcp · reading Acme context · Tony scope
Acme Corp · renewal Jun 30 · P1 #482 reopened
ACME-214 escalated
>
▸▸ auto Opus 5 · 1M context
Install to your Claude →

The same durable company context, everywhere your agents work.

Works with
ChatGPTClaudeCodexOpenClawAny MCP client
Connects to
DiscordGitHubGmailGoogle CalendarGoogle ChatHacker NewsLinearMicrosoft TeamsPostgreSQLProduct HuntRedditRSS / AtomSlackTelegramWhatsApp CloudX (Twitter)YouTube+5 more
[ 01/THE MULTIPLAYER OPERATING LAYER ]

The context agents need. The control people keep.

Sources stay inspectable, access stays scoped, and consequential actions stay under policy.

01

One current company state

Connect systems once. Resolve their events into current, source linked company context.

02

Identity follows the user

Each request inherits the right user, team, device, credential, and task scope.

03

Govern action, not intent

Agents prepare the work. Policy decides when a person must approve the exact action.

04

Every outcome becomes context

Approvals, corrections, and completed actions become durable context for whoever works next.

[ 02/AUTOMATIONS ]

Turn new events into repeatable work.

An Automation is a versioned job that wakes on an event or schedule, reads only what is new, and saves or proposes the next outcome.

Renewal risk

Keep every agent current as renewal signals arrive.

salesforce.opportunity.updated + slack.message

Wakes on a relevant change

A renewal date moves or a customer asks for an executive sponsor.

account_context

Reads only the new window

The Automation combines unprocessed events with a named, read-only SQL view of the account.

customer_risk + approval.requested

Saves a governed outcome

It updates shared account risk and proposes the follow-up task for your approval.

Connector subscriptions and syncs append durable events. Each Automation advances through only its unprocessed event window.

How Automations work →
[ 03/TWO WAYS IN ]

Bring any agent. Add shared context.

Use the agents your team already trusts. Managed agents are optional.

Start here

Bring your agents

Connect ChatGPT, Claude, Codex, OpenClaw, or any MCP client to the same company context, scoped to each user.

Connect an agent →
Optional runtime

Build a managed agent

Run repeatable work from live events or schedules under the same approval policy.

Build a managed agent →
[ 04/UNDER THE HOOD ]

One control plane. Any agent.

Share context, permissions, approvals, and connected actions with any agent. Add Lobu's runtime only when you need it.

Halftone figure: multi-socket plug bank
Halftone figure: stacked storage drives
Halftone figure: vacuum tube in a ceramic socket
Halftone figure: sealed glovebox isolation chamber
Halftone figure: balance scale with calibration weights
Halftone figure: freight container on a crane hook
Halftone figure: oscilloscope with waveform
01·CONNECTORS

Plug into everything.

22+ connectors (Slack, GitHub, Gmail, Linear, Postgres and more) stream events in, and actions flow back out under scoped identities. Anything with an API fits the connector SDK.

Connect your first agent to company context.

Connect any agent to shared context and keep consequential actions under approval.

Status:// connecting agent…
For humans For agents