Actian VectorAI DB vs DOOM MCP

Actian VectorAI DB is a portable vector database designed for AI applications that can't or won't rely on cloud-native infrastructure. It runs consistently across embedded devices, edge deployments, on-premises servers, and hybrid environments with a claimed 22x query-per-second advantage over Milvus and Qdrant at 10M vectors. The "build once, deploy anywhere" promise is aimed squarely at enterprise teams who need deterministic behavior across heterogeneous environments. The core technical differentiation is portability without performance compromise. Most high-performance vector databases are architected for cloud-native deployment and degrade significantly when moved to constrained environments. Actian's approach maintains performance characteristics across deployment targets while giving teams full data ownership — a growing concern for regulated industries and AI systems handling sensitive data. Product Hunt received the launch warmly, landing 177 upvotes on day one. The free pricing tier removes the usual barrier to evaluation, and the TypeScript SDK plus OpenAPI spec make integration straightforward. This fills a real gap for teams building RAG pipelines, semantic search, or agent memory systems that need to run at the edge or in air-gapped environments.

Chris Nager built a fully playable DOOM that runs as an MCP (Model Context Protocol) app, rendering inline inside Claude and ChatGPT without a separate browser tab. The architecture uses two MCP tools — create_doom_session for inline-capable hosts and get_doom_launch_url as a browser fallback — combined with cloudflare/doom-wasm for the game runtime and a signed token system that maintains session state across both surfaces. The result is the same session whether you're playing inline or in a tab. The key technical challenge was avoiding iframe and CSP (Content Security Policy) issues. Rather than embedding a browser page inside the MCP iframe, the DOOM canvas runs directly inside the host's iframe — a subtle but critical distinction that resolved a class of rendering and input-handling bugs. The final implementation is intentionally stripped down: no save/load, no persistence adapters, just stable playable DOOM. Beyond the novelty, this project is a concrete demonstration that MCP apps are interactive surfaces, not just tool-calling JSON endpoints. The progressive enhancement pattern — same signed-token foundation serving both inline and browser modes — is a reusable architecture for any game or interactive experience that wants to live inside an AI assistant. Nager open-sourced the implementation and the blog post is a detailed technical breakdown.