 Well, hello everybody. This is Anthony Ambrose, President and CEO of Datio Corporation, coming to you live and worldwide here in Nuremberg at Embedded World, where we're showing you how to make IoT simpler, easier, and allow you to design those great new products you've been talking about for the last three years. So what is this big machine we see here? This machine here, it looks big, but this is actually one of the smaller of our two handlers, is our PSV5000, and you'll notice it's equipped with our centric's capability to allow for secure provisioning of IoT devices. What that means for customers is now we have a production solution available to them in their own factory, or with our provisioning partners such as Avnet and Aero and Elsill, so that they can take their IoT designs that I'm looking for to secure with a strong hardware-based root of trust. That means you can't mess with it in layman terms, okay? And they can get it done and they have a factory solution so they can actually deploy those hardware-based roots of trust easily, cost-effectively using Datio technology. So every single chip gets to get unique security? It can. Pressed onto it. Right, you're a unique individual, right? Yeah. So why shouldn't every chip have a unique individual identity? People have unique individual identities, right? We can do that now with centric's using the PKI technology. The semiconductor companies enable that with the features they have in their chips. But what we do is we're the how. How does it get done in manufacturing? How can you design the system here in Germany and go to production in Mexico or Korea or Morocco, okay? And be assured that your device is secure. So maybe you don't want to do it at the chip fab. You want to do it more closely to where you are? Well, what you want to be able to do is make sure you have control. Now semiconductor companies can do security provisioning for you as well. They tend to do it in big batches with long lead time. And that works great for some customers. For a lot of customers that demand changes or their firmware updates are very regular, they really can't go with a 10 or 12-week lead time because everything changes. So a data I.O., you can change your firmware this morning. I can load it in this machine and I can provision your part instantaneously with your new job. What goes into provisioning a chip? So provisioning is a number of different things. So for example, people think of identity. What that means is key information can be stored in a secure location. So for example, if I have an identity, and when I say PKI, I mean the same technology used when you do secure transactions on the web, when you see a little lock on your browser, that's fundamentally the same technology we're talking about. And what it establishes is a way for us to give a unique identity to each chip that passes through the machine. It has a private key which is stored on the black box known as the HSM here. And then you also have a corresponding public key which can be used for things like management later on. So you take that public key and move it to the cloud, for example, you can later on associate devices with that information and then manage them effectively. By manage, I mean turn them on, associate them with a user, do a firmware update, retire them, etc. So when I think of a chip, it seems there's a lot of small, tiny little transistors inside. So the connector is somewhere, where in that product do you get in? So if you look closely, go ahead and zoom in on the machine here, and you zoom in on this tray. Okay? So you can see we're picking up parts right from the tray. So each of those parts has leads, so think of it like my fingers almost on my hand. So those leads on the parts will go into sockets, which are in the programmers there, and so we'll literally connect electrically with each of the leads to our programming engine. Okay? That's the benefit of programming the data IO way because we have access to every pin on the silicon. Okay? If you wait to the end of the line, you don't have access to every pin on the silicon, you must go through a special connector on the board, and that can be slow, can be insecure, and it can be very late in the game. Okay? So we have access to every pin, and we go and add the secure element. We can go to the secure region of the chip because we have access to every pin, and we work with the semiconductor companies to understand how we should talk to, how we should write, and how we should ultimately secure and prevent any future writing on all those regions of the device. This tray can have a lot of chips. Yes. And this is just one of the small devices you have, you say? This is our standard machine. We have one that's a little bit bigger called the PSV7000, has two heads and runs about twice as fast. And who are your customers? Who use these? So our customers today are who's who in the automotive industry. So 18 of the top 20 tier ones. When we say a tier one, we refer to somebody like a Bosch or Continental here in Europe, and we're the premier provider of programming for the automotive industry. But 60% of our business is automotive. The other one's leading industrial companies and programming centers and also emerging IOT companies that need security provisioning that we just talked about. So automotive, like as I understand 10 years ago, they didn't really understand, I won't say understand, but they didn't really implement security in the way that people should and that they are now totally thinking about. I think everybody 10 years ago didn't think about security the way they do now. It's completely evolved for a couple of reasons. People understand the threat more. They've seen it firsthand. Everybody has seen the hacks that have gone on on enterprise systems, consumer products, things like that, and nobody wants to be hacked. That's number one. People understand the problem. Number two, government regulation is really starting to take hold. The governments are saying, wait a minute. It's not only not nice for you to have insecure products. It's illegal and we're going to find you and not only find your company, but find the officers of the company personally if you do a lousy job securing your product. So now that's sort of the motivation kick in the pants, if you will, for people to get going on their secure designs. So now that they're asking the question, what am I supposed to do? They come to data IOT and we say, don't worry. We've got you covered. If you want to pass the safety check for your car, they should check if it's secure. That maybe that's too much, but that somebody can just hack your car and drive you off the highway or something. Yeah. I think that might be an extreme example. I think what we're really talking about in cars is saying, look, cars are fundamentally secure. It costs a lot for cars. They can spend the money on security. What we're talking about also is now less expensive devices also needing security. But with cars, again, we support all the major brands. We think they're doing a reasonable job on security and we see even more and more things coming down the road to simplify that using products like Centrax. And here they're in a better world. There's tens of billions of microcontrollers being shipped around the world. Yeah, about 30 billion every year. How many of them are secure enough and how many of them can you target to add the layers? Well, we can program today pretty much all the 30 billion on the data side. And more and more of them have unique security features. What needs to happen is those security features must be exposed. They must be understood. They must be made easy. You see the theme of our both simplifying IoT security. It's not enough to say you're secure. You have to make it simple, easy, straightforward to implement. And remember, if you're building 30 billion devices a year, this can't be a manual process. It can't be something where someone has to hand hold the process. It has to be something where it's easy to understand. And the way we do it at data.io, by the time you create your Centrax job and your package and your security, when you run it in manufacturing, it's just as easy for the operators to run a security job as it is a data job. And that's very important because look where the new factories are going, right? They're not hiring PhDs to operate equipment on the night shift. And so it must be really, really easy to operate and that's where data.io excels. You automate it. Yes. The machine just works. The machine just works. Do you program it in the beginning and it does thousands of chips? Yes. Our customers we estimate do between one and a half and two billion chips a year of program. So obviously something of that magnitude must be automated, repeatable and executable. Let's say there's a government agency of some kind or a big cooperation that has a lot of devices. Do they want to get this device to control their own security or is it some of the else that it takes? In the factories that are building their products because at the end of the day we provide the security provisioning but also we put firmware into chips as they're being built and the products are being manufactured. So we're not securing buildings or we're not securing their enterprise. What we're doing is making sure that their products, their meters, okay, the intelligent door alarms, the things that monitor equipment in the factory, fleet management units. Everything you can imagine that's connected that needs to be secured, that's what we do. We work on their products. There's a lot of talk of managing cyber security in different continents and that sometimes a chip is made in another continent but the continent in question, let's say Europe or something wants to manage the security themselves so maybe they get... You just highlighted a perfect example for centrists. So for example today, let's say you're designing over there in that next booth and you create all your intellectual property there and you put it on the chip. You can create it so you can do all of that work to create the security job and the security definition here and spread it out to factories all over the world including some locations that people might think are less secure. Now, data IO has been doing that for over 20 years, helping people take intellectual property design here and putting it out to their factories worldwide. So Centrix is just something that's a little bit better, a little bit more secure than what we've been doing for decades. So you also help with the security of the IP being not captured by some competitor or something like that? Absolutely, because if you protect your IP, when you do your job and you run it on Centrix, what happens is your IP is married with the algorithm and the technology around the programmer and that is encrypted and wrapped so that that whole package is sent in a secure way to wherever the product is being manufactured. That's a big deal. Has everybody understood this? Everybody's, you say it's already one or two billion chips per year but it's still 28 billion that are not using your technology? That's a really good question. People are becoming much more knowledgeable about why they need to do security now. A couple years ago it was more theoretical and remember we're just coming out of COVID, we're coming out of supply chain. People had a lot of things on their mind, okay? What we're seeing here at Embedded World now is people are coming up for air after three years and saying, I need to do new things. I need to create new things, new products, new designs and those new designs will have security and they're coming to us saying, I have a great idea for a new product, data IO, how do I deliver it in manufacturing and that's where we come in. That's one question I like asking but I'm not sure if it's, nobody's told me it's possible. Is it possible to have 100% security? No. For sure not. Even when you have very good encryption on one side, the other side, why can't you have it? So, products are designed by human beings. Human beings are imperfect therefore we can never have 100% security, QED. So that's not happening but you want to get as close to 100% as possible. You want to get the best possible security consistent with the product you're building and the risk you're managing. So for example, if I'm trying to protect a light bulb that's connected, I really don't need to spend a lot of money on that. If I'm protecting an armament or an airplane, that's a whole different story, okay? I'm going to spend a lot more money to get that much higher level of security. Now, we can have extraordinary levels of security but you ask me about 100%, there's no guarantee for 100% of anything. But it's possible to get orders of magnitude closer to 100%. Yes, that's a much better way of putting it. Get to 99.9. How many 9s do you want? You never get to 100, it's always 5, 9, 6, 9, 7, 9s for example. Here at the embedded world, some of the chips are less than a dollar and they're very affordable chips. How much does it cost to add this process to each chip? The way to look at it is not how much does it cost to add security to each chip. What is the risk you're mitigating on your product level? If you have a 99 cent chip and it's going into a $10 part, you're protecting a $10 part. But you're also protecting your brand image. You might be a billion dollar company. If your $10 part sucks, you have a potential to lose a lot more on your brand equity. If it's insecure and it gets hacked, that's a big deal. So you're protecting also your intellectual property. If your $10 product is also from a family of products that uses a common software architecture, then you really have to protect that as well. So your question is a fair question, but it's not the right question. Because you're protecting a lot more than a 99 cent chip. You're protecting the product. You're protecting your software stack and intellectual property. You're protecting your corporate brand image. If people buy one of your machines and then they just do millions of chips with one machine, then each chip is for free after that? Are there materials that are involved with every single... No, this is a high-volume manufacturing machine, so it's designed to be low-cost of operation from the start. But obviously if you run more parts, you have more electricity, you have more consumables. It's never a zero cost for the next chip. Once you design the job and the package, it's very, very cost-effective to program the parts in high volume. What do you show here on the presentation? There's a slide going around. It keeps looping, maybe stand right there. And it's just your... So this is a centric presentation. It's just something we have here in the booth. And what we're talking about, why you need security. Okay? And it's something that is happening for OEMs, for consumers, for enterprises as well. I think everyone has unique needs and differences here. Okay? All right. And on that screen is just a loop of your other machines that you have going on. Maybe the bigger ones and stuff are being shown on this screen. Yeah, this is just an example, a close-up, if you will, of some of the features on the machine. It's looking at our taper. We're talking now about security provisioning, for example. And again, here's the machine. You're seeing it right here, live. All right. Cool. So it's been a good embedded world. Lots of discussions. It's been outstanding. Great traffic, great leads, and the right questions coming from customers. All right. Thanks a lot. Thank you. And have a great day. Ciao from...