Hillnote vs myICOR

Hillnote and myICOR are both productivity tracked by AIDiveForge. Below is a side-by-side comparison of pricing, capabilities, platforms, and ownership — sourced from each tool's live website and verified before publishing.

Hillnote

The core workflow is a single markdown source shared across documents, databases, kanban boards, canvas, and slides — so there is no export step when switching views, and no proprietary schema blocking outside tools. Local models (Apple Intelligence, Ollama) handle inline edits and quick rephrasing without touching a server; auto-mode routes heavier requests to a frontier model. A built-in MCP server exposes your workspace to any MCP client over STDIO, so agents you already use can act on files without a custom integration. The wall appears at the collaboration layer — this is a single-user, file-first tool, and teams that need concurrent editing or shared permissions will find no native path to that here.

myICOR

The system is a local markdown folder pre-loaded with a six-person AI team: a routing orchestrator (Larry), a research specialist (Pax), a capture agent (Penn), and others — each with a named contract and a session journal so the next model picks up where the last one left off. You bring your own LLM; the folder supplies the memory. Research produces structured notes in place, drafts inherit your established voice, and weekly review prompts surface stale items automatically. The ceiling appears when you need real-time data, API integrations, or collaborative editing — none of that is in the folder. Teams that need those reach for purpose-built tools alongside this one.

Attribute	Hillnote	myICOR
Pricing	Paid	Paid
Free trial	No	No
Open source	No	No
Has API	No	No
Self-hosted option	Yes	Yes
Platforms	Mac, Windows, iOS, Android	Local disk (any OS with markdown support)
Pros	Every file is stored as plain markdown on your local disk, which means you can open, search, and version-control your entire knowledge base with any editor — no vendor dependency standing between you and your own work. Local AI models handle inline edits and rephrasing on-device even without a network connection, so writing assistance does not stop when your internet does. Auto-mode routes between local and frontier models based on task weight, so you avoid paying frontier API costs for simple rewrites while still having that capacity available for heavier lifting. A built-in STDIO MCP server exposes your workspace to Claude Code, Codex, and any MCP client as plain files — no exports, no schema translation — so agents you already use can act on your notes without a custom integration layer. Sync is opt-in and can be turned off entirely, which means your files genuinely stay on your machine when you want them to, rather than syncing by default and requiring you to trust a vendor's data handling.	LLM-agnostic folder architecture, so switching from Claude to Gemini mid-project is a matter of opening the same folder in a different app — no re-pasting context, no lost session history. Persistent agent journals mean each specialist picks up from the last session, so you stop spending the first ten minutes of every AI conversation re-explaining who you are and what you're working on. Plain markdown on your local disk means zero migration risk — if the vendor disappears tomorrow, every note, contract, and workflow you built is still readable by any text editor or LLM. Larry's routing layer matches requests to the right specialist automatically, so you don't have to remember which prompt style triggers good research versus good drafting — the team handles the handoff. Open-source scaffold under CC BY-NC-SA 4.0, so you can inspect, fork, and extend the agent contracts without waiting on a vendor roadmap or paying for access to the base system.
Cons	There is no concurrent editing or shared permissions model described anywhere in the vendor's documentation — a two-person team that needs to write to the same document simultaneously has no path forward here and will need to move to a tool like Notion or Obsidian Publish with a sync layer. The API surface is limited to the MCP pathway; there is no REST or webhook interface for programmatic access outside of agent tooling, which means teams trying to pipe Hillnote data into dashboards or external automations hit a dead end and typically resort to file-watching scripts on the markdown directory. Mac is the stated primary target (the download CTA is 'Download for Mac'), and while Windows, iOS, and Android are listed as sync targets, the maturity gap between platforms is not disclosed — teams standardized on Windows as a primary device are taking on unknown parity risk.	The folder has no mechanism for live data: API calls, web scraping, calendar reads, and CRM syncs are all outside its scope. Teams that need agents to pull live information must wire up a separate integration layer and maintain it alongside the folder — which is a second system to debug. There is no multi-user collaboration model. Two people cannot edit the same folder simultaneously with conflict resolution. Teams of more than one person sharing a PKM workspace hit this wall immediately and typically move the shared layer to a tool with real-time sync — Notion, Obsidian Sync, or a shared Git repo — while keeping individual folders local. No hosted inference or built-in LLM access means every new user must already have API credentials or a local model running before the team scaffold does anything. For non-technical users who came for the AI workflows, the setup friction before first use is real and the docs leave meaningful configuration detail to the user to figure out. The agent team is fixed at the scaffold level — expanding it requires running Nolan's eight-step hiring procedure, which is a prompt-driven workflow inside the folder. Teams used to GUI-based agent builders who want to add a specialist in two clicks will find the process slower and more text-heavy than competing tools that offer visual agent creation.

Bottom line

Hillnote and myICOR are closely matched on pricing model, openness, and API availability — pick by feature set and platform support in the table above.

Frequently asked questions

What is the difference between Hillnote and myICOR?

Hillnote is Paid, while myICOR is Paid. Compare pricing, free trial, API, platforms, and pros/cons in the table above on AIDiveForge.

Is Hillnote better than myICOR?

It depends on your workflow. Use the side-by-side attributes (pricing, open source, API, self-hosted, platforms) to decide. AIDiveForge does not rank a universal winner — we publish verified facts so you can choose.