Lix is an embeddable version control system designed to be imported directly into applications as a library, rather than operating as an external, daemon-based tool like Git. Developed by Opral, it provides a comprehensive framework for versioning that includes branches, checkpoints, semantic diffs, rollback, and immutable history. By running in-process, it eliminates the need for managing repository directories, worktrees, or complex protocol overhead, making it particularly well-suited for AI agents and applications that require programmatic control over versioned states. Its architecture revolves around an ACID-compliant transaction model, ensuring consistency across state, blobs, and history in a single operation.

Functionally, Lix parses various file formats into entities, such as spreadsheet cells, document clauses, or structured application records. This allows for granular, semantic change tracking instead of traditional line-based diffs. Changes are stored as a journal of data rather than snapshots, which enables developers to query history, audit trails, and specific entity modifications using standard SQL. This SQL-based interface allows AI agents or application logic to inspect, filter, and manipulate versions without the performance penalty of re-reading entire files, significantly improving efficiency in AI workflows.

Some of the key features are:

• In-Process Execution: Runs as a library inside the host application without requiring daemons, protocols, or external CLI calls.
• ACID Transactions: Ensures atomic, consistent, isolated, and durable operations across files, blobs, and history metadata.
• Semantic Change Tracking: Moves beyond line-based diffs by tracking entity-level changes in structured formats like XLSX, DOCX, and JSON.
• SQL Interface: Exposes version history and changes via standard SQL queries, enabling efficient programmatic access to historical data.
• Pluggable Backends: Supports multiple storage adapters including SQLite, Postgres, S3, and Cloudflare Workers, allowing integration with existing infrastructure.
• Parallel Versioning: Enables multiple isolated workspaces or branches simultaneously without the overhead associated with Git worktrees.

Lix is utilized by opening an instance within the host runtime and configuring a backend, such as a SQLite database. Once initialized, developers can interact with the system using SDK methods to manage files, create versions, and perform merges. Because Lix manages changes as queryable data, complex logic like rolling back a specific change or auditing who modified a particular entity becomes a straightforward database query. This approach provides a robust foundation for building versioned, AI-native applications where human-in-the-loop oversight is required for automated edits.

Some common use cases include:

• AI Agent Workspaces: Providing agents with isolated, versioned environments for task execution with automatic audit logs and rollback capabilities.
• Versioned Databases: Adding time-travel and version control to existing SQL databases like PostgreSQL or SQLite for reviewable migrations and record history.
• Document Collaboration: Implementing redlining, tracking changes, and versioning for complex formats like DOCX or CAD files at an entity or clause level.
• App State Versioning: Managing complex application states in CMS tools, design software, or configuration services to allow end-users to revert changes easily.