Capacities alternative for people who want less structure, not more

By Gerald · 15 July 2026

Simple lined notebook beside complex geometric objects on a desk, representing the choice between a structured object model and a lighter writing surface

Capacities markets itself as a studio for your mind. It uses an object model: types, properties, relations, and a flexible way to connect ideas that goes beyond plain pages and tags. For people who think in structures and who enjoy refining a personal ontology, it is an impressive and coherent piece of software.

For people who primarily want to write, capture, and occasionally turn a thought into a task without first deciding what type of object it is, the model can feel like an obligation rather than a tool.

This is not a review that pretends one approach is universally better. It is a map of the tradeoff, and a pointer toward the simpler end of the spectrum for the people who have decided the structure is costing more than it returns.

What Capacities gets right

The object model is genuinely powerful once it clicks. You can define a "Book" type with properties for author, status, and notes, then link books to authors, to projects, to ideas. The database-like queries and views that fall out of that model are useful for people who treat their notes as a personal research system rather than a long-term memory.

The focus on thinking rather than project management keeps the surface from turning into another task tracker with a notes feature bolted on. The people who love it usually describe it as the first tool that made their notes feel like an extension of their thinking rather than a filing cabinet.

The company is independent, EU-based, and has been explicit about not taking certain kinds of funding. That history matters to the audience that cares about longevity and data practices.

Where the structure becomes the work

Simple lined notebook beside complex geometric objects, showing the tradeoff between structure and simplicity — The object model is genuinely powerful once it clicks. For many people the structure becomes the work.

The cost of the model is that almost everything requires a decision about type and properties. A quick thought captured on a walk becomes an object that wants to be classified before it feels properly at home. Over time the overhead of maintaining the types and relations can become its own small administrative task.

For people whose notes are mostly narrative, meeting notes, reading highlights, and the occasional project plan, the object model can feel like using a spreadsheet when a notebook would have been enough. The power is real. The question is whether you are doing the kind of work that needs that power on a daily basis.

Tasks and kanban-style work are possible but feel secondary. The product is optimised for connected thinking, not for moving a card from Triage to Executing and back to a note with one drag. If your notes and your tasks are tightly interleaved, the model does not always make the interleaving easier.

The simpler alternatives

A plain notebook-plus-tag system (the classic Evernote model, or Flow's notebooks and tags) removes the type decision at capture time. You write. Later you can add a tag or move the note into a notebook. The structure emerges from use rather than being declared in advance.

A combined notes-and-kanban tool adds the ability to turn a line in a note into a task that lives on a short, active board without requiring you to model the task as a typed object with relations. The connection is direct because both halves of the work live in the same lightweight surface.

Local markdown tools with backlinks give you connection without the overhead of a formal type system. You get the graph when you want it and plain text when you do not.

None of these are "better" than Capacities in any absolute sense. They are different points on the spectrum between maximum structure and minimum overhead. The people who are happiest with Capacities are those who have decided the structure is the point. The people who are happiest with the simpler options are those who have decided the structure was becoming the work.

Frequently asked questions

Is Capacities too complex for normal note-taking?

It depends on what you mean by normal. For people who enjoy refining a personal knowledge model and who benefit from typed objects and relations, it is not too complex. It is the right level of power. For people who want to write a paragraph, tag it, and find it later without first declaring a schema, the model adds steps that feel unnecessary.

Can you use Capacities for tasks as well as notes?

You can. Tasks are objects like anything else. The experience is closer to a database of tasks with rich context than to a kanban board you glance at to see what to do next. If your task management is mostly "here are the things I have committed to and where they stand," it can work. If your task management is "what should I be working on today and what just came in," the board metaphor in a lighter tool is often faster.

How does the pricing compare?

As of July 2026, Capacities has a free tier with limits and paid plans (Pro and Believer) in the $10-12 per month range when paid annually. It is a subscription model with no one-time purchase option. The core promise of the product is the model, not the price.

What is the migration story like?

Exports are available. The object model means the export is richer (and more complex) than a folder of markdown files. Moving to a simpler tool is usually straightforward for the text. Moving the structure (types, relations, properties) is lossy by nature, because the destination does not have the same concepts.

Who is the ideal Capacities user?

Someone who has tried simpler tools, found them too flat, and genuinely enjoys the act of modelling their knowledge. Someone whose primary output is thinking and writing that benefits from explicit connections and typed data. Someone who is willing to invest time in the system because the system is part of the thinking process.

My verdict

Capacities is a coherent and well-executed answer to a specific question: what would a note tool look like if it were designed for people who want to model knowledge rather than just store it? The answer is impressive. It is also not the answer most people are looking for when they say they want a better place to write things down. For the subset of users who have already discovered that they think in objects and relations, it is one of the best tools available. For everyone else, the simpler notebook-and-tag or notes-and-kanban alternatives are not a downgrade. They are a different bet about where the value of note-taking actually lives.