> ## Documentation Index > Fetch the complete documentation index at: https://docs.vetrasuite.com/llms.txt > Use this file to discover all available pages before exploring further. # Vetra Blueprints > Build. Version. Migrate. Deploy. Version, migrate and deploy your Garry's Mod server setup. Your server setup is a build. It took weeks, it lives in one map on one server, and the only record of how it got there is your memory of doing it. Blueprints treats it as what it is: a project with a history. Two folders into `garrysmod/addons/`, then restart. No key, no config file. Capture a Version, change something, read the diff, put it back. Teach Blueprints to manage the objects your own addon owns. ## What it does Capture the managed state of your server as an immutable, timestamped Version. Browse the history, inspect what any Version contained, compare any two. Treat a market stall or a checkpoint as the one thing you built rather than as forty props. Each group carries its own anchor. Rebuild a group captured on one map onto another, with a ghost preview in the world before anything is created. Return the managed world toward an earlier Version. The full plan is shown before the first change, and a failed restore rolls back and verifies the rollback. Build on a development server, deploy to production. By exported package file, or through Vetra with Remote Deploy. Props, NPCs, DarkRP job spawns and MalboroDEV PermaProps ship in 1.0. The Adapter SDK is public, so any addon can add its own. ## Git for your server setup, up to a point The analogy is useful and it has an edge. Blueprints gives you an immutable history, an object-by-object diff and a way to move a build between machines. It is **not** a distributed version control system: there is no merge, no branch and no rebase, and a Version is a full record of the managed world rather than a patch on the one before it. It is also authoritative only over the object types it has an adapter for. Everything else on your server is outside its authority, and it says so rather than guessing. The support matrix, per object type, per operation. ## For developers An **adapter** teaches Blueprints one domain. It lives in your own addon, it registers through one public hook, and it never touches Blueprints' internals. What an adapter is responsible for, and what Blueprints does with it. A registered, capturable adapter in one file. The example adapter that ships with Blueprints, section by section. Every public function, with its exact signature and realm.