Inside OpenBao with Alex Scheel
November 17th, 2026
32 mins 35 secs
Tags
About this Episode
What does it take to run secrets management in production? Jay Faulkner talks with Alex Scheel, head of OpenBao development, about how OpenBao works, from hardware security modules (HSMs) and cloud key management services (KMS) to the new external auto-unseal plugin system. They also cover why the project exists after HashiCorp’s move to the Business Source License (BUSL), and what it takes to sustain an open source project that companies depend on.
Guest: Alex Scheel, head of OpenBao development (formerly of Red Hat and HashiCorp)
Host: Jay Faulkner
Topics discussed:
- Alex’s path from Gentoo and Red Hat’s Dogtag public key infrastructure (PKI) project to HashiCorp Vault and OpenBao
- What secrets management is, and where OpenBao and Vault fit
- HSMs, cloud KMS options (AWS, GCP), and OpenBao’s new external auto-unseal plugins
- How a request flows through OpenBao, from service identity to secret retrieval
- The HashiCorp license change and the Business Source License (BUSL)
- How OpenBao started under the Linux Foundation, and why governance matters for forks
- Open source and business sustainability, with comparisons to OpenStack, Redis, and Elasticsearch/OpenSearch
- Open Source Shoutout: Go Viper and the mapstructure library
- The GROSS story: an unpatched FreeBSD DNS server
Links mentioned:
- OpenBao: https://openbao.org
- Alex Scheel: https://cypherboy.com
- Go Viper: https://goforge.dev/gpviper/
G-Research is hiring in Dallas, TX and London, UK! Apply at https://gresearch.com/vacancies.
For a video version of this podcast, check out https://youtu.be/4FDB87Xlazo.
The GR-OSS OUT Podcast is produced by Ben Wiley.
Transcript
Alex Scheel
Large enterprises need that type of infrastructure for their own internal usage. And so it was a fun team to kind of cut my teeth on. About half of the team was originally from Netscape. Back in the day, they started it around, I think, '96, if I recall correctly. And so by 2015, 2018, you know, there was a good understanding both of the product space and of the technology, so....
Jay Faulkner
Hi, I'm Jay Faulkner. This is the G Research Open Source Software Outreach Podcast. The GR-OSS Out Podcast, where we give you the unvarnished reality of what it's like to work on open source in the world today. And I'm really happy to have a guest here who I get to talk to quite a bit about a software I don't know a lot about. Those are always the most fun to me, and that's Alex Scheel. Alex Scheel is one of the maintainers of OpenBao annd I'll let him tell you a little bit about his history at open source, how you might know him, where you might know him from, if you're not OpenBao. So go ahead, Alex, so you got the floor.
Read Full Transcript Hide Full Transcript
Alex Scheel
Yeah, thank you, Jay. I'm Alex Scheel. I spent some time at Red Hat originally back in the day. I first got interested in Linux, I think around 2008. Our family had an old computer and that was the first Ubuntu disto that worked. I think we tried 710 and didn't quite work for whatever reason, but 804 was a solid on that machine. So, overwrote Windows and installed Linux and haven't looked back since, so it's been a fun journey. One of my mentors got me into Gentoo and heating up the house with kernel builds on an old Celeron laptop, so that was fun. At Red Hat, I worked on a couple of areas under the identity management ecosystem. I started full-time on the dog tag PKI project, which serves PKI for the free IPA project.
Jay Faulkner
PKI being private key infrastructure, public key infrastructure.
Alex Scheel
Public key infrastructure, yep.
Jay Faulkner
Okay.
Alex Scheel
So there was certificates and identity, so I always explained it by, you know, the little lock icon in your browser when you're on your bank or Amazon. Large enterprises need that type of infrastructure for their own internal usage. And so it was a fun team to kind of cut my teeth on. About half of the team was original from Netscape. Back in the day, they started it around, I think, '96, if I recall correctly. And so by 2015, 2018, you know, there was a good understanding, both of the product space and of the technology. So that was really cool.
Jay Faulkner
That's super cool. I'm sorry, go on, you've got a long list. And I'm not sed to having someone who's been around so much. You've covered like 17 interesting things already and we're a minute in, so that's great.
Alex Scheel
Well, we'll see where I end up. But from there, I spent some time at a HashiCorp as well, working on vault. I was very fortunate to join the crypto team as it was getting started and I brought a lot of that PKI expertise over to HashiCorp, had a lot of fun building out our Acme support, building a roadmap for that side of the product in connection with our product management and getting to execute on portion of it. So from there, I kind of left over the relicensing issues and started working on OpenBao and I've moved a little around companies in that space, but happy to be at ... as head of OpenBao development focused on commercializing the project, so.
Jay Faulkner
Yeah, that sounds really cool. One of the things is I know you mentioned Gentoo in there, I was actually talking to one of my peers over there who's a Gentoo developer as well, and how like one of the things I appreciate about the community is the number of people I talk to like pass through as a learning experience. And like for me, like it's a victory every time I talk to someone who like, yeah, Gentoo helped me learn this stuff. And now here's a giant list of the things that I've had success with. So it's like, I always liked that, I like to call that out, but it seems like SSL has kind of been at the center of your career, right? Like you've been, you've been helping people keep things secure, is that just sort of the special to you stumbled into when you started or was that a specifically targeted idea?
Alex Scheel
So I went to a library book sale at one point in time as a kid and I worked for the biggest book there. And it was this, it wasn't really a technical manual so much as like a history kind of like storytelling book of code ciphers and other cryptic and clandestine communication is the title, but it was like a thick card cover book on everything from like Caesar ciphers to pigpen ciphers to esoteric trivia of how they wrote on tubes and whatever. You needed the right size tube to be able to unravel the message. Then eventually I think it ended just shy of modern cryptography. I think DES was first coming out kind of around when the book was published. And so that was kind of the end of that book. So absolutely nothing to do with modern cryptography, but all the storytelling, all the lore that really gets a young kid interested in it. And so from there I picked up the nickname "Cipherboy" 'cause I was interested in all the old ciphers and now it's stuck and it's been my career.
Jay Faulkner
It's interesting to me because I think that books like that information like that, looking at old cryptography is not only insightful in how digital cryptography work, but it almost like helps you see the physicality of how computers work at a low level. Like you're talking about the different sizes of tubes and stuff and how those actually, you know, like, oh, if this signal's supposed to reach here at this time, we might have to think about the physical dimensions of how long it takes. And that is really cool to me. And I think it maybe helps you appreciate the stuff that we get to completely ignore today that's hidden in the silicon chips.
Alex Scheel
Completely agree. And all of these modern ciphers, like I got a undergrad math degree, So I'm not, you know, PhD math expert by any sense. And a lot of the finer details of the algorithms completely go over my head. But, you know, having that history of looking at smaller ciphers, I think really makes you appreciate the modern ones that much more.
Jay Faulkner
Yeah, I don't have a math degree, but I do the countdown puzzles in the UK. So maybe that, you know, do some math there. Let's talk about how it like got applied though, right? Like you're here obviously to talk about OpenBao, but I know that sort of OpenBao and Vault are connected. I kind of want to take that and I just want to set it to the side for now. We can talk about that a little later. But if someone's not familiar with the space, if someone's never heard of OpenBao or never heard of Vault, or maybe doesn't really understand how the, you know, we went from talking about, you know, secret codes and spies to web browsers to, you know, some cloud service in one conversation. Can you maybe help us connect the dots?
Alex Scheel
Yeah, so I play a bit of music. So I always explain this to somebody who's interested in the music space a fair bit. And one of the things that I think a lot of people intuitively understand is there are entities banks that have physical means of storing data. They physically store like your safety deposit box. They physically store, you know, large amounts of money on site. And these are vaults, bank vaults, quite literally. And as companies in the tech space grow or even non-technical companies, so much of the world has become digitized that you have passwords as a regular human that you need to store securely. And so just like companies and people have passwords and have vaults, they need a digital equivalent of these things. And so you need a way for developers to take not only their own passwords, but also identities and passwords for other applications that they are writing. How do those applications prove their identity? How do those applications talk to other applications? How do they talk to third party resources? All of these things need to communicate and need a place to securely store data.
And so that's the basis of the secrets management space is it really encompasses a lot of different areas unlike your Gartner Magic quadrants. You have your privilege access management quadrant, you have your identity, non-human identity quadrant, you have your secrets management area and OpenBao and Vault really sit at the center of that ecosystem connecting a lot of related topics together in a single secure tool.
Jay Faulkner
Yeah, it seems like it would be analogous to like a password manager, right? Like you can store your secrets in there. A lot of them even have a way to say like, these secrets are family secrets, these secrets are work secrets. These are shared secrets and managing all that except for obviously in a cloud, you got to have an API pointing out one end and I would assume maybe an API pointing out the other end. You know, I think of when you describe the service, I think you OpenStack's Barbican, which is a service that kind of does the same things. I would venture to say, even though it's older, I would be suspicious it's more mature than Vault, basically just based on my knowledge of how it's used. So what about the other end? What do you, you know... What is your vault made of, so to speak? Like, how do you actually store them securely? Is it using, you know, like hardware managed keys? Or are we doing some of the work ourselves? Or is it a menu of options?
Alex Scheel
Yeah, it's a mix of options there. You definitely have support for HSM devices, hardware security modules, I call them toasters, is a colloquial term. As in your background, you often are buying a device that you physically rack yourself into a data center. And so you then connect that through network to OpenBao, and that gives you a secure way to bootstrap your secrets management. You place all of your trust in this HSM device, and then from there you can do a lot of cool things.
Jay Faulkner
So I want to ask a question about this specifically, 'cause I remember, I used to be a CA cert assurer, like way back in the day when getting SSL certificates were difficult. One of the things I remember reading was they talked in depth about how their HSM worked, and they actually didn't even network their HSM. They literally had it serial consoled up to the machine so that it was like network air gap. It literally would just receive cert data over a com port and spit out the sign cert out the other one in order to reduce the attack surface. Is that like you mentioned that, you know, you put the toaster in the rack and you plug it in. You know, is that, is that how they all work these days? Is there just trusting the network and physical isolation there? Or are there still fun solutions to trying to keep them somewhat air-gapped?
Alex Scheel
There are a broad spectrum of solutions there. You can go from everything from USB device and get a very low powered, low throughput HSM.
Jay Faulkner
Like a Yubikey. A Yubikey is kind of an HSM, isn't it?
Alex Scheel
And Yubikey, or Ubiquo the company makes UbHSM's, which is what I was thinking of. They're a little more expensive, but they support a lot more options and a lot more keys. But, you know, are very otherwise cost effective to go rack and do a bunch of servers if you want to, all the way up on the high grade end to PCIe attached. So no longer a serial console, but you can put it physically in the same box as your server. And if you want, I believe they still do some sort of clustering capability off the back end of that HSM to give you resiliency and redundancy, should you need it. But it gives you a very low latency high throughput link rather than going over untrusted network.
Jay Faulkner
I really love the detour into hardware. I'm a hardware guy, but I know that the reality is that probably most people that choose your software are not, you know, like having their own data center in, you know, a locked cage with a, you know, $20,000 toaster in it spitting out math. So like, what are the other options on the menu that I would assume, I mean, that they're probably the way most people run it.
Right, so we support KMS options as well. So AWS, GCP, choose your favorite cloud vendor. OpenBao recently added support for external auto and seal plugins as well. So previously both OpenBao involved required that HSM vendors library or KMS vendors library, integration library to be built into OpenBao or Vault and compiled with that binary tied to the release cycle, et cetera. In particular, that was a very gate-kept
integration point. OpenBao has opened that up, I think actually using the same technology that boundary used, same set of APIs and interfaces and boundary allows external, I don't know if they call auto and seal devices in the boundary, HAshiCorp boundary case, but external plugins for accessing these devices. And so any vendor you want to integrate with can be done without requiring me or any other OpenBao maintainers permission
or inclusion into the main line OpenBao software. So sort of just to lay the whole picture out, you know, like I've got a service running on a cloud on Kubernetes. It spins up and it needs a certificate to do mutual TLS. It's going to go call up the API for OpenBao, say "I'm Bob service over here, I need Bob service key. The OpenBao will mark that in a log somewhere. I'm assuming that goes off to an auditor with a very serious look on their face, you know, or at least an AI agent that's pretending to be. And then you've got the OpenBao self talking with whatever actually holds the secrets going into that vault and turning the key on the safety deposit box and coming out and reading you the secret at the end. So it's sort of end to end cloud password manager.
Alex Scheel
Yep, that's largely correct. And then there's like a plethora of other options depending on what your security preferences are.
Jay Faulkner
Oh yeah.
Alex Scheel
For the most part it's like master key level and we get a sub key and then it gets as complex as you wanna take it from there.
Jay Faulkner
I saw the same look come across your face that comes across my face when someone tries to summarize what Ironic does. So I know there are a large amount of important details that I missed but just how the data flows is useful to know. But you know, we did kind of allude to this earlier. You've said HashiCorp a lot and we've talked a little bit about the license issue. Can we get into that a little bit? Maybe, you know, like if someone's been under a rock in the last year and a half, do you maybe wanna talk about why you work on OpenBao now and not on Vault and like what happened there?
Alex Scheel
Yeah, so I think we might need to go back even a little further, probably about three years now.
Jay Faulkner
I'm sorry, the time just keeps on ticking into the future and goes faster than I realized sometimes I think.
Alex Scheel
All good, yeah, no. So about three years ago now, HashiCorp changed the license of all of its main flagship products. Vault, Console, Boundary, you name it. And the license they chose, I believe was from MariaDB, called the business source license. And this license is not OSI approved, which has a lot of interesting ramifications downstream from HashiCorp.
Jay Faulkner
I would venture to say, and I'll say this that you don't have to, that I don't think most reasonable open source contributors consider the BUSL a good license. It's not OSI approved. It is not Jay approved. I would never recommend someone use software that's BSL licensed. Like this is not a niche opinion in the community.
Alex Scheel
I think I largely concur with you. I think if we were to be charitable to HashiCorp, they were kind of a bit of a tight space and they wanted a lever to pull around competition. And so one of the causes that you and I and probably a lot of other people disagree with is, and I'm not a lawyer and will be the first to disclaim. You should not take anything as legal opinion, whatever, blah, blah, blah, but. It's this clause around, if you are using this software in a competitive manner, you have to stop and seek an additional license from HashiCorp that is not to be BUSL. And so it really comes down to this question is, what do you and I and our lawyers and HashiCorp's lawyers, most importantly, consider a competitive use case. In the case of Terraform, there was a large community using Terraform in all sorts of cool and unique ways. And so Open Tofu started, you know, almost day zero, if not day negative one of "yes, I know most reasonable people would say my use of Terraform is competitive with HashiCorp or HashiCorp Terraform Cloud or whatever. And so I can no longer use Terraform". And therefore a community formed nearly instantaneously around Terraform and created Open Tofu.
And this was all predicated on "what do we mean by competitive in this license?" In OpenBao's case, a lot of people are very secretive about how they use HashiCorp Vault for good reason. It is kind of at the core of a lot of people's infrastructure. A lot of their threat models hinge on the security of Vault.
Jay Faulkner
That certainly isn't the cage you want to have to unlock for an auditor, is maybe a perspective I would have on it.
Alex Scheel
Right, right. And so it was a lot slower to get started. I think it took us about three or four months for the community defined interest to sustain a fork of Vault, or at least initially this fork of Vault. Ironically, it came from IBM who later ended up buying HashiCorp. But IBM started it with a rather strong foundation. They started it under the Linux Foundation. So it was under this umbrella which brought a lot of governance expertise and contingency to OpenBao.
Jay Faulkner
Honestly, having a foundation with lawyers to stand in front of you when you're doing something like that is a massive boon. And I think it's something that if you're like a person who's commentating on Open Source, you maybe don't always understand that. But as the person in the seat, having someone with corporate lawyers say, "We're gonna back you if bad things happen," is freeing in terms of your ability to fork and maintain it and keep the community alive in situations like this.
Alex Scheel
I 100% agree there as well. I've been on the other side of that conversation with those lawyers supporting us, supporting this OpenBao ecosystem. And I've been very appreciative of all the companies, including G-Research, that fund the Linux Foundation and allow us to have those conversations with those lawyers around what can we do with the project? What can't we do? What are the balance of that fork? So thank you very much.
Jay Faulkner
Oh yeah, it's no problem. We're Linux Foundation brethren here. Like, I mean, OpenStack is kind of eventually under there. So I think we're all rolling up into the conglomeration of corporate protectorate of LF, which is so good. So I'm curious, and you know, I'll say like for me personally, I self-select for open-source jobs. Like the fact that other people can use my software without restriction is part of what motivates me in my job. So like I'm wondering if with the license change, like how much of that was like a personal decision versus like looking at the landscape and being like, I'm curious like what motivated you personally to be one of the people to step up and help make up and about happen?
Alex Scheel
Like you, I've been fortunate to have a career that has been only open-source. And so to some extent, I felt like my decision was forced by this license change. I was working on a lot of interesting challenges that I think HashiCorp faced that I was trying to provide solutions for around community building in particular and I didn't really see a way of moving forward with this real licensing happening at the same time, especially. I saw a lot of business risks around these forks. What would happen if open tofu in particular became a Linux Foundation member, like they are now under the CNCF? There was a lot of discourse from various commentators internally, not those in power, but the popcorn gallery around the side. "Oh, competing interests will never form a successful open-source project".
"Oh, they're all going to find that the first time they have conflict, they're all going to go separate ways and create more forks or whatever." And I'm like, no, this is the whole purpose of the Linux Foundation and the stewardship that they provide is we can have reasonable disagreements in public and still have a sense of how we move forward, how we still maintain a cohesive community and project and presence. And so this was a worry that I had that I communicated and was like, hey, if you keep Vault open source, I will be happy to stay, or if you come back to the open source later, I'd be happy to come back.
I still maintain that if they were to reopen Vault, I would be more than happy to come back and figure out how we integrate the changes that OpenBao did, how we bring HashiCorp to the community. But alas, they haven't taken me up on that. Yeah, so I ended up leaving.
Jay Faulkner
You've kind of nodded to this a couple of times and I definitely want to make sure we say this is like. That's actually a very difficult problem from like a business standpoint, is you create something that becomes almost larger than your business and the urge to control it, or like I would say, maybe control as the vector for monetization is maybe the default business button to press. But you know, if you look even at OpenStack, you can see like how these different businesses spun up around individual OpenStack services or professional services alongside OpenStack and many of those didn't clear the hump. Like there are some large companies that were created out of OpenStack that do great stuff today. But there's a littered graveyard of companies that tried to do it and couldn't make that work, so it is a very difficult problem. And I actually think, in open Source, it's something that we need to keep at the forefront, right? Like thinking about how to keep contribution to open source.
I mean, some of what GR-OSS does, this podcast, like I think we're trying to set an example for, you know, if you're a corporate person who's using this stuff, you know, you have a responsibility to help. But even beyond that, you have an interest in helping. Like helping is good. But I wonder if structurally the shape of that help will have to change over the next five to 10 years as the industry is changing to prevent the sort of, you know, open source meets capitalism. It's not the first time we've seen it, right? Like we've had similar things happen, I think with Redis. You know, there are other projects that have been down this route.
And I don't know about you, it breaks my heart a little bit every time I see a hard fork. Like, you know, we have Open Search and Elastic Search now, and we're less for it than if we had one. So I don't really know what that looks like. I mean, if you've got ideas, I'd love to hear them, but I'm not trying to put the solve all the open source all to my poor guests here, Alex, so...
Alex Scheel
I wish I had a magic wand and a magic answer for you, but I'm not quite sure that I do. I think that the biggest common denominator across all of these successful open source companies, for whatever definition of success we have, and I will admit, I probably have a different definition of success than, you know, a venture capitalist who has invested in a HashiCorp in early stage or in a later round. But the common expertise or the level and quality of that expertise that they have on their products, I think, make them stand out from a lot of competitors in that space. Red Hat and Open Stack, Red Hat and Open Shift, you know, has a very deep bench of expertise on those products. Certainly on RHEL and the entire Linux ecosystem is underpinned there. Similarly, you know, Redis has...
Jay Faulkner
And even if Red Hat doesn't have the person hired, they have people like me and you who, you know, you said you work for them for a little bit, I believe. You know, I've never worked for them, but they've put food on tables of friends of mine for years and years and years. So I think like Red Hat has earned some of that goodwill as well through, you know, being in the open source ecosystem and that long view is one of the things that I appreciate about them in particular, I want to put their tires a little bit too, right?
Alex Scheel
Right. And so as, you know, companies like my employer build that expertise in OpenBao and provide the support services to our customers as well, I think that helps give us, you know, a way to compete in this rather terrible business choice that we've made to focus on open source that a lot of people depend on for their livelihood.
Jay Faulkner
I mean, yeah, a lot of people do depend on open source and one question that I'm going to toss your way is, you know, we've started asking guests here, you know, is there a little open source project hiding over in a corner somewhere? You know, maybe it's that brick from the XKCD that like there's one person holding up an entire portion of the open source ecosystem through sheer strength of will. Like, is there a project that we want to send a little bit of love to today with that in mind?
The one that I have in mind that I haven't spoken with them about at all is there's this small community called Go Viper, which has maintained a number of forks again of libraries that ex-HashiCorp employees have created in the early days of Go when Go didn't have a lot of ecosystem built up around it and continued to support and maintain from there. The Go Viper ecosystem now maintains map structure,
which is used in a million places in both OpenBao and Open Tofu. It just does some type of reflection mapping between various structures and it does it wonderfully and very appreciative of like two or three times I've ever needed to have a change in the library and they've been very responsive and very helpful, even though there's absolutely no way to monetize this library or do anything with it. It was one of, I think, Mitchell's or Armond's,
one of the HashiCorp founders throw away libraries that got used in 32 different places. That's like the open source equivalent of like doing litter pickup or like filling in potholes. It's the stuff that no one ever notices that it's being done but the second it stops being done, no one notices. And I, we appreciate you the folks over at Go Viper like G-O Viper.
Alex Scheel
Yeah, Go Viper.
Jay Faulkner
Thank you folks at Go Viper. Keep up the good work and keep those libraries going. We're gonna make sure that the link to Go Viper, anything else we talked about in this ends up in the description afterwards. Like if you look us on YouTube, just scroll down a little bit, you got it there. If you're in your podcast app, just go to your podcast description and we'll have it there for a link. But if you go there, you will see that it's the G-OSS Out Podcast. And so that means we do have to ask about gross stuff because, you know, honestly, this whole episode's kind of been a little bit of a gross out moment, you know, but the reality is is that this is what it's like. You know, there are ups and downs, you know, to get to create something as cool as OpenBao, there's going to be valleys on the way. There's going to be times when you don't know if you're going to get there. And, you know, if you're a person out there today and you're in one of those valleys, you're going to get through it.
But I'm going to ask Alex here, if he has a story other than the giant when we just told of a gross moment during his open source life that, you know, he was able to overcome and make it,and you know, so you'll be able to as well.
Alex Scheel
I worked for a lab. I'm sure you'll find everything online, but I'll keep them nameless for the purpose of this discussion, where, you know, I had one of those long-term tenured professors who had been around about as long as the university perhaps had. You know, it felt like that some days. And so he had a lot of leverage, which meant he had a lot of, you know, oversight gaps, I guess I would say. And so he had a very large lab that he had, that had a number of machines and one of those machines ran quite a bit of interesting stuff for him, including his own DNS resolver for a lot of domains that he in the lab used and it was running on a free BSD box that hadn't been patched in probably about a decade. So whenever we had to make a change to that, it was not a recent version of Bind that was running a DNS resolution. It had some interesting other pieces of software on there as well, included early versions of the research software. It was, of course, at this particular university. Actually for a long time when I was there. And maybe this should have been my story, but for a long time, even students could get public IP addresses. This particular box had a public IP address.
It was, of course, the name server for a lot of important domains around this lab. And at one point during my time, it did indeed get compromised because its root password was about as weak as you expected and was publicly listening on external SSH. So that made for a bit of fun cleanup for the lab, sadly. But it makes you wonder what it took to get to that point because there were large IT services that said public university, but this particular box was well outside of their purview per, you know, no uncertain terms from professors, so...
Jay Faulkner
I've heard a lot of stories from like academic tech and IT people and any of them that involved like "the professor had his own little server closet with devices inside", it always ends up being like the messiest stuff you've ever heard of running on that. So, you know, it's important. I mean, hey, that's a valuable experience. You got to clean up an old broken free BSD, which I mean, that's the thing is like, the skills all transfer, right? Like the command may may smell the same, but not be the same, but it all transfers. But I really do appreciate you giving time. This has been one of the more fun chats I've had in a while talking about OpenBao. We're going to make sure that all of the links to all the things Alex cares about gets in the description. Do you have a blog or a social media that you'd like people to check out, maybe the website for OpenBao or something that you want to plug before we say goodbye?
Alex Scheel
Yeah, OpenBao.org has all of the information you could possibly want or need about getting involved with OpenBao and contributing to that. If you're looking for a little more about me, cypherboy.com has that as well, so.
Jay Faulkner
Well, thanks so much, Alex. I'd like to thank as usual G-Research for giving me the time to run this podcast and to have interesting folks like Alex on. If you're in the UK or visiting go to gresearch.com, they have events all the time with some of the smartest people in the world, whether it be at G-Research, you're coming to visit G-Research, talking about cool stuff. Or if you'll live there and you're looking for a job, gresearch.com/vacancies and just tell them that the GR_OSS Out podcast sent you. But for now, I'm Jay Faulkner, this is Alex Scheel on behalf of myself, our producer, Ben, who's working hard to get these out for you. Like thank you for your time. This has been The GR-OSS Out podcast.