CutWeaver¶
2D guillotine cutting as a hosted JSON API, with request-based dedicated deployments for teams that need private infrastructure.
CutWeaver focuses on one thing: taking a canonical request with pieces, sheets, and cutting constraints, and returning a guillotine layout that is ready to integrate into quoting, production, and planning flows.
Current availability
CutWeaver is in private beta. 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 request-based while onboarding is finalized.
What you can build with it¶
- Cutting and nesting inside SaaS products for sheet materials.
- Quoting or production planning tools for glass, wood, metal, or plastics.
- Internal optimization services behind ERP, MES, CAD, or e-commerce workflows.
- Packaging and atlas-style layout tools that need deterministic JSON contracts.
Access modes¶
| Hosted API | Dedicated deployment | |
|---|---|---|
| Where it runs | https://api.cutweaver.io |
Your private environment |
| Public auth contract | Anonymous playground or X-API-Key |
Provisioned during onboarding |
| Best for now | Evaluation, prototypes, low-volume integrations | Request-based private beta onboarding |
| Public docs on this site | Full | Same request and response contract |
The public site does not distribute the optimizer as browser WebAssembly. Evaluation traffic runs through the hosted API, and private binaries are handled through dedicated deployment licensing.
Start here¶
- Quick start for the first working request.
- JSON contract for the canonical
v1schema. - POST /api/v1/solve for the endpoint reference.
- POST /api/v1/request-key for evaluation-key issuance.
- Choosing a strategy for
greedyversusalns.
Why teams adopt it¶
- Quality that pays back.
greedyis fast enough for previews;alnssearches deeper when material savings matter. - Low integration friction. One canonical JSON contract, strict validation, and machine-readable schema discovery.
- Predictable service surface. The public API is versioned under
/api/v1/...and documented as an additive contract. - Flexible rollout. Start on the hosted API, then move the same contract into a dedicated deployment if needed.