Comparison
Memtro vs building it yourself
A vector database, a few connectors and a cron job, versus the parts you would end up building anyway.
It is tempting to wire a vector database to a few APIs and a cron job. Here is what that project turns into, and what Memtro already is.
The parts you end up building
| Week | What you build | What it needs to actually work |
|---|---|---|
| 1 | Embeddings into a vector database | Chunking, dedupe, a way to delete and correct facts, hybrid search because vectors alone miss names and ids |
| 2 | A chat endpoint | OpenAI compatibility so existing tools work, streaming, tool calls, per-user keys, organisations |
| 3 | A couple of connectors | OAuth with refresh, token encryption, read-only guarantees, caching so agent loops do not hammer APIs |
| 4 | Entity extraction | Aliases and external ids so "Sam Lee", "sam@bigco.com" and HubSpot contact 900 are one person; supersession when facts change; provenance |
| 5 | An agent loop | Parallel tool calls, delegation, step budgets, cross-referencing instructions, progress streaming |
| 6 | Scheduling | A runner with locks, timezones, run history, where results go |
| 7 | Personal vs shared | Classifying facts so one person's preferences do not become company knowledge |
| 8 | Sandboxing | If agents run code: containers with no capabilities, no mounts, limits |
What Memtro gives you on day one
- The OpenAI-compatible endpoint and MCP server, with per-user keys and organisations.
- Typed, time-aware memory with supersession, provenance, aliases and external ids, hybrid retrieval and nightly consolidation.
- Fifteen read-only connectors with OAuth, encryption, caching, deterministic anchoring and hourly sync.
- Routing by difficulty, agent mode with cross-referencing and delegates, OpenCode and Claude Code engines in sandboxes.
- Jobs created from chat, with run history and reports in saved chats.
- A dashboard for all of it.
When building it yourself is right
When the memory is a feature inside a product you sell, with requirements Memtro does not have. For the internal case, the company memory everyone's tools share, the parts above are the whole product, and they are built.