Hosted + Local Agent Memory
Agent memory built like boring infrastructure.
memnode treats memory as a database problem. You get typed provenance, a shared hosted control plane, a Rust data plane, and the local MCP path for teams that still want everything on their own machine.
Use it for persistent coding conventions, cross-session chat memory, research workflows with explicit sources, or a long-lived memory substrate behind your own agents.
- Sign up with Supabase Auth and create an account.
- Provision one hosted tenant through the control plane.
- Create a scoped API token and call the Rust data plane over HTTP.
Dashboard auth, hosted tenant provisioning, scoped API tokens, daily quota enforcement, and the local MCP path are now wired together.
Typed provenance
Memories carry observed, reported, inferred, or hypothesized status instead of collapsing into one flat blob.
Hosted tenants
Provision a shared hosted tenant in the dashboard, mint API tokens, and keep quota and billing in one place.
Local MCP stays
The hosted product does not replace local usage. You can still run `memnode mcp` over stdio on your own machine.
Rust data plane
A signed-control-plane path, multi-tenant registry, and hot-path token cache keep hosted latency practical.
Example Shapes
Three concrete ways teams use memnode
Conversational assistant
Persist user preferences and past turns across restarts using the standard recall -> answer -> record loop.
Coding assistant
Store project conventions as typed entities instead of free-form notes, then recall them as structured context.
Research agent
Track claims with explicit provenance so later answers can separate reported facts from inferred conclusions.
Start free, keep local in reserve
The hosted SaaS is for fast onboarding, quota-managed tenants, and shared team workflows. The local mode stays available when you need offline or self-managed memory instead.