Hi HN,

We’re building *Lix*, a change control SDK that tracks every modification in your files or apps—no matter the format. Think of it like Git, but for *any* digital file, running in your browser.

## What is Lix?

Lix is a *file-agnostic change control system* that works across different environments. It lets you: - *Track every change* made to a file or app, whether by humans or AI - -See what changed, when, and by whom** - - Integrate version tracking into your own applications via our SDK

This means *AI-generated edits* (e.g., AI-assisted writing, automated code suggestions) are no longer a black box—you can see exactly what changed and decide whether to keep or revert them.

## Why Did We Build It?

We originally built *inlang.com*, a localization solution, and realized that translators, designers, and developers all needed to track changes across different file types and platforms. Existing tools weren’t flexible enough.

As we iterated, we saw a broader need: *AI-assisted workflows and collaborative apps* require *transparent change tracking*. Whether it’s an AI rewriting text, auto-fixing code, or updating structured data, *users want to review and merge changes, just like they do with Git*.

## Try It Out

We built a few demo apps to showcase Lix: [*Markdown App*](https://lix-md.onrender.com/) – Write Markdown with AI assistance & see exactly what the AI changed. (I drafted this post in it!)

[*CSV App*](https://lix.opral.com/app/csv/?l=lTj18aPHiC93VDrpwW) – Ever had an intern mess up your cap table? Now you can track and revert every edit.

[*Fink*](https://fink2.onrender.com/) – Track and compare changes in the translated text.

## Feedback

We want to position Lix as the *change control SDK for AI-driven workflows*, but we’re still refining our messaging. Would love your thoughts on how to frame this better!

What use cases do you see where *human-AI collaboration* needs better versioning?

Any feedback, ideas, or brutal honesty is much appreciated!