45ms
median recall, measured on one laptop, zero cloud calls
Uteke is agent memory that runs on your infrastructure. Swap your base URL and key. Nothing else about your stack changes.
Private beta. One email at launch, nothing else.
1
static binary, zero dependencies
2 env vars
is the whole integration
0
cloud calls in the recall path
768-dim
local embeddings, no API key
The open-source core is a single binary your agents talk to over MCP. Uteke cloud runs that core for you: same API, managed, in a single EU region. No telemetry, by design.
UTEKE_BASE_URL=https://mem.yourco.dev
UTEKE_API_KEY=utk_live_…
# point it back at your box to leaveThe managed API is the same contract as the open-source core: plain JSON over HTTPS. The open-source docs describe every field.
POST /remember
{ "content":
"Payments need idempotency keys",
"tags": ["backend"] }Written once. Embedded and indexed on arrival.
POST /recall
{ "query":
"how do we avoid double charges?",
"limit": 5 }Keyword, vector, and rank votes fuse into one ordering. No mode to pick.
on schedule
duplicates merge
stale rows decay
contradictions surfaceMemory stays small and current without a cleanup ritual.
1.00
recall@5 on the fast50 eval, hybrid fusion on
1.00
rebuild parity: a fresh index matches the old one, exactly
CPU
embeddings run on-device. No GPU, no provider bill
EU
one region, no telemetry, no third parties on the memory path
Harness and raw results are public in the open-source repo.
The beta is invite-first. Self-hosted stays free and Apache-2.0, forever. Join the list and hear it first.
join_waitlist →