Connectivity software, backed by a dependable API.

One integration, three essentials

Device software shouldn't carry its own licensing server, its own telemetry pipeline, and its own configuration store. GemTek USB Services runs all three behind one authenticated API surface, so a deployment integrates once and gets everything it needs to operate in the field for years.

• Service Database AccessDevice applications synchronize configuration and state with the service database over authenticated, TLS-encrypted REST endpoints. Versioned schemas keep two-year-old clients fully functional; idempotent writes make retries after power loss harmless.
• Usage MetricsBatched usage events from deployed applications are validated and aggregated into per-deployment statistics for operational analytics — a few kilobytes per installation per day.
• License ValidationSigned entitlement responses keep deployed software compliant, with support for seat limits, expirations, and offline grace periods. Every validation lands in an exportable audit log.

Engineered for unglamorous networks

Device software lives in the places connectivity forgot: factory floors, retail back offices, remote sites on metered links. The platform is designed for exactly that reality.

• Outbound onlyAll traffic is HTTPS on TCP 443 to a documented, fixed set of hostnames. No inbound listeners, no exceptions to negotiate with the network team; a static IP option exists for allowlist-only firewalls.
• Offline is a normal stateCached configuration keeps devices configured, license grace windows keep them compliant, and metrics queue on disk until a path to the API exists again.
• Small by designCompressed batches and delta-based configuration sync keep the per-device footprint to a few kilobytes a day.
• AuditableLicense validations, configuration changes, and ingestion events form a trail your compliance team can export from the dashboard at any time.

Common questions

Which client platforms are supported?

Windows 10/11 and Server 2019+, glibc and musl Linux — via the client library or directly against the documented HTTPS/JSON API.

Does the platform see device payloads or user data?

No. It carries configuration records, usage counters, and license state for the software itself — keyed by deployment, never by individual. See the Privacy Policy.

What happens when a device is offline for weeks?

It keeps working on cached configuration and its license grace window, then reconciles automatically when it reconnects.

Who owns the metrics?

The deploying organization. We process them solely to provide the contracted service.