Free, open source parametric CAD for 3D printing. Sketch a shape, give it exact sizes, turn it into a solid and export a file for your slicer. Windows, macOS and Linux.
Get the build for your system from the beta release. There is no account and no cloud, and your files stay on your disk. The builds are not code signed, so Windows and macOS will warn you on the first start. The install page shows how to get past that.
- Sketch with lines, arcs, splines and text, and pin the shape down with constraints and dimensions.
- Turn sketches into solids with extrude, revolve, loft and sweep, then change them with fillets, chamfers, holes and shells.
- Keep every step in the History, go back to any of them, and let the part rebuild.
- Drive a design from named parameters, so a bracket 2 mm wider is one number away.
- Check a part before printing: measure it, cut it open, look for overhangs and thin walls.
- Render it with materials, glass and glowing parts in the Render workspace.
- Add optional plugins, such as a screws library, texture tools and a printer connection.
- Let an AI assistant build and check parts through the built-in MCP connection. (can be turned off if you do not use any AI assistance or have no need for a separately running process)
- Export STL, 3MF, STEP and GLB, and import STEP and meshes.
The manual is at paraxdev.github.io/FundaCAD. It starts with a first part from sketch to exported file.
Building from source, running the tests and fixing common build problems are in
CONTRIBUTING.md. The first build compiles the Open CASCADE geometry kernel
and takes about twenty minutes. The technical notes are in docs/.
docs/ARCHITECTURE.md, how the processes fit togetherdocs/ENGINE.md, the Funda Engine, its tests and the beta releasedocs/PROTOCOL.md, the messages the frontend and the engine exchangedocs/FUNDA-FORMAT.md, the.fundaand.fundabfile formatsdocs/PACKAGING.md, how a desktop bundle and the kernel are builtdocs/MCP.md, how an AI assistant connects and what it can dodocs/PLUGINS.md, writing plugins and what they may reach
Most of the code and tests here are written by AI. I decide what gets built, steer it, and use the app actively.
Im trying to apply real software engineering strategies and learnings to make sure the codebase and the features aren't a useless mess, and actively listening to any feedback that I get.
You may use AI for creating features and creating pull requests, for those you are responsible for the AI output and ensure that it serves a usable quality. you must write at least one test that, if the feature allows it, ensures it has one "known good" case
for creating issues and bug requests please read the AI output and ensure you can reproduce it, cheap incoherent bug reports may take a while to be understood and fixed.
due to the nature of AI im very open to any issues and bug requests that may arrive, and take the highest priority of having em fixed. the goal is a coherent program that actually can show itself in daily use cases and be as flexible as an open source project can get.
AGPL-3.0, see LICENSE. FundaCAD started as a fork of SindriCAD and has moved a long way since, mainly in the interface and a Rust backend.