Moats
999 apps · 13 moatsCode stopped being a moat. Every app here is tagged with what's left holding it up — 1 to 3 tags, strongest first.
533of 999 apps (53%) lean on execution polish — the moat AI erodes
67(7%) have nothing else: polish is the entire defence
💅 execution polishPolish, reliability, sync quality, import fidelity — execution, not structure.🏗️ infrastructure scaleInfrastructure one person can't match: global hosting, deliverability, uptime, media pipelines.🔌 integrationsConnector breadth, and the endless upkeep that keeps every connector working.👥 collaborationIt only pays off once the whole team is in it: shared editing, presence, permissions.🧠 proprietary modelsCustom-trained or frontier models, plus the compute and inference behind them.🎟️ content & rightsLicensed content, media rights, curriculum, template and asset libraries.💎 proprietary dataData you can't rebuild: indexes, crawls, live feeds, archives, maps.🏛️ compliance & regulationRegulated ground: licensing, payroll, tax, KYC, HIPAA, real legal exposure.🕸️ network effectsIt's better because other people are already on it: graphs, communities, audiences.🛡️ brand & trustPeople pay because it's this vendor, and nobody got fired for that.⛓️ switching costsYour own accumulated history, config and habits make leaving painful.🏪 marketplace liquidityTwo sides that need each other, and both of them showed up.🔩 hardwarePhysical devices, or data only the vendor's hardware produces.
Tags are part of the dataset, so they get argued about in public ·the definitions live in the repo ↗