 He actually is going to show you how to do that. We brought a customer, a partner, actually, who has been deploying Drupal for many, many years, from everybody from I heard time and all kinds of amazing, huge sites. Yeah, Zagat. We did the Thompson Reuters Olympic site for 2013. We worked on a certain house that is white in Washington D.C.'s website, so. So the thing about what we do is we do all of our stuff in open source. So the code that we are going to show you today, just like Drupal, is all open source. So it's freely available for you to use either in a hosted public environment or a private cloud environment. So I'm just going to go through these pretty quick. Use the right arrows. So we are a platform as a service offering from Red Hat, which is a large Linux distributor. Many people know us for that. And most of these, oops, allow. Whoops, I'm having fun with this. You can use the arrow keys too. Yeah, I just want to get rid of that little thing on the top. There we go, time's out. So almost all of the clouds that are out there right now are built on top of Linux. So the only one that I know of, a big public cloud that isn't, is Windows Azure Cloud. So almost everybody is using Linux. Most of the big ones are using Red Hat Linux under the hood. So we have lots of experience building clouds for people, big infrastructure clouds. But we have lots of different projects. I think there are over 100,000 open source projects that Red Hat sponsors and has people working on. So we're very much about open source and making software freely available. So one of those projects is a little one that I work on, the one on the bottom is called OpenShift Origin. And that is the platform as a service that deploys Drupal. And that's what we're here all here happy about today. I'm gonna skip through this. So when you look at a cloud, right? You, when you build a cloud, you have the infrastructure layer, which is all the servers up there in the sky and elastic so they expand and contract. So that's the infrastructure as a service layer. And then there's the platform as a service which is deploying the lamp stack. And then there's the SAS layer, which is the Drupal site. So that's the top piece. So basically what you get with the infrastructure is just the network, the storage and the compute resources. And with the SAS, you get your application. So you get your Drupal or you get your Python and Django or you get some other tools that you have or maybe you're using salesforce.com. You get that thing. And that's really what all the user cares about. They don't care about the stuff in the middle. And that's what we make sure that we deliver with platform as a service. It's all the runtime environments that you need, whether it's Apache, Tommy, Nginx, whether it's making sure you have the right version of PHP, the ability to run Drush inside the container, MySQL, maybe you're using MariaDB, which is the new version of MySQL. We make sure that we configure and stand up that Drupal instance for you and do it in an automated way that you can then auto-scale into the cloud. So that's really the role that platform as a service is. And so OpenShift is the name of a platform as a service offering from Red Hat with many community members. And what we do is we put the middle of the cake in there. So today we're here talking to people about Drupal, but we also support lots of other languages and do all the magic behind the scenes for that. So there are three flavors of OpenShift and all those three flavors derive from the first one, the OpenShift open-source project, which is Origin. And we use the Origin code base to host a public cloud. So you can go and if you come to the table afterwards, we'll give you a free account to play with. That is an actual production account that you can have forever with three one gigabyte instances with a half a gig of memory. And you can host there for free forever. It's a great way to try it because the user experience that you see in the public cloud is exactly the same one that you get when you install the software on your own cloud, whether it's a private cloud or not. So if you sign up for that, and then Red Hat also has OpenShift Enterprise, which is the enterprise offering for private cloud people. So a government agency might want to have it hosted behind their firewall, all of the OpenShift stuff. So you could do it that way. So I mentioned OpenShift online. If you come to the booth afterwards or after we're done talking, I will show you how to sign up and get an account at OpenShift.com. And that's the look and feel is pretty much the same. We're not the only ones that are using it. There are a number of other clouds that are offering OpenShift. So you can go, they've taken the open-source code and put it and created in their own public platform as a service offering at GetUpCloud. There's one other one that's in New York that's just about to announce. Lots of people use it. Tons of customers and clients are using it. So it's very easy to deploy. We have all the puppet scripts and everything. So if you want to run your own private pod as you can, or you can use our hosting service, or you can ask if you have a preferred hosting provider, so someone that the Atomos for Peace people want to work with, you can ask them to install OpenShift and run it there. So there's lots of options. Everything is in GitHub. So if you want anything from GitHub, all of this code is there. The things that make it different is that this is a super secure platform as a service. So it's using secure Linux, SE Linux for the containers that Drupal runs inside of. So it's basically an unbreakable container. Someone couldn't hack into it and change it to Peace for Atoms instead of Atoms for Peace. The container that you're in is super secure. We have a lot of government agencies in the United States that are using RHEL and using OpenShift. So I keep emphasizing this. It is open source, just like Drupal is open source, and you can take it and use it and fork it. And if you wanted your own flavor of it, you could do that as well. So for government agencies, sometimes they have special things that they want to do. They need to make it a fork of it and we help them do that. And we also help them merge it back in. So we work with a very big community of people from the Drupal community. We're working with Steven Merrill, who is going to come up now, and he's going to show you how it works because he's a Drupal expert and I am a bit of a pause expert. Switch to yours. Sure, so as Diane mentioned, my name's Steven Merrill. I do a lot of work with Drupal at phase two. We've done lots of big sites and OpenShift is really interesting to me for a number of reasons. I have a presentation, but I think I'm going to skip some of it because a lot of it goes pretty deep. But I did want to talk about, yeah, so with OpenShift, Diane mentioned there's OpenShift Online, which is for free, three apps, try it out. If you just want to try out Drupal 8 today, you can do that if you want to try out Drupal 7. You can do that. This is from my other one. I said, dobro por lo ten, gu dintak for everyone who is there. So I'm a director of engineering at phase two. And we helped to build a Drupal 8 quick start for OpenShift Online. Basically when I first came to OpenShift, to use OpenShift and to learn about it, it was about maybe four months ago and there was a Drupal 7 quick start. And Diane had said, we want people to be able to try Drupal 8 on OpenShift Online. And so we met at the Red Hat Community Summit in Boston and Diane had it almost working and she just asked me if I could do it. And I said, sure. And I may skip some of this, but the thing with OpenShift is that it comes with a ton of different languages and frameworks. There's PHP 5.3, there's Ruby 1.8, Ruby 1.9, Python 2.6, 2.7, and 3.3, Perl, Java with the JBoss app server. Yeah, basically anything you want. You've got Postgres, MySQL, MongoDB, and Node.js. So lots of stuff. There's a Cron cartridge, there's Jenkins if you want to build server for your tools as well. So that's what comes with it. But then there's also a ton of stuff that you can make or you can use from the community. So basically, I'll talk about this in a bit, anything that runs on Red Hat or Fedora, you can probably make work on OpenShift as well because the boxes that run this are Red Hat Enterprise Linux boxes. So in the case of Drupal 8, we had a little bit of an issue in that. Drupal 8 requires PHP 5.3.5 and REL typically keeps a single version and keeps back porting security fixes. So OpenShift Online runs REL 6.4 which has PHP 5.3.3. And so when we looked at that, we said nope, that's not gonna work. So my task of getting Drupal 8 to install on OpenShift got a little more complex. But luckily we could do that. I'm probably gonna skip over some of this since we don't have to do a deep dive into this. But the gist of it is that if something runs on REL or Fedora, as I said, it'll run on OpenShift. So for example, in this case, I was looking for some place where I could get PHP 5.4 so that we could get it running on OpenShift. And there's a repository called IUS maintained by Rackspace that has PHP 5.3 and 5.4 RPMs for REL. And so luckily I could just take those RPMs, grab the binaries out and make a cartridge. So I'll skip through the nitty gritty. Basically, there's a tool that you can use on Linux to sort of rip the binaries and the files out of these RPM packages. And I'll have all the links here and I'll post this online later. But suffice it to say, I'm gonna skip through most of this because it's very, very deep on how to create a cartridge. So we'll go through that. But yeah, once you've made your own cartridge, there's a couple different ways that you can do it. So once you've said, I have my PHP 5.4 cartridge, if you decide I really need to have, like, do you have another application you might wanna host on OpenShift? Sure, I mean, there's already quite a few that are, you can run WordPress, you can run Drupal, you can run Jenkins, you can run Joomla. There's quick starts for a lot of these. But if you make your own, it's actually pretty easy to go through and do this too, where you can go through and take something that's on GitHub and then just put it as a cartridge on OpenShift. So I'd actually like to show that. Diane also mentioned how OpenShift is completely open source, right? There's OpenShift Origin, which is the online, sorry, which is the sort of top level open source project. And then there's their hosted online version and the enterprise version. So what I did was I took OpenShift Origin and I installed it on a VPS running in Amsterdam. So this has literally took me about 10 minutes. There's a good puppet script for installing this and there's gonna be more support for different installers coming down the pipe too. I think someone's built in with Ansible. Yeah, so this is running on DigitalOcean, who's a VPS provider in Amsterdam. I spun it up on Sunday for my talk at the Community Day. And so you can see, every part of it is open source. And in this case, I'm actually just running it on a single machine, but I've got the broker here and I already logged in as my user. So I already have two apps here. I've got the Jenkins app. And I don't wanna understate how great it is to have Jenkins here. So Jenkins is a build server. It runs on OpenShift Origin. It also runs on OpenShift Online. In a couple of cases, we've had our customers sign up for OpenShift Online Silver, which is the plan where you can get up to six gigabytes of space and you can use bigger gears. And we were actually using the OpenShift Jenkins server alongside a project that's hosted on Aquia. So we can do all of our builds, compiling of SaaS or Compass, things like that, because you can set up an app to say this is a PHP app or this is a Ruby app or this is a Python app, but all the boxes have all the machines installed. So your Jenkins server also has PHP and it has Ruby and it has Python. So if your build script needs to use that kind of stuff, you can do it. And that's really great. There are other Jenkins platforms as a service offerings like CloudBees, but they don't have PHP or Ruby or Python. So it's really neat to have a platform like this that just has it included. And you can also in any app that you have add Jenkins builds to it. So I'll show you the default workflow for working with OpenShift in a little while, but, and it does have its own built-in sort of Git based deployment mechanism. You get a repository for every project so that you can easily, if you wanna make a copy of an app, you can actually just make a new one, push the same Git repository to it and you have a second one. So actually with that said, let's go through and just create an application. So this is my copy of OpenShift Origin and this is more or less what it looks like out of the box. This is running on CentOS 6.4. So running on the open source clone of REL 6.4. It also runs on Fedora. And most of the stuff comes out of the box. So I could make a PHP app if I wanted to and it's a little tough to see, but there's two different things, sets of things that are installed. There's the cartridges themselves. So PHP 5.3, you can't really see it, but that's a cartridge. Ruby 1.9 is a cartridge. Ruby 1.8 is a cartridge. And then there's also some quick starts and these are recipes that make it really easy to get up and running with a particular thing. And I took, there's just a file on the console here that I can edit and say, I want to make extra quick starts available. So I made this Drupal 7 quick start available, for example. So I'm going to say great, I want to use the Drupal quick start. We will call this Drupal 7. And every user on OpenShift gets their own kind of namespace. It's hard to see, but mine is community here. So you can have different users too. You could say each developer in my organization can launch five apps. And OpenShift also supports different gear sizes. So you could have like some very powerful servers where you ran large gears that had a lot of RAM and a lot of CPU. Maybe for developers you give them small gears that have just a little bit of RAM and a little bit of CPU. You can also do disc quotas. So you could say like, certain of my developers get one gig, certain of them get six gigs. That's exactly how online works. And more or less, all this quick start is going to do is it's going to start from a particular get repository. So I've already got a quick start here for Drupal 7. I'm just going to hit create here. I'll also note here that there is a scaling option. One of the other cool things about OpenShift is that it can automatically scale your applications for you. So you can go in and say, I have a PHP application with the MySQL database. And what it'll do is it'll put MySQL on its own gear and PHP on a separate gear. And then if a lot of requests start coming in, it'll automatically scale up and add PHP gears as you need capacity. So that's another really great thing is that it'll do that. And then as your app scales up when you do deploys, it'll send the code to each of your gears and restart them. So that's another great thing. You can either have it automatically scale or you can just set it to a certain threshold. You can say, I need a minimum of three PHP gears and a maximum of five. So if you know, you know, you've got a high traffic event coming up, you can actually tell the system to say, I need you to scale to this certain amount, but still have some headroom to go. So that's another really neat thing that OpenShift sort of takes care of for you. And so I started up my Drupal 7 app. And if I just click over to here, we've got a Drupal 7 site. I didn't select scaling, so this is all on one gear. So it's got PHP, Drash, MySQL, and the Cron cartridge as well to run Drupal Cron every hour. I can log into my site. And then just to show you how OpenShift's Git repository setup works, when you first create your application, it shows you the path to the Git repository. And every application gets a Git repository. So I could copy this and go into my command line and just say, Git clone. And it's gonna clone that down from the server. And just to show what the deployment looks like, I'm gonna CD it to the directory with Drupal 7. So you can see I've got regular Drupal 7. And let's say I wanted to make a change. So I'm gonna edit themes, bardic, CSS, style.css. And because the official color of OpenShift is red, I'm gonna make all the headings red, let's say. So I have my change. Look at me trying to get too fancy. All right, there we go. So I have my commit, I'll do a Git push. And then it'll just restart the application. So it receives the Git, it restarts Apache. And now if I go and reload my Drupal 7 app, then, oh, I did background color instead of color. Well, you know, whatever. It's very easy to fix, you know. I can change background color, push it back up. It's gonna restart it. There we go. Yep, and there we go. So now we have red headers up there. Some other things that OpenShift gives you out of the box. I mentioned it as Jenkins. It will let you build your applications from Jenkins. It has scaling built in. It has SE Linux controls so that, you know, all the applications are isolated from one another. Some of the other things that we've been working on are that cartridges can also put things into a user's path. So what we've done for our Drupal 7 and Drupal 8 cartridges in conjunction with some of the team like Voitec here who works on the PHP cartridge, is that we've made it so that, you know, just like developers are used to, they wanna have Drush when they're working with their app, right? So OpenShift also lets you have console access to your apps. It's pretty locked down, but so I could get that from the console up there or also note that OpenShift has a command line app called RHC and you can use RHC to log into OpenShift online. You can use it to log into your origin server. So I'm gonna just go in here and I've made a special RHC003 that just talks to my OpenShift box. There's a lot of things you can do. You can just say 003 apps and it'll give you a list of all your apps. So we could take a look and see that, for example, our Drupal 7 app here has one gear. This is the Git URL. It's using our PHP 5.4 and our MySQL 5.1 as gears. Then I could also do an RHC SSH to Drupal 7 and this just connects me into my gear. So I'm here and now I could say, you know, I could do a Drush CT all, for example. Great. And so it went through and cleared my cache or I could say, oh, let's say I wanted to download a module maybe. What's a good module to download? Is there a place to get a module? Yeah, or panels. Let's say we're gonna do a bunch of stuff on our site. We're gonna download panels or views maybe. Great. So it downloaded that for me. I could do a Drush EN panels to enable the panels modules. It tells me I need the CTools module. Great. It's gonna enable a bunch of stuff. Awesome. So I have CTools and panels on my site. And now if I go through and I go to the Modules page, we've got panels. So yeah, it works with Drupal very well. It works with Drush out of the box with our both Drupal 7 and Drupal 8 Quick Starts. And then as I mentioned before, so this is all on origin, but we also wanted to make sure that as a great first test, people could try out Drupal 8 just to see how it's working. And I have to make sure I actually have a plot available, but if you just go to OpenShift.com slash Quick Starts. Oops, that is a link right into my Quick Start. There's a whole list of all sorts of things that are available to run on OpenShift online today. So OpenShift.com slash Quick Starts. You can see, for example, OwnCloud. They gave a demo on Sunday. They're an app that kind of aims to give you your entire own personal cloud. So you can have your own Dropbox-like storage and your own, I think, calendar sync and lots of other things like that. And so it's a PHP app and it works on OpenShift. The OpenShift team maintains the WordPress Quick Start, the Ruby on Rails Quick Start. There's some interesting new ones that are coming up here like the Go language. So that's another example of something that isn't a native capability of the OpenShift platform, but someone just grabbed a binary of Go and made it so that you can run Go apps on OpenShift. I think that's the really attractive thing to me is that OpenShift provides all this infrastructure to let people spin up apps, to do scaling. There's a snapshotting and backup component. So if you're running with my SQL, you can say RHC snapshot and it'll give you a database backup. But then, yeah, literally anything that will run on RHEL or Fedora, you can make run on here. And so, of course, the thing that we'll probably wanna go to, looks like it dropped off the front page, but there is also our Drupal 8 Quick Start. And I can hit deploy now on this. That's gonna take me to OpenShift Online. Maybe, I might have all three already, we'll have to see. Okay, so we can get rid of Drupal 8 too here. Yep, so just to compare and contrast, there's only a tiny bit of branding taken out. So this is OpenShift, okay, this is OpenShift Online and that's Origin. Literally just a couple small changes and of course, you could also go through and add the CSS to this. The console here is a Rails application. So if you wanted to put your own branding on this, when you're running it inside your firewall or on some of the service provider, you can absolutely do that. Ah, so I got distracted, we need to go and spin up our Quick Start now. So when you click on one of those, it actually just takes the Quick Start and lets you know. And so, just to show you again, each user on the system gets their own prefix. And the reason that they do this is that you have your app name dash or prefix. That means you can have one wildcard SSL certificate and it works for all the machines. But you can also alias other things in. So if I make my Drupal 8 site and then I decide that I also wanted to respond to Drupal 8.face2technology.com, you can do that. So you can also add in names so you're not always using just the one domain name. But by default, for OpenShift Online, it'll be rhcloud.com. For your own, it can be whatever you want. So, let me get this spinning up because Drupal 8 still takes a little while to install since it's in development mode. So we'll create our application. Oh, I already have an app named Drupal 8. Well, of course I do. Yep, so we'll create this. And like I said, yeah, this'll take a while. The optimization of Drupal 8 is not yet complete. Any other stuff that I should talk about online or origin? Once you spin this up, you basically see the Drupal admin page. So if you have a system in that you work with that will help you set up the cron jobs and all that, you can just SSH in and set all of that page. Sure. We have about a quarter of a million users on the Red Hat Cloud using OpenShift now. If you sign up, you get, and anyone who signs up gets three instances. So you could set up three, a test, a dev, a QA, Drupal site, and then when you wanna go to production, you can push it to production. So it's a great way to do that. You can also download a virtual image of it and run it on your desktop so it's the same environment. So you can do all your testing on your desktop and then when you're ready, redeploy? Yeah, sure. So I mean, the thing that you'd have to do with that is, again, every app gets its own Git repository. So if you have your Git repository, you could deploy it back. Yeah, and that's actually how you could push things ahead is let's say you had a dev test and prod version. Yeah, you just say, when you've got some changes ready to go, you push that to test, they go up there. And then the other thing that you might need to do would be like, for example, you might at some point need to grab a database and pull it back from test into dev and the RHC tools also let you do a reverse proxy so you can connect to that database locally and restore a newer snapshot if you want. And we're also doing some work, Drush can support remote aliases. So we're actually doing some work to see if we can't get it so that you could grab Drush aliases for all your OpenShift gears. And then with that, you could just do a Drush at test at dev SQL sync to sync the database from the test instance to the dev instance. Yep, and actually, let's see if we, this does take a while to install. So hopefully it's done. Oh, Drupal 8, there we go. Great, and there's Drupal 8. So we've actually been working on improving that. The older QuickStart and the one that's currently online just downloads whatever the latest snapshot is is not what you get, but what we did recently, and I've been working with Vojtek to make this better is to make it so that literally we could just have it cloned directly from Drupal.org so you can just do a get pull and grab the latest version in or potentially use Drush to update it, to say Drush downloads, you know, 7.23 now, 7.24 is out, go and do that. But the QuickStarts give you a get repo to start with. So like for the Drupal 7 QuickStart, we're actually, we've built a new one that we're gonna hopefully phase in pretty soon where it's literally, it's got the get history from Drupal.org. So you could literally just go, you know, get fetch, d.o, that would pull in all the latest stuff for core. So this OpenShift is an open source project. So we hosted at Red Hat on Amazon in North America. So if you're hosting your website with us, you're gonna have latency issues if you're hitting it from Africa or whatever and you're gonna probably run into restrictions around jurisdictions. So what it is is an open source project. So you can take the same code that we used to run an OpenShift online and deploy it on Rackspace or on up cloud in Finland or get up cloud. And the same deployment, the same get repository can get pushed to anyone running OpenShift anywhere. We have a lot of customers that are running it in their private clouds behind firewalls and enterprise. We have a lot of public pauses that are using it under the hood to deliver platform as a service as an offering on their managed hosting services. So, and if you have a preferred, they can stand up and OpenShift to light Drupal. It's a community based project that's sponsored by Red Hat. And we're, it's, and we, Yes, and it's worth noting this does not require virtualization. So you can run this on bare metal or you can run it on Rackspace or EC2 or DigitalOcean or whatever. It just needs to be able to run rel and have SELenix enabled or even for origin it could be Fedora or Sentos. Yeah, that's all you need. You don't have to have OpenStack. You don't have to have some other kind of virtualization to run it. And that actually lets you get a performance increase too. If you actually can run it on bare metal, it's using containerization. So there's no sort of virtualization of the operating system. It's all just, there's one Apache process here running in a very specific SELenix namespace that's, you know, cordoned off from the rest. Over here you might be running Nginx and PHP here. But yeah, it actually could let you get better density of your services too. So you don't have to virtualize the kernel, virtualize all the low level drivers. Handle all of this. It's running using containerization SELenix, LXC and pretty soon it'll actually be interoperable with Docker as well. So you could run a Docker created image in your gears. That, you know, work is being done by like 15 members on the Red Hat team to bring Docker first to Fedora and then into rel. And that'll even open up, you know, the number of applications that you can run even further. Yes, we need to. I'm actually going to go, I need to go to the, thanks. No worries at all. I'm not sure these folks want to hear about translation. Does anyone want to hear about translation? Okay, that's all right. Hi, one night, one night is to come walk and talk to you guys. So basically, Lingotai has a term module that helps big challenge in translation is the idea that this content has to be synchronized across languages all the time, right? Web content is not static. So our modules sort of, you know, works with menus, taxonomies, blogs, all the different types. So you can site manage your work content by different things. Knowledge-based articles, it's going to be different from machine module, cloud-based transition management systems, it's going to be a workflow, and it's going to be human, it's going to start off in your site, it's going to have an initiates workflows. These workflows exist in separate software applications, cloud-based applications, the machine website will launch multiple languages and do a bunch of translation and immediately it's going to start spending money. Absolutely, so you think about it from, you know, the multiple elements of translation is one, just collecting the content, presenting to zip up, FTP, we automate that process, and it's presented in a French translator. It's complete. It ends up in instance or cloud-based. So we're not going to be interested in the guard. It can be two minutes. So I'll show you how it works. I can just project it up, make it easy for you guys. So if you're going to... Yeah, so I don't know why it's so fuzzy. Right, so it's sort of, you know, because it's web-based you can see the completion rate. If you're using internal translation, it's just totally fine. You can say, hey, we have a load of work to be done. It looks like they're 84% complete. And it might not be workflow or it's translation, content review, language review, whatever the workflow you create, different workflows. It tells you that it's a translation phase. It's got 2657 words. So there's a... there's an original text that's what they call source language. And on the right-hand side, there's the target. So you have context here. You're doing your translating on sentence-by-sentence basis. What it presents in the interface is the context and the rest of the paragraph and the rest of the document. So it has... And then you can type in the text and edit community voting, which is, you know, for here. That little box is basically where people... or in-house translation, you can have people like just vote on it, you know what I mean? So it's very good setting. It's a translate phase, but then you could say you need three votes to say this is different. And sort of right here is like there's a collaboration. Is that not just collecting the content out of Drupal but it also presents it inside an online software application which you actually do the translation. It's an illustration work, right? It's not like you can't do very much when you find the correct pages and map it to the correct pages in German or Italian. It sort of just pulls back in there. Now, you know, it's possible to do this on here, right? I mean, it's just this error-prone. It's manual. It's kind of consuming. It's soft, basically. But the real issue is that as this source content changes, right, I mean, you're looking through, you know, tens of thousands of orders. I mean, how do you find what happens to this? And so, because it's going on there's the Parallel Corporate, Parallel Data, it says that's the sentence, right? Those words change or this is the new pricing and new specifications or whatever it might be. And so that presents that to the translator to translate. So when they update, it just automatically pulls that thing back in as the new version of the translation. Exactly. So what they do is, like, continuous translation, right? I mean, web content is not static. Therefore, how could the translation be static? What generally would happen is people sort of do this new project, launch some site, and it has all the different versions. And then, you know, this changes, but these things don't change. And sometimes, this is, you know, our experience. If you didn't do these, you didn't do, you didn't see the video. That's sort of our objective. Yeah, that doesn't... Could this kind of work into workflow in the sense that we have people making notes that exist, project, participate in the wrong by saying, I'll look at the other thing you brought in, right? Exactly. And then the excellent thing, this is also a big problem in translation, is that, you know, people send it over the source content to edit or to start to translate, or we have a new version. Use this version instead, right? And so, it doesn't matter because we have the control version in here. And so, because there's this thing called translation memory, which aligns all this stuff, all it's doing is saying, well, this stuff is already translated, so it does a matching algorithm and applies the exact matches against that constant, so it's okay. You can try and just say, okay, here are your source edits. You know what I'm saying? Yeah, yeah, yeah. So, it's a big problem, and especially here in Europe, it's like almost every site's multilingual, and I look at your card, where do you work? Yeah, so I mean, inherently, you guys have to deal with all kinds of translation issues. And so, what this does is it allows you to leverage machine translation, allows you to use your own in-house translators, and you need to do probably some of these, and you overflow with other translation agencies or professionals? Yes. So, in our case, we look all in-house in the sense that does this go into your service, and then you guys... It's a good question. So, there's two different ways to process, right? So, we, the way we traditionally charge, right, is, you can drive modules free, you can get an expert content, do this community translation stuff, but it doesn't allow you to access our translation management system and create custom workflows and upload your past translation numbers. If you want to do that, the way we charge is $5,000 per language pair, you know, running on that, so if you do 12 languages, you know, finish $60,000 a year. Now, if you wanted to, you know, in oftentimes, like large organizations like you, and we work with a lot of government agencies in the U.S., what we do is we sell them premise-based software, and then we do it on a user model, you know, which seems to be like people that like... So, we sell them on that basis, too. So, in the case of the free version? It could do machine translation where you could do your own, just your own translation, just using this workbench, right? But what you don't get is you don't get a sort of upload translation memory, so this is, I don't see it, so there's a lot of translation research that's covered up, I've been noticed, but basically past translation show up. So, machine learning, it's all machine learning, right, and yes, you get some fuzzy matches, essentially, you can say, seriously, this is mostly translated, but what's really awesome about this, if you dive into translation is that how do you translate into a lot of translation memory? You can retrain the MTN, so machine translation is statistical, it's a feedback, so basically what happens is you have a UN-based machine translation of your content that you can use in the system. I mean, sometimes it's just like, you know, it collects all your translations in a parallel corpora structure, it allows you to retrain the MTN. That's sort of an advanced use case, but people do it, right? Well, if I have 100% human translation, they start to leverage machine translation, they can do 5,000 to 10,000, output, which is what their cost is, so that's where it starts to spin out into a really excellent use case. Exactly, so you look at like a baseline of 70% accuracy on machine translation, progression is trying to get up to 90% since you're having this sort of model located, so, you know, you might say in another setting, you know, trains on that, applies patterns to that and so it's likely to exist, in the case of all of these. Yeah, but, you know, most people upgrade, they almost everybody upgrade, so what they really want to do, and I don't know if I, let's see if I have a slide on this, is because this is just a workbench, I mean. Yeah, I mean this is, it's a hard hurdle to clear to get, it's hard to say, why would I pay for it, because you'd get access to project management, workflows, there's a whole project management engine, there's a whole workflow engine, you can literally create new workflows in here, you can, you know, you can manage all your translation memories, so, you know, inside now I'm just logged into the software, right, so I have a full dashboard, I have project management, I can create new projects, create new workflows, you know, manage all my resources, like past translation memories, glossaries, terminology, you know, community stuff, like I could, you know, set different thresholds for voting, I could embed certain things inside the CMS, you know, if I do system maintenance, I mean you literally get machine translation engines, you can manage all the MT engines, I mean it's a pretty, it's a big piece of software, you know, it's a little bit deceptive when you just see somebody like have a little editor, you know what I mean, exactly, and that's sort of the point, right, you just go like, you're here, you're translating, what you're really doing is you're managing all this stuff, you're managing, you know, really the whole language system of the UN, you know, and you'd have access to all this stuff. I think from your perspective, if you're managing Drupal at the UN, you know, what you're really trying to do, pull that stuff in and when it's done, it's not like here you go, it's like they're left, it's already loaded, it's done, right, you don't have to so we literally have and all we find a slide that's sort of cool, see if I can get any animation work, so it has all this stuff, so it's animated. What it's trying to show here is that independent of the translation process, which is probably speaking more to you and your team, is there's all these elements, these blocks that are like project management and web administration that precede, you know, the translation process and you have to have the content, you have to identify it, you have to download it, you have to either export some stuff, you know, you have to do all these things and so that's what the module is. That content here again, they have to translate it again. So the best way I've found established systems and people and all that kind of stuff is you spin something small up and say, hey, we're trying something now, we're testing something, yep. Yeah, there's, we're working on Drupal A right now, so we have Drupal 6 and Drupal 7, the Drupal 7 one is much, much better.