Tag: device management

  • 1.65 Million Devices Enrolled – Techstrong TV

    1.65 Million Devices Enrolled – Techstrong TV

    Fleet is an open-source device management platform Mike founded alongside Zach Wasserman, co-creator of OSquery. The company recently raised a $5M seed round. In this interview, we’ll learn more about what Fleet does, how they got 1.65M devices enrolled in less than a year, and why they believe open source is the future. The video and a transcript of the conversation are below.

    Recorded Voice:     This is Digital Anarchist.

     

    Alan Shimel:            Hey everyone welcome to another segment here on Techstrong TV. I’ve got a first-time guest, new company, open-source project I want to introduce you to. Say hello to Michael McNeil. Michael is a founder of Fleet or FleetO for Osquery is some we know. Hey Mike welcome to Techstrong TV.

     

    Mike McNeil:          Hey Allan, thanks for having me.

     

    Alan Shimel:            My pleasure. So Mike I, I, you know I guess we should jump right into it. Before we even get into who is Mike McNeil, let’s talk about Fleet and, and I guess to talk about Fleet we probably need to start with Osquery and then you know that kind of gave rise to Fleet.

     

    Mike McNeil:          Yeah, for sure. So back in ’14 my cofounder, Zach, he and a guy named, Mike Arpaia and a small team at Facebook built this tool called “Osquery.” They were kind of trying to DIY their own security and they started realizing, “Hey it would be really great instead of running all these little scripts all the time, if we could have a standard way to talk to any computer, whether it’s a Mac, it’s Linux, Windows and it would be great if we could do it in SQL.” And that’s where Osquery came from. So it’s kind of a _____ [crosstalk] utility.

     

    Alan Shimel:            Yep, but I mean look we’re being modest, it’s had a fair amount of success, yes?

     

    Mike McNeil:          Yeah, it’s gotten pretty wide adoption at this stage.

     

    Alan Shimel:            I mean can you give us some numbers to just put it in context? Like how many downloads, users, what have you, whatever you want.

     

    Mike McNeil:          I’ve seen, so I’ve seen a wide number of stats on Osquery itself, but I can say it is used by a lot of the Fortune 100. It turns out the people that have this problem have a lot of computers, right, it’s a scale.

     

    Alan Shimel:            It’s a scaled – you know it’s a problem and it’s at scale.

     

                                     So now, all right so we’ve got Osquery, now let’s talk about Fleet.

     

    Mike McNeil:          So one of the problems with Osquery by itself is you have to go build a server to receive all the data from Osquery. So you can use Osquery to say, “Hey, Linux server” or “Hey, Windows laptop” or “Hey, Mac laptop,” “Hey code machine, tell me some information about you right now.” You can also schedule those queries, right, to run in the background on a certain cadence. But you got to have somewhere to collect that data and send it to where you want it to go. So Fleet is that, it’s an Osquery management server originally and lately it’s become a lot more than that.

     

    Alan Shimel:            Okay. Now we’re going to get into what that “lot more” in one second, but while we’re, while we’re doing foundational stuff, Mike, let’s talk about you. Give us a little bit of your background and how you got to be here.

     

    Mike McNeil:          Yeah, so let’s see a few years ago I started a open-source framework called “Sails.js,” kind of in the early days of no js back in 2012. Got mixed up in open-source that way. Published my first open-source modules. Then lo and behold in like 2013 Sails.js kind of took off. We started to build a community. Went through Y Combinator in 2015. That’s actually where I met Sid Sijbrandij from GitLab. That’s how – that was actually later on the same folks that ended up coming up with the idea of to build a company around Osquery. So, so we kind of got together and with Sid’s help and with and obviously with Zach’s help we build Fleet. We were able to take this kind of stem of a new open source idea. Apply the open-core business model and then run with it.

     

    Alan Shimel:            Excellent. So Sid’s a friend. I mean he’s been on our show many, many times over the years. You know he’s – well since they’ve gone public he’s gotten a little bit more busier I guess. I should mention he’s also an investor in Fleet, right?

     

    Mike McNeil:          That’s right.

     

    Alan Shimel:            Yep. Okay, so now let’s talk about you know what, what’s Fleet doing and I mean recently it’s, it’s doing more than it sort of original sort of scope if you will, right? We’ve, we’ve added to the mission. And, and Fleet is – excuse me, Sid isn’t the only investor, right? You’ve raised some more money at seed rounds, there’s all kinds of stuff going on. But you tell us Mike what’s happening.

     

    Mike McNeil:          Yeah. So we’re up to 22 people now. We just announced the seed rounds led by CRV. We have support from Mike Arpaia, so one of the other creators of Osquery, Nico Waisman, CSO at Lyft, and Jack Naglieri, the CEO of Panther Labs.

     

    Alan Shimel:            Very cool. What, what’s, what’s you know beyond the amount of money what’s the money being used for?

     

    Mike McNeil:          Yeah, yeah so when we started talking to users of Fleet early on and really trying to like understand what were the bigger problems, so what you’re trying to solve. We started to realize that there were these jobs that needed to be done, right, that kind of just were – they weren’t really satisfactory solutions for it yet out there. So a lot of people were using Fleet to kind of sniff out or like spyglass, right, to see like, “What’s going on on this machine right now?” Maybe it’s for incident response, maybe they’re just trying to kind of like diagnose a weird issue with a server. There’s all these different use cases where device data is useful. But one of the strongest is people needed peace of mind that their MDM is working, that their EDR tool’s working, and that the actual agents are – that they think are installed are actually there. So that’s been one of the biggest use cases we’ve seen driving Fleet so far in the adoption we’d seen last year.

     

    Alan Shimel:            Absolutely. What about the go-to-market though, Mike? Like talk to us. How, how you know I mean at some level open source you know once you have an open-source product project like this the go-to-market is, “Hey man give it a try and if you like it you know maybe you’ll want a commercial version or added features or whatever. But here’s our GitHub, you know repo, download it and you know ask the community if you a question.” But is that the deal with Fleet? Talk to us about that.

     

    Mike McNeil:          Yeah, so that’s how it all starts, right? And for a lot of users that’s going to be enough. You know we try to make sure that Fleet is enterprise ready. The free version is low. Like we don’t want anyone that needs to use the product to not be able to use the product there, but we are adding additional features and we’ve added some additional features last year around role-based access control that are, that are especially useful for a larger team to – or it makes sense for them to upgrade. That’s kind of been the, been the pay wall. The other thing is support, so if you need a little bit more support or an SLA that’s included with the paid subscription.

     

    Alan Shimel:            Got it. What about going forward are there other… So this sounds almost like a little bit of an open-core model, right, where you’re going to get an open version and then there will be you know premium features. What other premium features do you see perhaps coming down the pike here?

     

    Mike McNeil:          So a lot of options for that. What’s, what’s currently paid is the team’s feature. So if you want to have multiple, multiple different teams at your organization, like maybe you have one group that manages the laptops, the productivity end points, right, and you got another group managing your production servers, maybe you’ve got another group managing a few of the remaining core servers or maybe some laptops from an acquisition. That segmentation you can do in a Fleet Premium using the team’s feature.

     

                                     You can also do self-hosted auto updates. So if you want to use – you know a lot of folks are using Chef Ansible, something like that to deploy out the latest version of Osquery to all of their hosts. But if you are someone who would rather have that be taken care of automatically Fleet offers auto updates out-of-the-box, they come from fleetdm.com. If you want to host your own version of that and use the register yourself and kind of decide when the update happens that’s currently a paid feature of Fleet Premium as well.

     

    Alan Shimel:            Excellent, very cool stuff. Mike are there any metrics in terms of how many Fleet downloads users or anything? Like give us a sense of, of just how widespread this is now?

     

    Mike McNeil:          Yeah, so not everybody has usage analytics turned on. Obviously, you know some folks it makes sense not to do that, but between, between the data that we have and what we know about our customers, kind of a conservative estimate is 1.65 million devices enrolled.

     

    Alan Shimel:            Wow, that’s crazy, huh when you think about it from a yeah.

     

    Mike McNeil:          Yeah.

     

    Alan Shimel:            From just a project you guys started up. That’s great. You know we didn’t mention for people wanting information where, what’s the URL for the Fleet project?

     

    Mike McNeil:          Yeah, so it’s fleetdm.com and the D-M stands for “device management.”

     

    Alan Shimel:            So it’s fleet device management, fleetdm.com.

     

    Mike McNeil:          That’s right.

     

    Alan Shimel:            Excellent. And then you probably don’t know this, but what, for someone that wants the open-source version they get it from there as well or do they got to go to like a GitHub or some other repo?

     

    Mike McNeil:          Yeah, so there’s a, there’s a few ways to build Fleet. Look if you want to run it locally on your laptop that’s the easiest way to kind of see what it looks like and try it out real quick. We have an easy-to-use installer on the website, you can get going in like five minutes, you’ve just got to have Docker installed.

     

                                     And if you’re going to production we’re actually we just finished a Terraform in fig, so you can take that deploy straight to AWS quickly. We’re working on one for Google Cloud and Azure now.

     

    Alan Shimel:            Yep, that seems to be the trail. Hey man, Mike, I want to thank you for coming onto Techstrong TV and enlightening our audience about Fleet. You know what it’s an open-source world so these are the kinds of projects that may not be household names in everyone’s house, but 1.6 million devices will tell you otherwise, right? Keep up the great work and come back and visit us.

     

    Mike McNeil:          Thanks Alan, thanks for having me.

     

    Alan Shimel:            My pleasure. Mike McNeil here for Fleet, fleetdm.com if you want to check that out.

     

                                     We’ll be going to take a break and we’ll be right back.

     

    [End of Audio]

     

  • JFrog Acquires Upswift to Push DevOps to the Edge

    JFrog Acquires Upswift to Push DevOps to the Edge

    JFrog today revealed it has acquired Upswift as part of an effort to extend its DevOps reach to edge computing platforms. Terms of the acquisition were not disclosed.

    Upswift has created agent software that is deployed as a binary file on an edge computing platform that makes it possible to continuously deliver software across a fleet of edge computing devices and platforms. That approach makes it possible for organizations to deploy software regardless of whether the target platform is only running Linux, containers or a virtual machine.

    JFrog CEO Shlomi Ben Haim said the agent software developed by Upswift will be integrated with the continuous integration/continuous delivery (CI/CD) platform created by JFrog to make it easier for organizations to manage the full life cycle of application workloads deployed on edge computing platforms.

    JFrog Upswift

    Organizations that deploy software on edge computing platforms and devices today typically have massive backlogs of updates that they are unable to deploy in a timely manner, said Ben Haim. By connecting the Upswift agent software to a (CI/CD) platform designed from the ground up to support binaries, it becomes possible to reduce that backlog as part of what JFrog describes as its ‘liquid vision’ for deploying software, he noted.

    In addition, after acquiring Vdoo to gain access to a set of analytics tools that discover vulnerabilities in application binaries, JFrog will also be able to bring DevSecOps best practices to edge computing applications as well, noted Ben Haim.

    The number of application workloads being deployed on edge computing platforms is rising sharply as organizations seek to process and analyze data closer to the point where it is being created and consumed. In fact, that shift is at the core of digital business transformation initiatives that depend on edge computing platforms and devices running, for example, internet of things (IoT) applications to process data in near-real-time.

    Upswift CEO Amit Ezer said it has already become apparent that the existing processes of updating software on edge computing platforms and devices are capable of handling that influx of software. Upswift created its tool to enable developers to assume more control over those processes, as responsibility for managing and securing software continues to shift left, he added. The issue in many cases is that organizations lack the ability to consistently deploy software on edge computing platforms, which results in a hodgepodge of homegrown tools being created to deploy software on edge computing platforms using largely manual processes.

    It’s too early to say just how much software will be deployed on the edge, but there may come a day when there is more software at the edge than there is in the cloud. Of course, the real challenge will be unifying the management of DevOps processes, regardless of where any given piece of software might be deployed. In fact, as edge computing continues to evolve, the line between edge computing and cloud computing will continue to blur until they are little more than natural extensions of each other.

  • DevOps Chat: Managing Apple Devices with Fleetsmith

    DevOps Chat: Managing Apple Devices with Fleetsmith

    Managing Macs, iPhones, iPads and other Apple devices at scale is not something really native to iOS or OSX. Enter Fleetsmith. In sort of a Puppet-meets-Apple environment, the Fleetsmith team automates configuration, management and security of your Apple devices.

    In this DevOps Chat we sit down with Fleetsmith co-founder and CEO Zack Blum and company adviser, Puppet co-founder Luke Kanies, to discuss the mission and challenge in managing Apple devices.

    As usual, the streaming audio is immediately below, followed by the transcript of our conversation.

    Transcript

    Alan Shimel: Hey everyone. Alan Shimel devopsy.kinsta.cloud and we are here for another DevOps Chat. Excuse me. This episode of DevOps Chat features an old friend and a new friend. We have, first of all, cofounder and CEO of Fleetsmith, Zack Blum, who is the new friend. Zack, welcome.

    Zack Blum:  Thanks, so much. Great to be here.

    Shimel: Okay. And then joining Zack is our old friend, Luke Kanies. And Luke really needs no introduction to our audience. Luke is the founder of Puppet.

    Luke Kanies: Famous on the internet.

    Shimel: Famous on the internet, but still puts a token in when he jumps on the subway. But anyway, Luke, welcome.

    Kanies: Thank you very much for having me.

    Shimel: So let’s get this out of the way right away. Luke, what’s your connection to Fleetsmith?

    Kanies: I have been trying to help Zack and his cofounders, trying to tell all the stories of all the ridiculous mistakes that I made in hopes that they make only new mistakes.

    Shimel: Wouldn’t that be a great thing? Man.

    Kanies: We can dream, right? We can dream.

    Shimel: Yeah. I was just going to say, if you can bottle that, man, you really would be famous. So Zack, before we even jump into Fleetsmith, then let – you know, Luke has told us what the connection is. Always interested to hear. How did you hook up with Luke and come about to – I’m going to assume you asked him to an advisor here.

    Blum:  Yeah. Well, it’s funny actually. Even before that, the interesting thing is Puppet itself was the inspiration for us starting Fleetsmith. So the connection goes really far back. I was the IT director at a company called wikia and we had this problem where we needed to manage our device fleet.  So I asked around my peers at IT and security and talked to a guy at Dropbox and asked how they did it internally. And it turns out that they use a bunch of open source tools traditionally used by DevOps pros actually to manage their laptops.

    So I went out and learned all about Puppet and realized, “Oh, my goodness. There is an amazing application opportunity here on the endpoint side.” So long story short, that guy at Dropbox, Jesse Endahl, became our cofounder and CSO; had a product. And Luke and Puppet were a major inspiration. So pretty cool.

    Shimel: Very cool. Very cool. So let’s address Fleetsmith, right? What is it you guys do?

    Blum:  Yeah. Thanks so much for asking. We do a few things. We are a modern Apple device management product. So we help companies manage their corporate Macs, iPhones, iPads, and Apple TVs. And we really try to accomplish four things for our customers. Number one is making on boarding new hires as seamless as possible. So employees ramp right away. We do that by automating new device set up. So straight out of the box, to have a computer set themselves up.

    The second one is we provide fleetwide device intelligence so that IT can see problems before employees get interrupted. We do that with really core reporting on exactly what’s going on out there. The third one is we provide employees with uniform, up-to-date computing environment. We do that through automating OS and third-party app packaging, patching, and the delivery of those as well as config for Wi-Fi printers and other tools.

    And the fourth one, the last one, is we decrease business risk for customers by allowing them to enforce, in an automated way, security best practice so features like disk encryption with automatic key escrow, remote lock and wipe. And so those are the four things we do; really try to help companies of any size, especially small and medium businesses, take those best practices and apply them in an automated way without huge teams and huge _____.

    Shimel: Excellent, man. You know, as crazy as it sounds, I almost feel like you serve an underserved business segment for first trillion dollar company ever, right?

    Blum:  Well, we think you’re right. Yeah unfortunately, too many of the companies that we come across have nothing in place at all; no visibility, no automation around this. Then there are a lot of companies who have something in place and it’s just incredibly tedious to administer. There are so many higher value things that IT and security can focus on than manual packaging of software updates.

    You know, providing great customer service to their employees, helping them do better work. So we are really excited.

    Shimel: You know, but this has always been a – I go back in my years in security. We – the company I helped found, kind of one of the pioneers in what we call the NAC market, the network access control. So it was a little different. As you would log onto a network, we would check your endpoint, whatever that might be, and make sure it conforms to whatever the policy that was set. And part of those policies were; were you up-to-date on your patches and your AVs and all that good stuff.

    Blum:  Right.

    Shimel: And even then – and by the way, this was for three letter agencies and U.S. Department of Defense networks. Even then, checking Macs was like a black hole. Right?

    Kanies: It’s always been that way.

    Shimel: I’m sorry, what?

    Kanies: It’s always been that way, for various reasons. And one of them is that they just haven’t been used as much. The second is that Macs have always been kind of cut out of IT policy. Either the Windows – the IT has always been run by Windows and they either say, no, you can’t have them, or, yes, you can have them, but don’t ever talk to us about them. So they’ve kind of always been out.

    In the last 10, 15 years, Apple has really done a great job of building a device that is better for actual usage. So it started out very much in the consumerization of IT, which is how PCs got started in the ’80s, course, as people bring their own computers in. What then they started bringing their own Macs in. Now you look at, especially small companies, and they’ve gone from, “I’ve got a couple of Macs for my designers.” To, “Everyone have a Mac and I’ve got a couple of PCs because my accounting people have to use the Windows version of Excel for whatever reason.

    Shimel: You know what? That’s exactly it. And it’s interesting that we get this kind of folks coming in. And one of my colleagues just joined here. I apologize. So when Macs were 2 percent of the market, maybe no one cared. But as we were talking off mic earlier, when you started getting to 20 percent or more of the market or thereabouts, that’s a number, right? That’s a sizable amount to worry about.

    But how much are the – and I will throw it both at Luke and Zack. How much are the guys – and due to Apple’s professed policy of not wanting to be in the enterprise or not wanting to be in that business market of being a consumer brand? Right? And as a result, you know, if it walks like a duck, it quacks like a duck, but it’s really not a duck. Right how much of that is to blame here for our, up to this point, neglect of managing Macs in the workplace?

    Blum:  You want to start on that Luke?

    Kanies: Sure. Honestly, I don’t think much is, for at least two reasons.  No. 1 is that it wouldn’t have mattered if Apple had decided they really wanted to be enterprise. They would have failed. We know that because of taking multiple cracks at trying to do enterprise stuff and all of them fail. If they are lucky, they deflate quietly and just get brushed into a corner. If they’re unlucky, they fail relatively spectacularly.

    So Apple has, in the past, fought against its own DNA and lost because that’s how it works, right?  And when you look at Microsoft today and they are resurgent. And one of the ways they are resurgent is that they are doing a better job of being who they are rather than trying to be who they are not.

    I think the second reason is that Windows was incredibly dominant for so long. The way in which Windows succeeded was very business oriented, very – and yes it was kind of user oriented at first, but that was long time ago. You know, when I came up and went to college in the 90s, my – first cut my teeth, I was a Solaris user. I was – back before there was Linux. So even then you wouldn’t choose between Windows and Mac and a corporate environment. You would choose between Windows and Solaris in a corporate environment.

    Shimel: Right.

    Kanies: And again, you had a couple of designers in the corner and they had Macs what they did was really specialized. But I don’t really think it had anything to do with Apple. If anything, Apple was struggling to hold on at all. It was less that they weren’t an enterprise company and more that, “Wow. We found like two people who can’t live without our product that we going to make sure we do everything you can to make them as happy as possible and we’re not going to worry about anybody else. ”

    And it was only when, kind of the world changed a lot, partially because Jobs came back. But partially because the world changed a lot, right? The internet came out. And the reason why you wanted a computer shifted from, “Because I need one for work,” to, “Because I need one at home.” Right? And if the iMac had been 10 years earlier, they wouldn’t have sold any because, why would you have a computer at your house in 1990. There was no – there is not nearly so much reason. But when you can dial-in, when you’ve got Internet, that really changed the world.

    Then the trends, the drivers of computing shifted from entirely business use cases to at least 50/50 personal, business use cases. And one can argue today that the majority of drivers of how people think about their relation to computing is mostly driven by consumer use cases and that pushes to the enterprise. And we’ve seen this consumerization of IT trend going back decades. It’s more of a treadmill or an escalator than it is a one-time blip. But to me, this really explains why it matters now and it didn’t matter before, because that consumer use case driving so much of the story.

    Shimel: Yeah. I mean, so Luke, I’m a little older than you, right? Solaris is … My first company, we ran you know, SPARC servers, UltraSPARC, actually. But –

    Kanies: They may be slow, but they sure are expensive.

    Shimel: Don’t even go there, man. But on top of that, I was an OS2 dude.  I loved OS. I was running OS2 really early on. I still don’t understand why Windows is here and not OS2. But that’s another story.

    Kanies: But you know, one of the things that I think has really enabled this is they used to be such a gulf, such a, frankly, a pain in the butt to move. If your colleague was on Mac and you are on Windows, you just had to give him a word file to use or spreadsheet or anything, for that matter. You know, reformatting discs and doing all that nonsense. Beyond the internet, interoperability between has really, I think forced it.  But that’s – you know, that, it speaks for itself, right? A lot of us are using Macs today. I’m on a Mac right now.

    Zack, one of the – and we shouldn’t just focus on Macs. We should focus on what the iPhones and the iPads and Apple TV and it’s is ubiquitous, man. Nothing drives security people battier then having sort of unknown devices or unmanaged devices or black holes in their network.

    Blum:  Absolutely.

    Shimel: And so I would imagine that’s the allure, if you will, of giving Fleetsmith a whirl.

    Blum:  Yeah, absolutely. And especially with the move to the internet of things. Even with computing devices like iOS and iPad, you had iPads, for example, in nontraditional computer roles like a front desk check in machine or the conference room calendar. Then you have, often, three devices comprising a conference room videoconference set up, right?

    So these aren’t as much for individual employees anymore. These are sort of use case driven, almost appliance type applications. So not only do you have these unassigned, if you will, devices floating out there, they’re just on the internet. The corporate network as far as computer management and security of devices is dead, we need to secure the endpoints wherever they are and provide visibility.

    So that’s one of the great things about a product like Fleetsmith is that we provide that things to security folks whatever network the devices on and whatever its application is. And I wanted to add one thing to what – continue Luke’s first point from before.

    Apple absolutely has been a consumer company and now that there is such a high enterprise market share, they’ve actually stepped up and are building a lot of really great management APIs, kind of recognizing that third-party providers of MDM like us are then able to run with that where that is in our DNA. We are experienced IT and security folks. So they are doing some really exciting stuff that’s enabling further penetration into the enterprise stream.

    Shimel: Absolutely. One other just question. This is something that’s kind of – it’s close to where I’ve come from in some ways. If I’m the IT guy or the security guy, I absolutely abhor having multiple management interface systems that I’ve got to work with. So I’ve got this to manage my Mac stuff and iOS. I got this to manage my Windows stuff. I got this to manage my Linux. I got my cloud management stuff.

    How – does Fleetsmith integrate with any of, sort of the larger Windows or other kinds of device management products out there?

    Blum:  Alan, you’re talking about the fabled, single pane of glass. I think that’s what I’m hearing.

    Shimel: Yeah. Well, the mythical single plane of glass, but okay.

    Blum:  That’s right. Well, you said it. To answer your question directly, we do integrate with G-Suite and Office365 so that when people adopt Fleetsmith they don’t have a ton of manual data entry for their inventory. But aside from that, as far as devices go, there’s kind of the suite – device management, there is the suite approach and the best-of-breed approach.

    Unless you have incredibly, incredibly simple needs, usually the suite approach, you know, these companies that build management for every single OS, really fall short in all but one. They really started as a signal platform and just tacked on a couple of checkboxes. So unfortunately, in today’s world the reality is that if you need zero touch deployment, you need to automate the setup of the devices and you need FileVault disk encryption with automated _____ _____ _____. You need to make sure everything is encrypted. You really need the best-of-breed solution.

    So we do all of Apple and there is some products that do all of Windows, a lot out of Microsoft. And past a certain point, those are pretty much just a requirement today.

    Kanies: I would go a little further and say I would add a different dimension that’s less platform because Puppet, for example, is promiscuously cross-platform, but almost entirely server-side. So you can use, as Zack found in the early days, you can use Puppet to manage your desktops. But what you will find is just a constant low-level of friction in doing so because so much of our workflow, so much of the experience is built around servers.

    You might say, “Why is it hard to – if you are servicing more complicated than desktops why is it hard to manage them?” The answer is, desktops are off all the time, laptops are off all the time, they check in from different networks all the time. You don’t get to decide when is a good time for the user to reboot their computer. The user really has to decide.

    You’ve got to build a completely different experience around the product. It’s something that could be done, but there was a lot of friction. So I would say that I agree with that point, that you got to pick best-of-breed. And part of that dimension is what platform you’re talking about managing. Certainly a Windows solution… A solution for Windows being used to manage your Macs is not a great idea. But also, I think a solution for servers, a solution for back in, is not a great solution to manage desktops and laptops.

    That’s really where you do need a different solution. And not that it’s impossible that you could have a company doing both, but it’s unlikely and it certainly hasn’t happened yet.

    Shimel: Got it. Got it. Got it. Guys, we are right on the top of the hour. Unfortunately, I need to end it right here. But before we do, Zack, really quickly, people can get more information about Fleetsmith at…?

    Blum:  Yeah, just go to Fleetsmith.com.

    Shimel: Okay. And you know what? Maybe we could follow up in a couple of weeks before the end of the year because I do think the whole issue of Mac management as well as non-computer – or nontraditional PC devices, whether they be iPads or some sort of IoT and whether they’re running, frankly iOS or some other non-windows, non-Linux – well, maybe Linux. The idea of keeping them compliant, with whether it be a security policy, access policies, what have you, is a really big problem a lot of companies try to tackle, but they tend to stay in the low hanging fruit way rather than maybe some of the corner cases, as bad as a corner case as it may be, you know, it’s still not the mainstream like that.

    Blum:  Yeah. Absolutely. I could talk about that all day. I would love to.

    Shimel: All right. We will schedule something. Hey Luke, I’m sorry we didn’t have enough time to really dig into what else you got going on. But maybe we can do a follow up at some point on that as well.

    Kanies: That would be great. I will warn you that most of what I’m doing next is pointedly not very DevOps. I took 20 years in one industry. It has been enough.

    Shimel: Thank you.

    Kanies: So there is a lot that I’m working on but it’s taking the lessons of the last 20 years and trying to use some of the same tools in different places with different people.

    Shimel: That’s not a bad thing either, my friend. As you said earlier, it’s life.

    Kanies: Yeah.

    Shimel: Good luck with it though, and we will be in touch. Guys, thanks for being our guests on this episode of DevOps Chat. Fleetsmith.com, that’s; F-L-E-E-T-S-M-I-T-H.com. If you’re looking to manage and secure your Macs or iOS devices, worth checking out.

    This is Alan Shimel for devopsy.kinsta.cloud. Until next time, everyone, have a great day. Bye-bye.

    Kanies: Thanks so much, Alan.

    Blum:  Thanks.

    — Alan Shimel