The LicenseSpring Go SDK lets you implement license activation, entitlement enforcement, and usage tracking directly inside your Go application or service with no external licensing infrastructure to build or maintain.
Built for modern backend systems, the SDK provides native Go methods for interacting with LicenseSpring's licensing APIs, covering backend services, cloud-native platforms, microservices, and DevOps tooling from a single integration.
Go SDK V2 is the current supported version and represents a complete rewrite of the SDK. All new integrations should use V2. V1 is deprecated and maintained only for backward compatibility.
ISO 27001 Certified
ISO 9001 Certified
Trusted by Software Vendors WorldwideThe Go SDK integrates natively into your Go application and connects directly to LicenseSpring's licensing APIs. Once installed, you have full access to LicenseSpring's licensing infrastructure.
With the SDK, you can:
Activate and validate licenses at runtime: online, offline, or in air-gapped environments
Enforce node-locked, floating, subscription, and consumption-based licensing: using the model that fits your product
Gate features by entitlement: control access to functionality at the SDK level, across any Go application type
Run local license checks with configurable grace periods: define how long the SDK honors a cached license before requiring revalidation, so connectivity loss never interrupts active users
Bind licenses to hardware: generate persistent hardware IDs using multiple device fingerprinting algorithms suited to the deployment environment
Track usage and activations: feed license telemetry back to the LicenseSpring platform in real time
The Go SDK is designed for developers building and distributing commercial software on modern backend infrastructure.
| Use Case | Description |
|---|---|
Backend APIs | Implement licensing validation inside Go-based APIs |
SaaS Infrastructure | Manage licensing for server-side software platforms |
Microservices | Enforce licensing across distributed Go services |
DevOps Tools | Protect proprietary command-line or developer utilities |
Cloud Platforms | Integrate licensing workflows into cloud-native systems |
LicenseSpring’s Go SDK V2 is the current supported version and represents a full rewrite of the SDK.
Key notes:
Go SDK V2 will receive all new updates and ongoing support
Go SDK V1 is deprecated and maintained only for backward compatibility
New integrations should always use SDK V2
The SDK includes usage examples demonstrating how to implement licensing workflows using the two available clients:
License Client: Validate licenses and retrieve license data
Management Client: Perform administrative licensing operations
The Go SDK requires two credentials to authenticate requests to the LicenseSpring API: an API Key and a Shared Key. You are responsible for managing these credentials securely within your application.
Common approaches include environment variables, configuration files, and secret management systems. Regardless of the method, ensure credentials are protected from unauthorized access, particularly in shared repositories or public codebases.
The Go SDK includes hardware fingerprinting support for node-locked licensing and device-bound activation. Multiple algorithms are available for computing a unique, persistent hardware identifier, selecting the approach appropriate for the deployment environment, whether a physical server, a virtual machine, or a cloud-hosted instance.
Generated hardware IDs are used for:
Node-locked license binding
Device identification and activation tracking
Consistent hardware fingerprinting across multi-SDK product deployments
Products that pair a Go service with other parts of their stack, whether that be a C++ core engine, a Java backend, a Python data layer, or a Node.js interface, can use multiple LicenseSpring SDKs simultaneously.
All LicenseSpring SDKs share a common license file format and compute hardware identifiers using the same underlying logic. A license issued to a device is recognized consistently across every component of your product, regardless of which SDK each part uses.
The Go SDK fully supports deployments with limited or no internet connectivity with two distinct activation paths:
Offline activation: uses a file-exchange flow for environments with occasional or restricted connectivity
Air-gapped activation: uses a code-exchange flow for environments where no external data transfer is permitted
Our developer support team can help you implement licensing quickly and correctly.