01 / SET UP
Start with a solid setup.
Bring in a STEP model or begin with stock. Define your work origin, choose your tools, and organize the program into operations.
Native CAM / Built for the shopSETUP → TOOLPATH → NC
From print.
To program.
Powerful CAM. Free to use.
Built for hobbyists and small to mid-sized machine shops. Feature-rich programming in a native workspace designed to be easy to learn and practical to use.
MILLINGDRILLING & TAPPINGPROFILINGENGRAVINGMANUAL INDEXING
Real client. Real interface.
CAST LONG PROTO · O7211 · real program, generated paths and material renderNO BROWSER. NO WEBVIEW.
01 Native Rust application02 GPU-rendered workspace03 Local or server-connected04 CPS postprocessors
01 / Built around the work
Your part.
Your process.
One clear workspace.
Our goal: everyday jobs from print to program in minutes. Straightforward setup, capable machining tools, and a clear view of the result—so you can spend less time programming and more time making parts.
02 / PROGRAM
Build the cut, your way.
Conversational processes and model-based workflows, with machining parameters where you need them. A compact process list keeps the sequence in view.
03 / REVIEW
Know what comes next.
Review toolpaths with playback, inspect the material preview, and look inside with cross-sections. Check the posted G-code before taking it to the machine.
02 / Tooling, not clutter
The right tool.
For the next cut.
End mills, drills, taps, and the rest of your library. Filter by tool type, narrow the diameter range, and find the cutter you need without scrolling past everything you don't.
Tool-type categories and diameter filters. Compact rows for larger libraries. Backend-owned tooling in the native client.
Actual Rustycam client · offline sample tools
03 / At home in your shop
Your machine.
Your way to connect.
One familiar interface, whether you're programming at a single workstation or connecting to a shared CAM server.
MODE / 01Self-contained workspace
Stay local.
Run the backend alongside the client, off the UI thread. Work with local SQLite storage or configure an external PostgreSQL database.
Your workstation. Your workspace.
MODE / 02Shared CAM infrastructure
Connect the shop.
Connect clients to a hosted CAM API. The server manages generation and storage, with program edit ownership for supported backends.
Shared resources. The same desktop.
Generation capabilities depend on the configured backend, installed workers, native libraries, and postprocessors.
Small tools. Real shop work.
The details belong here, too.
A library, not a long search.
Tool-type filters, diameter ranges, and compact rows. Built to make larger libraries easier to navigate.
The print, alongside the part.
Open blueprint PDFs in the client with a configured database or local-folder source.
Shop math, within reach.
Inch/mm conversion, feed-per-minute and feed-per-revolution calculations, plus drill and tap references.
Currently on the workbench
The next cut
starts here.
We're building Rustycam for Windows and Linux.
Available packages will appear here when published.
Before the first pass
A few things
worth knowing.
Who is Rustycam for, and will it be free?
Rustycam is being developed as free-to-use CAM for hobbyists and small to mid-sized machine shops. The aim is to make capable, feature-rich programming approachable—whether you're making parts in a home workshop or running a growing shop.
Can I download Rustycam today?
Check the Windows and Linux buttons above for current availability. Each platform stays marked Coming soon until a public package is ready. Rustycam is still in development.
Is this a browser-based CAM application?
No. Rustycam is a native desktop application built with Rust, egui, and wgpu. This website introduces the project; the CAM workspace runs on your computer.
Do I need a separate CAM server?
No. Standalone mode runs a local backend with Core and the database connector. A separate server is an option for shared workflows. Local generation still needs the appropriate runtime workers and geometry libraries.
What machining workflows are being developed?
Conversational operations include families such as facing, drilling, tapping, boring, slots, notches, chamfers, and engraving. STEP-based workflows and adaptive clearing are also in development. Coverage and validation vary by process; this is not a claim of complete feature parity or production readiness.
Are the images from the actual application?
Yes. The workspace screenshot shows CAST LONG PROTO (O7211), a real program with generated toolpaths and rendered material in the native Linux client. The tool-library screenshot uses offline sample entries. A rendering is a programming preview, not machining approval.