Hi HN, I’ve been building a licensing system called RegentLock and wanted to share it with the community to get feedback, criticism, and ideas for improvement.

What it is

RegentLock is a licensing and activation platform for independent software vendors and companies that ship desktop or enterprise software (not only SaaS). It handles license generation, activation, revocation, offline licensing, rehostability, and usage analytics.

Why I built it

Most existing solutions are either: • overly heavy, requiring SDK lock-ins or complex integrations • SaaS-only, ignoring desktop/offline use cases • missing cryptographic rigor, or • expensive for small teams

A lot of devs still need simple, secure, offline-friendly license handling. I originally built this for my own commercial engineering software, then expanded it into a standalone product.

Key features • Crypto: RSA-2048/4096, Ed25519 signing, ChaCha20-Poly1305 for encrypted license files • License models: node-locked, single-user, floating, feature-based, trial, subscription • Offline support: activations and validations for air-gapped environments • Rehostable licenses: customers can move licenses between machines in a controlled way • APIs + SDKs: REST API + integration examples in C, C#, Go, Python, Java • Dashboard: activation logs, usage metrics, expiration tracking • Lightweight: you don’t have to refactor your whole app to integrate it

Target users • Desktop app developers • Engineering/scientific software vendors • Companies delivering software into corporate or locked-down IT environments • Anyone who needs license validation without shipping raw “unlock codes”

Technical docs + demo

Website: https://regentlock.net Feature overview: https://regentlock.net/features.html Docs + API reference are on the site as well.