MongoDB config changes should not move by copy-paste
Many teams store critical product behavior inside MongoDB. That metadata controls how the product works, but changes are often moved manually between dev, staging, and production.
MaGit gives MongoDB metadata a release workflow
Treat MongoDB-backed configuration like a versioned repository. Save versions, push to remote, create releases, review deployment plans, and roll back safely.
Know exactly what changed, when it changed, and who changed it in your database.
Review structural metadata changes side-by-side before they ever reach production.
Promote stable, semantic versions instead of copying raw, unverified database state.
Plan first, apply second. Generate deployment plans to visualize the execution path.
Instantly restore a previous production state using automatically captured checkpoints.
Keep a permanent ledger of commits, releases, deployments, and rollback events.
MaGit feels familiar because the workflow maps directly to Git concepts. You keep MongoDB credentials on your machine or CI.
MaGit snapshots selected metadata, stores immutable objects, manages releases, and applies approved deployments to target environments. X12I storage acts as your remote repository.
MaGit is highly specialized. It is not a generic database tool.
Use MaGit to version and deploy collections that control product behavior:
MaGit is not for full database backup, transactional data, or high-volume operational collections.
Commit snapshots, push/pull history, and keep immutable objects in remote storage.
Create releases, plan deployments, apply to environments, and roll back from checkpoints.
Get up and running in minutes.
Install the CLI globally via npm.
npm install -g @x12i/magit
Login to set up your remote object store.
export X12I_MAGIT_TOKEN="..." magit login \ --storage-url https://api.x12i.com/magit-storage \ --token-env X12I_MAGIT_TOKEN \ --tenant customer-workspace
Connect your local database and initialize the metadata repo.
export MONGO_URI="mongodb+srv://..." magit init \ --driver mongo \ --url-env MONGO_URI \ --db customer_db \ --name customer-repo \ --storage-provider x12i-http
After using MaGit, you will say:
Version workflow definitions, approvals, routing rules, and automation logic.
Track dashboards, forms, admin settings, and feature configuration safely.
Promote tenant configuration, feature flags, templates, and catalog metadata.
Version agent instructions, tool configuration, memory descriptors, and workflow graphs.
Deploy forms, pages, automations, and customer-specific metadata without breaking live apps.
MaGit includes planning, protections, snapshots, and rollback workflows out of the box.
Preview exact insertions, updates, and deletions before applying.
Require plans, confirmations, and pre-deploy snapshots for prod.
Capture the exact target state before any deployment modifies it.
Run validation rules before release, deploy, or promote actions.
Preflight estimates, batching, throttling, and confirmation thresholds.
Use structured JSON output and progress events for automation pipelines.
Use X12I like GitHub for your metadata repositories.
Your MongoDB credentials stay local or in CI. MaGit pushes versioned metadata objects to X12I storage, where repositories, releases, and deployment history are managed centrally.
The MaGit CLI already supports the core workflow. The upcoming hosted dashboard will make metadata release management visible to the whole team.
Future UI Modules
Stop moving production configuration by hand. Commit your metadata, review the diff, create a release, deploy safely, and roll back when needed.
npm i -g @x12i/magit