Skip to content

Self-hosted access

Some teams need the CutWeaver contract inside a private network or on dedicated infrastructure.

This page covers the public-facing part of that offer: what stays the same and what is provisioned directly.

What stays the same

  • The JSON request and response contract remains the same as the hosted API.
  • The health and metadata endpoints stay the same.
  • The public v1 docs on this site remain the integration reference.

What is provisioned directly

  • Image reference and rollout instructions.
  • Deployment-specific access policy.
  • Capacity planning and operational guidance.

Browser and WASM builds

CutWeaver does not publish a public browser WASM demo. A WebAssembly build would ship the optimizer binary to the client, so browser-side distribution is treated as a private/licensed runtime decision, not as a free evaluation path.

Use the hosted API for evaluation and the self-hosted Docker path when the runtime must stay inside your infrastructure.

Typical use cases

  • Private ERP or MES environments.
  • Regulated or network-isolated installations.
  • Higher-volume workloads that need dedicated capacity.
  • Product teams that want the same contract on their own infrastructure.

Basic health check

curl http://localhost:8080/health
{
  "ok": true,
  "status": "healthy",
  "service": "cutnewweaver-http",
  "contractVersion": "v1"
}

How to start

Use Pricing to request a dedicated deployment discussion. The public docs stay valid for the request and response contract; the deployment path itself is provisioned during onboarding.