For today's final session, I would like to introduce Chief Artificial Intelligence Officer Ron Keesing to the stage.
All right, well sadly I have to admit I am in fact real. But I'm very excited to lead today's technology panel for the Supplier Symposium. I'm really incredibly happy to have this extraordinary panel we get to talk to today. First off, from CEO of Sourcegraph, Quinn Slack. Come on up, Quinn. Second of all, another great CEO from one of our partners, Bavin Shaw from Moveworks. All right, next up, our next great panelist, Tom Srom from AWS. Tom is the Enterprise Strategist for AWS and a deep expert in all things AI. I'm really excited to hear from him today. And finally, our last panelist from our Dig Mod sector, our CTO Eric Moore. All right, so really excited to talk to all of you today. For those who heard from Tom Bell this morning, you know you heard him talk about the importance of partnerships. One of the striking things, you know we're here at something we call the Supplier Symposium, and yet again and again we've heard this word 'partner' today far more than we've heard 'supplier'. For us, the importance of partners moving forward is huge. So I'd really like to talk with each of you about how we're going deeper in terms of technology partnership and developing differentiated solutions we can bring to our partners together. So my first question today is for Quinn and Bavin. Both of you lead companies that have developed great new partnerships with Leidos. I'd like you to tell us a little bit about Sourcegraph and Moveworks, and then also tell us about how you're working with Leidos to develop these deep technology partnerships and differentiated solutions. So Quinn, why don't you get us started?
So Sourcegraph solves this problem when an organization has so much code, old code, code that nobody understands, and yet they still need to be making new things. How do you deal with that complexity? We started out by building code search, like a Google for all of the code in an organization. We've gotten many of the biggest banks in the US, the biggest technology companies, and now through Leidos, some incredible missions in government and beyond. And on top of that code search foundation, with the advent of the new large language models, naturally we were experimenting and we found several years ago that if you feed code to an LLM and you ask it to fix this or help me understand why was this done 20 years ago this way, or all of these other hard things in software engineering, well, AI is actually incredibly good at that. And what's interesting too is it's very good at the parts of the job that software developers like the least and that are the most tedious. So it was that insight that led us to build Cody, our code AI product. And when we were building it more than a year ago, we heard from Leidos and we heard the incredible potential they saw in the government to modernize software, to accelerate software development, to make it more efficient, to increase quality. And at the time we thought, well, AI used by software engineers, it's still early, we don't know if these organizations are actually ready for it. But we saw such incredible insight and vision from Leidos, and they were the very first partner that we chose to work with to bring Cody to more organizations. So we've been thrilled by the partnership so far, and it's also very early, so we are excited to keep working with Leidos.
Awesome. So Moveworks, for those who don't know, is a generative AI co-pilot that employees use to search and take actions across all business systems. So think about IT support, HR questions, generalized search and automations, all being leveraged and used through the natural language interface that an LLM can provide. And we have about 5 million end users on the platform today, across mostly the private sector. And that was actually what brought us to partner with Leidos. They are, of course, the largest government IT provider, and we really wanted to bring this technology into the public sector, but didn't know the best practices and the best way to do that. So whether it was helping us along the FedRAMP journey, which Leidos has been doing, or it's working with them on creating specific instantiations of our platform for the IC community and the defense community, these collaborations have really helped us along this journey.
Great, thanks. Well, Tom, AWS needs no introduction to this audience, but I do want to share, you know, AWS has been a partner of Leidos and a deep technology partner for a long time. I mean, I go back to our groundbreaking work developing our Edge to Cloud solution, where we were kind of the first to bring the capability to use your Snowball and Snowcone technology to drive tactical data down out to the edge. So can you tell us a little more about how AWS and Leidos work closely together as technology partners?
Sure. And I think the more accurate question is how do we work together as partners, because it isn't just about technology anymore. When cloud came out, it was all about technology. With generative AI, it's much more so. We work together now. I think you can summarize it in six words: we think big together. So we now have a strategic collaboration agreement, so we come up with lots of crazy ideas. Then we start small, lots of ideas, white papers, proof of concepts, trying it out, and then we scale fast. And I think it's really about scale. AWS has the infrastructure, Leidos has the customer intelligence and relationships and knows the infrastructure. So part of the thinking big is co-investing here. We have 500 Leidos people who have been certified, so now you know that they can do the work, the customer knows they can do the work. So I think this is really key. Leidos has done many first things for AWS and for themselves, like using generative AI with SageMaker, first ones to migrate mainframes for HHS to approve a concept to migrate and then win the whole thing to migrate. So I think it's more and more thinking big, what can we do together? And for me, it's been an 11-year journey for AWS, it's been a 20-year journey for me because I was a Chief Technology Innovation Officer at NASA's Jet Propulsion Laboratory, and Leidos was a key partner there too. So I came to AWS to give back to the public sector, and I'm so thrilled that Leidos is doing so many good things.
Great, thanks. Well, Eric, can you share a little more about your perspective from the Dig Mod sector and Leidos more broadly about why external technology partnerships are so important to us?
Yeah, so let me start by just thanking the three of you on behalf of all the Leidos folks that are here for the partnership that you've engaged in with us. It's been really tremendously rewarding to work with each of your companies on the various initiatives you guys just talked about. So thank you. I had a bunch of really great notes that I took that I was going to talk about, the importance to the country, and then Tom and General Mattis got up here this morning and I thought, I can't possibly in any way be more convincing and eloquent than the two of them. But I do think I'll just maybe foot stomp a couple of things that they highlighted that I think are critical. They talked about the need to have speed to innovation, and it's absolutely critical. And Tom, you just mentioned scale. I think Leidos is uniquely positioned as a company at being big enough to be able to scale solutions, right, but agile enough to be able to be the bridge for our customers between commercial technology providers and the missions that our customers serve. And given the threats that we as a nation and a set of partner nations face, I think that is why it is so critical that we continue to exercise these partnerships, because the uniqueness that Leidos has in our market is to be that conduit to bring your commercial innovations like you all are driving into the market. So that's what I'll say.
All right, great. Well, you know, this next question is really for our partners. You know, these kinds of partnerships we're talking about really require a lot of trust, a lot of communication, a lot of deep collaboration. So as you look to potential partners, what do you look for in a partner? What has kind of made Leidos a partner of choice for you moving forward? Maybe Tom, you can get us started here.
Sure. I think it's, and I'm thrilled to see you guys by the way, these new things, new ideas starting to scale. So I think what you look for, what we look for in a partner, is that vision. Think big, what is the vision of what can we do together? And then come up with a story, why does this partnership matter? We all have to justify to somebody, so why do we partner with Leidos? Where we have a shared vision, we work together, we meet quarterly, monthly, daily on things. So we look for that in a partner: shared vision, co-investments, and being able to execute fast. But more than anything, trust. And how do you build trust over time? By doing things together. So it's that action that's what we really look forward to in a partner, and Leidos has been great.
Yeah, so look, I think we have 350 large enterprises on the platform, and Leidos is one of them. So from our perspective, your bias towards action has been really attractive for us to partner with you all. I mean, just after the keynote, I sat down with Tom and talked about new features that we're rolling out, right? And to be able to be a customer of ours, to have the insight into where we're strong, where we need to improve, really gives this partnership a different lens and a different sort of affordance when going out to the public sector. And I think that was sort of key for us in terms of figuring out who could do the job. Not only that, you guys have been instrumental in working with us on thinking about what is required to be successful, what are the components, and also training your team to work with us. So I think the combination, but also I think first and foremost, you being a customer, living what we do and understanding what we do, makes you an authentic seller when it comes to going to the public sector and saying, look, you should try this, you should use this, because you cannot just speak to a sheet of benefits, you can actually talk about your own use case.
Quinn, anything you'd like to add?
Yeah, for us, we love the inspiration from Leidos, the feedback, and the co-development. On inspiration, it's hard to come up with a set of missions that are more inspirational than the kind of stuff that we get to work with Leidos on. On the feedback, just as Bavin said, we love customer feedback, we love all customer feedback, but there's a special kind of feedback that comes from a customer who is also thinking not only how do they use the product, but how can they get a lot of other people to use it. And that kind of feedback is critical for us. In particular, one of the things that Leidos has brought, made really clear, is how can we focus on how Sourcegraph helps developers do the parts of their job that they least like to do and that they are worst at, and how can we message that to the audience there. And then finally, on the co-development, there are things that Leidos knows about the government that are years ahead of what we would have figured out. For example, the need to run an AI software development assistant in a fully air-gapped environment, how to actually do that. And I'd like to give a shout out to Rob Linger, who's been a fantastic partner on Leidos's side in helping us co-develop that capability.
All right, thank you. So Eric, next question for you, at least a topic I want you to help us get started on about open architectures. Why are open architectures so important to Leidos and to our customers?
