Request early access

Docs

Grixel

Grixel is a place to store, version, and share everything your project is made of — code, and the big binary files that code alone never captures: art, audio, levels, datasets, models. One server holds it all, your whole team works against it, and your AI assistants can read from it under the same rules you do.

If you have used Perforce, Grixel will feel familiar: there is one authoritative server, you check out a working copy, and you submit changes to it. If you have only used Git, the main difference is that Grixel keeps the history on the server rather than cloning it to every machine — which is what lets it handle huge files and fine-grained access control well.

#What you can do with it

  • Version big files without pain. Re-submitting a large asset after a small edit only stores what changed, so history stays cheap even for gigabyte files.
  • Work as a team on one source of truth. Everyone checks out from the same server. You pull others' changes with grixel sync and submit your own atomically.
  • Lock files that can't be merged. Claim an art file or a level before you edit it so two people never collide on something a merge can't fix.
  • See only what you're meant to. You see the projects and files you've been given access to; anything else simply isn't there for you.
  • Review and sign off inside the tool. Approvals are recorded against the exact content they approved, and a protected area won't accept a change until the right people have signed off.
  • Track the work. Lightweight jobs live next to the files they're about, so the backlog doesn't drift off into a separate tool.
  • Work with AI assistants safely. An assistant reads your project's context through a read-only connection and makes changes only through the same commands you'd run — so it can never see or do more than you can.

#Where to start

Then dip into the topic pages as you need them: large files and locking, removing files, branching, sharing and visibility, review and sign-off, jobs, AI assistants, the command reference, and troubleshooting.

#Running the server yourself

Grixel stores everything on a server. Often someone else runs it and just gives you an address and a token. If that person is you — even if it's only on your own machine — start here: