Lix is live · free · last verified 5 Nov 2026 · viability monitor
Lix
MIT-licensed version control that keeps any file format and your SQL tables in a single ACID repository.
Lix is the rare backend that can hold an agent's automation script, a customer's 4.8 GB launch video, and the orders row they touch in one branch, with accept-or-undo expressed as SQL against lix_change rather than a feature you build. The inlang move off Git is evidence the pattern has real users, and v0.17's partial replicas make the browser story practical. Go in knowing you are embedding an alpha-stage library with no shipped review UI and no shipped permissions, not installing an app — and that Git remains the simpler choice if you only version text source.
Verdict generatedVerified 9d ago · liveness 69/100 · cite: rightaichoice.com/tools/lix
- AI product teams whose agents write files or automations that need review and undo
- SaaS products giving each customer a hosted repository with diffs and rollback
- Apps that read and write SQL rows plus normal files and want history as a query
- Developers needing structured diffs on Markdown, CSV, JSON, or XLSX rather than byte diffs
- Teams wanting a finished GUI document version control app — Lix is a library you embed
- Projects versioning only text source code, where Git is simpler and familiar
- Non-technical users who cannot embed an SDK or write SQL against internal tables
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 want an off-the-shelf app for reviewing document revisions rather than an SDK plus SQL you embed and build a review UI around yourself.
Lix is MIT licensed at $0 to embed in commercial products, with no per-seat or per-repository fee in the published material. Your real cost is engineering time: the review UI, the diff views, and the accept-or-undo flow are yours to build, and plugin coverage beyond Markdown and CSV is work you take on. For a text-only code repository, Git costs you nothing and needs no integration.
In short
Lix — MIT-licensed version control that keeps any file format and your SQL tables in a single ACID repository. Best for AI product teams whose agents write files or automations that need review and undo, SaaS products giving each customer a hosted repository with diffs and rollback, Apps that read and write SQL rows plus normal files and want history as a query. Free to use.
What is Lix?
Lix — MIT-licensed version control that keeps any file format and your SQL tables in a single ACID repository. Best for AI product teams whose agents write files or automations that need review and undo, SaaS products giving each customer a hosted repository with diffs and rollback, Apps that read and write SQL rows plus normal files and want history as a query. Free to use.
Lix is an embeddable version control system for products whose data is split between files and a database. You store any file format — Word, PowerPoint, CAD, XLSX, multi-GB video — next to the SQL tables you define, and files, rows, and history share one ACID OLTP database. File plugins map parts of a document to rows, so a Markdown block, a CSV record, a JSON property, or a spreadsheet cell becomes something you query with SQL instead of diffing byte by byte. You run Lix in-process as a library through the JavaScript, Rust, Python, or Go SDK, or point it at a hosted server URL when several machines need the same repository. Storage is pluggable across memory, filesystem, browser OPFS, and S3; with FilesystemStorage the file stays a normal file on disk while its rows stay queryable. Tracked writes commit automatically, and every change carries an author, so history, blame, branching, and rollback become SQL queries against lix_change rather than features your team builds. The current release is v0.17, which added partial replicas: LixRay loads browser data on demand and syncs changes back to an S3-backed server. v0.16 crossed 500k weekly npm downloads, the project reports 767 GitHub stars, and inlang put Lix in front of more than 100,000 users. It is positioned against Git on a narrow point — Git versions files well, but the tables behind an app live elsewhere, and committing a SQLite file versions bytes rather than reviewable rows. If you want a finished GUI document versioning app, this is not it: Lix is a library and you define the tables.
Key features
- Store files of any format alongside SQL tables in one ACID OLTP repository
- Branch, diff, merge, and roll back files and app rows together
- Automatic commit on every tracked write — no commit command to run
- Query history, blame, and row snapshots with SQL against lix_change
- Structured diffs via plugins mapping paragraphs, CSV records, and properties to rows
- Markdown and CSV plugins ship with the JavaScript SDK
- JSON, plain text, and Excalidraw plugins install with one SQL statement
- SDKs for JavaScript, Rust, Python, and Go
- Pluggable storage: memory, FilesystemStorage, browser OPFS, or S3
- FilesystemStorage keeps files on disk as normal files while rows stay queryable
- Server mode via a hosted repository URL for multi-machine work
- Partial replicas with on-demand sync into browser storage (v0.17)
- Real-time collaboration: clients on the same server see changes via lix.observe()
- Handles text, binaries, CAD, Office files, and multi-GB media
- Per-customer hosted repository pattern for embedding version control in a SaaS
Behind the verdict
The pitch is narrower than "Git replacement" and stronger for it. Git versions files well, but the tables behind an application usually live in Postgres or SQLite, so committing a SQLite file records bytes rather than rows — hard to review, hard to merge, and each revision bloats the repository. Lix puts your app tables in the same repository as the files, versions them as queryable SQL rows, and commits every tracked write automatically, so there is no commit command to forget. The docs are explicit about the boundary: Lix versions tables your app defines and writes through Lix, and does not automatically version tables in an external database. What you actually get on day one is a library and a SQL surface. openLix() takes either a storage backend (memory, FilesystemStorage, browser OPFS, S3) or a server URL; from there you INSERT into lix_file, UPDATE your registered tables, and query lix_change for created_at, account_id, schema_key, row_pk, and snapshot_content to build a history sidebar, diff view, or undo button. With FilesystemStorage the directory stays a normal directory on disk while its rows stay queryable, which is the setup that makes sync between a machine and a server feel unremarkable. Clients on the same server see each other's changes through lix.observe(), and v0.17's partial replicas mean a browser client can pull data on demand instead of downloading a whole repository — LixRay uses exactly that against an S3-backed server. The plugin model is where structured diffs come from, and it is also where the honesty starts. Markdown and CSV plugins ship with the JavaScript SDK; JSON, plain text, and Excalidraw install with one SQL statement. Everything else — your .docx, your .step CAD model, your .mp4 — gets whole-file history, not a paragraph- or property-level diff. That is a real capability difference, not a footnote, and it decides whether Lix is worth adopting for a given format. The gaps are structural rather than bugs. There is no GUI for reviewing or merging changes; you build the accept/undo interface yourself. Permissions are listed as planned — per file, per group, stored in the repository and versioned like any other change — which means you cannot ship per-customer access control out of the box. The homepage says plainly that Lix is in alpha, so pin SDK versions and expect API movement across releases. And the audience is developers: if your team cannot embed an SDK and write SQL against internal tables, this is not the tool. Where it fits best is the agent workflow that is otherwise painful to build: run an agent against an isolated branch, then diff its file and row edits with one query and let a human accept or undo. The per-customer hosted repository pattern — one repository ID in the server URL per customer — follows naturally from the same API. If you only version text source code, Git is simpler and your team already knows it.
Limitations
- Lix is an embeddable version control backend, not a standalone application: there is no shipped GUI for reviewing or merging changes, so you build the diff and accept/undo interface yourself.
- Semantic diffs depend on plugins — Markdown and CSV ship with the JavaScript SDK, JSON, plain text, and Excalidraw install with one SQL statement, and every other format gets whole-file history only.
- The docs state it versions tables your app defines and writes through Lix and does not automatically version tables in an external database.
- Permissions are documented as planned (per file, per group, versioned like any other change), not shipped.
- The homepage labels the project alpha, so expect API churn across SDK versions and pin accordingly.
as of 2026-10-31
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.
Is Lix still active?
Lix is live · free · last verified 5 Nov 2026 · viability monitor.
Viability score
How well maintained and how widely used is Lix? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: November 2026
How we score →What's new in Lix
Checked 12 days agoAcross the latest 2 updates: 2 changelog entries.
Lix v0.17: Partial replicas with on-demand sync
Lix v0.17 adds partial replicas; LixRay loads data into browser storage on demand and syncs changes to an S3-backed server.
Lix v0.16: Over 500k weekly downloads
Lix crossed 500k weekly npm downloads and reaches over 100,000 users via inlang. Includes Git and SQLite-WASM benchmarks.
What do users say about Lix?
What people actually say about Lix — is it worth it?
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
ResearchedDiscussed by users across 6 sources (Hacker News, YouTube, Product Hunt, Bluesky, GitHub, Lemmy) · researched Nov 8, 2026.
Weighted by the 79 posts each of 6 sources contributed.
- +One ACID repository holds files of any format alongside queryable SQL rows
- +History, blame, and rollback become SQL queries against lix_change, not custom features
- +SDKs for JavaScript, Rust, Python, and Go cover most backend stacks
- +Storage is pluggable across memory, filesystem, OPFS, and S3
- +FilesystemStorage keeps files as normal on-disk files while rows stay queryable
- −Name clashes with the prominent Nix fork, confusing every public discussion
- −Almost no substantive third-party reviews across the scraped sources
- −Pre-1.0 at v0.17 with ongoing API and schema churn risk
- −No finished GUI — you define tables and file plugins yourself
- −Requires SQL modelling knowledge before it delivers any value
- • S3 storage and egress bills for hosted or partial-replica deployments
- • Engineering time to model tables and write custom file plugins
- • Operational cost of running and backing up your own repository server
How we verified this
Every listed fact about Lix — pricing, features, links, status — is re-read from the vendor's own pages by our verification pipeline and each change is logged with a date; the last pass ran on 5 Nov 2026. Analysis is drafted with AI models and checked against our editorial standards before publishing; see how we verify.
Verification history
We have re-verified Lix 12 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — changed who it suits, switching out, switching in, features, limitations, hidden costs, description, use cases, who should skip it, setup time, pricing fit, pricing tiers, our verdict, summary
- — changed limitations, platforms, pricing page
- — changed features, who it suits, description, our verdict, who should skip it, pricing tiers, summary
- — changed limitations, pricing page
- — changed features, hidden costs, integrations, limitations, switching in, switching out, who should skip it, our verdict, who it suits, pricing fit, setup time, description, use cases, summary
- — changed limitations, pricing page
Showing the 6 most recent of 12 verification passes.
Free to cite with attribution — this page re-verifies continuously.
How much does Lix cost in 2026?
Lix: Free to use. Pricing last verified 5 Nov 2026.
Plans compared
Every published Lix tier, its price as the vendor publishes it, who it fits, and what it adds over the tier below. The 12-month cost projection follows.
| Plan | Price | Billing | Who it's for |
|---|---|---|---|
| Open Source | Free | — | Developers embedding version control for files and app tables inside their own product, from a side project to a SaaS with per-customer repositoriesAdds: Starting tier: MIT licensed at $0, with JavaScript, Rust, Python, and Go SDKs, pluggable memory/filesystem/OPFS/S3 storage, and server mode via a hosted repository URL |
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.
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 MIT licensed at $0 to embed in commercial products, with no per-seat or per-repository fee in the published material. Your real cost is engineering time: the review UI, the diff views, and the accept-or-undo flow are yours to build, and plugin coverage beyond Markdown and CSV is work you take on. For a text-only code repository, Git costs you nothing and needs no integration.
Has Lix's pricing changed?
No plan price for Lix has moved since we began logging in Aug 2026; the pricing page is re-read on every verification pass.
Who should pick Lix?
Pick Lix if you are AI product teams whose agents write files or automations that need review and undo, SaaS products giving each customer a hosted repository with diffs and rollback, Apps that read and write SQL rows plus normal files and want history as a query, Developers needing structured diffs on Markdown, CSV, JSON, or XLSX rather than byte diffs.
Look elsewhere if you are Teams wanting a finished GUI document version control app — Lix is a library you embed, Projects versioning only text source code, where Git is simpler and familiar, Non-technical users who cannot embed an SDK or write SQL against internal tables, Teams needing shipped per-file or per-group permissions — the vendor lists these as planned.
Skip it if Skip Lix if you want an off-the-shelf app for reviewing document revisions rather than an SDK plus SQL you embed and build a review UI around yourself.
GeneratedReal-world workflow fit
Concrete scenarios for the personas Lix actually fits — and what changes day-one when you adopt it.
An agent writes an automation and updates the order rows it touches. You run it on a branch, then query lix_change filtered by account_id and schema_key to pull the changed files and row snapshots into a diff view.
Outcome: The reviewer accepts or undoes the whole change set in one action, and nothing reaches the main branch unreviewed.
Each customer gets a repository ID in the server URL. The customer's documents, spreadsheets, and app tables live in that repository; a browser client loads it as a partial replica instead of downloading everything.
Outcome: Every customer has rollback and history over their own files and app rows without you building a versioning subsystem per tenant.
You register the editor's blocks as rows through the Markdown plugin, write through Lix, and use lix.observe() so clients on the same server see each other's edits as they land.
Outcome: Per-block diffs and history come from SQL queries, and FilesystemStorage keeps the underlying files readable on disk.
Use cases
- Run AI agents on isolated branches and review their file and row edits with SQL queries
- Give each customer a hosted repository so agents can write automations with an accept-or-undo UI
- Track revisions in a collaborative Markdown editor with per-block structured diffs
- Add rollback and audit trail to a spreadsheet app at the cell level via a plugin
- Version configuration files for DevOps pipelines with property-level history
- Sync files agents and applications work on between machines and an S3-backed server
- Co-locate code, documents, media, and app tables under one version history
- Serve browser clients a repository on demand with partial replicas instead of a full download
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.
JavaScript developers reach first value fastest: npm install @lix-js/sdk plus the filesystem storage package, then openLix() against a local directory — a working repository in minutes. Against a server URL it is the same call once the endpoint exists. Rust, Python, and Go follow the same shape. Budget hours, not minutes, for table schemas, a plugin choice per format, and the review UI.
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 for app data: register your tables as Lix schemas, write through Lix, and query lix_change instead of parsing commit history — as inlang did when it moved off its Git pull-request workflow
- →From Git LFS for media: store the large files in a Lix repository with FilesystemStorage or S3-backed storage and keep whole-file history for formats without a plugin
- →From a separate SQLite file committed to Git: commit rows rather than database bytes so changes become reviewable and mergeable
- ↗To Git: export tracked files back to a normal directory with FilesystemStorage — the files were never rewritten — and keep only text source in Git
- ↗To a plain database: Lix tables are SQL, so app rows move to your existing Postgres or SQLite with an ordinary dump
Integrations
Resources & guides
- Documentationlix.dev
Docs · Lix
Full product docs from lix.dev
- Documentationlix.dev
Comparison To Git · Lix
Full product docs from lix.dev
- Documentationlix.dev
Plugins · Lix
Full product docs from lix.dev
- Documentationlix.dev
Storage · Lix
Full product docs from lix.dev
- Resourcelix.dev
Plugins · Lix
Helpful link from lix.dev
Tutorials & Learning
YouTube returned 6 videos for “Lix”, and we withheld 6: 6 could not be judged, because “Lix” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about Lix.
Official links
What are the best Lix alternatives?
The closest alternatives to Lix we list are Dolt, Autumn and Netron. Ranked by direct product-type match, not category overlap.
| Alternative | Pricing | Starts at | Last verified |
|---|---|---|---|
| Dolt | Freemium | Pricing not published | — |
| Autumn | Freemium | Pricing not published | — |
| Netron | Free | Free | — |
Alternatives to Lix
View all
Tools that pair well with Lix
Common stack mates teams adopt alongside Lix, with the specific reason each pairing earns its keep.
Dolt
Dolt is a SQL database with Git-style version control — branch, diff, merge and query your tables as of any past commit.
Autumn
Usage-based billing infrastructure for AI startups: a real-time credit ledger with entitlements and spend controls on top of Stripe.
Netron
Free, open-source visualizer that renders neural network and ML model files as an interactive graph you can inspect layer by layer.
Lix vs its closest rival
Lix's closest head-to-head is with Spider Cloud.
Our Lix vs Spider Cloud verdict written Jul 3, 2026 is more than 90 days old, so it is being re-reviewed against current data and is not shown.
Frequently asked questions
Categories
Best-of guides
For makers of Lix
- Get a Verified Listing for Lix ($39): a written decision within 1 working day.
- Free listing for another tool: Free reviews are decided in order, within 3 weeks of the review starting.
Used Lix? Help shape our editorial sentiment research.