Blog on Software Licensing, Commercialization, and Revenue Optimization

Should You Develop A SaaS Application?

Posted on

Should you develop a SaaS application? That question is very valid, because today, SaaS products are everywhere, and they are very profitable too. Just look at Microsoft, Oracle, and Adobe. Some of the world’s leading companies have adopted the SaaS business model, so should you?

Today’s blog is all about the SaaS business model. The advantages, disadvantages, and some tips on how to develop them. We have already made the following video covering this topic:

First of all, let’s make sure that we are all on the same page here. What is a SaaS application? Software as a Service, or SaaS, is a type of cloud-based software where customers are able to rent the use of an app and connect to it, usually using a web browser. A SaaS product does not have to be downloaded or installed because the underlying infrastructure and app data are stored in the service provider’s data center. GitHub, Slack, and Trello are some examples you might be familiar with.

Advantages for customers

With that in mind, a customer doesn’t necessarily buy a SaaS product, they rather buy the right to use it for a limited period of time. The subscription pricing model is commonly used, and we have already made a blog post covering that pricing model. One benefit that I mentioned in that video is that subscriptions lower the entry barriers for customers, and that is also one of the benefits of SaaS products, as seen from a customer’s point of view. It’s just cheaper to get started with subscriptions than a one-time payment!

Another benefit lies within the cloud itself. Since you do not download a SaaS product, customers can use it anywhere, with any device that is connected to the Internet. There are no download or setup time delays, just log in and start!

Advantages when developing a SaaS application

Great, but what about the developer’s point of view? When you begin to code a SaaS app, you can have a lower initial cost because you can leverage cloud services from Amazon, Microsoft, or Google to host your product so you don’t have to invest in hardware.

These providers also make the application very scalable and flexible, you can simply tell them to increase your computing power as you face a higher demand for growth or seasonality reasons. This does not come with any unnecessary overhead costs and can be done pretty quickly. You can then fully capitalize on the high demand!

Disadvantages and solutions when developing a SaaS application

Now, there are also some important disadvantages and challenges we need to consider. If you really want to develop a SaaS application, I also have some solutions to share. One issue is that you have to code a lot of functionalities to facilitate all kinds of users. That can easily take a lot of time and effort. The solution to that problem could be to integrate with third-party products instead of coding everything yourself. For example, some products might benefit from having a sophisticated map function. Why code such a feature yourself, when you can simply integrate your product with Google Maps?

Another third-party solution you can use to save significant time and money is a special type of SaaS product called LaaS, Licensing as a Service. Cryptolens offers such a service! Instead of coding your own software licensing system that controls who has access to your application, you can use Cryptolens.

A final remark on continuous improvements

My last remark will be a bit broader than both the developer and customer perspective. The process of continuous improvement is a commonly used term within business management that refers to the ongoing improvement cycle focusing on employee involvement and customer enjoyment.

The SaaS business model makes continuous improvements easier since you have greater access to usage analytics data. You will then know exactly what features your customers are using in real time, and you can focus on enhancing the features your customers love the most.

Thank you for reading, stay smart!

Implement Software Licensing for Free

Subscription Pricing Model For Software Products

Posted on

Today, subscriptions are everywhere. If you want to watch a movie, you need a subscription. What do you need to listen to music? A subscription! And what about a car? You guessed it, you can actually get a car with a subscription with some brands. But why is that? What made companies switch from perpetual, try-and-buy pricing models to the subscription pricing model for software products?

In this blog, we will answer that question and show you how a subscription pricing model can take your software business to the next level. We have also made a video covering this topic:

Advantages of the subscription pricing model

Firstly, subscriptions are oftentimes preferred over a one-time payment since they significantly lower the upfront cost for your customers. Most people do not have $50.000 in liquid cash to spend on a car, but they might be able to afford $500/month. And although software products are usually a bit cheaper than cars, the logic is still the same.

You can also create different pricing plans to attract different kinds of customers. A basic pricing plan can be sold for a small subscription fee of $50/month for users who will only use the basic functionality of your application. It is then possible to charge extra for an unlimited pricing plan with all features at a higher price, let’s say $350/month. Both newcomers and advanced users can buy your product!

But that’s not all. You can also get more predictability from the cash flow of your business. Instead of having them buy your product and then you never see them again, subscriptions will give your business an MRR – a Monthly Recurring Revenue.

For example, let’s say that you have 10 customers, 8 of them are on the basic plan, and 2 of them are on the unlimited plan. That would give you, in this example, a monthly recurring revenue of $1.000. This is a game-changer for budget planning, you know exactly how much money you can spend on ads each month, for example!

Unless a customer cancels their subscription…

Disadvantages of subscriptions

That gives me a perfect opportunity to cover some disadvantages. The churn rate can indeed be a problem. If you charge customers on a monthly basis, you give them a lot of opportunities to churn. In the previous example, we can see that it would be especially bad for the MRR if one of the 2 customers on the unlimited plan churns since they actually bring in most of the money each month. This highlights a dependence on a few customers that you don’t have if you let customers pay the entire price at once.

You can incentivize people to pay upfront even with subscriptions. A popular way is to offer a slightly cheaper price if customers pay once a year instead of once per month, but that is not always ideal. The churn rate is definitely something to consider before choosing to implement a subscription pricing model.

Implementing subscriptions with Cryptolens

If you sell a software application as a subscription, you need a system that can automatically restrict access to your application from customers who stop paying. The system you seek is a software licensing system, but coding such a system will take significant time and money.

Using Cryptolens and our easy-to-use software licensing system is a lot more effortless! Since Cryptolens is also completely free during the development phase of your application, there is no risk of trying it out. We are trusted by hundreds of innovative and world-leading companies worldwide.

With comprehensive implementation guides in the programming languages you love, you can implement the subscription pricing model within minutes!

Implement Software Licensing for Free

Implement Subscription Licenses

Posted on

Today’s blog will feature how you implement subscription licenses. The use cases you can have for subscription licenses will be covered, and how you integrate your payment provider such as Stripe.

The most common way to implement subscription licenses is the Software as a Service (SaaS) model. That is where you restrict access to the product when a license expires. You can also allow customers to use the product without a valid license, but they are not allowed newer upgrades. You can also tie the subscription to a support agreement so that only people with a valid license get access to support.

All of these methods will be covered today. For the full documentation page on this topic, click here.

We have made the following video tutorial for this topic:

The SaaS Model

The most common use case is where a customer has to pay a monthly or yearly subscription fee to use the product. If they do not pay, their access to the product will be restricted. They would then have to extend the license to continue to use the product. This method is oftentimes seen today with the Software as a Service (SaaS) business model.

In Cryptolens, you can implement this using our pre-made “Expires” field. We already have a blog post covering how to set up time-limited licenses that you can find here.

In short, you have to click on “Edit Feature Names” on the product page and click the checkbox “Treat all licenses as time-limited”. Now, Cryptolens knows that you want to use the SaaS Subscription Model.

When creating a license in Cryptolens, you can specify for how long the license should be valid. If you want to extend the expiry date, simply click on a particular license and you can either choose a date in the calendar or choose to extend the license for X amount of days. You can also automate this by integrating with your payment provider. We cover that topic at the end of this blog.

An important last step to remember is to make sure Cryptolens blocks all expired licenses. You can find that tutorial here, but that should only be done for this method of implementing subscriptions.

Restrict Access to Updates and Support

Some software developers want to continue to allow customers to use the software after the expiry date has been reached. However, without a valid license, a customer cannot get access to updates. This would still incentivize the customer to keep extending their license.

Let’s take an example of how this could work in practice. Let’s say that a customer buys your software at the launch of version 1.0. Their license expires right as you release a minor update, version 1.1. The customer can get access to that minor update and continue to use the product even though their license has expired. However, when you release a major update to version 2.0, the customer is not able to access that version without a valid license.

You implement this version of subscriptions by using data objects. In Cryptolens, you would create a new data object and use it as metadata. Create a new data object and call it, for example, “major_version”. Give the IntValue field the value 1 if you want your version to be 1.0. Click on Create. Now, you have a way to track major releases of your application.

If you want to keep allowing customers with expired licenses to use the product, another way to incentivize them to renew the license is to limit the support given to customers without a valid license. This essentially means that they subscribe to a support agreement rather than to the product itself.

For more information on how to implement this model, please check the full documentation page. For this method, you should not tell Cryptolens to block expired licenses automatically, since you want people to keep using their version of the application.

Implementation with Payment Providers

You can manually extend the expiry date in the Crypolens dashboard, but it might be beneficial for you to automate the process so that the expiry date of a client is automatically extended after a successful payment has been made.

In the Cryptolens API, there is a method called the ExtendLicense method. When a successful payment has been made by a client, use that method when calling our API to automatically extend their license. This method works no matter if you are using Stripe, PayPal, other providers, or even an internal payment system.

For more information, please read this page in our documentation. There, we also have API methods to automatically create a new license key, add features, block the license, and more.

You now know how to implement subscription licenses in Cryptolens!

Get Started with Cryptolens Today!

Start For Free

An Introduction To Pricing Models

Posted on

Choosing between different pricing models can be hard, but it is a crucial decision to get right. Should your software product be sold at a one-time price? Should you charge a continuous subscription fee? Or should you maybe even charge customers differently depending on how they use the product?

These questions will be answered in today’s blog, as I will briefly introduce three of the most common pricing models, Try-and-Buy (Perpetual), Subscriptions, and Pay-per-Use.

You can also find the video that we have made for this blog here:

The Try-and-Buy (Perpetual) Pricing Model

To illustrate some different ways a software product can be priced, consider the case of a music streaming app. They could let you try the application for one month before you have to pay the price of $50 to continue to use it forever, a so-called Perpetual, or Try-and-Buy model. That way, users are able to temporarily realize the value of your product for free, and at that point, they have an easier time justifying the one-time price.

The Subscription Pricing Model

The streaming app could, maybe more realistically, choose to impose a continuous fee. Let’s say a monthly fee of $12. Does that sound familiar? That is called a subscription model, and it can be beneficial from a business model perspective since you get a more predictable cash flow each month, and you might be able to attract users who are not willing to pay that high one-time price. The lifetime value of a customer can still be very high if they continue to use the app for a long time.

The Pay-per-Use Pricing Models

The last pricing model is to charge customers differently depending on how they use the application, the so-called Pay-per-Use model. The music streaming app could charge customers, let’s say $1, for every hour of streamed music. The more you use the application, the more you pay at the end of the month! This can create a more fair pricing plan – big users of your product pay a high price but they get a lot of value, small users pay a bit less but at that price, they still think it’s worth it.

Implementing Pricing Models with Cryptolens

So how do you implement these pricing models in practice? It all begins with a software licensing system. In short, the system is linked to your payment provider such as Stripe or PayPal, and it makes sure that only people who pay get access to your application.

With Cryptolens, you can implement an easy-to-use software licensing system within minutes with our comprehensive guides. Hundreds of innovative companies are using our licensing as a service (LaaS) platform to license all kinds of applications.

Implement Software Licensing for Free

Why Outsourced Software Licensing Systems Are Better Than Internal Solutions

Posted on

When developing a software application, many ask how they should implement a software licensing system. Should you code it yourself? Should you outsource software licensing?

I would generally say that outsourced software licensing is the most scalable, reliable, and cost-effective solution in the long run. This blog will cover exactly how a third party can help software developers save both time and money!

We have made the following video covering this topic as well:

Coding it yourself

First of all, what is a software licensing system? We have a short blog post covering that topic that I recommend you to read if you are unsure. You can find that blog post here.

This post will be all about implementing such as system in practice. One way is to code it yourself, and there are some situations where you might want to do that. If your application is not supposed to be sold on a large scale, and you want to grow your coding skills, coding a software licensing system can be a fun project for hobby developers.

You might also say that coding it yourself is the economically smart solution since you pay with your own time rather than your own money. That argument falls a bit flat when considering that some software licensing providers, such as Cryptolens, are completely free during the development phase of your application.

You can then implement software licensing without any risk!

Outsource software licensing – the benefits

Coding your own system will take time. Implementing a third-party solution is a lot more effortless, allowing you to quicker bring your product to the market. This also helps you save money, since there is no internal development cost.

So outsourcing helps you save both time and money, but let’s say that you completely ignored our recommendations and coded your own system anyway. You may suddenly find yourself in a problematic situation – your company grew so much that your self-coded system is no longer able to support your needs. Constantly getting angry emails from customers saying they can’t access your product is never good. This highlights the fact that a software licensing system needs to constantly be updated and maintained to work flawlessly.

What about coding your own system at first, and then switching to a third party when the maintenance gets out of hand? Well, at that point in time, switching licensing solutions will be a big project that will have an impact on all of your customers. Let’s face it, it is probably easier for your customers to go to a competitor than it is for you to switch solutions at that point.

A final shared value perspective

To conclude this blog, I would like to step away from the perspective of time, money, us and them, and step into a world of shared value – the concept that combines business success with providing value to society as a whole.

By outsourcing software licensing to experts, your company can focus on what truly matters:

Your own product.

That way, your company does not only become more productive and cost-effective, but it also helps you provide more value to your customers, and you make the world just a little bit better.

Thank you for reading, stay kind!

Implement Software Licensing for Free
Different types of software licenses - Cryptolens

Subscription VS Usage-based licensing

Posted on

Do you want to license and sell a software product? Then you might be interested in understanding the differences between subscription VS usage-based licensing. The two licensing models are beneficial in different ways, and we will in this blog give you guidance on what to choose.

If you want to read more about licensing models, please read our help pages. We made the following video covering subscription VS usage-based licensing:

When to choose usage-based licensing

First of all, what is usage-based licensing, and how does it work? Usage-based licensing is when you charge a customer for a specific action. For example, you might sell software to photographers where they can edit photos. Instead of charging your customers a subscription fee once a month, you can charge a customer per photo that they edit in your software.

One benefit is that you can charge the customer more fairly. Enterprises that use your software every day pay a high price. Startups that use your software once in a while are allowed to pay a lower price.

So when should you opt to charge per usage instead of a subscription fee? The value that your customers get from your product must be highly correlated to the specific action you want to charge for. This simply means that the actions you charge for need to provide a lot of value to your customers.

Your editing software from the example provides value to your customer only when the customer edits a photo. Therefore, it is appropriate to consider usage-based licensing for such a software product.

When to choose subscriptions

Great! But when is it not a good idea to charge customers for certain actions? We covered earlier that usage-based licensing allows you to attract both small and large customers since they can have their own prices depending on their usage.

If you are selling multi-purpose software where you cannot find one specific action that gives all of your customers a lot of value, subscriptions can still allow you to charge customers different prices.

By implementing different pricing plans with different feature sets, you can motivate enterprises to pay a higher subscription fee to get full access to your product. Startups can then get a more basic version without all of the features at a smaller price.

Cryptolens makes it effortless to license and sell any type of software application, no matter if you want to implement subscriptions or usage-based licensing.

Get Started with Cryptolens Today!

Start For Free
Pricing
Different types of software licenses - Cryptolens

Filter search results

Posted on

When you have a lot of licenses in the Cryptolens platform, it can be useful to search for specific properties such as blocked/active, the created-on date, and so on. In this blog, we feature some of the queries you can run to effectively filter search results in Cryptolens.

This blog is based on the following two help pages relating to sorting and ordering. For a video guide, please watch the following YouTube video.

Searching licenses using Linq Queries

One of the most basic ways of searching for licenses is to simply paste the license key into the search field.

You can also search for all licenses with a specific property. For example, you can find every license key that has Feature 1 set as true by pasting the following text into the search field.

f1=True

You can use the same logic to search license keys based on other features. Below, you will find the query for finding blocked licenses.

Block=True

If you instead want to find all licenses with the period set to 30, you can do so by pasting the following query into the search field.

Period=30

Advanced searching

A more advanced way of searching for licenses is to find licenses that have been issued after a particular date. To do so, please see the following query example.

created > DateTime(2024,05,01)

The same logic can be applied with the parameter “expires”.

Furthermore, you can search for all license keys that have been activated on a device. For this example, let’s find all license keys that have at least 2 activated devices.

ActivatedMachines.Count() >= 2

Let us now assume that you just received an email from a customer saying that they have lost their license key, but they provided their machine code.

You can then search for licenses that have been activated by a particular machine ID using the following query:

ActivatedMachines.Count(it.Mid="machine code") > 0

You would simply replace “machine code” with the machine ID of your customer.

There is a similar way to search for license keys if you are using the API. The method is called GetKeys, and the same queries can be used if you prefer to use the API.

There are many more properties you can use to filter search results in Cryptolens, and we have them all listed here.

Customizing the order of license keys

As you can see in the Cryptolens dashboard, there are different preset ways of ordering license keys. For example, you can order by feature and creation date.

For more advanced customization of the ordering, please visit this help page.

If you have any questions, please contact [email protected]. Thank you so much for reading!

Get Started with Cryptolens Today!

Start For Free
Pricing

Software Licensing System – Why More Developers Should Care

Posted on

Are you working on a software application that you one day want to sell? Then you need to think about software licensing early on. No, I am not talking about End-User License Agreements (EULA) or legal documents, I am talking about a software licensing system – the system that ensures that only customers get access to the application.

Why is a software licensing system so important? Because without it, you simply cannot sell a software application to customers.

In this blog, I will briefly, and in a non-technical, way describe what a software licensing system really is, and how it can enable you to take your software passion and turn it into a business.

We have also made a YouTube video about this blog if you prefer to watch rather than read (like me).

What is a software licensing system?

To make this blog a bit more fun, picture the following analogy. Let’s say that your software application is like a house. The different rooms of the house are the different features in your application. One room can house the most basic features, and another room can house more advanced functionality.

Without software licensing, your application does not have any locks. Users can enter whatever room they feel like without paying at all! It becomes clear that no one would ever pay for such a product, since everyone can just use it without paying.

A software licensing system would establish a lock on the front door, making sure that only people with a key can access your application.

How does this system work in practice? That is a great question! So great that we will cover it fully in a future blog post. For now, let us just assume that the system indeed works as it should.

Software licensing performs key verification

The next step for us is then to create keys for the front door and give them to our customers when their payment has gone through. In software licensing terms, that key is a digital license key that is unique to each customer.

So what happens when a customer tries to enter our application? In the most basic setup, they will be greeted by a locked front door. After providing their license key, the software licensing system checks so that their license key is valid, and if it is, the door is unlocked and the customer can begin to use the application.

The customer can then leave the application, and the key verification process is repeated whenever they try to run the application once more.

If a non-customer tries to access the application, they will be greeted by the same locked front door. Without a key, they cannot enter!

Some software applications choose to charge a customer a subscription fee. Monthly or yearly subscription fees are the most common ones. Then it can be useful to block the license key of customers who stop paying their fee. If such a customer, or ex-customer, tries to use the application, they will not be let in. That is because their license key stopped being valid when they stopped paying.

Charge extra for more features

Now you know the basic setup, but what about the different rooms I mentioned earlier? Let’s suppose that the house has two rooms, one with basic features, and one with more advanced functionalities.

It is sometimes beneficial to charge customers extra for using the more advanced features. You can then create two different types of license keys for the different rooms. A green license could, for example, cost $100 and give customers access to the basic features of your application. A red license could instead cost $500 and give customers access to all of the features in your application.

The moral of the story

So that’s it, right? Is software licensing really that simple?

Of course, it isn’t. But we hope that the simple analogy gave you an introduction to software licensing and how it enables you to sell a software application.

But remember – although a software licensing system enables you to sell your application, it alone can never make your application good enough for customers to want to buy it.

That is something only you have the power to do.

Thank you for reading, stay curious!

Implement Software Licensing for Free
Different types of software licenses - Cryptolens

How do you implement a Software Licensing System?

Posted on

When you are thinking about licensing and selling your software product, you probably come across the question “How do you implement a software licensing system?” In this blog, we will cover the basics of Cryptolens so you can get an idea of how you can implement a software licensing system and start to license and sell your software product.

Please visit our help pages if you want to learn more. You can also learn about software licensing basics in the following video:

Implement a software licensing system

Follow these easy steps to start:

1. Install our SDK in your programming language.

2. Create a free Cryptolens account.

3. Insert a code snippet into your code.

    Let us begin with the SDK. Cryptolens offers comprehensive SDKs in your favorite programming languages to make it effortless to implement a Licensing as a Service (LaaS) platform within minutes. Install our SDK in your language here.

    Create a free Cryptolens account to get access to our easy-to-use dashboard where you can create and manage license keys and restrictions. You can also find your access tokens and other parameters that you have to insert into your code. Cryptolens offers you a way to implement licensing for free at your own pace, and you only have to pay when you get customers of your own. Check out our pricing plans here.

    The last step is to insert a code snippet into your application’s code. We provide comprehensive help guides to make the implementation seem effortless. The following image gives a summary of how our code snippet looks. See the code snippet in your programming language here.

    License key verification is effortless with Cryptolens software licensing system in any coding language!

    Are you new to Cryptolens? Welcome! We are dedicated to offering an easy-to-use Licensing as a Service (LaaS) platform so you can license and sell your software application within minutes.

    Get Started with Cryptolens Today!

    Start for Free
    Pricing

    Offline license verifications

    Posted on

    Users expect some software products to run in offline settings. Then, the software needs offline license verifications to confirm the customer’s license key. In this blog, we will cover how to set up offline verification in theory and in practice, regarding two major use cases:

    1. When a customer is allowed to temporarily be offline (for example, use the license while they are in airplane mode).

    2. When a customer is allowed to permanently be offline (for example, behind a corporate firewall).

      This blog is based on the following page in our documentation.

      Here is a YouTube video covering the same topic:

      Background

      Let us refresh our memory of the standard license key verification code. For the remainder of this blog, we will cover example codes in Python, but the process is similar in other languages.

      Below you can find the basic key verification code in Python.

      result = Key.activate(token=auth,\
  rsa_pub_key=RSAPubKey,\
  product_id=3349, \
  key="ICVLD-VVSZR-ZTICT-YKGXL",\
  machine_code=Helpers.GetMachineCode(v=2))

if result[0] == None or not Helpers.IsOnRightMachine(result[0], v=2):
  # an error occurred or the key is invalid or it cannot be activated
  # (eg. the limit of activated devices was achieved)
  print("The license does not work: {0}".format(result[1]))
else:
  # everything went fine if we are here!
  print("The license is valid!")

      When Key.Activate is called, it calls Cryptolens API, which in turn returns a signed JSON object placed in the result variable. This allows you to proceed as normal and check features, expiry dates, and other parameters. In the code above, we are checking if the license is activated on the correct machine.

      Using the following code in Python, we can save the JSON object to disk, allowing us to read it again when the customer lacks internet access.

      # res is obtained from the code above
if result[0] != None:
  # saving license file to disk
  with open('licensefile.skm', 'w') as f:
    f.write(result[0].save_as_string())

      Case 1 – Temporarily offline

      If customers are expected to be offline once in a while, it is considered good practice to always attempt to make the key.activate call, and only load the saved license file from disk if the customer is offline and key.activate fails.

      The following Python code example shows you how to load the saved license file from disk:

      # read license file from file
with open('licensefile.skm', 'r') as f:
  license_key = LicenseKey.load_from_string(pubKey, f.read(), 30)

if license_key == None or not Helpers.IsOnRightMachine(license_key, v=2):
  print("NOTE: This license file does not belong to this machine.")
else:
  print("Feature 1: " + str(license_key.f1))
  print("License expires: " + str(license_key.expires))

      Notice that the parameter load_from_string has “30” set as a parameter. This means that the customer is only allowed to use the software offline for 30 days. You can customize this value so it suits your use case. For example, you may want to change it to 7, if you only want to allow a customer to be offline for a week.

      When the date has been reached, the customer will need a new license file (which may be obtained by successfully calling key.activate), which can be done with the LoadFromFile method.

      You could also remove the “30” parameter if you do not want to set a limit at all.

      If you want to see more code examples in Python, please visit our GitHub page.

      Case 2 – Permanently offline

      To support customers to be fully offline and still use your software for a long period of time, you would have to send the license file to your customers since they cannot call key.activate.

      There are four methods you can use:

      1. Calling key.activate on your end and sending the file to your customer. You can automate this method.
      2. Using Activation forms hosted by Cryptolens for an easier solution.
      3. Obtaining the file manually in the dashboard.
      4. An On-premise License Server by Cryptolens for when you anticipate many end users or want to support floating licenses offline.

      1:

      The first method is where you call key.activate on your end and send the license file to your customer, for example, over an email. If you would like, you could set up an automized way where your customers can request to download their license file from your dashboard. This could, however, become somewhat complex.

      2:

      An easier way is to use activation forms by Cryptolens. When inside the Cryptolens dashboard, open the tab called “Forms”, and click on Activation Forms. This form performs a call to key.activate much like you would do on your own in the previous method, but we provide a simpler GUI for your and your customer’s convenience.

      Using the form, customers can simply enter their license key and machine code, click on active, and they will obtain their license file that they can insert on their machines.

      3:

      You can also manually download the license file from the Cryptolens dashboard. Go to the desired product page, find the license key you want to download the license file of, and click on the yellow wrench icon to the right of the key. Click on “Download activation file” and send it in your desired way to your customer.

      4:

      All of the above-mentioned methods are useful when there are only a few employees on site who would use your software offline. But, if you anticipate that your customers will have many end users, or if you want to support floating licenses offline, you can use an on-premise license server that Cryptolens provides. Please read the documentation relating to the on-premise license server to learn more about this approach.

      Thank you for reading this blog about setting up offline license verifications in Cryptolens, please feel free to ask questions to [email protected].

      Get Started with Cryptolens Today!

      Start For Free
      Pricing