Own Your Agents · 02.05
Local-First Data & Zero External Services
Embedded SQLite, a bundled offline embedding model, and a content-addressed local asset store — how Agentis runs complete on your own machine.
What's actually on your disk
Everything durable lives under one directory, AGENTIS_DATA_DIR (default ./.agentis): the SQLite database holding every agent, memory episode, workflow, and run; an encrypted secrets store; per-agent managed home directories; and versioned backups. There's no hidden second database in a vendor's cloud that the local install is secretly a cache in front of — the SQLite file is the source of truth.
Semantic memory without a network call
Recall in the Brain depends on embeddings — and Agentis ships a bundled offline ONNX model (e5-small) as the default embedding provider, so semantic search over memory works from the very first boot, before any API key is configured for anything. This is a specific, checkable claim: disconnect the network, and recall still works, because nothing about turning text into a vector requires leaving the machine.
Generated content is deduplicated, not duplicated forever
Every image, document, and generated artifact an agent produces lands in a content-addressed asset store under AGENTIS_ASSETS_DIR, keyed by SHA-256 of its content. Generating "the same" output twice — the same image prompt, the same extracted document — costs zero additional storage; the store recognizes the identical hash and reuses the existing blob.
What this buys you, concretely
No account to create before the platform does anything useful. No data residency question to research before a compliance review, because there's no third party holding a copy by default. No feature that silently stops working when a vendor changes their pricing or deprecates an endpoint, because the Brain's core loop — write memory, recall memory — never depended on that vendor to begin with. What you attach externally (a model runtime, a channel, a media provider) is opt-in and additive, covered per-topic across Reach and the SDK.
Continue
The mechanics behind bootstrap and spawn: how a durable agent identity gets bound to a runtime adapter and a credential vault.
Encrypted, portable exports of an entire workspace — share it, sell it, or back it up. The profile is the secrets boundary.