If you're building something over more than a day or two, almost certainly yes. This page explains what version control is in plain terms, how to tell when you need it, and where Grixel fits. No prior knowledge assumed.
#What version control actually is
Version control is a complete memory of your project. Every time you reach a point worth keeping, you submit: the system records the exact state of every file at that moment, forever. Later you can look at any of those moments, compare two of them to see what changed, or bring any file back exactly as it was.
That's the whole idea. Everything else is detail.
#Five signs you need it
Your folder has copies of copies.
final_v2, final_v3_FINAL,
final_v3_FINAL_actually. This is version control done by
hand, and it breaks the first time you can't remember which copy has the
good change. With real version control there is one name per file and
the history lives behind it.
You can't undo past a certain point. Your editor's undo stack ends when you close it. If yesterday's version was better and you saved over it, it's gone. Under version control, yesterday's version still exists, along with every version before it.
An AI assistant edits your files. Assistants are fast and confident, and sometimes wrong. If one rewrote something three days ago and you only notice now, you need to answer two questions: what exactly did it change, and how do I get the old behaviour back? Version control answers both, line by line.
Your files are too big for the usual tools. Most version control was designed for source code, which is small text. Game art, audio, CAD assemblies, video, and datasets defeat it, so those files end up loose on a shared drive with no history at all. The half of your project that's hardest to recreate is the half with no memory.
"It worked yesterday." When something breaks, the fastest question is: what changed since it last worked? Without history, that's archaeology. With it, it's a single comparison.
#Where Grixel fits
Grixel is version control built for the cases the usual tools handle worst:
Big files are normal, not a special case. A 2 GB model file and a 2 KB script live in the same project with the same history. When a big file changes, Grixel stores only the parts that changed, so keeping every version stays affordable.
You take only what you need. Your project might be 200 GB on the server. Your laptop only ever downloads the folders you choose to work on.
Files that can't be merged get locks. Two people editing the same Photoshop or CAD file can't be combined afterwards; one of them loses their work. Grixel lets the person editing hold an exclusive lock, so the collision never happens.
Your AI assistant works inside the same rules.
Connect Claude Code, Codex, opencode, or any tool that reads an
AGENTS.md file, and it sees your project through Grixel:
only the parts you allow, with every change it makes recorded, including
which tool and model made it. Anything you haven't shared is invisible
to it, and invisible means invisible: asking for a hidden folder looks
identical to asking for one that never existed.
It can stay entirely on your hardware. Grixel is one server program you can run yourself, with no cloud account, no third party holding your files, and nothing leaving your machine unless you choose to share it. For client work under NDA, unannounced products, or regulated designs, that's the difference between a policy and a fact. And if you'd rather not look after a server, we can host one for you: your secrets are still encrypted before they ever leave your machine, and a full backup lets you move to your own hardware whenever you like.
History that stands up to questions. Every change records who made it and when. Approvals are bound to the exact content that was reviewed, so "who signed off on this revision?" has a provable answer. If your work ever faces an audit, the trail is already there.
#What it looks like day to day
You work in a normal folder on your machine. When you reach a point worth keeping, you submit with a one-line note about what you did. When you want other people's work, you sync. That's the core loop; the everyday work page shows each step.
You don't need to learn everything at once. Keeping versions and getting them back covers most of what most people need on day one. Locks, reviews, and AI wiring are there when the project grows into them.
#Where to start
- Install the tools and sign in.
- Follow the tutorial: from nothing to a working, versioned project, including connecting an AI assistant.
- Or read what Grixel is for the fuller picture first.
Grixel is pre-release. If it sounds like what you've been missing, request early access and tell us what you're building.