---
title: "Memory.wiki Business Plan and Architecture"
url: https://memory.wiki/pBEnMXSs
updated: 2026-05-20T14:29:26.281Z
source: "auto-synthesis"
---
# Memory.wiki Business Plan and Architecture

> These documents chronicle the evolution of memory.wiki from concept to finalized business plan, articulating a vision to solve AI knowledge delivery through URLs that serve as APIs for any AI system. The project underwent significant rebranding from "mdfy" to "memory.wiki" while maintaining its core architectural principle of URL-native knowledge sharing.

## Key claims

- [EXTRACTED] "A memory.wiki URL is an API for any AI" - users can paste `memory.wiki/<id>`, `memory.wiki/b/<id>`, or `memory.wiki/hub/<slug>` into ChatGPT, Claude, Gemini, or Cursor [doc-1, doc-4]
- [EXTRACTED] The system operates on a three-tier architecture: "수집/소화/활용" (capture/digestion/utilization) where users author content, AI organizes it into graphs, and any AI can consume it [doc-1, doc-4]
- [EXTRACTED] The core problem is knowledge delivery, not AI memory: "매일 수백만 명이 ChatGPT, Claude, Gemini, Cursor에 자신의 사고를 쏟아붓니다... 그리고 탭을 닫습니다" [doc-5]
- [INFERRED] The project underwent significant strategic pivoting between versions v6 and v7, including a complete rebrand from "mdfy.app" to "memory.wiki" while preserving the fundamental URL-as-API architecture [doc-3, doc-4]
- [EXTRACTED] The business model positions memory.wiki as "LLM 서비스의 기본 지원 메모리 레이어" (fundamental memory layer for LLM services) [doc-1]
- [AMBIGUOUS] The system involves four core components - markdown source, AI-generated graphs, concept index, and embeddings - but the exact automation boundaries between user authoring and AI organization vary across descriptions [doc-3, doc-4]

## Cross-references

- **URL Architecture**: Both the original "mdfy" concept [doc-3] and final "memory.wiki" plan [doc-1, doc-4] emphasize the same three-tier URL pattern, showing consistency in technical vision despite branding changes
- **AI Integration Philosophy**: Document 5's manifesto complements the business plans by framing the problem as knowledge delivery rather than memory, supporting the URL-native solution described in the technical documents
- **Timeline Evolution**: The launch deadline shifted to "2026년 8월 말 (16주)" [doc-1, doc-4], indicating project acceleration from initial concept to full-time development

## Open questions / gaps

- How will the platform handle authentication and privacy for sensitive knowledge graphs?
- What specific competitive advantages exist over existing knowledge management tools that might add AI integration?
- How will the semantic search and concept indexing perform at scale across diverse user knowledge domains?

## Provenance

- [doc-1]: Business plan v7 providing executive summary and strategic positioning for memory.wiki
- [doc-2]: Meta-document synthesizing the overall development journey and vision
- [doc-3]: Technical architecture explanation for the original "mdfy" concept, detailing the four core system components
- [doc-4]: Full business plan v7 with detailed roadmap, business model, and go-to-market strategy
- [doc-5]: Founder's manifesto explaining the philosophical motivation and problem definition behind memory.wiki