HISE Copy Protection / pay-to-own

[Gabor.K]

Hi everyone,

I'm quite new to the copy protection topic in general, and I am just learning HISE as well, so I would like to ask for some support.

I would like to implement a "pay-to-own"-based copy protection, and I found in the HISE documentation that I can do that by adding an expiration date to the activation.

What is the way of adding this expiration date, and checking regularly on each startup?

Any help, or even just some direction would be greatly appreciated.

Thanks!
Gabor

[Dan Korneff]

@Gabor-K This would require that you interface your plug-in with a server backend. With the help of a few awesome people on the forum, I've been working on implementing my own solution, but it's not an easy task. Although I may be slower than most programmers, I'm still a year in to the project.
If you're looking for something that's easy that you can use right away, check out https://activate.hise.dev/
It's simple and affordable.

[Gabor.K]

Thanks @Dan-Korneff !

Well, I guess I was naive to think I could do it myself. :) I will check this solution, it looks promising.

Is the complicated part the server backend, or the HISE-side? Or both? I think my responsibility would be only on the plugin side.

[d.healey]

@Gabor-K said in HISE Copy Protection / pay-to-own:

Is the complicated part the server backend, or the HISE-side? Or both? I think my responsibility would be only on the plugin side.

Complicated is a relative term, it depends on your skill set. If you're asking the question then the answer is probably both.

[Gabor.K]

@d-healey
I am a beginner, but also a fast learner. Do you have any tips for topics I should look into?

[d.healey]

@Gabor-K For server stuff you'll need to learn PHP and REST. On the HISE side I'm not sure what specifically would be required for this, but probably the server and file APIs.

[Gabor.K]

Thanks @d-healey ! I will have a deep dive into the server and file APIs then.