Licence Self-hosted
Run the renderer inside your own network
For companies whose CAD data may not be uploaded to a cloud service. You get the same renderer and the same HTTP API as the hosted product, on servers you control.
01 What you get
Small enough to audit, simple enough to operate
ASingle binary
The renderer and the HTTP server are one executable. No container orchestration, no runtime to install, no job queue to keep alive.
BNo GPU
Rendering is CPU-only. It runs on an ordinary server or virtual machine, and a typical part still renders in tens of milliseconds.
CFiles never leave your network
Requests go from your application to your server. Nothing is sent to us: no models and no thumbnails.
DSame API
The endpoints, parameters and error codes are the ones in the public docs. Code written against the hosted API works against your own instance.
ESTEP included
STEP support uses the OpenCascade CAD kernel, which is licensed under the LGPL. It is linked dynamically, as a separate shared library that you can inspect or replace.
FNo per-render charge
The licence covers unlimited renders on your servers. You decide how much hardware to give it.
02 When it fits
Hosted or self-hosted?
Most teams should start with the hosted API: it is EU-hosted, input files are deleted right after rendering, and there is nothing to operate. Self-hosting is for the cases where that is still not enough.
- Policy
- Customer or export-control rules forbid sending CAD to any third party.
- Network
- The files live in a network segment without outbound internet access.
- Volume
- You render so much that a flat licence is simpler than metered units.
- Latency
- You want the renderer next to your storage, on the same network.
03 Contact
Ask about a self-hosted licence
Tell us roughly what you need and we will reply by email. Licence terms and pricing depend on your setup, so there is no price list yet.