I have a Notion full of pages. Half of them are stubs. The other half aren't linked to anything. I open it once a quarter, get overwhelmed, and close it. The wiki was supposed to be a network. What I have is a directory.
A directory remembers where. A wiki remembers what. Most personal wikis collapse into the first because the second takes ongoing labor — naming, filing, linking, refactoring. We didn't build another wiki app. We built the part that was always supposed to happen by itself: the structure that emerges from how you actually write.
The hub put it plainly: a directory is a worse search engine than Google. Most personal wikis are not failing as wikis — they're failing because they were never wikis. They were directories with wiki ambitions, and the ambition required maintenance the directory couldn't do for itself.
You opened a Notion. You made a database for "Topics" and another for "Notes." You set up relations. Three months in, the relations were two rows deep. You added a page about a thing, but you couldn't remember which database it belonged to, so you created a new one. By month six, half the pages were stubs and the other half had no links pointing at them. The schema was right. The schema was the problem.
A schema decides the shape of your knowledge before you have it. A wiki — the original 1995 one, on c2.com — let the shape emerge from the writing. That difference looks small on paper. After a year, it's the difference between a network and a graveyard.
Knovya doesn't ask you to set up a wiki. You write a page. You mention another page. The mention becomes a backlink visible from both sides — automatically. That page already has three semantic neighbors waiting; you didn't link them, the embedding model did. The wiki is forming as you type.
A graph view, when you open it, shows the topology you actually built — not the one you intended. The dense regions are the topics you keep returning to. The peripheries are the ones drifting. The bridges are where ideas cross-pollinate. You can read the structure of your own thinking from the outside, in a way you can't with folders or databases.
The phrase "personal wiki" is what people search for. Spine is what we actually built — and we don't make you carve it.
A directory remembers where you put it. A wiki remembers what it's about.
Three moments of a personal wiki's life — the day you start a topic, the quarter you read it back, the year you hand it off. No live data, no signup; the moves are real, the pages are illustrative.
You start a page called @observability. You don't title it carefully — you can rename later. The page exists; the wiki is one node larger.
Before you finish typing, the page already shows three semantic neighbors — @debugging, @monitoring, @incident-response — that you wrote weeks ago and forgot. You drop an @debugging mention. The backlink lands both ways, automatically.
When you write a related page next month, this one returns — by meaning, not by remembering its title. The wiki knows what's adjacent to what you're working on right now.
Eventually, the @observability cluster — page plus its connected neighbors — is mature enough to publish. One toggle; the rest of the wiki stays private.
Forte called four moves CODE for the second-brain shape. For a personal wiki the four are different — Capture, Connect, Surface, Share — because the wiki's job isn't synthesis, it's topology.
Knovya doesn't ask you to maintain a wiki — the wiki maintains itself through these four moves. Each move is carried by elements from the periodic table at /features. Together they form the loop: capture feeds connect, connect surfaces, surface shares, and the share — when read by your future self or another AI — captures again.
A page enters the wiki the way the thought arrived — voice, web, conversation, drag.
Speak a topic, get a wiki page already written.
A Claude or ChatGPT thread arrives as a real, editable page.
Any URL becomes a wiki page with the source attached.
The spine forms — backlinks land both ways, semantic neighbors pre-suggest, the page knows the topology.
Every @mention becomes a link visible from both sides — automatically.
The shape of your wiki — dense regions, drifting peripheries, bridges.
Pages ranked by how load-bearing they are — your spine, made readable.
The right page comes back — by meaning, not just by phrasing — and old pages return when their topic does.
Keyword and meaning, ranked together — find a page without remembering its title.
Forgotten pages return when their topic comes up in a new draft or question.
Outline a topic from its sub-pages, extract a list, summarize a cluster.
A page or a cluster goes outward — to a public URL, to your future self, to the AI tools you already use.
Publish one page or a whole connected cluster — the rest of the wiki stays private.
Claude, ChatGPT, Cursor read your wiki natively — your spine, inside the conversation.
A personal wiki isn't a 2018 invention. It's a phrase that arrived after eighty years of people trying to make a network of pages keep its own shape. Knovya is the latest answer to a question Bush was asking before the web existed: how does a private archive stay legible to its owner?
Bush's "As We May Think" describes a microfilm desk where documents are linked by association, not filed by category. Half a century before the web, fifty years before hyperlinks, he names the move that every wiki since has been trying to honor: knowledge wants to be a network.
On March 25, 1995, Cunningham launches WikiWikiWeb on c2.com. CamelCase auto-links pages together. The radical idea isn't the technology — it's radical trust: any visitor can edit any page. The shape of a wiki is whatever the writers leave behind. The name comes from a Honolulu airport shuttle; "wiki" is Hawaiian for quick.
Wikipedia (2001) takes Cunningham's idea and proves it scales to encyclopedic ambition. MediaWiki (2002) becomes the engine, free and portable. The wiki escapes c2.com and lands on every domain that wants to host one. Every reader is also an editor becomes a cultural assumption rather than a programmer's experiment.
Jeremy Ruston releases TiddlyWiki on September 20, 2004 — a non-linear notebook in a single HTML file, with content split into tiddlers. Andreas Gohr ships DokuWiki the same year — flat-file, no database, run-it-yourself. For the first time the wiki isn't a community medium; it's a personal one. The phrase "personal wiki" enters circulation.
March 2018: Notion 2.0 lands with relational databases. "Build a personal wiki in Notion" becomes a tutorial category overnight. The bet: schema first. A year later Roam, Obsidian, Logseq make the opposite bet — bidirectional links, Andy Matuschak's evergreen-notes pattern, no databases at all. The bet: connections first. Both still leave the user doing the structural work, just at different ends of the day.
Schemas were too rigid; manual links were too much labor. Knovya picks a third option: backlinks land both ways automatically, semantic neighbors are pre-suggested, NoteRank weights what's load-bearing. The graph view shows the spine you actually built — not the one you intended. MCP makes the same wiki readable inside Claude, ChatGPT, and Cursor. The wiki, finally maintaining itself.
The phrase "personal wiki" has been claimed by tools with very different theories of structure. The honest comparison isn't features — it's which kind of structure each app wagered on, and which structural work each one still leaves to you.
The bet Databases as the spine. If you can model your knowledge as tables and relations before you write, Notion will hold the model and let you build views on top.
What's left to you The schema, forever. Pages drift outside the model you set up; relations decay; stubs accumulate. The wiki is whatever your databases describe — and your databases need you.
The bet Ownership and bidirectional links. Plain markdown on your disk, plugin-rich, every [[link]] manual and reciprocal. The vault is yours, fully and forever.
What's left to you The linking discipline, daily. Connections only exist where you typed them. The graph is honest about your effort — sparse where you got tired, dense where you didn't.
The bet Beautiful surface, hashtag taxonomy. Refined typography, Apple-native, organized by #tags instead of folders. A pleasure to write in; a personal wiki by aesthetic osmosis.
What's left to you The graph. Hashtags are a flat taxonomy, not a network. There's no backlink view, no graph, no semantic neighbors — and the wiki only lives where Apple does.
The bet Outliner with relational power. Supertags turn nodes into typed entities; queries let the wiki answer questions about itself. The most structurally ambitious bet in the category.
What's left to you The schema and the queries. The structure is more powerful than Notion's, and maintained by the same human — you. The learning curve is the price of the precision.
The bet The structure is a consequence, not a precondition. Backlinks land both ways automatically, semantic neighbors are pre-suggested, NoteRank weights what's load-bearing. The wiki forms as you write — and the graph view shows you what you actually built.
What's left to you The next page. No schema to set up, no [[brackets]] to remember, no queries to maintain. The only structural decision is which topic to write about now.
Every other wiki app picks a structure for you to keep up. We picked the one that builds itself.
A personal wiki is only useful if it shows up where the work happens — phone in your pocket, browser mid-read, graph view at the end of a quarter, conversation with Claude on Tuesday. The spine forms regardless of where the page came from.
Mid-walk, mid-meeting, mid-shower — voice or text, the page enters the wiki already mentioning related topics. The links don't wait for the desktop.
Open the graph view at the end of a quarter and the wiki shows you what you actually wrote about — dense regions where you returned, peripheries drifting, bridges where ideas crossed. The structure is a consequence of the work, not a plan you had to keep.
The Chrome extension turns any URL into a wiki page with source attached. Three semantic neighbors are already wired in before you close the tab.
Through MCP, every AI tool you already use can read your wiki — and follow the backlinks. The connections you wrote travel with the page, into whichever conversation needs them.
A wiki isn't a single feature — it's a constellation. Four elements carry the spine, two sibling problems share the diagnosis, and two concept primers live next door for readers who want the framing first.
The shape of your wiki — dense regions, drifting peripheries, bridges.
See featureEvery @mention visible from both sides — automatically, no brackets.
Find a wiki page by meaning, not just by the title you used.
See featureClaude, ChatGPT, Cursor read your wiki natively — backlinks travel.
See feature"Everything I read is somewhere. I can't find any of it."
An archive that surfaces — same problem at the recall layer, not the structure layer.
See the workflow Problem 03 · Chapter I"Six weeks of Zettelkasten in Obsidian. Three hundred orphan cards."
A slip-box that organizes itself — atomic-notes cousin, same emergence philosophy.
See the workflowThe practice underneath every personal-wiki tool — capture, link, retrieve, the recall-to-recognition shift.
Read the primer DefinitionThe data structure underneath a personal wiki — nodes, edges, density, why it scales where folders don't.
Read the primerA personal wiki isn't planned, it's accumulated. The spine forms after page three, the graph shape becomes legible after the first quarter, the archive starts answering you in the second. You only need the first page to start.
Or scroll back to the diagnosis.
Eight questions we keep getting. If yours isn't here, the contact page reaches us directly.
A personal wiki is a private, networked notebook organized by links rather than folders. Each page is a small, self-contained idea; pages reference each other; the structure of your knowledge emerges from the connections instead of being decided up front. The format goes back to Ward Cunningham's WikiWikiWeb in 1995 and was adapted for individuals with TiddlyWiki and DokuWiki in 2004. This page is about the knowledge-worker use of a personal wiki — not the world-building or game-lore variety.
In Knovya, every reference becomes a backlink automatically. Every page is matched against the rest of your archive by meaning, not just keywords. NoteRank ranks pages by how connected they are. The result is that the spine — the load-bearing topics, the dense regions, the orphan pages, the bridges — emerges from the writing itself. You don't decide it in advance; you read it back from the graph.
Notion is database-with-pages: you decide the schema, and the wiki is whatever your databases describe. It's strong if you can model your knowledge as a table; weak when topics drift outside the schema you set up. Knovya is link-with-pages: the structure is implicit in the references, and a graph view lets you see the topology you actually built. There's no schema to maintain — the spine is a consequence of writing, not a precondition for it.
Obsidian is local-first markdown with bidirectional links — strong on ownership, strong on plugin culture. The thing it leaves to you is the linking discipline itself: you write [[wiki-style brackets]] every time you want a connection, and you maintain the vault by hand. Knovya makes the linking ambient — semantic neighbors are suggested as you write, mentions become bidirectional automatically, and the graph is rendered, not curated. Obsidian is a vault you tend; Knovya is a wiki that tends itself.
Yes. Knovya imports markdown files (Obsidian, Logseq, DokuWiki) preserving wiki-style bracket links, and exports/imports Notion pages with their database structure flattened into linked notes. Existing backlinks survive the migration; AI then enriches the archive with semantic neighbors that weren't manually linked before.
No. You can type @page-name to mention any other page, and the link is created bidirectionally. Wiki-style [[double brackets]] also work for users coming from Obsidian or Logseq. CamelCase auto-linking — the original 1995 WikiWikiWeb convention — is supported but off by default. The wiki-ness is in the connections, not the markup.
By default, every page is private to your account. Sharing is page-by-page or cluster-by-cluster — you can publish a single page or a connected set of pages while the rest of the wiki stays private. Pro and Team plans include note-level end-to-end encryption (AES-256-GCM); encrypted notes are not searchable or embeddable on the server.
Yes. Knovya Free includes 50 notes, semantic search, full backlinks, the knowledge graph view, and 50 MCP calls per month — enough to build and operate a working personal wiki, and enough to see whether the spine starts to form for you before paying anything.