Name: Software Monetization Roadmap Update 2026
Uploaded: 2026-02-03T15:46:03.022Z
Duration: 30 min 12 s
Description: Software Monetization Roadmap Update 2026

Transcript for "Software Monetization Roadmap Update 2026": Hello, and welcome, everyone, to our software monetization office hours. In this session, our product team will be sharing prerecorded presentations of our upcoming FlexNet operations, FlexNet Embedded, and FlexNet Publisher roadmaps. The team is in attendance today, so if you have any questions or comments, we invite you to enter them in chat and Puja, Pushpa, and Ravi will get to them as soon as they can. A recording of this event will be shared later today, so please watch your inbox for the on demand viewing link. As always, we're happy to have you here and we look forward to sharing what we have in store for our software monetization solutions. With that, I'll kick things off with the FlexNet operations roadmap. Hello everyone. Today we'll be talking about FlexNet operations roadmap for Q1 twenty twenty six and beyond. Before we go into a roadmap for 2026, let's just see what we've accomplished in twenty twenty five q four. In 2025, last quarter, we finished API modernization for creating and managing orders in both REST and GraphQL. We are now able we do have APIs for creating entitlements, users, accounts, and products for creating and viewing those. And in role based access control using SSO and IAM, We now have SSO onboarding for producers using OIDC protocol. And now we have simplified token generation in the authentication service for all applications who are consuming data from Cloud license service. Moving on, in innovation, we have improved easy administration during renewals. That is, the changes which are done at the entitlement level are easily rolled down to line items, and from line items, the changes are trickled down to licenses. We have also input the performance and scalability to support SaaS applications. We can now change up to 25,000 licenses and update simultaneously to cloud license service, which is a huge help for dynamic packaging and of the products. This slide talks about all the accomplishments of year 2025 starting from quarter one to quarter four. You can look at these later to get the complete gist of 2025 delivery. Now let's see what are the business drivers for 2026. We have three main drivers. Number one is enabling our producers to get better data insights and software business intelligence in our product analytics, F and O analytics. Whole world is moving to SaaS and hybrid transformation, and we are doing everything to support and accelerate this transformation for our producers in our application. And the third one is innovation, where we continue to future proof our application by adding new monetization models to support better monetization in hybrid, SaaS, and AI applications. Now with these three drivers in mind, let us look at the roadmap items for 2026. Here the Q1 items are already committed and they are being implemented. We will also see the probable candidates for Q2, Q3 and beyond. Let's talk about the data insights driver and analytics under that. In analytics dashboard, we have added lot of personalization. Producers can customize, save, and share dashboard views with personalized filters and table selections. Producers can define their own reports, save, share, and then add them to their dashboards. With this, producer can gain insights into license usage from device, transaction history, using a data share of Snowflake. We'll continue in Q2 to add AI and analytics, where we will enable data focused AI agents through MCP server, which will give access to Raveniro's data warehouse. With that, producers can then in Q2 access transaction history of entitlements, line items and devices in analytics dashboards through data access APIs. And in Q2, we will be adding predictive analytics, where we can forecast entitlement creation trends using machine learning and AI driven analytics. We will continue improving our AI analytics and predictive analytics in Q3 and Q1 of next year. We will introduce natural language query processing to better for to get the better insights from data, and we'll continue to add also more customization, more support to the analytics dashboard, and allow end customers also to access and learn from the analytics dashboard. So far, it was only producer who was who will be accessing the dashboard. But in q three, end customers will also be able to have access to analytics dashboard. Moving on to our roadmap item to support SaaS and hybrid transformation. Channel partner is one important aspect in the business. And this entire year we'll be adding a lot of features to enable channel partner to have better control on the system. In Q1, channel partner will get access will give users and partner accounts access to software download. So partner accounts can also download software in Q1. And in Q2, partners will get ability to move devices between the linked customer accounts, which is not possible today. And in Q3, channel partners will allow partners to subscribe for renewal notifications and then they allow partners to view information about the downloaded files and to understand proper customer adoption. Channel partners also partner will also get the ability to report on usage of metered features in Q3. And beyond that, producers can offer trials to partners to encourage channel partner sign up. So these are the different features we will be adding to enable channel partners. Moving on, to support SaaS transformation, we are strengthening our APIs. We are modernizing through REST and GraphQL. In Q1, we will continue REST and GraphQL APIs for entitlement line item adoption readiness, to modify the accounts, modify entitlements and line items, and then we will add APIs to create, read and modify product lines and their relationships. In Q2, there will be APIs to modify users of these accounts, and in Q3 we will have more product and license model related APIs along with some peripheral APIs which will be like merge, license, transfer, host those kind of an email entitlement, those kind of peripheral APIs. And towards the end of the year, we will start working on bulk operations and continue adding more peripheral APIs. These APIs I was talking about are mostly for creating and managing orders. Parallelly we will also work on APIs for managing the devices, the FlexNet embedded devices and their licenses. So in Q2, we will be able to generate and activate licenses, and we'll be able to create and view the devices, and then we will be able to map and unmap the license to to those devices. In q three, we will have APIs to modify the devices, and in q one twenty twenty seven, we will get APIs to delete, obsolete the embedded devices. Moving on, we are going to add product packaging to help flexible selling models. Producers will be able to package their products to enable sell by suite and report by product, using our package suites and package structure, new package structure. And after this, we will be able to add configurable pricing models to this different way of packaged products. Producers can allow buyers to customize their product package at the time of purchase, and according to the selection, there will be a create order will be created using the REST API. We'll continue to see a ad configuration configurable pricing model, where producers and customers can activate a purchased product onto a device. Producer then can create a product packaging model in a very few simple steps through UI. Next, we will continue to improve our role based access control and single sign on. There'll be a centralized authentication service, which will simplify the token generation for applications which are consuming Data Access API, and then for applications which will contact Dynamic Monetization Implementation. In Q3, this centralized authentication will cover software container delivery calls, and then we will also simplify through SSO the on prem FlexNet operations. Towards the end of the year, we want to add software container delivery, where producers can add pre existing products to new container delivery packages. Producers can also replicate their own registry to a Ravenera registry to get embedded into CIICD workflows. For the usability and user experience, delivered in Q4. The changes which were done from entitlement would roll down to line items. And now they will then from accounts to we have completed from entitlement to line items and line item to server. Now in Q2, the changes will be rolled down all the way from account till the line items. So these are the items for 2026. There are couple of other slides which will give you more details into each of this feature. You can go through this, which will be shared with you. Thank you. Hi, everyone. I'm Rabbit Trivedi. This is the roadmap readout for our FlexNet embedded customers on what we shipped in q four twenty twenty five and what's coming up in 2026. Let's start with the business drivers, also known as goals, that shape the work we are doing. Number one, streamlining operations to raise the end customer or buyer satisfaction, monetization models to help you producer to be more effective on prem and give you the kind of flexibility you need in SaaS monetization, especially thinking about multi device and multi user experiences that you want to deliver to your customers at different price points. Right? And the platform support that enable you to expand into new markets monetization. So what we achieved in q four twenty twenty five, the first one is user centric monetization. We've started our journey into a native out of the box user centric monetization that we want to provide to you. And starting with what if US seller could start answering five critical questions about who the user is, where is the user logged in across devices, what capabilities are held by the user, when and how long were the capabilities held, and how many counts were borrowed when such licensing operations were done. And as you move on, under the streamline operations goal, we, have, reduced the outages and support cases, with stronger binding and better host ID stability for virtualized deployments. Right? This is a benefit for your local license server. And moving on, if you look at the UI assisted license pools that we've delivered, that will help your buyer customers do a fair allocation and cleaner budgeting using a easy user interface. Right? It doesn't stop here. Your buyer benefits have multiplied. We now have a wizard based installer for streamlining the deployments of your GUI based license server manager and also your license servers. All these capabilities are already available, and there have been office hours recorded for you. Alright. So that was what we shipped in q four twenty twenty five. Let's move on to what you can expect in 2026 on our road map starting with license sharing policy that will enable you as a seller to sell at differentiated price points with policy based license sharing. Meaning, if you want a license to be shared, can be sold at higher price point versus a license that can't be shared. So that's that's one. The second one is usability and user experience where we want to enable your buyers, the end customers, to be able to apportion the metered features so that the licenses are fairly used across the business units in their organization. It will improve on the kind of budgeting that they want to do. Right? The third one is usage for monetization analytics. By now, you know that you have the capability to have usage on your cloud license servers. You have insights and also a lot of transaction history. We'll be improving that story, and we'll enable you to get usage from point of access in even ad gap and offline servers. This will enable you to do better upsell, cross sell, and a compliance check. In later part of the year, we'll also be enabling you to take your own analytics application, give it to your end customers, extract usage from Airgap environment, and enable them to do analytics on point basis in their environment. Right? And moving on, the focus of 2026 is largely going to be on user centric monetization. There are some buyer benefits in terms of how they can create a load list of users per features and also give a UI assisted way of browsing the employees in their organizations and then making direct assignments to the licenses that are available on their cloud and local license server. Right? So those are buyer benefits. However, as a seller, we also want to enable you to set policies like default deny where the buyer admin will be required to explicitly assign a user an access onto a cloud licensing service and its licenses and to to be able to enforce such policies. You will also be able to sell your packages based on certain roles. A lot of companies have told us that they want to be able to sell at different price points for people who could view or be an operator, an admin, or an advanced user, or an executive in a c suite, and then create all these as different packages and to be able to sell to your customers. You will also have policies where you can control how many times a seat can be reassigned to a user. If you are worried about certain segments of your customers who would kind of deliberately overuse by reassigning counts to various users in your organization. Right? So that was part one. Now in part two, under platform support, you will see that we'll be enhancing our local license server and SDK support on more platforms. Think about Alpin Linux that enables you to do licensing on smaller images that has faster startup or the security is hardened hardened for such environments to even ship a native ARM 64 Linux or ARM 64 Windows license clients for better performance and energy efficiency that your customers expect from you. You will also have official Docker image for our local license server for a standardized repeatable deployments. And, of course, to include all this into a kind of Kubernetes or OpenShift kind of cluster scale where, you can include how the local license server and your clients will work in an orchestrated, environment for, high availability and nonstop licensing. Right? Under product security, we will be making our efforts into being FIPS one forty dash three compliant to enable you to run-in the government and regulated situations also, your licensing, because these companies will soon move from FIPS one forty dash two, which is an older specification to FIPS one forty dash three. Right? And moving on, we'll also eliminate the need for you as a seller to ship a default admin login to avoid the password sharing and all that. We'll enable you to connect with single sign on of the enterprise buyer organization, and then add users and assign roles like admin and view only, etcetera. Right? Under streamlining operations of your licensing infrastructure, we'll continue to reduce outages and support cases that your customers would log in to you in the physic physical environment due to a binding break, and that will be delivered through host ID stability that we are working on. And this will again be enhanced to even support the environment like containers. Right? Apart from that, we've delivered high availability to avoid license server being a single point of failure. However, there are couple of enhancements like automatic clustering and replication that we will be doing in q two twenty twenty six for a better server uptime. And the last initiative is the user experience for monetization services. You will have a wizard based way of configuring your named license pools and roles of access within FlexNet operations for cloud license servers. And you will also see that such wizard based capabilities will be added to the GUI based license server, FlexNet license server manager, for the on prem situation to manage your local license servers features and really to enable your buyers to do fair allocation and do cleaner, budgeting self-service on the license server for their purchases. With that, this is the part two of 2026 road map. Thank you all. Hi, everyone. Welcome to roadmap readout of q one twenty twenty six. Today, we are mainly focused on FlexNet Publisher. The business drivers for FlexNet Publisher remains the same. The first one is platform support, where we are enabling the producers to expand into new markets and grow their ARR. The second one is the streamlining operations. We are mainly focused on reducing the operational cost and optimizing the license infrastructure here. The third one is the revenue maximization where we are working on future proofing the host IDs, clone suspect reporting, tamper deductions, and compliance integration. In Q1, Q4 twenty twenty five, as part of FlexNet Publisher, we have delivered the enterprise scale reporting via a new service, which is called as LMISD and license server file updates, which works with zero downtime and on high capacity and high throughput environments. As part of a transferable counted model, the end customer would get a visibility on what type of license they are using. It might be a transferred license, a borrowed license, or a floating license. And this information can be used for the reporting. This functionality will be out in PLC along with twenty twenty six Q1 release of FNP. So this is the roadmap of Q1 twenty twenty six and beyond. So first one is the platform support. Here the companies are committed to reduce cabin footprint and then there is a massive trend to reduce the power consumption and the cooling needs. The ARM chips are favorable for both of these aspects, and hence, FNP is aiming to ship native ARM 64 Windows licensed server and clients for better performance and energy efficiency. And followed by the Debian support for Linux distributions. Next, the focus is on license servers to make it as an official Docker image for deployments and further to operate the licensing at cluster scale in Kubernetes and in OpenShift environments. On the revenue maximization part, on piracy front, the license servers would be enhanced to flag off the server cloning and tamper detect and detect the tampers and notify these information to the back office or to any producer's app and then the producers can decide and take the actions accordingly. Further, the producer can integrate these piracy events into Ravennaire compliance intelligence integrations for faster time and faster response. As part of future proofing, we are building a stronger and more stable host IDs for containers and for macOS containers against the deliberate overuse. On the trusted storage for any back office, we are enabling producers to activate, return and repair the licenses in an air gapped environment who are using trusted storage. This can be done with any of the homegrown back offices or also without the back offices as well. On the streamlining operations on F and P Enterprise front, we are working to get a parity between F and P Classic and F and P Enterprise by supporting more wider APIs and utilities. Followed by the border functionality that performed can under high capacity environment where it is occasionally connected. And then we are working on getting an enterprise grade reporting which can be used for analytics tool. Further, we would be giving a high availability, high available F and P enterprise for the buyers who would want to have full uptime and with a high capacity and throughput. Lastly, on the TCM front, we are enabling producers to set the same capabilities at different price points by differentiating them between the functionalities such as borrow and transfer, and then extend the full TCM support on the Linux platform. On the piracy response, which was part of revenue maximization, we have delivered some of the features. The first one is the notification framework where we are enabling producers to take action on the piracy events that will be detected. The producers can take actions such as like send these information into server logs or notify the engineering applications and then many more. The second one is the built in composite host ID. So this is a more futuristic, more secure host IDs, which is built using many fingerprints of a certain machine and this host ID prevents cloning and spoofing. The third one is the server line enforcement. Here we are allowing producers to control where the server should run at an end customer's end. So the producers can set the combinations between physical, virtual, and containers and allow end customers to run only on the selected environments. Further, clone detection, the tamper detection, and the RCA integration would be coming up in the upcoming quarters, which we spoke earlier in the previous slide. So the top three features are already part of eleven ninety nine, which was released in the 2025. Also, have done the office hours and have given the demo on these three features on how they work and how producers can integrate the notification frameworks and take the actions accordingly. If any customers are interested, they can just request for a demo, the recorded demo, yeah, we would be sharing it across. So this was the roadmap update of FNP for Q1 twenty twenty six. Thank you. This concludes our roadmap presentation. If you have any additional questions or comments, please reach out to your Revenueera account or customer success manager, and they'll be happy to get those questions onto our product team. Thank you, and we hope you have a great rest of your day.