No hassle web app licensing

You are an honest, very skilled web developer, delivering awesome web apps to your clients all over the world. Even though most of these apps run on a server only you or your team have access to, there is the occasional client which wants your code on their server.

On-premise deployment gives them full access to your code, introducing the risk of them copying it and using it in a way they were not supposed to. And since the price they paid covers only one copy of the application, you are going to prevent this from happening.

Qeys allows you to generate unique license keys for applications you made, and offers you a one line solution (in combination with a 0.8KB JavaScript file) into protecting your applications from being copied. Invalid use will be reported to you by email or Slack, and if you want, further access to the application is prevented by showing an Access Denied message which you can fully customize.

Getting your themes to your customers has never been so easy with websites such as ThemeForest. Whether it's a Wordpress or a plain HTML theme, your products are used by users all around the world. But keeping control of what happens to your work after your customer downloads the zip file has always been difficult. Until now.

Qeys offers an instant solution into making sure that your themes are only used by the clients who paid for them, or who you allowed access. Simply download and implement your project-specific JavaScript file into your theme, and instruct your users to start using the license key you gave them.

License key activation is done by adding a single meta tag. This makes license activation a piece of cake for developers using your theme. If you are developing Wordpress themes, simply add a theme setting which fills the meta tag and you're good to go.

Get notified about breaches

Email and Slack notifications when your app is used w/o a valid license.

Configure your licenses

(temporarily) deactivate or limit license usage based on domain.

Custom styling per project

Show an error page which matches the look of your web app.

Simple yet powerful dashboard

Keep your license keys organised per project and see what is going on at a glance.

Easy to install, hard to break

Download your project-specific JS file and add one HTML meta tag to your project. Don't worry, if the meta tag is removed you'll still be in control. Read our FAQ.

Get notified as soon as something fishy is going on

We'll send you an email message as soon as your product is used with an invalid license key. Like Slack? So do we. Simply add your webook URL and we'll notify you there too.

Choose your plan

All plans are monthly and can be cancelled at any time. Looking for a tailored solution? Send us an email

$199*

Frequently Asked Questions

What happens when I use your service?

When you use your project specific Javascript file and add the license key meta tag to your project's HTML, we'll validate the use of your product on pageload with a GET request to our server. We'll check our records to see if a valid license is used and that the license is used on an allowed domain. If not, we'll show the user an Access Denied page (which you can customize) and notify you about the breach.

Doesn't that slow down my product?

No, not at all. The GET request is sent asynchronously and your project will run just fine until it receives a response and either grants or refuses access. In a very bad scenario where our service is slow, the worst thing that happens is a user being able to use the web app for a couple of seconds before it is denied access.

Validating each pageload, isn't that overkill?

Definitely, that's why we don't. Whenever a valid license key is used and access is granted, we'll place a small cookie. Until that cookie has expired (after 7 days), we won't check again. Keep this in account when testing and clear your cookies before reloading if you are expecting something to happen.

What prevents my client from removing the license validation from the code they are trying to copy?

Most importantly, by the time they realise that license validation is in place, it's too late for them. You will have been notified about a breach and can take action accordingly. Besides, we strongly recommend to let our JavaScript file blend in with the rest of your application's JavaScript. Webpack, compress and uglify the best you can, to make the code responsible for validation as difficult as possible to find and break.

But what if my client simply removes the meta tag from the HTML code? That's something anyone can do!

That's right! Luckily, we came prepared. If no (or an invalid) license key is found, access to the project is denied and based on the project uuid (embedded in the JavaScript file you'll download for your project), we will find you and tell you what happened. Things get a bit more complicated if the project uuid is changed or removed from that JavaScript file, but Auto project detection is your friend.

Auto project detection? Sounds awesome, tell me more.

Sure. Whenever we receive a validation request and grant access, we create a fingerprint of the page from which the validation was requested. Then, when we deny access to a page which did not provide a (valid) project uuid, we try to match the fingerprint of that page with one of the ones we indexed. This means that in many cases, we will still be able to notify you about invalid use of your project.

And what if I don't have Auto project detection in my plan?

Access to the product will be denied, and the default error page will be shown. Your client will then realise that what they are doing is a bad idea, will call you and ask if it is possible to pay a lot of money for another copy of your awesome software*.