Your knowledge. Further.
Notes you can still
find in ten years.
Most notes apps are judged on how they feel to write in. CODNARA is built to be judged on what happens afterwards — when there are a hundred thousand notes, when you search for something you half remember, when you decide to leave.
A note in the margin. This page is laid out the way CODNARA lays out a document — one reading column, one margin for the things worth saying beside it. It is where comments live in the product, too.
notes in the workspace every performance budget is tested against. Not a demo library.
to search all of them, with row-level security active — the same query a real account runs.
notes withheld from an export. No cap on the free plan, no cap on any plan.
thing that does not survive an export — and we name it, further down this page.
Seven promises, and how each one is kept.
A search that never quietly fails
If you cannot retrieve a note, it does not matter that we still store it. A silent zero-result is indistinguishable from data loss — so search is exact first, then forgiving: it tolerates a typo, ignores an accent, and tells you when it fell back rather than pretending it always meant to.
Multilingual from the schema up. “diseño”, “diseno” and “DISEÑO” are one word here, and one tag.
Comments that stay on the words they were about
A comment is anchored inside the document itself, not to a character count. Insert three paragraphs above a commented sentence and the note stays on the same words — because it never described a position in the first place. That is why comments drift in most editors, and why they do not here.
Delete the sentence a thread was attached to and the conversation survives, holding a copy of what it was about. It leaves the margin; it does not vanish.
Files that answer your search
Attach a document and its contents are read and folded into the note’s own index, so a phrase buried on page four of a PDF finds the note that holds it. Until that has happened, the file says so — and when a format cannot be read yet, it names the engine that is missing rather than showing a spinner that never resolves.
Stored and searchable are two different claims. We make them separately, on every file.
Projects that are private when you say they are
Share a project with colleagues, or keep one to yourself. Privacy is decided in the database, not by hiding a menu — and revoking someone’s access revokes the attachments and the extracted text with it, which is the part most products forget. Every note shows who can see it, before you write in it.
A file whose bytes are locked while its text sits in someone else’s search results is a leak with better manners. We test for that one specifically.
Bring your library, and hear what could not come
Evernote exports, folders of Markdown, single files. Notebooks are restored as notebooks rather than flattened into one pile. And anything the importer could not convert is listed by name with a reason — because an import that quietly drops six notes out of four thousand is worse than one that refuses outright.
The thing standing between someone and leaving Evernote is mechanical, not emotional. So we made it mechanical.
An export you could read without us
One Markdown file per note, in folders named after your notebooks, with your original attachments beside them. It opens in Finder. It opens in Obsidian, Bear, iA Writer, VS Code, TextEdit. Nothing in the archive needs CODNARA to be running, or to exist.
Tested rather than asserted: a workspace exported, re-imported into an empty one, and compared. Every note came back with its text, formatting and notebook intact.
Failures you are told about
Background work that gave up appears in the product with a sentence and a button, not in a dashboard only we can open. Nothing is retried forever in silence, and nothing is dropped quietly. If we could not do something for you, that is your information, not ours.
The opposite of a spinner that never resolves.
Ask CODNARA
In developmentAnswers drawn from your own notes, where every claim carries a numbered citation back to the note it came from — an uncited answer is treated as a bug, not a feature. And generated answers never appear mixed in with search results, because a thing that exists and a thing that was written for you are different kinds of thing and should never be hard to tell apart.
Your notes are never used to train a model, and nothing is sent to a provider without an explicit action from you.
Marked in development because it is. This page does not advertise things that do not exist yet — which is the same commitment the rest of it is about.
A comment loses its exact place in the text.
Comments are anchored to a precise range of words. Markdown has no way to write that down, and inventing a syntax would produce files no other program could open — which would defeat the point of exporting Markdown at all.
So every comment is in your archive, with a copy of the passage it was written about. What is missing is the invisible marker tying it to those exact characters. The archive says so in its own README, before you find out yourself.
Every product has edges like this one. Most of them are discovered by the customer.
Built to be audited, not just trusted.
Every table carries row-level security, and it is the boundary — not a convenience on top of one. Access is decided in the database, so a mistake in the interface cannot expose a workspace. Security-relevant actions are recorded in an append-only log that workspace admins can read themselves.
Hidden UI is never authorisation. That sentence is in our architecture document, and it is the reason the rest of this section is possible to say.
The free plan holds a real library.
Not a trial with a note counter. We differentiate on AI and on processing — transcription, OCR, retrieval — never on whether your own writing fits.
A price that rises after you have committed your life’s notes is a lock-in with better manners. Ours does not.