When Octarine is—and is not—the right notes app

Choosing a notes app is mostly choosing which constraints you are willing to live with. Octarine makes a deliberate trade: it keeps the durable content in a folder of Markdown files and provides an opinionated writing environment around them. That is valuable to some people and irrelevant to others.

Start with the requirement you cannot compromise on, then see which app protects it. A longer feature page cannot compensate for missing that requirement.

Octarine is a good fit for personal, file-owned work

Octarine suits people who want to point at the location of a note on disk. A workspace is a folder you choose. Core note-taking works offline, and Octarine does not upload note content to its servers. Notes can be read with another text editor and backed up using ordinary file tools.

That foundation is a good match for:

• personal knowledge bases where long-term access matters;
• journals and Daily Desk entries that should remain private by default;
• research notes and long-form drafts built from linked Markdown;
• people moving from an existing folder of Markdown files;
• writers who want a visual editor without giving up the underlying syntax;
• people who prefer a smaller, coherent set of features over assembling an app from community plugins.

Octarine adds folders, tags, links, backlinks, graph view, YAML properties, search, Inbox, Quick Capture, and configurable views. Those are organization tools around files rather than a replacement for the files.

Octarine is a good fit when optional AI needs a clear boundary

AI is not required for ordinary writing. With Pro or a trial, the Writing Assistant and Ask Octarine can use a cloud API, a supported account, or a local model. Workspace indexing and retrieval remain on-device. A cloud request sends the prompt and included context to the selected provider; Ollama, LM Studio, or another local endpoint can keep inference local.

This makes Octarine useful for someone who wants AI available but does not want all notes automatically copied into an app-owned AI cloud. It still requires judgment. If you connect a cloud provider and include a private note, that provider receives the request. The AI setup documentation describes the current providers and storage boundary.

Octarine is not the right fit for plugin-led customization

There is no large third-party plugin marketplace. If the appeal of a notes app is installing community data views, niche importers, custom commands, themes, and experimental workflows, Obsidian is the clearer match. Octarine chooses a more controlled product surface, which means less assembly and less extensibility at the same time.

This also matters during migration. Markdown transfers more easily than plugin behavior. A query block or plugin-specific field may remain in the file while no longer producing the same interface.

Octarine is not a collaborative workspace suite

Octarine is built first for personal work. It does not provide the real-time, multi-user document editing, granular permissions, comments, and shared databases expected from a team workspace such as Notion or a collaborative document editor. Octarine Teams is planned and has a wishlist, but it is not generally available for purchase.

If several people must edit the same live page, assign work in a shared database, or depend on organization-wide access controls, choose a tool designed around that model. File sync is not a substitute for conflict-aware live collaboration.

Octarine is not a relational database or specialist production tool

Views can display filtered notes as tables, Kanban boards, and graphs, but the core object remains a Markdown note. If your work is fundamentally a relational database with formulas, rollups, automations, forms, and many linked record types, a database-first product will fit better.

Likewise, Octarine can be an excellent place to draft a paper, newsletter, or book, but it is not every final-production system. Academic citations, page layout, tracked changes, complex publishing pipelines, or high-volume PDF annotation may require dedicated tools alongside it.

Mobile access may be the deciding constraint

Octarine supports macOS 13+, Windows 10/11, and Linux on desktop. An iOS beta is available to eligible Pro users through TestFlight, but there is no public App Store release. There is no Android app.

Do not treat that as a footnote if most capture happens on a phone. A product whose desktop workflow is ideal can still be the wrong daily system when its mobile availability does not meet your needs.

Pricing favors ownership, but not every budget

The core app is free. Octarine Pro is a $79 USD one-time purchase and includes three active devices. Extra device seats are add-ons to an existing Pro license. AI provider costs are separate when you use a paid cloud API.

This model can suit someone who dislikes a recurring app subscription. It does not automatically make Octarine cheaper than every alternative, and a one-time license should not override a missing requirement. Check the current pricing page before buying because commercial details can change.

Run a decision test with real notes

Create a temporary workspace from copies of notes you already understand. Include one long document, nested folders, frontmatter, internal links, images, and a file edited by another program. Then answer five questions:

1. Does the editor make writing feel calmer or more constrained?
2. Can you find and connect material without recreating your entire system?
3. Do the files look sensible in a plain text editor?
4. Can your backup method restore the complete workspace?
5. Are any missing mobile, collaboration, plugin, or database features actually non-negotiable?

If the plain-file model solves a problem you care about and the missing features do not block the daily workflow, Octarine is worth adopting. If the test exposes a hard requirement it does not meet, believe the test. A candid no is better than building a fragile workaround around the wrong tool.