Why Keylight exists
You built an app. Someone wants to pay for it. Now you need license keys, a trial, a device limit, a way to revoke a refund, and a place your customers can find their key at 2am. None of that is your product. All of it is two weeks of work you did not plan for, and most of it is easy to get wrong.
Stripe, Paddle, and the rest are great at taking money. They do not know what a license is. The App Store knows, and charges 30% and a review queue for the privilege. Keylight is the layer in between: your payment tool takes the payment, Keylight hands out the key, and your app checks it, online or not. No backend to build, no server to babysit.
Who's behind it
Keylight is built by Nicolas Demanez, a solo builder who runs a business by day and ships software in the evenings. He wired license keys, refund edge cases, and payment webhooks by hand across his own apps enough times to decide the problem deserved its own product. One person, no investors, a product that has to earn its place every month.
What we believe
Licensing is set up before you ship, not after. The moment you have a paying customer you need it, and the moment you need it you have no time to build it.
You own your customers. Keep your own payment tool, your own billing relationship, and your own list. Keylight plugs in next to them. It never sits between you and your buyer.
Simple beats clever. Any app you sell, whatever you built it with: Swift, Rust, JavaScript, C++, C#, or a plain API. Drop it in, point it at your dashboard, ship. Should take an hour, not a fortnight.
Expired should not mean locked out. A customer who stops paying keeps a working app with the free features. They stay a user, and the upgrade path stays one click away.
Tell us what to build
Keylight is built in the open and shaped by the people using it. If something is missing, broken, or does not fit how you ship, say so: send your feedback. Every note is read and most get an answer the same week.