LCC SDK

Official Go SDK for integrating applications with LCC (License Control Center).

Features

• 🔐 Zero-configuration authentication - Self-signed RSA key pairs, no pre-registration needed
• 📝 Declarative license control - YAML-based feature protection
• 🔧 Code generation - Automatic function wrapping with minimal code intrusion
• 📊 Automatic usage reporting - Built-in quota management and usage tracking
• 🎯 Graceful degradation - Automatic fallback to basic features
• 🚀 Production-ready - Caching, retry logic, and offline support

Quick Start

Installation

go get github.com/yourorg/lcc-sdk

Basic Usage

1. Create feature manifest:

# lcc-features.yaml
sdk:
  lcc_url: "http://localhost:7086"
  product_id: "my-app"
  product_version: "1.0.0"

features:
  - id: advanced_analytics
    name: "Advanced Analytics"
    description: "ML-powered analytics features"
    intercept:
      package: "myapp/analytics"
      function: "AdvancedAnalytics"
    fallback:
      package: "myapp/analytics"
      function: "BasicAnalytics"
    # Note: Authorization is controlled by License file, not YAML
    # Do NOT specify tier or quota here

2. Add to build process:

# Makefile
.PHONY: generate
generate:
	go generate ./...

.PHONY: build
build: generate
	go build -o myapp ./cmd/myapp

3. Initialize SDK in your app:

package main

import (
    _ "github.com/yourorg/lcc-sdk/auto"
)

func main() {
    // Your code - SDK works transparently
    result := analytics.AdvancedAnalytics(data)
}

Documentation

Quick Start

• Getting Started Guide
• Configuration Reference

Feature & Capability Documentation

• LCC Features Overview - Complete feature set and capabilities
• Feature Comparison Guide - Compare LCC features across different scenarios
• Best Practices Guide - Implementation best practices and patterns

Advanced Topics

• API Documentation
• Code Generation Guide

Examples

See lcc-demo-app for a complete working example.

Architecture

Application Code
       ↓
Feature Manifest (YAML)
       ↓
Code Generator (lcc-codegen)
       ↓
Generated Wrappers
       ↓
LCC Client (runtime)
       ↓
LCC Server (license verification)

Authorization Model

New Model (Recommended)

Separation of Concerns:

• YAML Configuration (lcc-features.yaml)

  • Maps feature IDs to functions (technical mapping)
  • Defines fallback behavior
  • Does NOT control authorization

• License File (.lic)

  • Controls which features are enabled/disabled
  • Defines quotas, rate limits, capacity limits
  • Source of truth for authorization

Example License:

{
  "planInfo": {
    "features": {
      "advanced_analytics": {
        "enabled": true,
        "quota": {"daily": 10000}
      },
      "excel_export": {
        "enabled": false
      }
    }
  }
}

Benefits:

• License has full control over feature enablement
• Can customize per customer without code changes
• Stable feature IDs as business interface
• Flexible function implementation

Old Model (Deprecated)

The old model where YAML defines tier requirements is deprecated but still supported for backward compatibility.

# Old approach (deprecated)
features:
  - id: advanced_analytics
    tier: professional  # Deprecated - don't use this

Development

# Clone repository
git clone https://github.com/yourorg/lcc-sdk
cd lcc-sdk

# Install dependencies
go mod download

# Run tests
make test

# Build CLI tools
make build

Related Projects

• lcc-demo-app - Complete demo application
• LCC Server - Commercial license server

License

MIT License - see LICENSE for details.

Support

• Documentation: https://docs.yourcompany.com/lcc-sdk
• Issues: https://github.com/yourorg/lcc-sdk/issues
• Community: https://community.yourcompany.com