Lix
Embeddable version control with semantic tracking for any file format
Lix fills a genuine gap: semantic version control for non-code files, embeddable as a library. Its SQL query over changes and parallel branching are powerful, but integration effort is real. Best for product teams and AI agents needing fine-grained, programmatic versioning, not casual users.
- Product builders needing version control for non-code file editors (documents, spreadsheets, CAD)
- AI engineers wanting workspace isolation and change review for agent edits
- Teams managing binary document reviews (contracts, spreadsheets, legal drafts)
- Developers building a branchable file-based product or artifact registry
- Teams needing a distributed, remote-first VCS like Git with hosting providers
- Users looking for a polished GUI version control for documents (Lix is a library, not an app)
- Projects that require version control solely for plain-text source code (use Git)
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Lix if you need a turnkey version control GUI for documents without coding, or if your primary need is distributed source-code version control (use Git).
There are no direct monetary costs for Lix itself (it's MIT open-source), but you'll incur engineering time to integrate the SDK and build any UI/API around it.
Lix is free (MIT open-source), making it cost-effective for any team that can invest in integration. Compared to hosted document-VCS solutions like Notion or Git-based platforms (GitHub, GitLab) that charge per-seat for private repos, Lix has no recurring fees—but you pay in engineering effort. It's ideal for startups building a file-centric product, not for teams wanting an out-of-the-box solution.
In short
Lix — Embeddable version control with semantic tracking for any file format. Best for Product builders needing version control for non-code file editors (documents, spreadsheets, CAD), AI engineers wanting workspace isolation and change review for agent edits, Teams managing binary document reviews (contracts, spreadsheets, legal drafts). Free to use.
What's new in Lix
Checked 11 days agoAcross the latest 5 updates: 5 changelog entries.
Lix v0.7 Release: Plugin API and a Rebuilt Storage Engine
Lix v0.7 stabilizes the file plugin API and rebuilds the storage engine, resulting in 1.8x faster merges. CSV, Markdown, and text plugins now expose semantic changes.
Lix v0.6 Release: Ready to Embed
Lix v0.6 is the first usable embeddable SDK—open Lix in-process, use in-memory or SQLite backends, branch app state, and query history.
April 2026 Update: Adopting DataFusion
DataFusion path runs core MVP flow. April missed 10k insert target, clarified need for control from query to storage.
March 2026 Update: No Corruption Bugs, 8x Faster Than Git, Semantic Writes Still Too Slow
500 real commits replayed with no corruption. Without semantic layer, 8x faster than Git; semantic writes bottleneck on write amplification.
February 2026 Update: Rust Rewrite Complete
Rust rewrite complete. 33x faster file writes, trended on HackerNews.
Viability Score
How likely is Lix to still be operational in 12 months? Based on 4 signals — momentum (how recently it shipped), wrapper dependency, revenue model, and web presence.
Last calculated: July 2026
How we score →Key Features
- Semantic change tracking per entity (cell, clause, property)
- Branching and merging for any file format
- ACID transactions over files and history
- SQL query interface for change history
- Plugin system for custom file format parsers
- In-process embedding (no daemon/remote protocol)
- Real-time sync across users, agents, and devices
- Revision checkpoints and rollback
- Validation and automation triggers on file changes
- Pluggable storage backends (SQLite, Postgres, S3, in-memory)
- Rust rewrite for performance (1.8x faster merges in v0.7)
- Immutable change journal with SQL access
- File support: Markdown, DOCX, XLSX, JSON, PDF, CAD, custom
- Built-in plugins: CSV, Markdown, text
About Lix
Lix is an open-source (MIT) version control library that tracks, branches, merges, and rolls back changes across Markdown, DOCX, XLSX, JSON, PDFs, CAD files, and custom file formats. Instead of whole-file text diffs like Git, Lix exposes structured entity-level changes—paragraphs, cells, properties, clauses—and lets you query change history with SQL. It runs in-process inside your runtime (browser, desktop, server, CLI, worker) with no daemon or remote protocol. With pluggable storage (SQLite, Postgres, S3, in-memory), ACID transactions, and real-time sync, Lix is designed for product builders, AI workflows, and knowledge base editors who need programmatic version control beyond source code. As of v0.7, the Rust rewrite delivers 33x faster file writes and 1.8x faster merges, and the plugin API is stabilized for CSV, Markdown, and text.
Behind the Verdict
Lix is a unique open-source library that brings Git-like workflows to files that Git handles poorly—binary documents, spreadsheets, JSON configs, CAD models. Its semantic change tracking (e.g., 'this cell changed from pending to shipped') is a genuine innovation over whole-file diffs, and exposing history via SQL is a developer-friendly touch. The Rust rewrite (v0.7) makes it fast: 33x faster file writes and 1.8x faster merges. Pluggable storage backends and in-process embedding mean you can drop it into an Electron app, a CLI, or a Cloudflare Worker without running a separate daemon. Weaknesses: it's early stage (v0.7 as of June 2026), so documentation and plugin ecosystem are still maturing. Semantic writes are a noted bottleneck—write amplification can slow down large-scale use. There's no hosted cloud service or GUI, so non-technical users are effectively locked out. It won't replace Git for source code (and doesn't try to), and teams needing a turnkey VCS for documents should look at Notion or Git-based tools instead. For product builders shipping an editor, knowledge base, or AI agent workspace, Lix is a compelling foundation.
Researching Lix? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas Lix actually fits — and what changes day-one when you adopt it.
You're building a collaborative Markdown editor for technical writers. You embed Lix via npm, open it with an FsBackend pointing to a local workspace, and register a Markdown plugin. As writers edit documents, Lix tracks per-paragraph changes. You build a review UI that queries lix_change with SQL to show diffs, and allow rollback to any checkpoint.
Outcome: Your editor ships with undo/redo, branching for drafts, and audit history—built in days instead of months, with no custom history system.
You deploy an AI agent that edits JSON configuration files. For each agent run, you call lix.createBranch() to isolate changes. After the agent finishes, you query lix_change to review which fields were modified, then merge accepted changes back to main or discard the branch.
Outcome: You have full visibility into agent decisions, can revert mistakes with a single SQL query, and never lose the original state—no manual diffing or copy-paste.
You use Lix to version infrastructure-as-code configuration files (YAML/JSON) across environments. You script Lix in a CI pipeline to create a branch per deployment, capture changes, and then merge to main after validation. SQL queries alert on unexpected property modifications.
Outcome: Configuration drift is caught early, every environment change is auditable, and rollback is as simple as switching to a previous branch.
Use Cases
- Track revisions in a collaborative markdown editor with per-paragraph diffs
- Run AI agents on isolated branches and review their edits via SQL queries
- Add rollback and audit trail to a spreadsheet application
- Merge conflicting edits in a CAD model by viewing per-part changes
- Version configuration files for DevOps pipelines with property-level history
- Build a versioned artifact registry for machine learning models
Models Under the Hood
as of 2026-07-06
Limitations
- Lix is early stage (v0.7 as of June 2026); it may have bugs and limited documentation.
- It is a library, not a standalone application, so users must integrate it themselves.
- Semantic writes have been noted as a bottleneck (write amplification).
- There is no hosted cloud service or GUI for non-developers.
as of 2026-07-06
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Plans compared
For each published Lix tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Open Source
$0
Ideal for
Any developer or team that can integrate an SDK; no per-seat cost, full feature access including SQL query, branching, and pluggable storage.
What this tier adds
Free entry point—no commercial license needed; all features available under MIT license.
Where the pricing makes sense
The company stage and team size where Lix's pricing actually pencils out — and where peers do it cheaper.
Lix is free (MIT open-source), making it cost-effective for any team that can invest in integration. Compared to hosted document-VCS solutions like Notion or Git-based platforms (GitHub, GitLab) that charge per-seat for private repos, Lix has no recurring fees—but you pay in engineering effort. It's ideal for startups building a file-centric product, not for teams wanting an out-of-the-box solution.
Setup time & first value
How long it actually takes to get something useful out of Lix — broken out by persona, not the marketing-page minute.
For developers: <1 hour to install the SDK and run the getting-started demo. Adding a custom file-format plugin takes a few days depending on complexity. Non-technical users: no direct setup path (Lix is a library).
Switching to or from Lix
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From Git: Rewrite file repositories to use Lix's SDK—no automated migration tool available; you'll need to replay file history into Lix via the SQL interface.
- ↗To Git: You could export file snapshots per branch/version and commit them to Git, but you'd lose semantic change history and SQL queryability.
Resources & Guides
- Documentationlix.dev
Docs · Lix
Full product docs from lix.dev
- Documentationlix.dev
What Is Lix · Lix
Full product docs from lix.dev
- Quickstartlix.dev
Getting Started · Lix
Get up and running fast from lix.dev
- Documentationlix.dev
Comparison To Git · Lix
Full product docs from lix.dev
- Resourcelix.dev
Blog · Lix
Helpful link from lix.dev
- Resourcegithub.com
Lix · Lix
Helpful link from github.com
Official links
Tools that pair well with Lix
Common stack mates teams adopt alongside Lix, with the specific reason each pairing earns its keep.
Featured Head-to-Head Comparisons
Alternatives to Lix
View all
Chrome DevTools MCP
Open-source MCP server for live Chrome browser control and DevTools debugging
Spider Cloud
Fast web crawling, scraping & search API for AI agents
Arize Phoenix
Open-source AI observability for LLM agent tracing and evaluation.
Frequently Asked Questions
Used Lix? Help shape our editorial sentiment research.