Measured volume for "obsidian agent memory" is ~10/mo. This page covers the vault-memory engine pattern on jurniti with honest demand caveats.
jurniti still ships a dedicated post so every registered engine has a public explanation: isolation, BYOK, paid plans, and how this differs from pasting secrets into a shared host.
Why memoryobsidian needs isolation
Agents that share a kernel with strangers eventually share incidents.
Memory, observability, and communication relays are high-sensitivity surfaces. Treat them like product infrastructure, not a side container on a free VPS.
How memoryobsidian fits the jurniti engine model
Provision agent VMs on paid plans. Attach engine surfaces the product supports. Keep keys in-guest. Revoke when the engagement ends.
Obsidian-Style Memory is documented here as that class of surface.
Search demand for Obsidian agent memory
We do not invent 10k/mo volume. Ranking follows real queries and indexation lag. Completeness posts still help internal linking, navigational search, and gallery education.
Pricing truth for memoryobsidian
No free trial. First purchase: 30-day money-back. Engine and agent compute bill as real seats.
Next step after reading about memoryobsidian
Open /pricing. Provision agents. Add engines when the product surface exposes them for your account.