Version control for Fusion 360 designs
Fusion is cloud-native. OpenVault adds an offline Git-based layer for exporting STEP, native Fusion files, drawings, and BOMs. Get a complete design history, branching for variants, and conflict-free collaboration.
The Fusion 360 workflow with OpenVault
Autodesk Fusion 360 stores designs in the cloud, which is convenient for real-time collaboration and automatic backups. But cloud-only storage can feel fragile when your design work depends on network connectivity, and audit trails live inside Fusion's UI rather than in a portable, Git-based history.
OpenVault sits alongside Fusion, tracking the files you export: STEP models, native Fusion exports, engineering drawings, and bills of materials. When you finish a design pass, you export the model to STEP, save the drawing PDF, and export the BOM CSV. Those files land in an OpenVault repository, where they become a commit: timestamped, authored, with a message explaining the change.
The result is a parallel version history that lives in Git, independent of Fusion's cloud. You can branch to explore design variants, diff two revisions to see what geometry changed, work offline, and sync when connected. The history is yours to keep, export, and audit.
What you version in OpenVault
STEP models
Fusion exports to STEP (.step, .stp), the universal 3D format. OpenVault routes STEP files through Git LFS for efficient storage and tracks full revision history.
Native Fusion exports
Export Fusion's native format (.f3d or proprietary exports). OpenVault tracks these files as-is for a faithful backup of your original design.
Engineering drawings
Fusion generates PDF drawings linked to the model. Version them alongside the geometry so drawing revisions stay coherent with model changes.
Bills of materials
Export BOM data as CSV or spreadsheet. Track component lists, quantities, and sourcing info as part of the design commit.
A day with Fusion and OpenVault
You're working on a mechanical enclosure in Fusion. You sketch a feature, extrude it, and the model looks good. Now you export: STEP to a folder, PDF drawing to the same place, and a CSV BOM. You run openvault commit "Add mounting tabs" and those files become a timestamped entry in your history.
Tomorrow, a team member suggests a different approach. You create a branch: openvault branch variant/side-mounts. Now you can iterate freely in Fusion, exporting new versions to the branch. The main design stays stable. When the variant is ready, you merge it back. All the revisions are recorded.
Later, a manufacturing review asks "what changed in the bracket between last month's release and this week's version?" Without version control, you'd search email and shared drives. With OpenVault, you run openvault log and see every export, author, and commit message. You can diff the two STEP files with ToolCrib to see exact geometry changes.
The audit trail is a byproduct of how you work. Tracking files as commits is how you do your job, so the audit trail happens automatically.
How Fusion + OpenVault + ToolCrib work together
Fusion handles design: parametric modeling, cloud collaboration, real-time updates. OpenVault handles version control: commits, branches, offline sync, portable history. ToolCrib CLI handles CAD operations: format conversion, visual 3D diff, batch automation.
When you have two STEP versions exported from Fusion, ToolCrib's 3D diff command shows you exactly what geometry changed. Color-coded output (green for added faces, red for removed, gray for unchanged) makes it instant to spot design deltas.
The three tools form a complete workflow: design in Fusion, version in OpenVault, analyze with ToolCrib. Each tool does one thing well.
OpenVault capabilities for Fusion workflows
Commit and branch
Every design export becomes a commit. Branch to explore variants without touching the main design.
Offline-first workflow
Export files locally, commit to OpenVault, sync when you're connected. No network dependency.
Multi-file coherence
One commit captures the model, drawing, and BOM together. The pieces that belong together travel together.
Audit trail
Every change recorded with author, timestamp, and message. Compliance-ready history for regulated industries.
Diff and history
See what changed between revisions. Full timeline of who changed what and when.
Git LFS for large binaries
STEP files and native Fusion exports handled efficiently. No bloated repositories.
Fusion and OpenVault
- Does OpenVault replace Fusion's cloud storage?
- No. Fusion's cloud is your primary design workspace. OpenVault sits alongside it, capturing exported files (STEP, drawings, BOMs) as an offline Git-based history. You keep using Fusion as normal. When you want a version-controlled snapshot, you export and commit to OpenVault. The two systems complement each other.
- Why export to STEP instead of keeping Fusion files?
- STEP is the universal 3D format. Any CAD tool can read it, and ToolCrib can perform geometry operations on it (diff, conversion, properties). Storing STEP files in OpenVault gives you a format-agnostic, multi-CAD history. You can also export Fusion's native format if you want a Fusion-specific backup, but STEP makes the data portable.
- Can I use OpenVault offline while designing in Fusion?
- Fusion itself requires internet for real-time cloud collaboration. OpenVault works offline for its own operations (commit, branch, diff, history), but you export from Fusion while connected. Once exported, you can commit to OpenVault without network access, then sync when you reconnect.
- How do I handle design variants with Fusion and OpenVault?
- In Fusion, you might have multiple feature branches or parameters to explore a design. When you land on a variant worth keeping, export the STEP and drawings. In OpenVault, create a branch (e.g., 'variant/reinforced-base'), commit those exports there, and iterate. Once the variant is approved, merge it back to main. All variants and their timelines remain in the history.
- What happens if two people export from Fusion to the same OpenVault file?
- OpenVault will flag the conflict and show both versions. It does not try to automatically merge two STEP files because automatic merging of 3D geometry is not a solved problem. You manually review both versions and commit the one that reflects the correct design intent. This conflict handling keeps your design safe and your history trustworthy.
- Can I use ToolCrib to compare Fusion exports?
- Yes. Export two STEP files from Fusion at different points (e.g., before and after a design review). Run ToolCrib's 3D diff command to see exactly what geometry changed: additions in green, removals in red, unchanged geometry in gray. This is much faster than manually inspecting the files.
Start versioning your Fusion designs
OpenVault is free and open source. Install it with pip, export your Fusion files, and build a version history you own and can audit.