Aletheia is currently under development. For early access,contact us.

Aletheia
Sign up

Section

Operations

Local EngineDeploymentObservabilityBenchmarkingSecurity ModelTroubleshooting
Local Engine

The Local-First Memory Engine

Development shouldn't stop when the internet does. Aletheia's local engine allows you to build, test, and refine your AI agent's memory right on your laptop.

Why we built a local sidecar

Most AI memory solutions force you to send every test query to a distant cloud server. This is slow, expensive, and makes integration testing a nightmare. We built the Aletheia engine in Rust so it can run as a lightweight sidecar directly in your development environment.

What this means for your workflow:

  • Instant Iteration: Test your memory schemas and retrieval quality with sub-10ms latency. No network round-trips required.
  • Robust Integration Testing: Run your entire agentic flow in a CI/CD pipeline or locally without needing a cloud API key.
  • Privacy by Default: Keep sensitive user data on your machine while you are in the "lab" phase of your project.
  • Benchmark Readiness: Evaluate how your agent handles thousands of memories using our local benchmark harness before you ever ship to production.

Best practices for local development

To get the most out of the local engine, we recommend a few simple habits:

  • Isolate Your Data: Use a dedicated cache directory for your local development memories so they don't interfere with your production state.
  • Mirror Production: The local engine uses the exact same HTTP API surface as our cloud deployment. This means you can switch from local to cloud by changing a single environment variable—no code changes needed.

How the SDK finds the engine

The Aletheia SDK is smart about finding your local binary. It follows a clear resolution path:

  1. Explicit Path: You can tell the SDK exactly where your binary lives.
  2. Environment Variables: Set ALETHEIA_BINARY_PATH to override defaults.
  3. Repo-Local: It looks in target/release/aletheia if you've just finished a fresh build.
  4. SDK Cache: If no binary is found, the SDK can automatically download and cache the latest signed release for your architecture.

Ready to see it in action? Head over to the [Quickstart](/docs/quickstart) to launch your first local instance.