Context storage for agentic apps

Context storage for AI agents.

Your agents store user context and recall it as a prompt-ready block. Every user gets their own isolated store — created on first write, built on LodeDB, the open-source embedded vector engine.

1import orecloud
2
3client = orecloud.Client()
4memory = client.store("user-42")
5memory.add("likes hiking near Seattle")
6context = memory.context_block("plan my weekend")

One store per user, created on first write. Recall returns a prompt-ready block.

How it works

Name a store per user

A store name is the whole setup — the first write provisions it. No create step, no collections to manage.

Agents add memories

Writes are concurrent and read-your-writes. Attach TTLs to expire, or agent_id and run_id for provenance.

Recall in one call

Pass the raw message to get a prompt-ready context block — or point any MCP client at the store's endpoint.

Use cases

Support agents

Voice and chat agents recall the relationship, not just the ticket.

call 1 · mon

Still nothing back on that cancelled flight.

add
storeuser-7d2f
refund pendingrun-9114
prefers SMS over email
fee waiver promisedrun-8842
recall
call 2 · thu

Your refund cleared this morning — confirmation is in your texts.

Shopping assistants

A correction made once holds across every future session.

session 1

Too flashy — I never wear logo prints.

add
storeuser-58a2
never suggest logo prints
wears EU 38, likes linen
budget around €120
recall
session 2

Twelve plain linen picks, all under €120.

Coding agents

Memory written in one tool is recalled in another — any MCP client, no app code.

claude code

Stop using pip — this repo is uv-only.

add
storeuser-04dd
repo is uv-only, never pipclaude-code
deploys go through CI only
prefers small, reviewed diffs
recall
cursor

Set up with uv sync — pip never touched.

What you get

One database per user

Isolation is structural — delete the store and the user is forgotten.

Prompt-ready recall

Pass the raw message, get back a fused context block in one call.

Hosted MCP per store

Every store is an MCP endpoint — agents connect with one command.

01Server-side embeddingspick a preset, no pipeline to run.
02Concurrent writesdurable, ordered, read-your-writes.
03Memory TTLsplus agent_id and run_id provenance.
04Text double-gatedrank with any key, but never read.
05Environment-bound keysswap the key for testing or production.
06Metrics-only telemetrywe never read your stored text.
07Open formatpull your store out to disk anytime.
08Python SDK + CLIfour lines to store and recall.
No lock-in

A store is just LodeDB — pull it down and open it locally.

The store IS the open-source on-disk format. Pull one to disk and open it with the embedded engine — the read API is identical. No export step, no proprietary conversion.

orecloud pull orecloud://acme/production/user-7d2f ./user-7d2f <index-key>
# open locally — same read API
db = lodedb.LodeDB(path="./user-7d2f")

Give your agents memory.

Request access