Peermitly – Modern License-Key Management for Software Projects
I’m currently building Peermitly, a modern platform for managing license keys for SaaS products, desktop tools, plugins, apps, and internal systems.
The idea behind it is simple:
Many software projects eventually need license keys, activations, expiration dates, subscriptions, or validation through an external system. Very often, teams build something quickly themselves, and over time it becomes messy, hard to maintain, or difficult to scale.
That is exactly the problem Peermitly is designed to solve.
With Peermitly, license keys can be created, managed, validated, revoked, restored, and tracked in a clean and structured way.
What Peermitly is designed for
Peermitly is planned to support different types of keys, for example:
* classic license keys
* UUID-based keys
* invitation codes
* time-limited keys
* keys with expiration dates
* keys where the validity period starts after the first activation
* revoked and restorable keys
* customer-bound keys
* validation through an external interface
For me, the important part is that Peermitly should not just generate keys. It should manage the full lifecycle of a license key.
A key can be created, activated, checked, blocked, revoked, restored, extended, or assigned to a customer. This makes Peermitly useful not only for small tools, but also for larger projects where license management needs to be clean, reliable, and traceable.
Why Peermitly?
I did not want to build another overloaded enterprise tool.
The goal is to create a license-key system that developers, agencies, and software vendors would actually enjoy using.
The focus is on:
Flexible key types
Not every project needs the same kind of license key. Some projects need UUIDs, others need classic grouped keys with prefixes, custom length, uppercase/lowercase rules, or specific patterns.
Clear management
Keys should be easy to find, edit, revoke, extend, restore, and assign.
Simple integration
External applications should be able to quickly check whether a license key is valid.
Security and traceability
Especially with license systems, it is important to know when a key was created, activated, checked, revoked, blocked, or restored.
Example use cases
Peermitly can be used for:
* SaaS products
* plugins
* desktop software
* internal business tools
* beta access
* lifetime licenses
* trial keys
* reseller models
* API access
* customer portals
One feature I personally find very useful is delayed validity.
Example:
A customer buys a key with 12 months of validity. The 12 months do not start immediately after purchase, but only once the key is activated for the first time.
That can be very useful for many software licensing scenarios.
Planned features
Some features currently on the roadmap are:
* domain or device binding
* access keys for external systems
* webhooks
* customer management
* reseller system
* audit logs
* statistics
Feedback wanted
I would love to hear your thoughts:
What would a license-key management system absolutely need for you?
Would you prefer classic license keys or UUID-based keys?
Which features would matter most to you: device binding, domain binding, expiration dates, activation limits, external validation, webhooks?
Any feedback, ideas, or criticism is welcome.
The goal with Peermitly is to build a clean and serious license-key management solution for developers, agencies, and software vendors — not just another half-finished licensing tool.
u can check it out on
or add me on discord: hireshire
