 Rwy'n cael ei wneud o'r syniad hwn o'r pwysig o'r gweithio mewn gwirionedd. Welch i nim yn y sesfa, rydym yn cymryd ar symfyniad me'n mynd i gymeran Rhyw Pwysigol ond mae'r cymryd mewn cyfryd yn ymgyrch yn ymgyrch yn ymgyrch. Mae'n cymryd Sambrych. Mae'r cymryd comersial rhai o'r cyffredinol. Rydyn ni'n rhaid i'r Prannag Paiush, rydyn ni'n rhaid i'r cymryd mewn cyfryd i'r cymryd me'n mynd i'r cymryd. Mae Gen they launch their climb about a year ago and they've won hundreds of customers this year they're looking to win even more than that then we'll hear from Fabian Potent protons CGI who is the CEO of Scenceo Labs Scenceo Cloud was soft launched in December last year and they're looking to win some quite large customers imminently we'll hear from Fabian about those ac rwy'n meddwlogi o'r rolyn i Benedeti, sy'n meddwlio leodau popeth provide'r dyfodol. Falle gofyn nhw gyda sy'n meddwlol i'r hydllunio'di ar ysferthau a Rolyn i'r cy behalf, a Rolyn i'r cyffredinol iawn cyllid yn ein gennyd, fel y cyfgriadau o'r rolyn i'r cyffredinol yn gwneud hefyd. Ond dweud, llywb am oedd yr actor yng Nghymru. Mae'r cyfeir. Felly mae'r ddeifan o'r awdd ymdd nhw mae'n mynd arweinydd o'i adael nôr hon o'r awdd yma, dod mewn ffordd yn ffordd maes ar y cyfrifiadau am ymddorol wrth yng Nghymru. Llywodraeth, nid yn hyn, mae'n ddim yn arweinydd o'u awdd yn digwydd mae'n ddw i'w gweld, er klwyddoch chi sgwmp iawn o gydigfodol i'r tynnu adrod gwasanaethau cy Promodol i'r pwysig. If you're able to automate a large block of DevOps processes, then you've just removed the majority of problems associated with the administration of consistent environments. That has a huge effect on many related activities, development, deployment, testing, upscaling, integration testing and so on. It's the confidence that comes with this that allows you to think differently about your working practices and your service offerings. And likely gain a competitive advantage. And of course all this leads to risk free continuous delivery. If you can make an exact copy of staging or live in 30 seconds, you can make your changes and test this feature, this feature branch and know with certainty when you promote that change back to the staging or back to the live environment. It's going to work exactly as you expected it to. And that means you can start to stream many changes into live all day long, small or large, whatever the priority, whatever the site is doing at the time, be it midnight or be it in the middle of the biggest sale you've ever had. Well, you might not do it then but you could and our online retailing customers do exactly that. Platform gives our customers fast development, fast deployment and a much better live service and all at lower overall costs. And here is some feedback that we collect from our customer case studies. We collect metrics in 10 different categories and briefly running through those. You know our customers are able to set up new projects and on board new developers very quickly instantly in a matter of hours, not weeks. Every get branch comes with its own infrastructure making the workflow far superior. Productivity is typically 20 to 40% better but some customers tell us their dev teams are doing twice more than twice what they were doing. Approvals are 5, 10, 15x quicker in some cases. It's obvious really when you think about it every feature branch has its own URL. And that means you can test your feature to your satisfaction, drop it into Slack, the URL into Slack or an email. And the approver can get very quick sight of that and can see the change in a live running copy of the site. So that speeds up the whole process massively. We've automated all the environmental management and no more tickets for resource changes, new service versions, upscaling configuration changes, all that's gone. And all that's within the power of the developer to do themselves. Customers are delivering many new features into live every day now. And our high availability clusters deliver extremely good performance and practically zero interruptions even during emergency upscaling. And all this is happening at a much lower overall cost. So that's just a couple of words on platform. I'm going to hand over now to Pranav Payash, who's the head of growth at Magento Cloud. Pranav. Thank you, if you're on. If you just move on to the next slide, I'll sort of introduce Magento. I'm not sure if everyone in the room is familiar with it, but we'll go through a quick introduction of Magento and Enterprise Cloud Edition and what all that is about. And then, you know, why we chose to work for platform. So moving on, if you look at the ecosystem and the industry around e-commerce, there's a lot of things that are changing in the market. If you think about a lot of the offline retailers moving, increasingly moving online and not just in the B2C space, but also in the B2B space, you see a lot of sort of internationalization and cross border trade. You see a lot of channel growth. And finally, you see a lot of people wanting to move to a cloud environment and not sort of having to maintain their own servers and DevOps and so on and so forth. And so if you look at these market trends holistically, Magento's effort has been over the last couple of years to provide an end-to-end solution that can solve all of these different needs that merchants have and sort of move with the times and the needs that the customers have. So if you move to the next slide, what you'll see is, Ciaran, do you mind if I see the slides a little bit? So we're going to focus on the digital commerce side of things today. So we have other tools like auto management and the market phase. The focus really is on the digital commerce side of things for this conversation and why we have chosen to move to the cloud and specifically move with our forums past. So moving on. Okay. So Magento's digital commerce solution is really sort of the market leading solution across the board from small and medium businesses to really large enterprises. And it forms sort of the backbone of the overall experience that customers have and so on. And if you look at sort of the overall spectrum of our enterprise base, we really have sort of customers in a variety of verticals and some really big brand names. We've got our community edition, which is more of an open source sort of platform. That's where we originally sort of developed from and lots of developers and channel partners that have arisen because of that, the open source framework. But we have the enterprise edition, which takes that open source version adds a whole bunch of enterprise great capabilities and obviously the support that we offer. It's a subscription license based on the amount of sales and revenue that the customer is doing. And customers have sort of full control over how they deploy this in the Magento cloud on their own servers and obviously that trend has been moving towards deploying in Magento's cloud. So moving to the next slide. I just want to sort of highlight some of the big names and brands that are using Magento's platform. So you'll see folks like Cannon and Ikea and the New York Times all the way to folks like Team Bureau based in Europe, Lexus Nexus, Coca-Cola, Burger King, lots of sort of big, big brands. And it's a quick end is another example that are using Magento to power their commerce experiences. And it's really sort of a broad spectrum across B2C, B2B, and what we recently also been calling B2C sort of a full stack merchant who's doing their own production manufacturing and distribution. So let's move on to the next slide. So the core sort of e-commerce capabilities that a merchant gets out of the box, span everything from basic content management, getting your product catalog up and running to things like SEO, to things like promotions, and obviously sort of working hand in hand with the shipping and payments and marketing tools. And it's really sort of a very rich set of capabilities that a merchant gets out of the box, especially if you're running an advanced store with multiple currencies or multiple locales and so on and so forth. So that's sort of the core e-commerce capabilities themselves. But if you go to the next slide, what you'll see is the move to Enterprise Cloud Edition. Now, this launched in Q2 of last year, so we've had about three quarters of momentum behind us at this point. And what Enterprise Cloud Edition does is it takes our core Magento offering with this Enterprise Edition, packages it together with the cloud infrastructure that we've built, and also some business intelligence and monitoring tools, and provides us a complete solution to our customer base. This is a natural evolution of our flagship product, and going forward, this is the solution that we will be leading with. And if you want to sort of deploy on your own servers, that's going to be more of just something that you can do, but there would be no real reason to want to do that in the future. And if you look at the cloud infrastructure piece, if you go to the next slide, this is where we rely pretty heavily on platform usage. If you just want to advance the slide a little bit more, I think there's some animation here which is kind of missing. So the cloud infrastructure piece is really powered by three technologies. You've got the core sort of hosting, the infrastructure from AWS, and you've got the CDN and the DDoC protection from Fastly. The platform is what brings it all together into a path layer, and customers only have to interact with the white-label platform solution that we have offered them. So they don't have to worry about managing AWS infrastructure or how exactly Fastly works. They deal with the platform and we take care of, and that takes care of the end-to-end DevOps experience for the customer. Obviously it comes along with, as I mentioned, Magento business intelligence and Neuralic and Blackfire, which are basically performance management or performance monitoring tools. And on the other side, you've got Magento that provides of the onboarding and the launch management and 24-7 support across the application and the infrastructure working hand-in-hand with platform's team. So why do we choose this approach that will address on the next slide? When we think about our merchants, they don't really want to be involved in the day-to-day DevOps activities and sort of being involved in managing servers and infrastructure. What they want is a more agile way of getting their changes and e-commerce experiences shipped to their clients and their users and their buyers. And the concept of the past really sort of helps our merchants focus on what they do best without having to worry about deployment and developer efficiency and so on and so forth. So it's really good for merchants from that perspective. It's also really good for our channel partners. Now, most of our merchants engage a solution partner or a channel partner that helps them implement the sites or maintain the site over a period of their contract. And those solution partners also don't want to be involved in the DevOps work. They want to be sort of focusing on delivering the customization that their merchants are asking for. And it helps them focus on that sort of core development work rather than worry about the DevOps work that they've been used to doing in the past by having to manage their infrastructure on their own. So the past sort of makes this a very consistent, repeatable process to make a change in development and getting it into production and focusing on the testing article rather than the management of the infrastructure. So that's why we chose past. And, you know, when we looked at all the different technologies that were available and the distance of players in the market, we found that platform solution, platform exchange solution was really sort of a leading edge in terms of the capabilities that it provides. And that's why our technology team felt that that was the best move for us with enterprise cloud addition. So we were firmly strong, strong believers in platforms tech and want to see this partnership sort of continue for years to come. So moving on to the next slide. The benefits of the sort of past solution and the enterprise cloud addition solution overall, merchants have continued flexible, right? So it's still sort of coding and manage and customizations that they can deliver with the core magenta application. And at the same time, the past and platform solution helps to keep the site very performant and manage scale in a very graceful manner. And then obviously, you know, reliability and security are key part of the platforms and all sort of magentos emphasis. And so that's something that customers get. And finally, if you think about customer success and support by providing both the core application and the infrastructure, magenta makes it a lot easier for merchants to sort of get support of help from one party rather than having to go to a different company or provider for the application was the same perspective. So it's added benefit for merchants from that perspective. Let's move on. Okay, so here's an example Oliver Sweeney, which is a luxury lifestyle brand in the UK. They basically made custom shoes. And they had to sort of move from a bespoke platform to whatever they were going to choose next. And magenta enterprise cloud addition powered by platform was a great sort of option for them. And I don't know if any of you were at Imagine, which is magenta's conference annual conference. We had a case study with Oliver Sweeney talking about sort of all the different things that they were able to achieve the business outcomes. Around faster site performance and conversion rates and so on and so forth. And all of that is really enabled by the fast iteration and the agile way in which you see you work. A big part of that is platform. So we're seeing sort of continued momentum. I believe at this point, 20, 25 live customers with hundreds of customers who are sort of the soft and soft development and going live in the coming quarters. And we see the trend and so the overall move to the cloud a big sort of approach for our business in the next 12 months and platform is going to be a big part of that. All right, let's move on. There is a video if you guys want to I don't know if it actually power if it came through in the in the presentation it may not have. So let's let's just keep moving on and we'll skip the video for the time being. Okay, so if you think about sort of, you know, in the end, this is all about enabling our merchants and their customers expectations. And enterprise accreditation sort of enables that right to make sure that the customers are interacting and having a great experience with their website have access to the website, especially during the county. This is a part of our offering and something that platform helps us deliver. And through sort of, you know, our CDN strategy, making websites accessible across different locations outside of the primary market for our merchants and really sort of with the core enterprise edition code accessible from any device. And all of this so that without sort of seeing any delays and latency and being able to process orders without getting stuck and purchasing with confidence. These are the things that we are able to deliver because of the technology that we've put in place with platform. And we were very happy with the results. And and want to see us have continued success with platform. That pretty much wraps up the presentation around magenta enterprise accreditation. If you guys have any questions, this would be the right time to ask them. So any questions for Pranav before he drops off. No, I think you covered it very well. Thanks, Pranav. Really appreciate that. I'll leave the audio open if you want to continue listening. And we'll move. Sounds good. I probably dropped off, but let me know if there are any questions and I can answer them offline as well. Great. Okay. Many thanks, Pranav. Thank you. So that was Pranav from Magento. So now we're going to ask Fabian to come up and talk to us about Sensio Cloud. Just to move the slides on. Hi everyone. So I'm going to talk about Sensio Cloud and why Sensio Labs and Symphony we actually chose platform message for our new cloud. Before I start talking about Sensio Cloud, I wanted to talk a bit about Sensio Labs and why and who we are because it's very important to understand. The reason why we actually chose platform message. So Sensio Labs provides products and services to PHP developers. We're trying to ease PHP developers' life, which means trying to make them more productive and of course make their companies more successful. So basically, so here I'm talking about Symphony. Symphony is in top 10 most active projects on GitHub. It's been the case for the last few years now. We estimate that we have something like 600,000 developers in the world using Symphony. And Symphony is downloaded almost. It's not almost. It's actually more than one million times per day. The great thing about Symphony is that it's not just about the framework. It's also the fact that it's used by many different open source software. That's the case with Drupal or Easy and a bunch of other ones, which means that around 10% of the web actually runs with Symphony or some of the Symphony components. And actually we reached a great milestone a few months ago with 500 million downloads in October last year actually. It keeps growing. So this presentation actually says 1700 million and we are more than that now. So the great thing about that is that we have a lot of people using Symphony and they are very different needs, of course. And we're trying to address all those needs with Sensor Labs and all the products that we have and especially Sensor Cloud, which is really a product that we want to be part of the ecosystem of the Symphony world and not just a product that is on the side. And that's the important point because that's why we actually chose Platform Message for Sensor Cloud. So Sensor Cloud is a platform as a service optimized for Symphony. So I'm going to tell you a bit more about why we actually chose Platform Message as a foundation for Sensor Cloud. And I'd like to think about Platform Message as being a framework you can use to actually create your own Platform as a Service. So, sorry, a few years back when I created Symphony, so almost 10 years, more than 10 years now, there was a clear separation between developers. We were responsible for the code and people responsible for deploying code to servers. So developers and CISN means with different responsibilities, different skills as well. But I think that's not really the case anymore because web applications are more complex and companies want to deploy or to be able to deploy code every single day. And that's why there is this Dev Ops movement and it gains traction. And with Symphony we want to embrace those changes of course. So code is, and code deployment, so the way you actually deploy the code is mostly a solved problems nowadays with Docker and services like Google App Engine and Heroku and things like that. It's pretty easy to actually deploy code from a staging environment to a production environment. And along the years we actually made some changes to Symphony to actually make that use case easy and simple. So, and with those platforms what you gain is that you have more scalability, you have higher availability, but that's not good enough or not anymore because it's not just about code deployment anymore. Web projects nowadays, they depend on a lot of different services. So it can be a database, it can be a queue system, a cache layer, a search engine, whatever. So websites are getting bigger and bigger with more traffic and even for smaller applications. And the thing is the framework in Symphony cannot really help. It's just about the code, so we need something else. And that's the limit where we have the code and the infrastructure. So deploying code is really about synchronisation and code synchronisation between a staging environment and a production environment. But it should also be about all those services and how you can provision those services and how you can manage data into those third party services really. And those features cannot be covered by Symphony itself or any framework for that matter. So when we were looking and when I was thinking about the next version, major version of Symphony, I was thinking about how can we solve that problem, how we can make sure that Symphony developers, they have an end-to-end solution that works not only for the code, but only also for services and data. And that's where Sensio Cloud and Platform Assets come together to actually trying to solve this problem. So one very small but very meaningful example, okay, here, like that. So that's a very small example, but it's really explained why we think that Platform Assets was the right platform to build Sensio Cloud. On the left side on the screen, you can see the composer of the JSON of a Symphony application. That's where we actually declare and we define all the dependencies, the code dependencies that we are relying on for the code. And the exact same thing is possible with Sensio Cloud and Platform Assets with all the services. So you can declare and define the dependencies for your services. So on the right-hand side of the screen, you can see that I'm also depending on PostgreSQL and ready for my cache. And that's great because in my project now, I can say, okay, I need Symphony or Sylex or Web Profiler or whatever plus PostgreSQL in the code directly in my Git repository. So I don't need something else for that. And that's great. And the infrastructure is powered by Git and that's the main selling point, I think, of the platform. Because the configuration of your code and the configuration of your platform and services are in the same place. Which means that, for instance, if you want to add a new feature and for this feature, you need a new service like Redis, for instance. You can create a proof quest, make your code changes, add a dependency in your configuration file, the Sensio Cloud configuration file, and then you can deploy the code on a staging environment. And on a staging environment, you will have the new code, the new services, and even more important than that, you will have the data coming from production directly into your staging environment. So you have everything so you can really test your new code and infrastructure really. So, and that's possible because when you define the services, all the services are actually managed by Sensio Cloud and Platform. Which means that you don't need a third party service for most typical services. So if you want a cache, a search engine, or if you want RabbitMQ or things like that, it's built in, which means that you don't need to rely on a third party service for that. And that's very important because that's how you can configure them really easily in one place and not relying on other things. And that opens up a lot of interesting opportunities, really. And the first one is the SLA. The SLA is 99% but that's not just on your code. It's not just on the network. It's not just on the PHP stack. It's for everything. It's for all the services. And that's kind of unique and that's because all the services are actually on the same platform. Think of that for a minute. If you are using Oracle, for instance, and then you are using third party service for RabbitMQ and another one for Redis, even if each of them has an SLA of 99.99, at the end of the day, the real SLA that you get is 99.99 multiplied by 99.99 multiplied by 99.99 which is way less than what we can get. So that's the first main thing about the fact that we have everything on the same platform. The other one is that, of course, because everything is on the same network. You don't have any latency or the latency is actually really small. Everything is on the same local network. So that means that performance is also much better than any other platform as a service. The next one, and that's the second really key point of the platform, and that's data snapshots. So this one is very important. So as SensorCloud manages all your services, not just the code, it also manages your data. And when we create a snapshot, we are actually creating a snapshot of everything, the code and the data for all the services, which means that we also have a snapshot that is consistent across all the services. So you have the RevitMQ data which is really synchronised with what you have in the database or in Redis or in Solar or whatever you have in your service definition. Which means that you can snapshot the production environment, so the production data, and use them in development or staging, which is great. Instead of using Lorem and Zoom in your database, you get the real data, which means that it feels like you are actually working in production because you have the exact same infrastructure, the code, the services and the data. And that works for, you know, whenever you create a new branch in Git, you get that free. So you create a new branch in Git, you get a new cluster of servers where you have the new code, the newest version of your code, the changes that you have just made to create a new feature or to fix a bug, the services and the data coming from production. So that's a great feeling, really. And the other great consequence of that is if you are doing continuous integration. Okay, so you develop on your laptop, then you deploy the code, and you are probably using some kind of continuous integration servers where you are running your test before you deploy the code to production. So just the fact that you have the services and data means that you can do more than just running your unit test. What you can do is, for instance, take browser snapshots to be sure that the output is really what you are expecting, or you can run performance tests with Blackfair or things like that. So it means that you can add more steps to your deployment pipeline, really, to be sure that whenever you deploy, performance is great, the display is great, so the DHTMA is great, compatibility with browser is great, and of course your unit test as well. So it's just more than just being able to run your unit test. I'm talking, I talk a bit about, so I talk about the continuous integration thing, the fact that you are trained for requests and things like that. The last thing I wanted to talk about is this command line, and this command is very interesting because sometimes, so platform is such, it's not something you can install on your laptop, of course, but what you can do is if you are working on a bug and you can't produce the bug on your laptop because you don't have the data coming from production, what you can do is you can create a branch getting a snapshot from production to the real data, and then you can open a tunnel between your laptop and this environment. And all of a sudden, on your laptop, it's like you have everything from production, all the services, all the data. It means that it's much easier to actually fix a bug, trying to find why there's a bug that you can't produce on your laptop but happens on production. And that's great because there is no difference between the services in production and the services that you have access to locally on your machine. So I can talk about that for a very long time, but I think you get the point now. In fact, as I started with that, I think that platform is such a really great framework to actually create your own staging environment, a continuous integration pipeline, and really the environment that you need to really develop with confidence, making changes and being sure that before getting to production, everything works really fine. So that's very powerful, and that's also why we chose a platform message for SensorCloud and this integration between the framework and the infrastructure management. I think that's all I have. So if you have any questions about SensorCloud and whatever I've just talked about. Okay. In any case, I'm here. So if you have any questions after the talk, I can answer them. Great. Thanks very much. That was Fabian, and now we're going to hear from Roland Bandatasi. He's just... Cool. Hi everyone. Nice to be here. Thanks, Kiran. So the great thing is I could almost just say, well, just like him, or many respect. There are many reasons we decided to work with platform and all the things we heard from Magento and Fabian are actually probably valid for us. I will just tell you a little bit more about our use case and how we work together. Before jumping on us and what's specific about us, just to say where we are, we, I think, started to collaborate a year ago with Platform Message. It's a technology partnership, so we didn't package a product together, but we basically used their technology and we started to push this to our channels. And things are going great and the more time spent, the more we are convinced it's a good partner for us on the infrastructure and the past side. So that's a little bit of the story I'm going to tell here. But first, about us. I don't know, who knows about Easy here? Good. Who knows about Drupal? Well, I'm very glad to experience my first Drupal con. Easy is another CMS vendor, much smaller than Drupal. We have conference as well, but they are in a smaller order of magnitude. And what we build is an intercontinental management platform for people to build digital experiences. It's really a platform. It's used to be called Easy Publish, so the chances you know us might be through Easy Publish, but now the name of our latest product is Easy Platform. The reason why it's a platform is because it's more than out of the box CMS, it's really something you build on. I think this is key. One of the main reasons we work with Platform Message is because of our stack. What is it that we have in our platform? It's not innocent, but like three or four years ago, I don't actually remember when we decided to re-platform and to move from a product called Easy Publish to a product called Easy Platform, we decided that we would stop to do the framework, the application framework ourselves. We were always a lump player. We've been open source since 1999, and we were doing our own application in PHP. Three or four years ago, we decided to stop doing so to focus on what we do best, which is content management, and to use Symfony as a framework. So we use PHP, we use Symfony. We use a tech stack, which is increasingly more complex. You would think that with the progress, things would get smaller and simpler, but actually the lump stack is getting more complex. There are components which used to be not taken as granted that you should have them, such as Solar, such as Memcache or Radis or all those things. So very complex tech stack, and we don't necessarily want to be the masters of this tech stack. More importantly, the agencies and the developers working with our platform, they are not experts in that domain. So when thinking about PAS and when trying to find a PAS technology that could accompany us through that journey and provide our CMS on the cloud as a platform, as a service offering, very clearly it was crucial for us to work with some people who understand well our stack, which is Symfony, PHP, all the underlying component on the storage level, of course MySQL, MyIDB, Postgre, and other things such as Lucin and Solar coming into the search now. So that's probably the first reason for us. Very important. We actually tried to work with other vendors and maybe not so much expert on this stack and it didn't work so well. So let me tell you a bit about easy on what we do. We do a CMS, but it's a CMS that can be used in many, many, many situations. So it's not just about making websites. We have a lot of customers in the news and media industry, but it's also about actually e-commerce like Magento. Sometime we compete with them. It's also about building things which are not websites because we deliver content headless as well. So a lot of APIs. So a native apps on the Internet of Things or a lot of a big variety of things. A smaller footprint. I will skip this because this is marketing and that's not really the goal of this session. But the interesting thing is that we work with all kinds of customers, but mostly on the enterprise-ish side. So way smaller than the Drupal, much more on projects which are usually very complex and distributed on an infrastructure which is not easy to set up. So the trend we see with our customers is that they are not making websites. Digital is not anymore a website. Digital is not anymore marketing. It's really they are moving their business model onto digital. They are totally changing this. A typical case for us is working with newspaper industry. A newspaper decided to go digital first and stopping doing a daily print of their newspaper. That's a massive change of their business model and that's the kind of thing our customers are looking at and that's why they are choosing us. And those business models are changing all the time because users and their habits are changing all the time. And they are moving beyond the web with the Internet of Things. We more and more push content actually to devices and the top right is KitchenAid. For instance, they have connected device and actually we collect data from those devices in the project we have together. So that's quite different than making a website. And again for them it's a race to be the first to be there. So the reason I go through this part which is more high level and not as technical is that at the end of the day what we need to deliver to our customers is two things. We need to deliver them with the capability to create and publish content. That's so key. Content is like the cornerstone of the digital transformation but more than that we need to deliver them something that helped them become a software company. Who is it that was saying software is the world? Andreessen or something like this? They are all turning into a software company. It's not anymore about let's buy a CMS from our agency and let's have the CMS three years and in three years we will do a revamp. Let's invest in infrastructure which will help us build a digital business. So this second part of our mission providing something to build a software company it's crucial. And those are the two things. And the second part for that, we need partners, we need people who are experts because guess what? What we learn is that this won't happen on premise. This will happen on the cloud. Very, very, very important. So that's the reason why because being a CMS vendor today such as being an e-commerce software, yes please. I'm saying there will always be people who want to run our software on-prem just like Magento who started but this will step by step become a very rare use case. And the fact is that today customers are asking for the cloud delivery. There's even banks that are moving to the cloud when even just in our market the content management software three years ago they would not want to hear about it. They also would not want to hear about PHP by the way. And now they love PHP and symphony so that's good. So that's why I don't know if it's... Yeah, definitely. So yeah, we're moving to the cloud and the CMS industry is moving to the cloud. The CMS industry though is moving to the cloud way slower than others because building a project on the CMS is much more complicated than starting to use a CRM for instance. Salesforce was in the cloud 20 years ago now almost. I don't know when was Salesforce.com but a CMS cannot be on the cloud like a CRM or document management on an ERP system or even a collaborative suite like Google, Gmail and so on. A CMS is a special beast. It's a beast that you build something with. A project with a CMS is never just by installed and used. It's always by installed maybe but then you build something with it. So it's a platform you build on. And this was just a snapshot of an article on CMS. A granon from Forester Research. I was talking with him at the CMS wire conference actually and we had those long talks about why CMS is behind when it comes to cloud adoption and so on and the real reason why is that the cloud that fits the CMS industry is the pass. It's not a software as a service that's not something that will run out of the box that's still something that each and every project needs to make its own, to customise, to integrate with so many systems to add so many add-ons. So in a very evolved way maybe one day this might be software as a service but that's not the case. People still need to develop templates to show their unique content in a unique way. They still want to use Tweak to do this. They still want to build their own digital experience and they still need front-end developers to build those. So this cannot be a software as a service offering. Even if we tried, we tried to make CSS... we tried to make filming capabilities so that people could define the CSS and the layout of their website. Google Calendar wants to speak to you. Should I go play? Yeah, we can go and see. OK. So yes, pass. Platform as a service is the way to go for the CMS industry and content management systems and a way to illustrate this is our story with Easy Publish. In 2007 we launched something called Easy Publish now that was a SaaS offering with the site factory and the style editor and we wanted to abstract the creation of templates and so on for our customers. It kind of worked for small customers so... It never worked for big enterprises or large-scale project. We kept this project alive a little bit but as our focus is on enterprise we eventually sunsetted it. We did the same thing not really on our demand but in 2010 actually with Dutch Telecom we created an offering called... I guess I'll let this... an offering called Easy Publish International. That was a SaaS as well and it worked kind of for SMB but the SMB market is different. It's the market for site builders such as Squarespace but it's not the market for content management platforms. And in 2012 and 2013 really honestly we started something called Easy Publish Cloud which was a pass. We invested in this technology we started to put some resources and we tried to build this ourselves and to be honest I mean it's trendy to say that you need to fail so it's good to fail I didn't feel like it was good back then but we definitely failed at doing this ourselves. And the main reason for that is that we are not experts in this area. Our expertise is the application layer, the CMS and it's not building infrastructure. Our goal was to provide on the cloud hosted but a way for people to simply deploy and roll back their changes on the platform and that's actually one of the many things that platform message can offer us to do. Our next move when it comes to cloud technology which is in no way in disconnect with what we do with platform message is to dockerize our new platform so Easy Platform unlike Easy Publish has been done in a cloud way, it's by design made to be dockerized and to be containerized and it's basically something a lot of effort too but which benefits our work. So at the end of the day working with platform message why instead of doing this ourselves it's because focus is key for our business to be successful in our business. We need to identify where is our focus, where we put our resources where we put our money and where we grow our people. If you want and try to do everything you will not be able to be successful and we are a small company with a little bit less than 100 employees so we definitely could not tackle everything. So together with platform and soon in a more closer way because we will have a package offering together in the coming months. Platform takes care of the infrastructure operation not only the operation but also the roadmap because when we bet on platform we don't bet on what it does now we also bet on what it will do in the future and every day in our talks with the team and that's where the whole side is also very important we have some more proof and some more input that platform message will be our partner in the future with new features really helping us. So that's where they can focus just like our partners who are digital agencies, web agencies, implementation developers and so on can focus on things such as creative and content strategy, project implementation project management and us easy this gives us the freedom to focus on what we do the platform CMS, the CMS platform the content management side of things to support this one and to provide a few marketing cloud services on top of it. So that's a key point with platform message we find a good match where they have the good expertise that complements our expertise to have basically a full full blown cloud offering and really one thing I want to emphasize but Fabian did a lot of that with Wysensio cloud is also building that it's not just about hosting it's not a CMS vendor who choose platform message to provide a hosted offering it's a CMS vendor who choose platform message to provide a new development workflow to our developers, partners and customers so what we try to achieve is to provide a continuous development flow there are things which are in our CMS which are very important enabling people to really have continuous integration set up and working well and delivering features continuously to their customers and to their end users and that was already a revolution when we moved from waterfall to something more continuous and agile and iterative the piece which was missing was automation and part of the automation we started with testing automation we started with deployment automation with CI and so on but we never got the real developer everyday task automation of deploying to their product managers of deploying to testing of deploying to production so this is about really offering our customers a much more agile, efficient and productive development workflow than what they used to do and it's really needed because our stack got so complex that if you don't set up such a workflow you will have a you will lose a lot of energy and money by always trying to fix the same problems so the best way for us to assess the value of this I don't know where I am with time but I guess I'm getting close yeah okay so for us this is, we do this for our customers for our partners that is our mission but we also do it for us and it's because we eat our own dog food and we develop our website with our CMS and working with platforms solve some problems which seems so obvious but which are unsolved up to now at least they are not always easy to solve typical product management issue getting product managers touching the features as early as possible from the development foundry so typically we work agile, we have sprints of two weeks every two weeks we have spring demos where our product goes into features goes on merge product managers could not touch the feature before every spring demo so it's quite fast already but that's not fast enough actually everyday you want a product manager to be able to have a discussion with a developer and to ask this developer can I see this feature can I test it even if it's not finished I want to test it I want to have a real feel of what it is maybe I want to organize user testing on your feature well this is very hard to achieve but with platform as such it's great because there's this feature which is not just many development environment one staging environment one production but it's many development environment that can spin up as many staging as you want just to test your feature and when you are happy with this feature you can decide to merge in git the fact that it uses git of course is key and you can move to production so product manager can test new features before being merged better collaborate with developers this is key UX designers can equally access prototypes for user testing it's key because user testing on mockups is cool but when you do user testing on real working applications it's even better and last but not least sales engineers with such a tool and an offering we go to a prospect we set up a prototype the prototype is ready to be developed on we can have the prospect using the prototype eventually develop with the prototype because at the end of the day they will probably want to develop themselves and we can ship this to them they can start to use it if they are happy by RCMS if they are happy by the infrastructure just move and just keep it so it's a fantastic sales tool as well it's a fantastic sales tool for our partners who are digital agencies for us and of course for platform so that's about it for the reasons I think I enunciated quite a few so we are very happy to keep going and keep working with you thank you very much Roland so we finished bang on time sorry about the Skype messaging that was my 5 year old or my 7 year old it's bedtime in London and they were conference calling me I didn't switch Skype off so thanks to all our speakers symphony and platform do have stands in the main hall you don't have to be a global software vendor to come and talk to us we'll host your site if it's small, medium or large or whatever so thanks very much unless there's any questions then I think we need to probably wrap up thank you very much