NativeCAD vs OpenCascade.js vs replicad

A B-rep kernel that installs like any npm package and loads before your page finishes painting. Measured against the two WASM kernels developers reach for first — same machine, same script, one command to rerun.

—smaller download than opencascade.js

—faster cold start than opencascade.js

—runtime dependencies

Every number here is rendered from one run of node tools/bench_vs_competitors.js — run it yourself and you get the same report.

Measured: — Node: — Platform: — Pinned versions: —

Failed to load or parse the embedded benchmark report — see console.

1. Download size — what a user actually pulls

Our built package next to the compiled OCCT .wasm and its JS glue, exactly as npm installs them, gzip at the same level for all three.

Library	Raw	Gzip	vs our kernel (gzip)

2. Cold start — from import to a callable kernel

Fresh Node process every run, back-to-back on the same machine, median of five.

3. Dependencies — what npm install actually brings

npm install @nativecad/kernel is the whole install.

Library	Declared deps	What it actually takes

Ready to try it? npm install @nativecad/kernel Get a free key · Kernel SDK

OpenCascade.js, OCCT and replicad are named to identify the software measured; they are their owners' marks and NativeCAD is not affiliated with or endorsed by those projects (full notices: legal notes). If a maintainer believes a figure is wrong, tell us; the measurement is one command and we re-run it.