LogMem Product Plan
LogMem is the public product name. It is built on the ACMI protocol. ACMI is only the internal protocol name. The open-source release is free under the MIT license. Paid work is an audit, a done-for-you build, a monthly retainer, or a dedicated stack for one client on Elestio.
The Pitch
LogMem coordinates fleets of AI agents. LogMem is built on the ACMI protocol. The protocol keeps state in three Redis keys: Profile, Signals, and Timeline. These keys replace 800 lines of agent memory code. A custom LogMem deployment uses Qdrant. Core operations do not use a knowledge graph. Core operations do not call an LLM. A read completes in under 5 ms. LogMem works with any model, and it works with every agent framework.
User Personas
🛠️ Indie AI Builder
Who: A solo developer who builds multi-agent tools with Claude Code, Cursor, or a similar tool.
Pain: Agents lose context between sessions. Coordinating 2 to 5 agents is hard to do at a low cost.
Value: The free open-source release covers this fleet. Setup takes about 10 minutes. LogMem speaks MCP.
🏢 Startup CTO
Who: A CTO who leads an AI team of 5 to 20 people and ships autonomous agent products.
Pain: Coordination breaks as the fleet grows. The team cannot see what agents are doing, and agents repeat the same work.
Value: The lock protocol stops conflicts. The fleet dashboard shows the whole fleet.
🔬 Research Lab
Who: An academic or corporate team that studies multi-agent systems.
Pain: The team needs a coordination baseline that another team can repeat.
Value: The license is MIT. The audit trail is a log of events. The design is easy to benchmark.
Pricing Tiers
The audit, the done-for-you build, and the retainer replace the old software subscription tiers. A dedicated Elestio stack is quoted on request.
| Tier | Price | Included |
|---|---|---|
| LogMem Open Source | Free. MIT license. | The full protocol, the CLI, and the MCP server. You host it yourself. |
| LogMem Audit | $497 | An audit of a LogMem setup. |
| LogMem Done for you | $2,500+ | LogMem work delivered for the client. The price starts at $2,500. |
| LogMem Retainer | $500-1,500/mo | Ongoing LogMem work, billed each month. |
| LogMem dedicated Elestio stack | Contact us | A separate LogMem stack for one client, deployed on Elestio. |
| LogMem Enterprise | Contact | On-premise deployment, an SLA, custom integrations, and dedicated support. This row is separate from the dedicated Elestio stack. |
MVP Scope
These lists stop at v1.2. This page does not add later versions or new features.
✅ Shipped (v1.0–v1.2)
- Profile, Signals, Timeline CRUD via CLI
- Communication Standard v1.1
- Lock Protocol for duplicate-work prevention
- MCP Server (14 tools, stdio transport)
- Agent extensions: spawn, bootstrap, active context, rollups
- Work Items for cross-session projects
- Multi-stream cat view
- Anti-dead heartbeat monitoring
🔄 Next (v1.3)
- Webhook ingestion pipeline (Gmail, Slack, Stripe)
- Multi-tenant workspaces with namespace isolation
- REST API gateway (for non-MCP agents)
- Fleet dashboard (real-time visualization)
📋 Roadmap (v2.0)
- Schema validation layer (reject malformed events at storage)
- Reinforcement learning loop with persistent quality scores
- Memory adapter interface (Hindsight, Mem0, Zep plugins)
- npm package as standalone install
- Conformance test suite for third-party adapters
Ship Timeline
| Phase | Timeline | Key Deliverables |
|---|---|---|
| Phase 1: Indie Dev Hero | Months 1–6 | Manifesto essay. npm package. Five YouTube explainers. Show HN launch. Benchmark numbers. |
| Phase 2: Thought Leader | Months 6–18 | Conference talks. arXiv preprint. Podcast circuit. Target of 10K stars. |
| Phase 3: Founder Cred | Months 18–36 | Fundraise decision gate. Book deal. Possible foundation donation. |
Competitive Moat
- Fleet primitives. LogMem ships the Lock Protocol, anti-dead heartbeats, and an RL cycle. No other memory system ships this set.
- Node.js first. Most competitors are Python only. LogMem targets the JavaScript and TypeScript gap. LogMem is built on the ACMI protocol.
- Redis keys, plus Qdrant on custom deployments. The core path does not use SQL. A read completes in under 5 ms. Core reads do not depend on an LLM. A custom deployment uses Qdrant.
- MCP. LogMem works with every MCP-compatible tool. MCP is a growing standard.
- Names. LogMem is the public product name. ACMI is only the internal protocol name. The brand idea is Agent Context Engineering.
Distribution Strategy
- Show HN. Use the title "Three Redis keys for multi-agent memory." The post is there to earn technical trust.
- Twitter/X threads. Post threads of 8 to 12 messages that show the 10-line quickstart.
- YouTube. Publish "Profile / Signals / Timeline in 5 minutes" each week.
- Conference circuit. AI Engineer World's Fair, AI Tinkerers, and the Latent Space podcast.
- Dev communities. r/LocalLLaMA, r/MachineLearning, Dev.to, and Hashnode.
- Newsletter.
theagentcontext.dev, sent each week. It can continue if the product plan changes. - Developer relations. Contact swyx, Cole Medin, Charity Majors, and the developer-relations teams at Upstash or Redis.