The Fingerprint SDK as a Service
Privacy controls for GDPR-aligned deployments
Biometrics integration has traditionally forced teams to manage platform-specific DLLs, JNI bridges, and fragile native dependencies. Every language stack becomes a separate integration project, which slows delivery and increases maintenance risk.
As systems grow, teams often duplicate logic across desktop, web, and backend services. That creates version drift, inconsistent behavior, and long release cycles whenever device SDK components change.
Why SecuGen Connect
Connect Bridge replaces the library-first model with a loopback HTTP/JSON service. Call the API directly or use an optional Connect SDK—without platform-specific or language-specific application code.
For licensed deployments, local entitlement validation supports offline operation while the entitlement and its offline policy remain valid. Activation and periodic refresh or renewal require cloud connectivity when the selected license model requires them.
Before: per-language SDK wrappers, runtime dependency conflicts, and repeated integration/debug cycles.
After: one secure Connect Bridge endpoint and a unified response model across all clients.
Operational gain: simpler rollout, fewer moving parts, and faster issue isolation.
Business gain: predictable delivery cadence with lower integration cost.
Connect Bridge keeps application requests, device capture, and licensing policy in one controlled flow.
Java, Python, C#, Node.js, Go, Rust, PHP, Delphi, and more can call the same HTTP/JSON API directly or through an optional Connect SDK.
Submit supported raw8 fingerprint images and generate ANSI 378, ISO 19794-2, or SG400 templates through the shared biometric engine.
Enroll templates and run local 1:N identification with the integrated SQLite-backed matching engine. No external matching database is required.
Supports Chrome, Edge, and Firefox after loopback origin and session policy setup. Windows is production-ready; macOS is packaged and hardware-verified; Android is a hardware-verified preview; Linux packages and an iOS implementation preview are available with platform-specific rollout requirements. No browser extension, plugin, or applet is required.
Loopback-only binding, origin controls, short-lived session authentication, AES-256-GCM template storage, SHA-256 nonce replay prevention, and TLS 1.2+ for cloud traffic.
The Rust desktop runtime and shared core provide session, nonce, rate-limit, device, and biometric logic. Mobile shells reuse the shared core through JNI or C FFI where applicable.
Centralized license management with Ed25519/EdDSA-signed entitlements for subscription, perpetual, and trial licensing models.
Capture, extraction, and matching execute on the endpoint. Cloud use is limited to licensing and account workflows when the selected policy requires it.
Capture, match, and identify without an internet connection while a valid entitlement and offline policy permit. Activation and periodic refresh or renewal may require cloud access.
For capture, template, verify, and identify workflows, SecuGen Connect can consolidate multiple legacy integration paths (including Linux SDK flows) into one service API.
Move from handle lifecycle and buffer management to clean local HTTP request/response calls.
Remove per-distro `.so` packaging, linker/runtime path issues, and language-specific wrapper maintenance.
Remove JAR + native library packaging and eliminate PATH / JVM-native compatibility issues.
Avoid x86/x64 binary drift and use the same API contract already used by other stacks.
Move device-specific AAR and JNI handling behind Connect Bridge, then use the local API or optional Android SDK from application code.
Upgrade browser-centric flows to a secure service model ready for multi-channel apps.
Connect Bridge runs on the user's endpoint, connecting the application to fingerprint hardware while keeping biometric operations local. It contacts the cloud control plane only for licensing and account workflows when required.
Desktop Bridge runtime plus shared session, nonce, rate-limit, device, and biometric logic. Mobile shells use JNI or C FFI where applicable.
Go services power the License Server, customer and admin portals, Stripe/PayPal billing workflows, the download catalog, and the optional server-matching service.
Embedded, serverless 1:N matching engine. Local template storage with zero external dependencies.
Primary cloud persistence for License Server state, seat governance, audit, and multi-tenant operations.
Tamper-evident EdDSA-signed entitlements validated locally by Connect Bridge, subject to the entitlement's validity and offline policy.
AES-256-GCM protects the local template store at rest with configured or generated key material. Applications remain responsible for downstream template handling.
Mainstream loopback traffic uses HTTP while remaining bound to the endpoint and policy-protected; HTTPS is available where required. Cloud connections use TLS 1.2+.
Typed client for the maintained v1/v2 Bridge surface and authenticated event stream. npm install secugen
SecuGen Connect keeps the simplicity of web-style integration, then extends it to a secure, enterprise-ready runtime for web, desktop, and mobile teams with one consistent API contract.
| Feature | SecuGen Connect | SecuGen Web API | Legacy SDK / Plugin Stack |
|---|---|---|---|
| Architecture | Loopback REST + authenticated WebSocket events | Web-first local bridge | DLL/JNI/ActiveX split stack |
| Developer Onboarding | Direct HTTP/JSON or optional Connect SDK | Browser/JS-oriented integration | Per-language binaries and runtime setup |
| Language Coverage | Any language that can call HTTP | Best fit for web JavaScript flows | SDK-specific (Java/.NET/C++ each separate) |
| Desktop/Mobile Reuse | Same endpoint contract across channels | Additional wrappers typically required | Rebuild per platform |
| 1:N Identification | Built-in encrypted SQLite engine | External matching logic needed | External matching logic needed |
| Template Interoperability | Supported raw8 image → ANSI 378 / ISO 19794-2 / SG400 | Primarily capture-focused web workflows | Often device/SDK-bound flows |
| Licensing Server | Built-in cloud licensing server (JWT) | External/app-side licensing flow typically required | Dongle/local key distribution model |
| Cross-Platform Parity | Shared Rust logic with platform-specific runtime and rollout status | Windows-focused with limited portability | Per-platform SDK rebuild required |
| Deployment Operations | Central policy + token-based control | Application-managed rollout | Manual DLL/plugin distribution |
Why this matters: teams standardize on one API, ship features faster, and reduce support tickets tied to native library or browser dependency issues.
Use these deployment baselines for planning, then confirm the current package, platform, device, and entitlement requirements for your rollout.
Note: platform status reflects repository evidence reviewed on 2026-08-18. Confirm the current Download Center, device compatibility matrix, and target artifact before rollout.
Install Connect Bridge, validate the local integration flow, or continue with the developer guide.