Product Plan
ACMI's commercial strategy: open protocol + paid cloud layer. The same model as Next.js→Vercel, Postgres→Supabase, MCP→Anthropic.
The Pitch
ACMI is the coordination backbone for AI agent fleets. Three Redis keys — Profile, Signals, Timeline — replace 800 lines of agent memory code. No vector databases. No knowledge graphs. No LLM calls for core operations. Sub-5ms reads. Model-agnostic. Works with every agent framework.
User Personas
🛠️ Indie AI Builder
Who: Solo dev building multi-agent tools. Uses Claude Code, Cursor, or similar.
Pain: Agents lose context between sessions. No cheap way to coordinate 2-5 agents.
Value: Free tier covers their fleet. 10-minute setup. MCP-native.
🏢 Startup CTO
Who: Leading a 5-20 person AI team. Building autonomous agent products.
Pain: Agent coordination breaks at scale. No observability. Duplicate work.
Value: Lock protocol prevents conflicts. Fleet dashboard shows everything.
🔬 Research Lab
Who: Academic or corporate research team studying multi-agent systems.
Pain: Need a reproducible coordination baseline for experiments.
Value: MIT license. Event-sourced audit trail. Benchmark-friendly.
Pricing Tiers
| Tier | Price | Included |
|---|---|---|
| Open Source | Free forever | Full protocol, CLI, MCP server, MIT license. Self-host with your own Redis. |
| Hyvmynd Cloud | $0 (free tier) / $29/mo (pro) | Managed Upstash hosting, fleet dashboard, webhook ingestion, multi-tenant workspaces. |
| Hyvmynd Studio | $49/mo | Visual debugger for Profile/Signals/Timeline, fleet visualization, team collaboration. |
| Enterprise | Contact | On-premise, SLA, custom integrations, dedicated support. |
MVP Scope
✅ 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, 5 YouTube explainers, Show HN launch, benchmark numbers |
| Phase 2: Thought Leader | Months 6–18 | Conference talks, Hyvmynd Cloud beta, arXiv preprint, podcast circuit, 10K stars |
| Phase 3: Founder Cred | Months 18–36 | Fundraise decision gate, Hyvmynd Studio launch, book deal, possible foundation donation |
Competitive Moat
- Fleet primitives — Lock Protocol, Anti-Dead Heartbeats, RL cycle. No other memory system ships these.
- Node.js-first — Most competitors are Python-only. ACMI targets the JS/TS ecosystem gap.
- Redis-native thesis — Anti-SQL opinion. Sub-5ms reads with zero LLM dependency.
- MCP-native — Works out of the box with every MCP-compatible tool. Growing standard.
- Brand strategy — Anchor on the idea ("Agent Context Engineering"), not the artifact. Protocol-not-product positioning.
Distribution Strategy
- Show HN — "Three Redis keys for multi-agent memory." Technical credibility play.
- Twitter/X threads — 8-12 tweet threads showing the 10-line quickstart.
- YouTube — "Profile / Signals / Timeline in 5 minutes" weekly series.
- Conference circuit — AI Engineer World's Fair, AI Tinkerers, Latent Space podcast.
- Dev communities — r/LocalLLaMA, r/MachineLearning, Dev.to, Hashnode.
- Newsletter —
theagentcontext.dev— weekly, survives pivots. - Developer relations — Cold outreach to swyx, Cole Medin, Charity Majors, Upstash/Redis devrel.