Node.js SaaS Integration

How a SaaS platform enhances user-uploaded images in the background with the VIESUS Node.js module — and which interface and settings fit the workflow.

The scenario: A SaaS platform lets users upload images that are enhanced in the background and made available to download. The service must handle many concurrent uploads without blocking, and keep enhancement off the main request path.

---

Recommended interface

Use the VIESUS Node.js module. It calls the enhancement engine in-process from Node.js via a worker thread pool, so enhancement runs off the main event loop without the overhead of launching an external process per image.

Choose this over the CLI when enhancement is part of a running Node.js service rather than a batch job. If you'd rather not host infrastructure at all, the Cloud API offers the same engine over HTTP.

---

How it works

• The native module loads the VIESUS library inside your Node.js process. A pool of worker threads each holds one reusable enhancement instance, so requests are processed in parallel without blocking the event loop.
• A typical service accepts an upload, hands the image to the pool, stores the enhanced result, and returns a link the user can retrieve — all asynchronously.
• The same viesusini.json you tuned in the Viewer drives the enhancement, so results match your other interfaces.

---

What to consider

Factor	Guidance
Platform	The Node.js module is Linux only, and AI features need an NVIDIA driver with CUDA 12.6+. See System Requirements.
Concurrency	Size the worker pool to your CPU cores (or GPUs). Cap the queue so the service rejects early under overload rather than piling up.
Licensing	The GUID is passed at runtime — keep it in an environment variable or secrets manager, never in source.
Output handling	Clean up enhanced files on a TTL; don't rely on per-request deletion.
Resilience	Set timeouts for very large images and track latency and queue depth.
Deployment	Containerize for production — see Docker Production Deployment.