Skip to main content
Guide
Embedded clients execute operation-tree requests without HTTP. The process opens a writer or read-only handle against memory, disk, or S3-compatible object storage.

Install

Install the forthcoming v3 SDK and its embedded runtime package. These package commands describe the upcoming release and are not expected to resolve before the v3 SDKs are published.

Open a writer

Choose a storage source

Configure caches

Cache configuration is optional and fixed when the handle opens. Omit it to use these defaults: Pass an explicit cache configuration to change the vector-memory budget or enable bounded disk caches:
Cache byte budgets bound those caches. They are not a hard cap on total process RSS; requests and index work can allocate transient memory.

Open a read-only database

Use a read-only handle for processes that must never mutate the database. It opens an existing disk or object-storage database, executes read requests, and rejects writes.

Embedded request rules

  • Use the same QueryRequest and response contract as server mode.
  • Writer handles can execute read and write requests.
  • Server routing options such as writer-only, warm-only, API headers, and durability headers are rejected because there is no gateway.
  • Reopen the same disk or object-storage source to retain canonical data across process lifetimes.

Next steps

Local server

Run the production-shaped HTTP interface on your machine.

Deployment options

Compare local server, embedded, and Cloud execution.