| emne | af SolidCraft | Frigør |
|---|---|---|
| Tilladelse | MIT eller Apache 2.0 (dual) | LGPL-2.0 eller senere (applikation) |
| Geometri af kernel | Pure-Rust B-rep stack (SolidCore / projektkernel arbejde) | OpenCASCADE teknologi (OCCT) |
| UI model | Enkeltparametrisk editor + funktion timeline | Workbench-baseret (PartDesign, Sketcher, TechDraw, Path, FEM, ...) |
| Sketch begrænsninger | Begrænsede skitser på timeline | Sketcher arbejdsbænk (mature constraint solver) |
| Maturitet | Tidligt; “anvendelig til enkle dele” pr. projekt | Moderne 1.x linje (1.1.4 vedligeholdelse fra 2026-09) |
| Tegninger / CAM / FEM | Ingen CAM/FEM i appen; tegninger er i gang (ikke leveret) | TechDraw, Path (CAM), FEM arbejdspladser |
| Native format | .scÆldre.solidcraftDet er åbent) | .FCStd |
| Udveksling | STEP, IGES, 3MF, STL og OBJ.FCStd/Rhino via cadmpeg | STEP, IGES, STL, SVG, DXF, OBJ, IFC, DAE, and more |
Fusion .f3d | No native importer documented — use STEP | No first-party Fusion native importer (use STEP/interchange) |
| platforme | Windows / macOS / Linux desktop + official wasm web app | Windows / macOS / Linux desktop (primary) |
| Scripting | JSON command scripts, headless CLI, unit-aware parameters | Deep Python API, macros, workbench addons |
| AI / MCP | Built-in SolidCraft-cli mcp | Community MCP bridges (e.g. FreeCAD-mcp); not core |
af SolidCraft models solids with a pure-Rust B-rep approach and an editable feature timeline (sketch → extrude/fillet/shell/… → change a parameter and rebuild). The project also develops solidkørsel as a Rust geometry kernel effort.
Kernel status (October 2026): current releases still model with the project’s own Rust kernel
(crates/kernel/). On 21 October 2026 the maintainers paused new kernel work while they evaluate moving
SolidCraft to SolidCore, a safe-Rust port of NVIDIA’s SMLib B-rep kernel (Apache-2.0). SolidCore’s README says about a third
is ported and it is not usable end to end yet. Work outside the kernel (interface, sketching, drawings, assemblies) carries on,
and crash or data-loss reports are still welcome
(announcement,
SolidCore status). Background:
SolidCraft’s kernel, truck and SolidCore explained.
Frigør builds on OpenCASCADE (OCCT), a long-standing C++ CAD kernel, and exposes modelling through specialized workbenches. That modularity is FreeCAD’s strength for drawings, CAM, FEM, and BIM-oriented tasks.
examples/bracket.json opened in the SolidCraft web app — typical simple-part scope..FCStd via cadmpeg on desktop, in the browser app and in the CLI (geometry import; history not preserved)..f3d: neither project documents a faithful native Fusion history importer; export STEP from Fusion first.Not today for most production workflows. FreeCAD (latest stable 1.1.x) is a mature, workbench-based suite with TechDraw, Path/CAM, FEM and a huge addon ecosystem. SolidCraft is early, focused on parametric solids, a single editor workflow, and first-class MCP/CLI automation.
Yes for solids via the documented cadmpeg path (same family as STEP import) in the desktop app, browser app and CLI: you get geometry as an Import base feature, not FreeCAD’s full parametric history. Prefer STEP when you only need B-rep interchange.
SolidCraft ships SolidCraft-cli mcp in-tree. FreeCAD MCP exists as community projects (for example neka-nat/FreeCAD-mcp) that typically require FreeCAD running with an addon or bridge—not a built-in stdio server in the core app.
If you want a local, headless CAD command surface with one binary, SolidCraft’s MCP is designed for that. FreeCAD agents usually drive FreeCAD through community MCP bridges and Python. Pick based on whether you need FreeCAD’s workbenches or SolidCraft’s agent-native CLI.
FreeCAD includes TechDraw, Path (CAM), and FEM workbenches. SolidCraft’s public roadmap defers drawings, CAM/manufacture, and simulation.
Relateret til:Læs mere om SolidCraft vs Fusion 360 · Installation af guide · MCP Tutorials · FreeCAD MCP vs other CAD MCP servers · SolidCraft anmeldelse.