C/C++ SDK

Integrate the VIESUS enhancement engine directly into C/C++ applications via the IsEnhance.h native API. When to use the SDK, platform support, and how to get access.

The VIESUS CLI, PDF Enhancer, and Node.js module are all built on the same C++ enhancement library. The SDK gives you direct access to that library — enhancement becomes a function call inside your application rather than an external subprocess.

The SDK is the highest-effort integration option. Most teams should start with the CLI, the Node.js Module, or the Cloud API. Use the SDK only when those don't meet your needs.

---

When to use the SDK

Use case	Why the SDK
Tight latency budget	No subprocess startup cost per image. The library stays loaded in your process.
High-frequency calls	Worth avoiding the CLI's per-call overhead when you process tens of thousands of small operations.
Existing C/C++ stack	Native linking is cleaner than shelling out to the CLI from C/C++.
Custom pipeline integration	Embed enhancement inside an existing image-processing pipeline rather than around it.
Non-C language with FFI	Any language with a C foreign-function interface (Python, Go, Rust, Java JNI, .NET P/Invoke) can call the SDK directly.

When not to use the SDK

• One-shot batch processing — use the CLI. Simpler, no compilation.
• Hot folder ingest — use the Folder Enhancer or PDF Enhancer. Already built for this.
• Node.js / TypeScript stack — use the Node.js module. Native bindings already provided.
• Cloud or low-effort deploy — use the Cloud API. No infrastructure to manage.

---

Platform support

Platform	SDK availability
Windows (x64)	Supported
Linux (x64)	Supported
Linux (ARM64)	Supported
macOS	Library available — contact support
iOS	Library available since V8.50 — contact support
Android	Not currently supported

GPU acceleration (for AI features) requires CUDA 12.6 and an NVIDIA GPU with Ampere architecture or newer.

---

Architectural benefits

The SDK is the same C++ engine that powers every other VIESUS interface:

• Same enhancement algorithms
• Same viesusini.json configuration format
• Identical output for the same input and configuration
• Same licensing model (GUID or Software Key)

This means you can prototype with the CLI, then migrate to the SDK without changing your configuration or expecting different results.

---

API surface

The primary header is IsEnhance.h. The API exposes:

• Engine initialisation and configuration loading
• Per-image enhancement calls (synchronous)
• Per-image enhancement with progress callbacks (asynchronous)
• GPU model loading/unloading hooks (relevant for VIESUS_UNLOAD workflows)
• License management entrypoints

Detailed function signatures, threading model, memory ownership, and example code ship with the SDK package.

---

How to get the SDK

The SDK is not a self-service download. Access is granted as part of an SDK-tier license agreement with Viesus AG, which includes:

• Headers, libraries, and sample code
• The bundled AI model files (large; not in the public installer)
• A dedicated technical contact during integration
• Build configurations for your target platforms

To request SDK access, email [e-mail] with:

• Your company and intended product
• Target platforms (OS, architecture, GPU presence)
• Expected production volume
• Whether you need GPU AI features (AI upscaling, Facial Reconstruction, Artifacts Removal)