Who it is for

Four kinds of users, one deliberate order

Textrix does not try to please everyone. It serves the people who treat knowledge as an asset first, and expands outward from there — the order is public, and so are the trade-offs.

Four kinds of users

Ordered by the sequence they are served, not by importance — the last two are deferred, not dropped.

Readers

The base · 01

Reading books, taking notes, highlighting excerpts — no conflict with an existing note-taking habit.

  • Markdown is the source of truth; a vault is just a folder on disk
  • Wikilinks, tags and a graph connect what you read
  • Works offline, no account required

Developers

The difference · 02

Writing code, debugging, keeping technical notes — the extension ecosystem is the long-term moat.

  • A VS Code-style multi-pane workbench
  • One command palette for every action
  • Compatible with VS Code extensions and Obsidian data

Researchers

The growth · 03

Reading papers, writing articles, managing citations — a natural extension of the reader.

  • Reference management, citation and content organisation
  • No attempt at general-purpose Word layout (journals have templates)
  • Thinking happens in Textrix; delivery goes through export

Office work

Deferred · 04

Reports, processes, spreadsheets — deep water, pushed back on purpose.

  • Pivot tables, drag-and-drop layout and flowcharts are thirty years of work
  • Users are usually locked into a suite their company buys
  • Migration cost is enormous, so we do not charge at it

The order

Why this sequence — every step reuses what the previous one built.

  1. Readers

    The base · no conflict with an existing habit

  2. Developers

    The difference · the ecosystem is the moat

  3. Researchers

    The growth · a natural extension of readers

  4. Office work

    Deferred · deep water

Two product philosophies

Both are about handling documents in software, yet the producer mindset and the process mindset want nearly opposite things. Discussing them together pleases nobody.

Process

Readers · Developers

A document is a node, not an endpoint. What matters is linking, search, history and plugins — so that accumulation compounds.

  • Built for long-term knowledge accumulation
  • Success means accumulation compounding
  • Requires portable source text that AI can read

Produce

Researchers · Office

A document is an endpoint, not a node. What matters is formatting rules, layout and export — the deliverable has to pass.

  • Benchmarked against Word, Excel and PowerPoint
  • Success means a deliverable that passes
  • Requires what-you-see-is-what-you-get

Entry points

Where each group starts

The page in this site that answers each group's first question.

Writerdaily notesoutlinesexport to WordResearcherpaper notesbacklinksgraph mapTeam leadmeeting logswiki linkslocal-first

The resolution: thinking in Textrix, delivery by export

One editor cannot be optimal for both philosophies at once — so instead of forcing it, Textrix draws the boundary clearly.

Common questions

I am not one of these four. Can I still use it?

Yes. The four groups are an order of entry, not a gate — if your knowledge is worth accumulating, Textrix applies to you.

Why not start with office work?

Spreadsheets, drag-and-drop layout and flowcharts are thirty years of accumulated depth, and users are usually locked into the suite their company buys. Rather than charge at that, we would rather do the knowledge side as well as it can be done.

Why do researchers not need general-purpose layout?

Journals and universities provide their own templates, so general layout has low marginal value for researchers. The real pain is reference management, citation and organising content — which is exactly Textrix territory.

Related

Keep exploring

From who it serves to how the pieces fit together.

Still in development

Downloads are not open yet. Join the waitlist and we will invite you the moment it opens.

Email-collection mode: submitting opens a pre-filled message in your mail client.