Modular boundary representation for mechanical CAD. Solid modelling, booleans, blends, STEP interchange — 1.1 million lines of Rust, and nothing else underneath.
Every CAD, CAM, CAE and BIM product needs a geometry kernel. Until now the choice was a closed C++ kernel you licence from a competitor, or an open C++ kernel you inherit the maintenance of.
| Kernel | Language | Source | Memory safety | WASM / embedded | Price |
|---|---|---|---|---|---|
| Parasolid | C++ | Closed | Manual | No | On application |
| ACIS | C++ | Closed | Manual | No | On application |
| OpenCASCADE | C++ | LGPL | Manual | Emscripten only | Free |
| OxiCAD | Rust | Licensed source | Compiler-enforced | Native target | Published below |
Two of those vendors also sell CAD applications. If you build a product on their kernel, your roadmap is visible to a competitor and your unit economics are theirs to set. We sell one thing and we do not compete with you downstream.
A modular workspace, not a monolith. Take the topology layer alone, or the whole modelling stack.
You should be able to find out whether this fits your budget without talking to anyone. Annual terms, per company, invoiced once.
Complete kernel, unrestricted technically, non-commercial use only. No sales contact unless you ask for it.
Binary redistribution inside your product, unlimited end users, source access for debugging, security patches, 5 business day response.
Full source licence with the right to modify and fork, all product lines, escrow on request, named engineering contact.
No royalty on your revenue, no per-seat runtime fee, no audit clause. Perpetual licences and acquisition of exclusive rights within a vertical are available — those two do require a conversation.
Nine years removing C. The kernel is what got built on top.
A geometry kernel is not a weekend project, and it is not the first thing you write. It sits on linear algebra, on transforms, on tessellation, on spatial indexing, on numerical robustness — and in every existing kernel, all of that is C or C++ or Fortran underneath.
So we started at the bottom and worked up. BLAS and LAPACK first. Then FFT. Then the scientific core. Then the geometry and point cloud layers. OxiCAD is the floor we reached after the foundations were already Rust all the way down.
That order matters, and it cannot be shortcut. A kernel written in Rust on top of a C numerics library still has C in the audit. Ours does not, because the layer beneath it was rewritten first, and the layer beneath that one before it.
The full stack is public on GitHub — 60+ projects, most of it Apache-2.0. The kernel is the part we licence.
Send one line saying what you are building. You will get the evaluation source and the technical dossier — architecture, test coverage, benchmark methodology, licence text — within one business day. No qualification call, no discovery deck.