Developer preview · hosted evaluation available
Drop-in cutting/packing optimization for sheet materials, texture atlases, PCB panelization, CNC nesting. Improve cutting quality, reduce material waste, and get from curl to production faster than building your own optimizer. Greedy is available for evaluation today; deeper hosted and self-hosted access is being onboarded manually during private beta.
curl -X POST https://api.cutweaver.io/api/v1/solve \
-H "Content-Type: application/json" \
-d '{
"sheets": [{"width": 3210, "height": 2250}],
"pieces": [
{"width": 800, "height": 600, "quantity": 4},
{"width": 1200, "height": 900, "quantity": 2}
],
"params": {"kerf": 4},
"strategy": "greedy"
}'
Public evaluation goes through api.cutweaver.io, not a downloadable browser engine.
That keeps the optimizer server-side while still giving you a real JSON contract to integrate against.
No key
Run the quickstart request within a small beta quota to verify payload shape and response parsing.
Free key
Request a reusable evaluation key by email for a larger private-beta integration window.
Private beta
Move live workflows only after manual onboarding for a paid hosted tier or licensed private runtime.
Commercial terms are intentionally hidden until production launch. Free evaluation is available now; production hosted and self-hosted access starts through a manual beta request.
Evaluation and hobby use
Betalimited
If this tier fully covers your workload, you are still in evaluation territory.
Read quickstartGet an evaluation key now
Same email returns the same free key. No separate signup flow.
Use it as X-API-Key for POST https://api.cutweaver.io/api/v1/solve
and GET https://api.cutweaver.io/api/v1/usage.
Commercial hosted usage
Privateterms
The paid ladder starts where free should stop being comfortable. During beta, access is provisioned manually.
No card is charged from this page. Requests are reviewed manually until billing and legal pages go live.
On-prem and redistribution
Privateterms
Use this when data must stay on your side or the API volume never stops.
Request self-hosted betaNeed high-volume access, on-prem with invoicing, or a custom SLA? Contact us.
Built to improve utilization, reduce scrap, and turn expensive sheet material into more shipped parts per job.
Use fast Greedy for instant quoting and UI feedback, then switch to ALNS when the job deserves deeper optimization.
Beam search, adaptive large neighborhood search, and exact solving for small tail cases give you a practical mix of speed and quality.
JSON API, hosted evaluation, docs examples, or self-hosted Docker. Fit it behind your frontend, ERP, MES, CAD, or quoting flow without UI lock-in.
Not yet. The hosted evaluation API is live for smoke tests and integration checks, but paid hosted plans, self-hosted delivery, legal pages, and billing are still in private beta. Use the request links on this page if you want to discuss a real production rollout.
Given a list of rectangular pieces and sheets (with kerf, margins, rotation, defects), we return a guillotine cutting layout that improves utilization and reduces wasted material. In practice that means faster quoting, fewer manual layout iterations, and better yield on the shop floor.
The core is closed-source. The self-hosted Docker license includes binary distribution rights for end-projects. Public benchmark code and example clients live on GitHub. We do not publish a public browser WASM demo because it would distribute the optimizer engine to every visitor.
OR-Tools needs you to model and tune a CP-SAT problem yourself. rectpack2D is non-guillotine
and lacks production constraints. OptiCut is a desktop app, not an API.
See the engine guide for the current Greedy and ALNS surface.
Because free is for evaluation, demos, and hobby tooling. If evaluation access fully covered a small commercial workflow, we'd be subsidizing production usage and learning nothing about real willingness to pay. Exact limits and commercial terms stay private until production launch.
Today paid access starts through the beta request flow while billing rails are still being finalized. The target path is provider-backed checkout or invoiced access depending on jurisdiction and customer type, with a Merchant of Record or invoice path instead of a Stripe-only assumption.
OEM-machine integrations (Lisec/Hegla/Bottero formats), ERP modules, end-user UI for SMB producers, custom G-code per machine. We sell to developers, they decide the rest.