---
title: "The structural moat: cross-AI portability"
url: https://mdfy.app/rBRZ_nni
updated: 2026-05-14T17:52:48.410Z
source: "mdfy.app"
---
# The structural moat: cross-AI portability

## One line summary

> A single AI vendor can build deeper integration against its own model than mdfy ever could. None of them can deliver a URL that works across their competitors. The portability is the product.

## Why this matters

Notion, Mem.ai, Roam, Obsidian — each is a destination. The user is asked to live inside the tool. mdfy is the opposite shape: the user lives wherever they already work (ChatGPT, Cursor, Claude Code) and mdfy is the thing that travels with them.

## What gets ported

- The doc body (clean markdown)
- The graph analysis (themes, insights, concept relations) attached to bundles
- The concept index attached to hubs
- Privacy gating (Public / Restricted / Private) — the URL behaves the same way the rendered viewer does

## Why the AI vendors can't replicate

OpenAI building "ChatGPT memory that Claude can read" is a competitive negative for them. Anthropic the same. The asymmetry is structural — mdfy benefits from being *not aligned* with any single vendor.

## Failure modes

- If one vendor builds a dominant memory layer that all AIs respect → mdfy still survives as the UX layer (curate, capture, share) but loses the "they can't" part
- If `llms.txt` adoption stalls → the URL contract weakens. Mitigate by treating `llms.txt` as one of multiple paths; raw markdown + clean URLs are the durable spec.

Bottom line: the moat depends on the URL contract, not on any one feature.