Windows
In the "Windows protected your PC" dialog: <strong>More info</strong> → <strong>Run anyway</strong>.
DOWNLOAD
A desktop application for macOS, Windows and Linux. Drawing, cut list, G-code and quotes all run on your own computer, with or without an internet connection.
The pilot is not a public download: we send the installer <strong>directly</strong> to the workshops that will use it. That way we know who is on which version and can tell you when a fix lands. If you would like to try it, <a href="/en/iletisim.html">write to us</a>.
01 / SYSTEMS
| System | Installer | State |
|---|---|---|
| Windows 10 / 11 | .exe · .msi | Works. A "Windows protected your PC" warning appears during install; it is stepped past as described below. |
| macOS (Apple Silicon) | .dmg | Works. An Intel Mac needs a separate build; say so if you need one. |
| Linux (x86_64) | .deb · .rpm · .AppImage | The packages are produced, <strong>but have not yet been run on a Linux desktop.</strong> The first Linux user will also be the first test — give and take it knowing that. |
02 / INSTALL WARNING
The pilot build is unsigned. A code-signing certificate needs a registered company, and the pilot deliberately is not waiting for one. The only consequence is a warning on first install; it has nothing to do with the program.
In the "Windows protected your PC" dialog: <strong>More info</strong> → <strong>Run anyway</strong>.
If you got the file by hand or on a USB stick, no warning appears at all. If you downloaded it, press <strong>Open Anyway</strong> once at the bottom of <strong>System Settings ▸ Privacy & Security</strong>.
There is no such gate; no warning appears.
Being unsigned only concerns the first install. Every update after that is verified against <strong>our own signature</strong>.
03 / UPDATES
When a new version is published, the app asks you the next time you open it; accept and it downloads and installs. To check by hand: <strong>Settings ▸ About ▸ Check for updates</strong>. Every downloaded package is signature-verified before it installs, and the verifying key is embedded in the program — so a package altered in transit cannot install.
If you are on <strong>0.1.0 or 0.1.1</strong>, update. 0.1.0 has no autosave — unsaved work is lost if the program closes unexpectedly. 0.1.1 has no in-app updater, so it cannot pick up later fixes on its own. Move to <strong>0.3.0</strong> from either.
NEXT