 Yeah, so hi everybody. This was Pantheon when I joined it That's for we have four founders. They started out building Drupal sites for for schools like UC Berkeley and sort of the initial proof that you could run Drupal at scale for the economist and sort of big first generation Drupal sites at that point it was probably Drupal 6 and and I worked at an agency in Chicago and after running a big multi-site for an agency I talked to them and they said that they were looking for help with support and They asked me to join and and I did and Just a little trivia if you look on the right there that guy look at his phone there is Kyle Matthews who later went on to start Gatsby he built our first dashboards and And and there's a couple other actually several of those people are still at the company. So they've they've found a It's a it's a good crowd of people and they've managed to tolerate me so I like it and so you know early on and what we've learned is we kind of grew is that we would talk to people and They they would have a part like a column in a sheet where they were filling in different options for Drupal hosting and They would ask for features like Ram and you know CPUs and that sort of thing and our platform doesn't really work like that Like it's every site on our platform is kind of a distributed infrastructure and there's like the get stuff like the version control is built in and there's a bunch of other things that are In there and we were having trouble sort of connecting with customers and we started thinking about it and You know if you buy any book on sales One of the things that they talk about is like moving off of this the solution and talk about the problems Which is basically, you know Discovery you know and do ample discovery and so we started talking to people in IT teams and in marketing teams about what they're trying to do and What the problem is and why they were trying to see coasting and sometimes it was performance and you know sort of obvious like kind of break fix things but Ultimately what we found is that a lot of them were trying to bring to reality What they had in their heads and trying to keep up with like the changing sort of competitive landscape and keep up with with demands within the organization and also to be able to come up with new ideas and turn them into reality And one of the things that we realized is that one of the ways that we were helping these customers is that we had this workflow that Was essentially kind of a DevOps, you know go to market that we had built of like well, we're your DevOps team but like Marketers didn't so much care about DevOps But what they did care about is the fact that like not only could they not push? Changes and make things happen that they wanted to like they they couldn't even get to that point because they were worried about downtime or bottlenecked by central IT and provisioning and things like that and We were kind of solving that for them, but we weren't explaining it very well and we realized that part of what we had to do was not just sell hosting but also pitch DevOps to non-technical stakeholders and One of the things that we realized was a good way to explain it was in terms of agility because like You know DevOps is you know, it's kind of a technical Promise that that's made if you do these things like you can have dependable software and get dependable results and You know agility was a big part of that and going back to like the 12-factor app and things like that You know and about pushing small changes and it was sort of part of our Initial kind of value proposition and what we wanted to bring to kind of the Drupal world when we were building these initial sites as a Before we became kind of a platform as a service and we're doing these consulting projects But when we started talking about agility even within the last three You know two three years like it really started connecting with the non-technical stakeholders in a way that we hadn't before when it was just kind of a technical art conversation and Now like agility and marketing is sort of a big deal and there's you know something like 65 percent of of organizations Are trying to become more agile and then trying you know Trying to take you know, they're what they want what they like about agile development and and rather than You know build a website every two years and just start from scratch and build it over and over and You know think in terms of monoliths they wanted to be able to to Push changes and that sort of thing and sort of iterate and a B test and that kind of thing and you know overall they were looking for productivity and Talking about agility made that kind of connection in a way that just DevOps didn't and You know so now now when we talk to folks, you know, if it's a div it's a dev centric organization We talk in terms of features and things like that But really we're trying to help people within these organizations align better on The fundamentals of DevOps but sort of talk about it in a language that that straddles kind of different departments and hopefully breaks down silos and You know helps helps drive Drive, you know turning You know your website into this iterating evolving living thing And one of the companies that we often cite is Tableau Because they came to us as sort of these young punks a few years ago now They're all kind of like me. They're kind of middle-aged and getting crinkly But they came up to us and they were like we're trying to do all this stuff but like our we keep taking down our website and Like it looks like you have the version control and that sort of stuff built in and the pull request workflow You can work with our ups, you know with our git repos and things like that But we need like different things and you know, we need more environments and that kind of thing and and We started looking at what they were doing and we really like these these guys have like at any given point in time Like if you don't know Tableau, they're sort of this analytics and visualization Platform and like at any given point they're running like 7,000 different landing pages and different variations and AB testing to kind of figure out what gets You know good results and then they double down on that kind of thing and We they found a home in our platform and we sort of found like you know the the ideal State for a lot of our existing customers, you know I think when when you talk to customers you ask them about their present state And where do you want to be but a lot of times like where they want to be just isn't Like it's it's not where they should be, you know where they want to be is something like well We just want our site to not go down all the time, you know, and you know So what we've tried to say is like yeah, well, that's like table stakes, of course Let's get you to like where the site is performing Let's get you to where the site is is up all the time But let's move past that to like more of an ideal state where you can iterate where you can try new things where when there's an idea You can spin it up like websites aren't meant to be this, you know, sort of Delicate flower that gets read Reconstituted every few years, you know, it should be something that's always kind of changing and So we've sort of looked to these folks And other companies like this on our platform to kind of drive that and so we've we've shown we've sort of Nailed down a few common goals, you know, like good good clients are able to publish in real time They're able to try and iterate design and tweak things and they're able to make use of martec and AB Testing and or even just different messaging and simple things like that And they're able to like measure their website in a way that aligns with their corporate KPIs So like they can follow, you know, like marketing attribution is a difficult thing But you know, your website is kind of where you drive everybody like that's where you have to kind of send everybody So like you should be able to get past the the table stakes and get to where you can kind of measure Results and conversions or whatever is relevant. And so part of that is Drupal you know as a CMS because it's awesome and it hooks into anything and You know, it's it's tested and there's the community and the plot the modules and and all the different things you can plug into it And so we we that's sort of been our core What we've built around and tried to support for for years but then on top of that We've tried to enforce the like reliability table stakes with You know with our container-based platform and horizontal scaling and multi-zone fell over and having you know If you're a global company, you can have your site in whatever region and you know, you have support there when you need it And that sort of thing sort of the things that that You know, if you've used our platform, you're familiar with but they sort of emerged from sort of being able to try and deliver this Promise secondly, there should be like the workflows that enforce these guardrails on the system where you know your live site is locked down changes are pushed through get and You know, you can make changes safely without you know without you know Without worrying that a developer is is doing stuff in production and things like that So, you know, we've always had sort of an opinionated workflow about our platform and this sort of enforces that and You know, we work to train people on our platform. So then you're working You know what you're dealing with and and the expectations are kind of set And so like every site on our platform has dev test in live and More that I'll show you in a second But you know, it's tailored for for Drupal where there is you know There's stuff being stored in the database and you need to be able to sync and do that kind of stuff safely and securely And so we've built a platform where every site on the platform has those things and It's meant to be a very friendly developer experience, you know from the beginning Pantheon has always been free for developers like a developer or an agency should never have to pay for a site on the platform Should always be able to use it free and that's one of the sort of the fundamental things that we've believed in like over the years We've added other features We've added multi dev which allows for different feature branching and allows you to use those things for continuous integration and that sort of thing We've built everything into a dashboard because Like we believe that CLI is awesome We offer command line like we believe in it But at the same time there's non technical stakeholders who want to use it And there's also just the ability to be able to wrap your head around what your you know, what your web Assets look like at any given point. We think that that's that's important We've added several other features that I'll show you I have about four minutes. So I want to kind of blast through some of the stuff and Just get to the demo because that's like fun. And so, you know g2 crowd likes us. That's awesome We've added things like a global CDN Which has significantly kind of improved just overall performance and help drive down Time to first bite and other sorts of things that we think are important. And again, that's just like again It's kind of table sticks. It's there. You just turn it on and it should just work in most cases And then yeah, so like there's some managed updates that are built in like if you can do it yourself That's awesome But as we've grown we've added professional services to our list of things that we do and so if there's migrations that need to be done or things like that we build that in So my my former team I've hired five of those folks and And we're hiring by the way actually five of six of those are still with the company and they're all in different departments one of the Really the best thing about the job is that I've I've gotten to see these people grow and like Rachel started in our docs team there and now she's in professional services and Up at the top right is Alex who's in Romania and he started has a What did he start as he started as a support guy and now he's a sre And we've gotten to see you know sort of grow with these folks together And we have a bunch of awesome customers every Ivy League school In the US is on our platform and a lot of other Nestle and some other customers and Yeah, so we have stuff on the roadmap and but I'd rather just show you the demo and show you what it looks like and And then we can sort of talk about any questions. So This is my This is my fictitious company Um, it's uh Arcadius. It's named after the worst Byzantine empire. He was a weak ruler I think about that during covid like, you know, you're an emperor, but you're the worst emperor. Like is that a good thing or a bad thing? um, so like uh Every site on the platform like I mentioned has dev test and live You make your changes in the dev environment You can push them up to test see what those changes are if you are happy with them you push it to live All that is built in when you spin up a site Every site on our platform is container based so you can go There's no bifurcation in our platform So you don't get to a point and you need to be migrated to another part of the platform You can literally go from being the smallest site on our platform to the largest site on our platform, uh through Up pressing a button and every site on our platform is horizontally scalable You can hook into, you know, that it's all connected on the back end via private key Uh infrastructure to the database and to solar and any sort of uh components that you use The uh what i'm showing here is actually our new dashboard, uh, which is not Uh, generally like you if you've seen pantheon you've probably seen something more like this and more like this But we uh currently behind a feature flag. We have a new dashboard that we're working on and um You know your sites are in here if Because we don't really Do multi site what we offer instead is a git based upstream workflow Where you can spin up sites based on your upstream and so you could put those here And when you push updates to your upstream you could pull them down to the sites below uh one of the things that's in um about to be released is is called um autopilot and autopilot is a way to just make sure that updates are done on your site and we uh basically what it does is you have a site on the platform you uh go into autopilot And you turn it on And you say that uh for example, I wanted to check core cms. I wanted to check plugins. I wanted to check themes If everything passes push sites to the lot push updates to the live environment do this once a week Take some do some visual regression testing on these pages here and as long as it's within a certain threshold That's considered pass or fail and don't do any updates on these modules So you set that up and then you can run updates And then what it does is weekly it looks for updates to core Or contribe it runs visual regression testing If those tests pass then it pushes it up to It pushes it either to the dev environment for you to wait Or uh it can push it up to the live environment. So Uh, you know if you have um If you have uh sites where you have your own kind of automated testing and cicd You can augment it with that or you can not use it at all But if you're an agency or something like that and you're you know, you're supporting a bunch of sites And you know, you have a small client who doesn't have the budget But you want them to stay updated Like this is one awesome way that we're making it super easy for you to be able to do that kind of thing. So um So yeah, I'm I'm over for time. But uh, that's kind of like an overview of Of what we're about like there's you know, obviously a lot more that I can talk about but um You know, like I said, it's always free to try like anyone can spin up sites and you only pay for a site when you take it live And uh, we have support that's always chat first so you can always reach out and ask us questions or um You know, you can ping me directly. I'm on I'm on this time zone. So I'm always around hanging out looking to To harass uh customers and talk with them about stuff So yeah, that's that's what I got