2D guillotine cutting, as a REST API

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 for instant feedback, multi-threaded ALNS for better layouts under real production constraints. Hosted API or self-hosted Docker.

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"
  }'

Try the hosted API safely

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

Anonymous smoke test

Run the quickstart request up to 5 times per day per IP to verify payload shape and response parsing.

Free key

Evaluation window

Request a reusable evaluation key by email for 25 solves/day and 250/month during integration.

Production

Hosted or self-hosted

Move live workflows to a paid hosted tier or a licensed private runtime with the same request contract.

Pricing

Free is intentionally small: enough to validate the contract, not enough to quietly run a real workshop on our infra. If customer quotes, shop-floor jobs, or daily internal workflows depend on the API, start with a paid tier.

Evaluation and hobby use

Hosted API — Playground

$0/month

  • 5 solves/day per IP without signup
  • 25 solves/day and 250/month with an instant evaluation key by email
  • Small jobs, shared queue, and evaluation-focused limits
  • Best for demos, smoke tests, and early integration checks

If this tier fully covers your workload, you are still in evaluation territory.

Read quickstart

Get an evaluation key now

Same email returns the same free key. No separate signup flow.

On-prem and redistribution

Self-hosted Docker

from $199/month

  • Solo — $199: 1 deployment, async support in 48 h
  • Team — $499: up to 5 deployments, Slack/email support
  • Project — $1.5K–5K: one-time license for one named product
  • Ed25519-signed license, offline validation, resell-in-project rights

Use this when data must stay on your side or the API volume never stops.

Request access

Need 100K+ solves/month, on-prem with invoicing, or a custom SLA? Contact us.

Why CutWeaver

Better yield, less waste

Built to improve utilization, reduce scrap, and turn expensive sheet material into more shipped parts per job.

Faster production decisions

Use fast Greedy for instant quoting and UI feedback, then switch to ALNS when the job deserves deeper optimization.

Modern optimization stack

Beam search, adaptive large neighborhood search, and exact solving for small tail cases give you a practical mix of speed and quality.

Flexible integration path

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.

FAQ

What problem does this solve?

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.

Is the source available?

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.

How is this different from OR-Tools / rectpack2D / OptiCut?

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.

Why is the free tier intentionally small?

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. Paid tiers start where recurring customer traffic begins.

Can I pay from RU/EU/US?

Today paid access starts through the request flow on this pricing page 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.

What are you NOT building?

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.