PermitCore
Create, manage, implement, and sell software licenses
Hey everyone,
A quick PermitCore update, and probably the part of the product I should have explained much more clearly from the beginning.
PermitCore is not only for creating and managing software licenses. The goal is to cover the entire create → implement → sell workflow.
You can create license keys, manage devices, activations, entitlements, expiration, revocation, subscriptions, offline use, floating seats, and the rest of the licensing lifecycle. You can then implement validation through the REST API or one of our eight official SDKs: .NET, Node.js, Python, Java, C++, PHP, Go, and Unity.
But the part that really changes the workflow is the built-in PermitCore Store.
A buyer can visit your storefront, see your software, pay through your connected Stripe account, and receive the license automatically after checkout. PermitCore takes 0% commission on those software sales.
Most licensing systems stop at “send us a webhook after somebody pays.” That still leaves the developer to assemble and host the storefront, checkout, payment automation, webhook flow, and license delivery. We wanted those parts to work together from the start.
So the main PermitCore idea is now simple:
Create the licenses. Implement and manage them. Sell them directly.
We are still an early-stage startup and I would really value feedback, especially from developers who have had to combine a licensing backend with a separate checkout and fulfillment setup.
Website: https://permitcore.dev
Documentation: https://permitcore.dev/docs/getting-started
YouTube: https://www.youtube.com/@PermitCore
🙂 🚀
Hey everyone,
I’m building PermitCore, a software licensing platform for indie developers and software teams.
The idea came from a problem we kept running into while building software ourselves. Adding license keys was one thing, but maintaining the infrastructure behind activations, device limits, renewals, offline use, customer access, and security quickly started feeling like a separate product.
That pushed us to build PermitCore: licensing infrastructure made by developers for developers.
It includes license key management, device activation limits, expiration and revocation, offline and floating licenses, entitlements, customer and reseller portals, payments, webhooks, a REST API, and SDKs for .NET, Node.js, Python, Java, C++, and PHP.
We offer a three-month free trial so you can test everything without any commitment. There is also a free plan that stays free forever because we want indie developers to have access to proper licensing infrastructure from the beginning.
Website: https://permitcore.dev
Documentation: https://permitcore.dev/docs/getting-started
YouTube: https://www.youtube.com/@PermitCore
X: https://x.com/permitcore
PermitCore is still a young startup, and we’re currently working on producing more tutorials and other useful content. We hope you won’t mind that our social channels are still a little quiet. If you need anything or have questions, you can reach us through the Contact Us page on our website.
I’d also love to hear how you currently handle licensing and which parts cause you the most trouble. 🙂 👋
-
1
The “second product” problem is concrete, but switching licensing infrastructure can be painful too. Have early developers actually replaced an existing licensing setup with PermitCore, or are most users still evaluating it alongside what they've already built?
-
1
Hi Aryan
Currently we are having users that are evaluating look and feel, we are in very very early stages so we did not have any transition requests. But that is great point to me personally to try to advance the product to make it easier but first i want to hear about problems and try to tackle it. Thank you for helpfull post :).
Feel free to come and test the product, every feedback is gold...good or bad
-
1
That early-stage signal is useful. I’d be interested in following how the transition problem develops. If you’re open to it, what’s the best email to reach you on?
-
-
Comment