QR codes is a well-established means to enabling payments, website discovery and more. SLASCONE enables devices equipped with a camera or a scanner to use QR codes for their activation. Similarly to traditional alphanumeric license keys, QR license codes can be sent via email to the authorized persons. Alternatively, the authorized persons can log in [...]
Visit us on the 4th of December @TechCrunch DISRUPT to discover how SLASCONE can help you protect and monetize your software and devices. See you in Berlin!
Software licensing solutions are usually associated with desktop or server software applications. Nevertheless, hardware and intelligent device vendors, both in industrial and consumer space, are becoming software vendors too since: Hardware is becoming a commodity Software has traditionally higher profit margins than hardware Accompanying software modules enrich the offered product Device vendors require business model [...]
We proudly announce the general availability of SLASCONE 1.0. Register to our Argus Demo Vendor now in order to experience SLASCONE 1.0 live.
The licensing policy of the majority of (B2B) software and device vendors falls in one of the following categories: Technical (proactive) In-house licensing solution External/professional licensing solution Audits (reactive): no technical licensing, terms regulated on paper Hybrid - combination of technical licensing and audits The challenge for every vendor is to choose the policy that [...]
A fundamental objective of most software vendors is to find partners/resellers that will help them scale their business. Resellers can be particularly beneficial, in many case the only way, for expansion and international growth. Nevertheless, establishing successful channels is particularly challenging for software vendors: Enablement/Attractiveness: providing resellers with the necessary support (training, material, marketing) for [...]
A surprisingly big number of software vendors rely on software audits instead of a real licensing solution in order to prevent over-usage. I call this the reactive approach. The majority does opt for a proactive approach. Nevertheless, instead of integrating a professional solution, it chooses to develop an in-house solution (let's call this solution EasyLic). [...]
Being responsible for our licensing, every time that a new, to be licensed feature was developed, I had to update the (master) license definition. In parallel, our engineers had to make sure that the software worked seamlessly with our licenses. While neither this process nor the subsequent generation of new licenses was a headache, existing [...]
As I explained in my first post, my first acquaintance with licensing came through my analysis requirements. Since we already had an in-house solution (which experienced colleagues of mine praised, considering it superior to others) and everything seemed to work fine, I naively believed that licensing would not considerably bother me. After all, product managers [...]