简体中文
English
Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Lokus?
Lokus is a personal knowledge management (PKM) app for macOS, Windows, and Linux, described on its site as an "operating system for your ideas" and "your personal system for thinking, researching, and creating." In practice, it's a writing and note-taking environment where you store ideas as Markdown files, connect them with wiki links and backlinks, explore those connections in a graph view, and arrange material spatially on an infinite canvas.
Who it suits
- Researchers and writers who want to draft in plain Markdown and link notes into a web of references rather than a folder tree.
- People building a "second brain" who want backlinks and a graph view to surface connections between notes.
- Visual thinkers who benefit from an infinite canvas for mapping ideas, sources, and drafts in one space.
- Cross-platform users who move between Mac, Windows, and Linux and want the same environment on each.
What the page emphasizes
The site foregrounds Markdown, wiki links, backlinks, graph view, and infinite canvas, and pairs this with a "Your data, your control" message—a signal that local, portable files matter to the product's pitch. It also points to plugins and documentation, suggesting an extensible tool rather than a fixed one.
Trade-offs to weigh
A linked, canvas-based system rewards consistent linking habits; if you prefer rigid folders and simple lists, the graph and canvas may add clutter rather than clarity. Markdown-based tools also tend to expect some comfort with plain-text conventions.
Next step
If you're evaluating it, try a small real project—say, a research topic with a dozen notes—and test whether linking, backlinks, and the canvas help you find connections faster than your current setup. For comparison, established alternatives include Obsidian and Logseq for linked Markdown notes, or Notion if you want databases alongside notes.
How does Lokus compare to other personal knowledge management apps like Obsidian or Notion?
Lokus is best understood as a local-first, Markdown-based knowledge tool in the same family as Obsidian, rather than a workspace-and-database tool like Notion. Its page describes a personal knowledge OS for macOS, Windows, and Linux built around Markdown, wiki links, graph view, and an infinite canvas, with the emphasis that "your data, your control."
Where the differences land
| Lokus | Obsidian | Notion | |
|---|---|---|---|
| Core model | Markdown notes plus wiki links, graph, and infinite canvas | Markdown notes plus links and graph, extensible via plugins | Block-based pages and databases in a hosted workspace |
| Data ownership | Local files, described as under your control | Local Markdown vault | Cloud-hosted workspace |
| Best fit | Writers and researchers who want linked notes and a spatial canvas in one app | Users who want a large plugin ecosystem and a mature vault workflow | Teams and individuals who want databases, project tracking, and shared pages |
| Trade-off | Smaller ecosystem, so fewer integrations and community plugins to lean on | Plugin sprawl and configuration overhead | Less suited to plain-file ownership and offline-first note-taking |
The practical split: if your work is mostly prose, research notes, and connections between ideas, Lokus and Obsidian compete on similar ground. Lokus's distinguishing pitch is bundling the infinite canvas alongside linked Markdown notes, which suits people who think spatially—mapping arguments, sources, and drafts on one board. Notion wins when the work is structured: task boards, content calendars, lightweight databases shared with other people.
Choosing between them
A concrete test: take one real project—say, a literature review or a long article—and ask where each tool would slow you down. In Notion, you would likely miss direct file ownership and fast plain-text editing. In Obsidian, you might spend early hours choosing plugins. In Lokus, check whether the features you depend on exist natively, since a smaller app means less third-party coverage.
For broader context on the category, Obsidian and Notion document their own approaches directly. If local Markdown files and a canvas-first workspace matter more to you than ecosystem size, Lokus is worth a trial on a single project before committing your whole system to it.
How do I set up Lokus on macOS, Windows, or Linux and start my first note?
Lokus runs on macOS, Windows and Linux, and the first step is to download the build for your platform from Lokus and install it like any other desktop app. Once it opens, you land in a workspace where you can immediately create a note and start typing in Markdown.
A practical first session
- Create a note. Start with something small and real, such as today's tasks or a project idea, rather than a blank "system."
- Write in Markdown. Use headings, lists and bold text as you go; the formatting is plain text, so it stays readable even outside the app.
- Link it. Type a wiki link to a related topic (for example, a project name). The first time you do this, you are effectively creating that topic as a future note.
- Follow the backlinks. Open the new topic note and check which notes point to it. This backlink view is where the "second brain" effect starts to show.
- Try the graph view. After a handful of linked notes, the graph gives you a visual sense of clusters and orphan notes.
- Use the canvas for messy thinking. If a topic involves several notes, an infinite canvas lets you arrange them spatially instead of forcing a linear outline.
Choosing where to start
| If you are… | Start with | Why |
|---|---|---|
| New to linked notes | One daily note plus 3–5 topic notes | Keeps the graph legible while you learn the linking habit |
| Researching a subject | A source note per article or book, linked to topic notes | Makes backlinks a genuine index of what supports each idea |
| Planning a project | A canvas with notes for goals, tasks and references | Spatial layout suits non-linear planning better than a single long note |
| Migrating from another tool | Import or paste a small folder first | Lets you test how links and formatting survive before committing everything |
A concrete example
Suppose you are preparing a talk. Create a note called "Talk outline," link it to "Audience research" and "Slide ideas," then open the graph to see whether those topics connect to anything you already wrote. If "Audience research" has no backlinks, that is a signal to either write it properly or remove the link.
As general advice rather than a Lokus-specific feature: keep your notes in a folder you control and back it up, since the page emphasizes "your data, your control." Decide early whether you want one vault for everything or separate vaults for work and personal material; a single vault makes cross-links easier, while separate ones reduce noise.
How do wiki links, backlinks, and graph view work together in Lokus?
In Lokus, wiki links, backlinks and graph view are three views of the same connection: you create a link, the app records the reverse direction, and the graph draws the result. The page lists all three as core features of its Markdown-based knowledge OS for macOS, Windows and Linux, alongside an infinite canvas.
How each layer works
- Wiki links are the input. You type a link to another note inside your Markdown text, which turns a plain document into part of a network. Because the notes stay as Markdown files, the links are readable in any editor, not only in Lokus.
- Backlinks are the automatic reverse index. When note B links to note A, note A can show that B points to it. This is what makes the system useful for research: you find related material without remembering where you filed it.
- Graph view is the map. It plots notes as nodes and links as connections, so clusters, orphans and bridge notes become visible at a glance.
A concrete use
Suppose you are researching a topic and keep a "Reading notes" file. You link each new source note to it. Backlinks on the reading-notes file become a running bibliography, and the graph shows whether your sources cluster around one theme or sprawl across several. If a note has no links in the graph, it is a candidate for merging or deleting.
The trade-off
Links and backlinks reward deliberate linking; the graph rewards browsing. A dense graph can become a hairball as the vault grows, so the practical habit is to link to a few hub notes rather than to everything. Markdown files also mean your links survive outside the app, which matters if you later switch tools.
Next step
Pick one active project and create a single hub note for it. Link every new note to that hub for a week, then open graph view and check which notes sit outside the cluster. For alternative approaches to the same link-and-graph model, compare Obsidian and Logseq.
What can I use the infinite canvas for in my research and creative workflow?
The infinite canvas is best used as a spatial thinking surface: a place to arrange notes, images and fragments freely rather than in a linear document. In a research and creative workflow, that makes it useful for mapping how ideas relate before you commit them to written form.
Practical uses
- Literature and source mapping: Place one note per source, then draw connections between papers, themes and open questions. Useful when you are still deciding what your argument is.
- Project and thesis planning: Lay out chapters, experiments or deliverables as clusters, with wiki links back to the detailed notes. The canvas gives you the overview; the notes keep the depth.
- Creative mood boards and drafting: Collect references, quotes and half-formed ideas in one space, then promote the strongest ones into linked notes.
- Synthesis before writing: Rearrange clusters until patterns emerge, then write from the layout rather than from a flat list.
Who benefits, and the trade-off
The canvas rewards visual and associative thinkers—researchers juggling many sources, writers developing structure, students planning long projects. The trade-off is that spatial layouts can become hard to search and maintain as they grow. A workable rule: use the canvas for exploration, and wiki links plus regular notes for anything you need to retrieve later. If you prefer strict outlines, a plain Markdown editor will serve you better than a canvas.
Next step
Start with one bounded question—say, a single chapter or paper—and build a canvas of no more than ten to fifteen notes. If the spatial view helps you see connections you would have missed in a list, expand from there.
For comparison, Obsidian offers a similar canvas-and-links model, and Logseq takes a more outliner-driven approach to connected notes.
How does Lokus keep my notes and data under my control, and what are the paid supporter tiers?
Lokus keeps your notes under your control by storing them as plain Markdown files on your own machine rather than in a vendor cloud. The page's "Your data, your control" message and its Markdown-first design mean your notes stay readable and portable in any text editor, and you can back them up, sync or move them however you like. The app runs natively on macOS, Windows and Linux, so your files live locally on each device you use. Wiki links, backlinks and graph view are ways of connecting those local files; they don't require uploading your content to a hosted service. In practice, a researcher can keep a folder of Markdown notes in a synced directory (for example, a cloud drive or Git repo they choose) and still get linking and a graph view inside Lokus.
Paid supporter tiers
The page's contribution links point to two recurring supporter options through Open Collective:
| Tier | Suggested amount | What it signals |
|---|---|---|
| Knowledge Seeker | About $5/month | Entry-level backing for the project |
| Archivist | About $15/month | Higher-level support for ongoing development |
These are voluntary contributions to support the project, not feature-gated subscriptions described on the page. Treat the amounts as suggested contribution levels rather than confirmed plan pricing, and check the Open Collective page for what each tier currently includes.
Next step
If data ownership is your priority, decide where your Markdown folder should live (local disk, a sync service you trust, or a version-controlled repo) before you start writing, so linking and backups work the way you expect. Then choose a supporter tier based on how much you want to fund development, not on access to features.
Cloudflare
Vercel
Namecheap Private Email
User reviews (0)