SolidCraft's code is developed in the open on GitHub. This page explains where the official repository is, what is inside it and how to use it, whether you only want to download the app or want to build it yourself.
Where is the official SolidCraft repo?
The repository is github.com/tangency-labs/solidcraft. Older guides, and parts of the documentation, still link to bherbruck/solidcraft, the earlier home of the project. SolidCraft's docs say GitHub redirects links to the renamed repository, so old links keep working, and the redirect leads to the same project.
At the time of writing, the repository's own description reads: "an open-source parametric 3D CAD application built in pure Rust. Desktop, web, and automation through MCP."
| Item | Detail |
|---|---|
| Repository | tangency-labs/solidcraft |
| Language | Rust |
| Licence | MIT or Apache-2.0, at your option |
| Project website | solidcraft.io |
| Docs | docs.solidcraft.io |
| Topics on GitHub | 3d-modeling, brep, cad, egui, mcp, parametric-cad, rust, step, wasm |
Star and fork counts change daily, so check the repository page for current numbers.
What is in the repository?
The top level of the repo has these main folders and files:
| Path | What it holds |
|---|---|
crates/ |
The Rust libraries: geometry, sketch solver, B-rep kernel, document model, file I/O, engine, UI and MCP server |
apps/ |
The programs: solidcraft (desktop), solidcraft-cli and solidcraft-web |
docs/ |
The documentation book and reference pages such as features.md and compatibility.md |
examples/ |
Sample designs and scripts, for example a bracket you can run through the CLI |
tests/ |
Reference tests, including reference parts checked against known volumes and areas |
packaging/ and scripts/ |
Installer and release tooling |
README.md, ROADMAP.md, CONTRIBUTING.md, SECURITY.md |
Overview, plans, contribution rules and security policy |
According to the contributing guide, everything a user can do in SolidCraft is a command, and the toolbar, dialogs, scripts, CLI and MCP server all run the same commands. That is why the same repository serves the desktop app, the browser build and the AI-agent interface. For the agent side, see SolidCraft MCP setup.
Which release file should I download?
Go to the Releases page and open the newest release. At the time of writing the latest release is v0.18.1 (20 October 2026). Each release lists installers for many systems plus a SHA256SUMS.txt file for checking downloads.
| You use | Download |
|---|---|
| Windows (most PCs) | The x64 .msi, or the portable zip |
| Windows on ARM | The arm64 .msi |
| macOS | The universal .dmg |
| Linux | AppImage, .deb, .rpm, Flatpak or Snap |
| Command line only | The solidcraft-cli archive (the macOS build is listed separately) |
| Self-hosting the web app | The solidcraft-web zip |
Because release assets have a version number in the file name, the easiest path is our SolidCraft download page, which links to the latest files and explains the unsigned-installer warning.
How do I build SolidCraft from source?
According to the contributing guide you need a stable Rust toolchain, version 1.95 or newer. Then:
git clone https://github.com/tangency-labs/solidcraft
cd solidcraft
cargo run --release -p solidcraft -- --sample
That builds the desktop app and opens it with a sample part. A few more commands from the docs:
cargo xtask testruns the unit, engine and UI-scenario tests.cargo xtask ciruns everything a pull request has to pass.cargo run --release -p solidcraft-cli -- commandslists every command the engine has.cargo run --release -p solidcraft-cli -- run examples/bracket.json --out bracket.stepbuilds a part from a script and writes a STEP file.
For the browser build you also add the wasm32-unknown-unknown Rust target and the trunk tool, then run trunk serve --release inside apps/solidcraft-web. Saving and opening files in the browser needs HTTPS or localhost.
The first build compiles a lot of code, so expect it to take a while; the contributing guide estimates about ten minutes on a fast machine.
How do I report a problem or suggest a feature?
- Search the issues first. The README says open work and known bugs are tracked in GitHub Issues.
- Update to the latest release. The security policy says only the latest release gets fixes, and bugs are often already fixed.
- Use the in-app draft. According to the README, feature errors and Help can open an editable Create Issue draft with relevant context filled in.
- Ask in chat. The README and contributing guide link to the project's Discord for questions and ideas.
Security problems have their own process described in SECURITY.md in the repository.
Can I contribute?
Yes, help is welcome, from one-line fixes to owning a whole area. The contributing guide sets a few firm rules worth reading before you start:
- Clean-room. Code from GPL, LGPL or AGPL projects, including OpenCASCADE and FreeCAD, must not be copied or even read for reference.
- Every feature is a command with a test. New features need engine tests that measure the result.
- Never crash. An unsupported case returns an error, not a panic.
- Assets need attribution. Every icon or file must be original or openly licensed.
If you only want to learn the app, skip the code and follow the SolidCraft tutorial. To see how it compares with another open-source CAD, read SolidCraft vs FreeCAD.