Aletheia
Log in
Local Engine

Local Engine

The local engine exists so teams can evaluate retrieval quality, iterate on memory schemas, and test agent flows without immediately standing up hosted infrastructure.

What local mode is good for

  • Laptop development
  • Integration tests
  • Benchmark runs
  • SDK onboarding

Recommended behavior

  • Bind the engine to loopback.
  • Store data in a cache directory dedicated to local development.
  • Reuse the same HTTP API surface as the cloud deployment where practical.

Binary resolution

  1. Explicit binary path
  2. Environment variable override
  3. Repo-local target/release/aletheia
  4. Cached binary in the local SDK cache
  5. Manifest-driven download