Documents and notes decision

Octree

A capable developer can build a single-user AI-assisted LaTeX editor with a compile service and basic AI integration within a few weeks, but reproducing Octree's full product (collaboration, enterprise features, and hosted compile caching at scale) is more work and not practical as a small DIY.

Visit website
You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off160 h to build

$40/mo6 h/mo upkeep

No published price to break even against.

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Octree alternatives, with the arithmetic →

What a replacement has to do

  • A single-user web LaTeX editor that accepts/edits .tex files, offers AI-assisted text suggestions, and produces PDF output via a compilation service.

What it still won’t have

  • Real-time multi-user collaboration and fine-grained version control
  • Enterprise features (privately hosted AI model, dedicated support, integrations)
  • Octree's compile-service caching optimizations and LRU-managed in-memory cache
  • Built-in templates, tutorials, and curated LaTeX tools library

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Octree does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a single-user web LaTeX editor and compile service using React + Monaco editor for the frontend, Node.js (Express) backend, Postgres (or SQLite) for project metadata, and a Dockerized TeX Live container to run pdflatex/xelatex. Core features in scope: (1) upload/create multi-file LaTeX projects, (2) edit .tex files in-browser with syntax highlighting, (3) compile endpoint that runs TeX Live in a sandboxed container, returns PDF binary, and implements file-set content hashing for caching, (4) PDF preview using pdf.js, (5) AI-assisted edit endpoint that forwards selected text to an LLM (OpenAI-compatible) and applies returned edits, (6) basic user auth and project persistence. Out of scope: real-time multi-user collaboration, enterprise private-model hosting, advanced template marketplace, and billing/subscription management. Include error handling for compile timeouts, sandbox failures, and LLM errors; include unit tests for backend endpoints and end-to-end tests for compile+preview flow.
How we checked4 sources · 3/3 runs agreed · evidence score 64

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 4 cited sources+3
  • 3/3 assessment runs agreed+4
  • Evidence score64

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 4

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded