HakanSeven12/OpenCADStudio

The problem

Anyone who receives a .dwg file and doesn't own AutoCAD is stuck: the format is proprietary, viewers are limited, and conversion services add a step and a privacy risk to every round trip. Open CAD Studio reads and writes DWG and DXF directly, in the editor, with versioned save targets from R14 through 2018, and does the same work in a browser or on the desktop from one codebase.

What's different

Most free CAD options split into two camps: viewers that open files but can't edit them meaningfully, and full editors that have grown around decades of legacy code. This project takes a different route — a Rust core, wgpu-based GPU viewports, and native DWG handling rather than a DXF-only subset with conversion on the side. The two things that actually stand out are the write path (not just read) and the automation surface: a headless --export/--serve mode plus an MCP endpoint that lets AI clients drive the live editor. That makes it more scriptable than a typical desktop CAD tool, though the README claims a lot without publishing precision or performance benchmarks — treat the feature list as a statement of intent, not verified parity.

Who it's for

Developers and small engineering teams who need to open, tweak and re-export DWG/DXF files programmatically or in a lightweight editor, and are comfortable with an early-stage application. It suits Linux users especially, since the release matrix covers AppImage, Flatpak and snap in addition to Windows and Apple Silicon macOS. It is not for production drafting shops that depend on battle-tested dimensioning, ACIS solids and standards compliance — the project itself warns users to back up production drawings. Users on Intel Macs, Windows-on-ARM or 32-bit anything are out of luck with the published packages.

Cost of adoption

Desktop builds are downloadable, so trying it costs little; building from source needs a current stable Rust toolchain plus graphics and font dev libraries. The web build requires the wasm32-unknown-unknown target and trunk. Expect rough edges: ad-hoc-signed, non-notarized macOS builds, a snap that only installs with --dangerous, Flatpak file access that needs manual override for external references, and no browser plugins. The license is GPL-3.0, which matters if you plan to embed or redistribute it in a commercial product. Documentation is present (automation, plugins, tessellation) but the README gives no maturity guarantees beyond "active development".

Verdict

At roughly seven months old and 3,500 stars, this is a young project that arrived with a serious engineering surface rather than a weekend demo — the breadth of formats, platforms and automation in the README is unusual for that age. It picked up about 1,250 stars in a single month and reached #15 on the monthly Rust board, so interest is rising fast, but it has never hit the daily trending board and shows no Hacker News discussion; that pattern fits a project being shared within a niche community rather than one with broad validation. The MCP and headless automation angles are genuinely differentiating and worth a look for tooling builders. For anyone doing billable drafting, wait for more field evidence on file fidelity before trusting it as a primary tool.