Locara

Obsidian

What it is: A note-taking and personal knowledge base app built around plain markdown files in a local “vault.” Founded 2020. Privately held, profitable, indie-spirited. Status: Mature, beloved by a passionate community. Millions of users. Self-funded, no VC. Most relevant to Locara: The single best product-philosophy match for what Locara is trying to be. The “file over app” thesis, the privacy-by-architecture stance, the five-value manifesto, the plugin ecosystem, and the indie business model are all near-perfect templates.

Background

Obsidian was created by Shida Li and Erica Xu (formerly Dynalist), with Steph Ango as CEO. They built it on a simple insight: every note-taking app eventually goes away, but your notes shouldn’t. So Obsidian doesn’t store your data — it’s a viewer/editor over plain markdown files in a folder on your disk. The app could vanish tomorrow and your notes would still be readable in any text editor for the next 50 years.

This sounds like a small product detail. It’s actually a worldview. And it’s the same worldview Locara is built on, applied to AI apps instead of notes.

Key design decisions

  • “Files over app” — your data lives as plain markdown files in a folder you control. Obsidian provides a UI; the files are the truth.
  • Local-first by architecture, not policy. No servers. No accounts required. The app works offline forever; sync is opt-in via paid Obsidian Sync (or third-party tools like iCloud, Dropbox, Git).
  • Privacy as a structural property. “Your data is stored on your device, inaccessible to us.” This is verifiable (the app makes no calls); not a marketing claim.
  • Plugin-first extensibility. Core app is small; community plugins extend it massively. ~2000+ plugins for everything from spaced repetition to canvas-based mind-mapping.
  • Five-value manifesto (Yours, Durable, Private, Malleable, Independent) — published, referenced, stuck-to.
  • Free for personal use; paid for commercial. Honor-system commercial licensing. Sync + Publish are paid add-ons.
  • Independent / user-supported — no VC, no acquisition, no exit pressure.
  • Cross-platform — Mac, Windows, Linux, iOS, Android. All consume the same vault.
  • Markdown is the substrate. Standard CommonMark + Obsidian-specific extensions (wiki-links [[...]], callouts, embeds).

What worked

  • The “files over app” pitch is unbeatably trustworthy. Users adopt Obsidian because the worst case is benign — you’d still have your notes. Compare to Notion: if Notion shuts down, your data exits as JSON exports if you remember.
  • Plugin ecosystem became a moat. Power users build entire workflows around plugins. Switching cost = re-learning your plugin stack.
  • Honor-system commercial licensing works. Companies pay because the value is real and the team is trusted, not because they’re forced.
  • Indie + profitable + sustainable. They don’t have growth pressure. They ship at their own pace. Quality is consistently high.
  • Documentation + community are excellent. Forum, Discord, YouTube creators all driving each other.
  • Founder-driven product voice. Steph Ango’s blog (stephango.com), essays, and tweets carry the brand without performative hype.

What failed / criticisms

  • Closed source. This is a recurring complaint. They argue: open source ≠ better; we’re durable + private without it. But for some users (especially those concerned with auditability), it’s a deal-breaker.
  • Mobile UX trails desktop. Mobile apps are functional but less polished.
  • Sync is paid and somewhat expensive ($4–$10/mo). Power users use Git or Syncthing instead.
  • Plugin quality varies. No formal review; users have to assess plugin trust themselves.
  • Onboarding is rough. First-time users see an empty vault and a steep learning curve.
  • Performance issues at huge vault sizes (10k+ notes). Improving but real.
  • Discovery is bad. Plugin discovery, theme discovery, even feature discovery is largely community-driven not in-app.

Specific learnings for Locara

Philosophy

  1. “File over app” is the perfect parallel for “Local over cloud.” Locara should adopt the same framing: apps come and go, but if your data is local in standard formats (sqlite + exportable), you keep it forever. Make this explicit in the manifesto.

  2. Privacy as a structural property, not a policy. Obsidian’s “your data is stored on your device, inaccessible to us” line is exactly the framing Locara should use. Not “we promise not to look at your data” but “your data is on your device, so the question doesn’t apply.” Already in 13-security-privacy.md; reinforce in marketing copy.

  3. Five-value manifesto is a great template. Adapt directly:

    • Yours — your apps, your data, your hardware
    • Durable — apps written today work in 10 years
    • Private — local-first; the architecture, not the policy
    • Malleable — extensible via tools, components, custom apps
    • Independent — OSS, no VC, user-supported

    This becomes the Locara manifesto. The five-value structure is recognizable and effective.

Business model

  1. Free-for-personal + paid-for-commercial is viable. If Locara ever monetizes, Obsidian’s model is the cleanest precedent. Free framework + free local registry + paid services (sync? backup? enterprise registry? verified-privacy certification?) for commercial users.
  2. Honor-system commercial licensing works. No DRM, no enforcement infrastructure. Trust the buyer; recover lost revenue with goodwill from the broader user base.
  3. Indie + profitable + sustainable is achievable. Obsidian proves you don’t need VC to build a serious product with millions of users. They’ve been profitable since early on. Locara should target the same trajectory.

Engineering

  1. Plain-format storage is a competitive moat. Obsidian’s bet on markdown gave users a guarantee of data portability that no SaaS competitor could match. Locara’s bet on per-app SQLite + content-addressed model storage is structurally similar — apps can be exported, inspected, migrated.
  2. Apps that produce exportable artifacts are more trustworthy. Locara apps should default to “export your data to a portable format” being a one-click operation. Steph Ango’s argument: the worst case (the app dies) should be benign.
  3. Plugin ecosystem as long-tail value. Locara’s component registry + tool registry are the equivalent of Obsidian’s plugin ecosystem. Embrace community contributions; the ecosystem becomes the moat.
  4. No formal plugin review = ecosystem leakage. Obsidian’s plugin marketplace is largely community-policed. Locara’s review pipeline (signed builds, capability declarations, automated review) is more than what Obsidian has — and that’s part of the wedge.

Positioning + voice

  1. Founder voice is real and recognizable. Steph Ango’s blog has a distinctive, calm, craft-oriented voice. He writes about personal questions to ask yearly, color theory, software craft. The brand carries that voice. Locara should similarly aim for founder-driven content with a recognizable register.
  2. Don’t compete on features. Compete on values. Obsidian doesn’t try to out-Notion Notion. They differentiate on durability, privacy, malleability. Locara should similarly avoid the “more features than Pinokio” framing and instead lead with “apps you can trust forever.”
  3. Educational content builds the audience. Obsidian’s docs, YouTube creators, and forums are the engine. Plan for Locara to invest in this — first-party docs + tutorials + content + visible founder voice.

Specific tactical moves

  1. Adopt a manifesto page. Modeled directly on Obsidian’s. One sentence per value, linked from the README, prominent on the website. Steph’s “file over app” essay is the gold standard for one-idea pitch.
  2. Cross-platform from the start (architecturally). Obsidian shipped Mac/Windows/Linux/iOS/Android. Locara is Mac-only in v1, but the manifest schema should be platform-agnostic; cross-platform is a deferred build, not a blocked architecture.
  3. Make sideloading a feature, not a bypass. Obsidian doesn’t have “sideloading” as a concept — vaults are just folders. Locara’s .locapp files should similarly feel native and trusted, not “scary alternative.” Already designed this way; reinforce in UX.
  4. Steph’s broader writing as a model for Locara’s content surface. stephango.com has annual reflection questions, design essays, color theory, photography. Eclectic, personal, craft-oriented. The blog isn’t always about the product. Locara’s content surface can be similarly broad — the privacy thesis, model evaluation, AI history, software craft. Brand-without-performance.

A reading list

References