OreCloud

Portability

Pull a store to disk and open it locally — your data is never trapped.

A store is the open-source LodeDB on-disk format — the cloud and the embedded engine share one implementation of it. There is no export step and no proprietary conversion: pull the committed store down and open it with the embedded engine.

pip install lodedb
orecloud pull orecloud://<org>/<environment>/user-42 ./user-42 <index-key>
import lodedb

db = lodedb.LodeDB(path="./user-42")
db.search("hiking", k=5)

pull verifies every artifact's checksum against the manifest and proves the copy opens through the engine before it reports success.

The read API is identical

The cloud handle duck-types the local lodedb.LodeDB read surface — hits are (score, id, metadata) rows either way — so RAG adapters and MCP tool bodies written against a local index work against the hosted copy unmodified, and vice versa.

Redaction posture

What leaves a machine is explicit. Pushes of local stores are redacted by default (no raw text ships unless you pass --include-text), and cloud stores only return text under the double gate described in Keys & environments.

On this page