---
id: "concept-file-over-app"
type: "concept"
source_timestamps: ["00:39:05"]
tags: ["data-ownership", "software-philosophy"]
related: ["concept-ai-wiki", "concept-openbrain-architecture"]
definition: "The philosophy that users should store their knowledge in open, durable formats they control, rather than locking it inside proprietary SaaS applications."
sources: ["s11-wiki-vs-open-brain"]
sourceVaultSlug: "s11-wiki-vs-open-brain"
originDay: 11
---
# File Over App Principle

# File Over App Principle

> The philosophy that users should store their knowledge in open, durable formats they control, rather than locking it inside proprietary SaaS applications.

## Shared Foundation

The **File Over App** principle is a software philosophy shared by both [[concept-ai-wiki]] and [[concept-openbrain-architecture]]. It asserts that users should retain absolute ownership and control over their data in open, durable formats — local Markdown files (e.g., via [[entity-obsidian]]) or a self-hosted SQLite/Postgres database — rather than locking their knowledge inside a proprietary SaaS platform.

## Why It Matters

- **Model agnosticism**: by owning the context layer, users can plug in any AI model (OpenAI, Anthropic, local open-source models) to act upon their data.
- **Resilience**: if a SaaS company changes its pricing, alters its privacy policy, or goes out of business, the user's compounding knowledge asset remains entirely safe and functional.
- **Sovereignty**: knowledge is the compounding asset; the model is the disposable consumer of that asset.

## Action

See [[action-own-your-context-layer]] for the concrete implementation guidance.


## Related across days
- [[concept-vertical-context]]
- [[concept-openbrain-architecture]]
- [[action-own-your-context-layer]]