About

A small editor for a focused craft.

Citet is a self-hostable collaborative LaTeX editor built by people who use LaTeX every day. It is not trying to be a research-management platform or an office suite — it is trying to be a good editor.

01

Why Citet exists

LaTeX work tends to fragment across local editors, cloud drives, email threads, and git repositories. Existing collaborative editors fix some of that, but often at the cost of giving up the local toolchain researchers rely on.

Citet aims for the smaller goal of being a real-time collaborative editor that is comfortable for people who would otherwise stay in Neovim or VSCode, and pleasant enough for people who prefer the browser. The two should be able to work on the same document at the same time without friction.

02

What this project values

  • OpenThe source is public and the data is portable. A research group should be able to walk away with their projects intact at any time.
  • QuietNo nudges, no upsells, no animated onboarding flows. The editor opens, the document compiles, the cursor blinks.
  • Local-friendlyEditor integrations are first-class. Collaboration should not be punishment for preferring vim or LSP-driven workflows.
  • EuropeanThe hosted instance runs in the EU. Self-hosting is a first-class option for groups that need full control.
03

Who builds it

Citet is maintained by a small group of programmers and researchers who write LaTeX themselves. That has shaped the priorities: SyncTeX, BibTeX/Zotero, real editor keymaps, and a compile pipeline that does the obvious thing on the first run.

Contributions, issues, and questions are welcome on the GitHub repository. If you use Citet in a research group or course and want to share what is working or missing, we would like to hear about it.

04

Project status

Citet is under active development. Core editor, collaboration, compilation, citation support, and editor integrations are functional. Multi-organization workspaces and a few operational features are still being built out.

The roadmap is intentionally narrow. Features that pull the project away from the core editing experience are usually deferred or declined.