Okay, we'll get going. Thank you for joining us for our next session. My name is Paul Treiber. I cover Canadian technology stocks at RBC. I'm really pleased to be hosting BlackBerry. From BlackBerry, we have Tim Foote, the CFO, and John Wall, President of QNX. Thank you both for joining me.
Thank you.
[inaudible]
Just wanted to start, just to make sure everyone's on the same page in terms of BlackBerry, more specifically QNX, and the value proposition with QNX within vehicles. Can you explain the landscape to software-defined vehicles and where BlackBerry and QNX sit within that landscape?
Yeah, absolutely. QNX makes an operating system and a virtualization solution. The way we like to describe it is we're the foundation that runs on the chip that allows the car makers to write their applications. The way I like to talk about this is think of iOS or think of Windows on your laptop. We're the equivalent of that, but on embedded hardware in mission-critical applications. We have safety certifications, security certifications. We have the highest level of robustness in our products that allows our customers to write mission-critical applications, whether it's in the vehicle or whether it's in physical AI, industrial automation, or medical.
From a competitive landscape point of view, who do you typically see most frequently?
From a competitive landscape, I think we see Linux more predominantly. I think if you look back to three, four years ago in automotive in particular, we might see Green Hills or we might see Wind River. But since there's been a jump in the performance of the processors that are being used in the cars, we don't see them anymore. It's really, I would say our main competitor is Linux. And even in that case, Linux has had difficulty becoming safety certified. I think our customers have really gelled around QNX because we provide the best solution for them to build safety-certified applications on top of us.
On that, you mentioned that the compute has gone up. One of the things with software-defined vehicles is the move to domain controllers.
Yeah.
I think that ties into SDP 8 or part of SDP 8. The question is, in terms of the growth that you are seeing, one of the things is sockets, and then I guess the price per socket. What has been probably the bigger driver? Is it one or the other? Is it a combination of both?
I think it is a combination of both. What we are seeing in the vehicle is more high-performance compute. When we think about high-performance compute within the vehicle, we tend to think that we are kind of there, and all the cars have high-performance compute. It is actually really only about 30% of current automotive volume has high-performance compute. We are very dominant in that area where there is high-performance compute. But the opportunity to grow, if you look, we have some data from S&P that shows that in the next five years, 3/4 of that volume of automotive will have these domain controllers. The growth projection for us, even with automotive volume staying even, is very strong. At the same time, you are going to see more cars have domain controllers, but you are also going to see more domain controllers within those individual vehicles.
We feel really strongly about the growth that we can see in automotive just with our baseline products.
You see that, BlackBerry discloses annually, then you give a mid-year update, the royalty backlog. Year- to- date, for the six months, it has jumped up quite nicely. What is underpinning that, behind the scenes, in terms of the wins that you are gaining?
Yeah, this is most definitely one of the key performance indicators for this business. It gives us a great line of sight, Paul, into the future of the revenue generation for the QNX business. This is a backlog that's been growing at a very healthy rate. The CAGR over the last four years or so has been approaching 20%. So, in the last six months, for it to inflect like this up by, as you mentioned, $250 million in just six months, shows the potential for growth further down the line. There's always a design phase, which is typically has been two to three years. That's compressing as we go forward. That points to growth further down the line. That's really coming down to two things.
We're going to probably talk a bit more about our Alloy Kore product, which is a significant move up the stack for us. So, beyond that operating system, the Windows of the car that John was talking about, to include pre-packaged, fully integrated software as more of a platform to solve a number of industry issues. Significant uplift in ASP. So, we've been pointing to 3x to 5x. That's part of it. The other part is the move from our previous version of QNX, which was called SDP 7, to the latest version, which is SDP 8. Higher performance operating system, and with it, a higher price tag as well.
Just to add to that is I also think there was a lot of noise in the industry in the last two or three years about Safe Linux and Red Hat playing a role in there and some others. I think that noise has subsided, and the overwhelming majority are using QNX as their foundation. I think that the design wins are coming quicker. The auto industry has matured. I think software is becoming something they're more comfortable with than previous years. There's also much more of a make versus buy, and I think they're starting to realize there's certain areas where they should buy and not necessarily make. I think that's all played very well for QNX.
Can you speak to, on the procurement side, I think automakers historically have bought components. Are you seeing a change where they're thinking more strategically about software in terms of buying an actual platform, as opposed to individual pieces?
Absolutely. I can't emphasize this enough, but Alloy Kore was a pull from a particular OEM that said, "We're tired of working in the underwear of software." It's a German car company, so that was the expression they used, and they really felt that there needed to be a de facto standard at the platform level to really allow them to reuse their assets so that they're not thinking project, they're thinking product. So when they're building software for their cars and they're building features that matter to their consumers, they really wanted to start looking at, "How do I have this platform that I can rely on going forward and just continue to build my assets of features that they can monetize with their customers?" I think they quickly realized owning the entire vertical stack was more work than they anticipated.
It was more difficult than they anticipated, and at the end of the day, there was a part of that vertical stack that consumer didn't care about.
In some way, you mentioned Linux as a competitor, like Linux is trying to be a similar stack. I guess they haven't had much success, but they're trying. Is that where you see them?
Yeah, we've seen a number of initiatives from people that distribute distributions of Linux, like Red Hat, that have worked very hard to try to provide a safety story around Linux. They've been mildly successful, but what's happened is it's put a lot of the onus of doing the safety work on the integrator, on the OEM. They haven't been able to reach the same level of safety certification, so they've reached a level that's good enough for telltales on an instrument cluster, but not good enough to control steering, braking, acceleration. I think that the solution that QNX provides, which is a Safety Element out of Context, makes the job a lot easier for the OEM to get their entire system certified. I think we've provided an easier path to certification.
Alloy Kore was one of the drivers of the big jump in the royalty backlog. Specifically, it was a joint venture called Coretura. Can you elaborate a bit more on that win in terms of what they were looking for, maybe some of the alternatives perhaps they looked at, why they ultimately selected QNX?
Yeah, so Coretura is a joint venture between Volvo Trucks and Daimler Truck, and they were formed specifically to create a trucking platform that would serve not only Daimler and Volvo, but other trucking companies as well. We had been working with both Daimler and Volvo, and they had taken on individually the initiative of building their own ECUs, and I think they saw one of the bigger challenges was the platform, the integration of the platform, a lot of the low-level work that companies like QNX do. So they were asking us to do more. When they got together and they formed Coretura, I think it was a natural for us to start having discussions with them about how we could help them get to their trucking platform. Alloy Kore is not a specific trucking platform.
It is a base ECU platform that takes care of common things like diagnostics, communication, thermal management, lifecycle management, which is ubiquitous to trucking or cars. Coretura's job now is to take that platform and add the extra special sauce that makes it more relevant to the trucking industry, because the trucking industry is much more challenged. When you build one platform for trucking, it could be a dump truck, it could be a cement truck. There is a lot of variations of what that platform can do. We stay out of that. That is Coretura that is building that. But we felt very good about our opportunity. I mean, they did look at alternatives, but ultimately they selected QNX and Alloy Kore.
Is it logical when you look at your install base, would they naturally migrate from SDP 7 to SDP 8, then up to Coretura? Do you see them potentially skipping over eight? How do you think most of your customers would sort of evolve over time?
Yeah, I think definitely they're going to move from SDP 7. Every design win that we're talking about is SDP 8 at least. There are some companies that we expect to move straight to Alloy Kore. But the good news is every single one of our customers is moving to SDP 8. Really the discussion is on the upsell for Alloy Kore. We've secured, I think, SDP 8 across all the car companies that we're working with. That's the first thing that they look at. I should remind everybody, Alloy Kore has not even released product yet. It's actually going to be released in February of next year. But the platform approach resonates. SDP 8 resonates from a performance perspective, but the platform bringing more software, having the cooperation that we have with Vector, providing a pre-integrated platform, it resonates. It's not a hard argument to make with our customers.
The bigger picture in terms of software-defined vehicles, there's one stat that BlackBerry mentioned in the past, I think it's like 24 out of 25 top EV platforms. I think EVs were where most of the automakers were migrating over to new platforms. I think there was a little bit of headwind over ICE vehicles. But in terms of the migration to software-defined vehicles, what stage do you think we are in? Which automakers tend to be leading it, and are those automakers aligned or using QNX to do that?
Yeah. I think you're absolutely correct. I think that EVs were going to be the launch platform for new architectures for the simple reason they're lower volume. So, when car companies launch something new, they tend not to launch it on their volume vehicles because if it goes wrong, you don't want an F-150 problem since it's such a high-volume vehicle, or an Audi A4 or a Golf. So typically, they launch on lower volume platforms. So the EV struggles have caused, I think, a launch issue, which caused some delays. But the reality of it is, from an architecture perspective, software-defined vehicle, what they're putting in the car, it's immaterial, whether it's a hybrid, an ICE. So I think the industry has gelled around QNX as being kind of the gold standard solution that's being used within the vehicle pretty much around the world.
And for Tim, I'll bring you in here. When you break out QNX revenue, like last quarter, royalties did jump. So you have this big royalty backlog. Are you beginning to see that backlog convert? Is that really what last quarter proved out like?
Yeah. Like I was saying, we've got this great line of sight that a lot of software companies don't have into multiple years in the future. What we're seeing now is the impact of some of these really large design wins that we picked up two to three years ago now moving into production. So, there had been a period of time just over a year ago for the last four quarters, six quarters before that, where OEMs were really struggling to solve this software problem, which is part of the reason that Alloy Kore is resonating so well. It's largely getting through some of that now and moving into production. So yeah, we had a really strong quarter. In fact, we've had a very strong year for QNX so far, and we're guiding to a similarly strong quarter this quarter. So, momentum with this business right now.
But it is important just to remember it's not a quarterly business. So, there will be strong quarters, there'll be less strong quarters, but you need to focus on the sort of the longer term trend line that runs through the whole thing.
In terms of the variability between quarters, is that dependent on when automakers launch new platforms, new vehicles, and—
Yeah. So it's not only the launch of production, but it's also the decision point of when they're actually selecting and beginning the process to design the software. So, one of the things we sell, in addition to getting a royalty for every time a vehicle ships, we sell tools. Tools and services to help them get to that start of production. A lot of the revenue that's related to those tools, what we call development licenses, is taken in quarter. So if this quarter you've got Ford and BMW and Nissan are deciding to design on QNX, and that's going to take another couple of years before it hits production, we could sell a whole bunch of licenses this quarter and get a load of revenue. Next quarter, that revenue might not be there at that level. Doesn't mean that the business has suddenly downturned.
It just means that timing of selection is not even.
Just want to turn to robotaxis. Autonomous vehicles is obviously an extension. You have some autonomous features in current vehicles. How are the automakers looking? Obviously, there are very few robotaxis in existence right now. When they are deploying software, are they looking to use a single vendor, single operating system to run that entire stack? Is there multiple operating systems involved? How does that play?
Strictly speaking, operating systems, I would say QNX underpins those. Are we talking about production cars?
Yeah.
Yeah. Production cars, it is QNX by and large. Part of the reason for that is, again, our certification, our relationship with NVIDIA, the DRIVE OS, which is used for a lot of autonomous features in vehicles, uses QNX. What I have seen with the car makers, though, is I have seen them pull back from Level 3 to more of Level 2 and more of an assist function, and actually not pushing to the higher levels of autonomy. Now what we are seeing in the robotaxis is, when you think of Waymo and some of these other companies that have been providing us some service for the last year, really geo-fenced service, I think they are starting to see a business case, and they are looking at how they have deployed those vehicles. Typically, they have deployed them with very powerful hardware, a lot of redundancy, a lot of safety done through hardware.
Now those robotaxi companies are starting to look at, how do I make this more kind of automotive? Automotive hardware, automotive software, start to bring the price down, start to look at safety through software. We're seeing the traditional OEMs not really going beyond Level 2+ or Level 2++. BMW and Mercedes launched L3 systems a couple of years ago. Their next generation systems are L2+. The robotaxis, we're seeing them really start to look at, how can they bring the cost down of building these Level 4 systems in these geo-fenced areas? We're seeing more opportunity for QNX in those opportunities, more move to NVIDIA hardware, which is more purpose-built for automotive.
Dovetailing to that is, what you call in general embedded, I think the market calls it physical AI, but all these different end markets. How do you look at the value proposition for QNX in those industrial markets, and then the potential revenue opportunity? How does it differ from automotive? How is it similar?
I think from a value proposition that we can bring to those markets, it's very similar to automotive. It's a move to high-performance compute. It's a move to more automation. It's a move to more software-defined. Actually, some of those adjacent markets, such as industrial automation, robotics, and medical, actually require some things with QNX that we haven't talked about in automotive, which is, QNX is an RTOS, it's a real-time operating system. What that typically means, it means our product is very deterministic, and what that means is our product reacts predictably to events. When you're controlling robots, you're controlling conveyor belts, or you're controlling a robotic surgery, knowing when you tell that scalpel to stop cutting, it needs to stop cutting when you've given it that signal. We think there's a lot of possibility there.
We think that industry is changing, and we think it's changing actually quite rapidly, and a lot of it is around software-defined factories, software-defined warehouses, more automation, more robots. When I talk about robots, I'm not talking about humanoid robots, I'm talking automated forklifts, AMRs, skateboards that move product around, more need for safety around those systems.
How do you think about the pricing in those markets? Because obviously, the volumes at this point are lower than automotive. Is the pricing proportionally lower? How do you think about pricing? Because the value add is probably quite similar or even higher in those markets.
Yeah, with today, we have a model that is, our royalties are based on a curve, and it's a volume-based curve. So, as the volumes are smaller, the price is higher. That's something we're looking at as well, because we recognize in a lot of those industries, the volumes are not going to necessarily be automotive-sized volumes. So, we're looking at other models that might be enterprise models, other ways of creating a situation for more broad adoption within some of these companies. Everything's on the table. We do think it's going to be a sizable market, and that we're at the very early stages.
Also with pricing, I think it was last quarter that there's some contracts that are having minimums as well.
Yeah.
Could you speak through that?
Yeah. Ultimately, we're bringing a lot of value to this market with the products that we're bringing, and really responding to what the industry's asking for. As John mentioned, we got a curve. At the beginning of a project, we will agree a price based on projected volumes. In the past, if those volumes were not met, that's really on us, so we'd have to eat that difference. What we're saying now is if you want to commit to a price on that curve, you have to commit to that volume as well. This is something we're easing in. I think it reflects our position in the industry as a reliable supplier that's key in this ecosystem. What it means for us is obviously more certainty in our backlog, but also cash earlier.
We'd look for cash earlier, and potentially, if all the conditions are met, revenue recognition as well. For us, this is a really good business decision to secure our position and firm up our backlog.
I wanted to bring up AI in terms of its ability to help you be more productive in terms of your development. To what extent are you able to leverage AI tools, particularly in light of being in a safety-certified environment? Is that a challenge for using AI or not?
It absolutely is a challenge for using AI. We have been extremely thoughtful on how we use AI internally at QNX. We don't use it to develop code that goes into a customer's system. One of the things about safety is it does not contemplate AI generating that code, because you don't necessarily know how AI generated that code. The other thing that's very important, when you've seen some outages recently that have taken a long time to resolve, in a safety-critical situation, you need a human that understands the system, that can go in and debug that system and understand the code, understand how that code was written. Where we are using AI is we're using AI to generate test vectors that allow us to have more coverage of our products.
But again, we're doing it always with a human in the loop, because that's what the safety standards mandate. We're also using it to run a lot more code coverage to allow us to see where we might have race conditions in our product. We use it to identify things that we can look at more carefully, but we do not use it to generate any code for us. We're taking a very thoughtful approach. We've made sure that we train our engineers to understand responsible use of AI in the context of our products. It's something we take very, very seriously internally at QNX.
I want to touch on growth and profitability. One of the metrics that BlackBerry's achieved or hit is Rule of 40.
Yeah.
The growth has been one factor of it, but improved profitability has been the other factor. How do you think about profitability from here? I mean, you've made a lot of good gains to date. Where do you think of margins in terms of operating leverage? Not in terms of giving a target, but just where do you see the potential for further expansion versus how do you think about, well, do you put those dollars into driving faster growth?
Yeah, it's a great question. Clearly, the QNX business is already very profitable. As we were discussing, it's been growing at a very, very decent pace. Rule of 40, Rule of 50, in fact, last quarter. As I look forward in terms of thinking about this business, definitely, as John's been outlining, there's some really exciting growth opportunities here. What we've got in automotive has got a long way to run, and we'll continue to support that and develop the products that the industry needs. But the GEM side is going to need more investment. We are not the household name that we are in automotive in all of these other verticals, so we need to invest in there.
As I am thinking about it, I am more thinking almost like Rule of X as opposed to Rule of 40, which is that there is more value potentially in the long run if we can accelerate growth. We will be investing to back John and the business to seize these opportunities and grow the businesses as appropriate.
BlackBerry does have another business, Secure Communications, even though we spoke about QNX. What is the messaging around Secure Communications now?
Yeah, we are really pleased about the turnaround that we have had in that business. I think if you looked at it two or three years ago, it would look very different to where it is now. We have had four consecutive quarters of ARR growth, which provides a very solid foundation to that business. And within the portfolio, there are some assets which we think can grow a lot further, particularly the Secusmart asset. But we are realistic about it. At this point in time, its position in the portfolio is to generate a significant amount of profitability and cash flow, which at this point in time, we are funneling towards the QNX business to help support the growth there. But we are realistic about its growth profile. And we are a public company.
What we continually say is, if there were to be an offer for that side of the business, it is our duty to evaluate that with the board and decide if it makes sense from a shareholder value perspective. We remain open-minded, but right now, our focus is on making that the very best business that we can and driving as much value as we can whilst it is in the company.
I want to open up to the audience if anyone has any questions. All right, just another one. It relates to the Secure Communications business, data sovereignty, the push for sovereignty. Is that one of the biggest catalysts coming for that business over the next several years?
Yeah, so data sovereignty is definitely a catalyst. Up until very recently, everything was about cloud. Let's move off on-premise into the cloud. I think the geopolitical climate has made a number of governments, because this Secure Comms business is very focused on governments, to just think twice about that strategy and whether they really want to control the data within their own geographical borders. Because the BlackBerry Secure Comms solutions are tailor-made for that type of deployment, it's actually been a little bit of a tailwind for it. In the German market, for instance, our UEM product, we got certification called BSI. We're the only man standing there now with our product on-prem with that certification. So, it's opened up some interesting possibilities. Yeah, the market has kind of turned our way in recent months.
We'll see what that looks like in the future, but for now, we're definitely trying to lean into that as much as we can.
Okay. I think we'll wrap up there. I want to thank you both for joining me today.
Thank you very much.
Thanks.
It was our pleasure. Thank you.