 So I think I had a very good talk today where I want to set the stage for this year. What we want to do at next year out. What's different to other projects and for others so far. What we are going to be able to do today already at the next year of ten. And what's coming in the future. So let's get started. The agenda is I want to talk a little bit about the next year out version but not too much because I assume that most of the story otherwise you wouldn't be here. But just a little bit what we want to achieve. And then I want to answer the question that I heard the most the last few months. What is different here. What is different with next year out. Then something that a lot of people asked us what's going into the next release. Next year out is not a classic, proper, very close software product. We are a company, we manage everything and then we'll give the next release a little bit different. Here I want to explain how this works. Then we all knew what's new and cool in next year out already. Which is already out as we know. And that was coming for 11 years in the future. And then hopefully we still have time for more questions. So with someone watching the clock a bit and telling me if I'm using too much light. Which is likely to be protected. Okay so what is the next year out version. The next year out version is that we want to enable users and organizations to take back control over their data. As you know there's a huge trend going on in this pretty cloud computing. Which means basically outsourcing infrastructure and data and applications to other entities. And that's a good thing, that's a good thing. But it's important that the users and organizations and the companies and universities are still in control of their data choice. But I can decide to be like Amazon to provide some infrastructure. But if there's no one like Amazon that should be able to go into some of those. It's very important. So this is what we do. Data and this is how we manage. Okay so what do we need for this vision plan? First of all it should be very easy to go to wherever you want. So obviously it's super important that you can deploy or run it very easily wherever you want. And this is a very small installation like Raspberry Pi. Up to 8 clusters for 10000 users. There should be many data silos. But there should be no login effect. If you decide to use some infrastructure and service and whatever. Then you should always be able to move it out of this system. Then move it somewhere else. Or data servers. Scaling is a small issue. I guess that's very important. The user experience is very key. You hear this a lot from our users and customers. That they're really nice to use. Because it's so easy and nice to use. But to be honest with ourselves. Most of the features that you can move next in our desk. We also have some cryptic mark lines. Which can be set up. But the customer is using it. Because you can't use it. So user experience is super super important. There's humidity to integrate. Most of you who are running next door. They integrate with some others. There's some authentication. There's some monitoring. So integration is very important. It should be cross-platform. So this should work on many windows with iOS and Android. And of course security. Security is optional. This is the key of everything. If the solution is not secure. Then you might do it in the first place. So here it is. If all of you run your own next door installation somewhere. That's great. And this is of course different to the big cloud installations out there. Where everybody, everywhere, collaborate. So this is what we want to achieve with our Federation concept. So here's a picture. Where we have different next cloud servers here in the middle. And we have different users using this service. And this one of them can be at the university. Another one would be in your company. Another can be your Raspberry Pi at home. Or use service provider somewhere to measure. With the Federation concept. You can actually share and communicate between different servers. Some kind of server to communicate. That's a very key mission and vision and feature for us. Because only then we can, we can basically turn this centralized cloud into a key to be here. We have a different server. We have different servers again. We have a repo we want to achieve. Let's talk a little bit about what is the difference. So this is something that so many people, customers, prospects, shareholders, everybody asked us, hey, there's an Excel cloud that's new and made great. But what is the difference? There should be something different. Nothing is different than this. What is different is that we want to listen to feedback that people give us. We come from customers, prospects, from powerful community users from developers. So we see next cloud as something that you want to listen to what you want. And this should fall in in what we do. And there are different ways to do that. What is that we want to hear feedback. But we are also working on other ways to get more feedback on how next.10 we have a new feature developed here. The users can optionally report back to us what apps they're using, what database they're using, how we use it, how they share it, and so on. This is popular and this helps us when we have a new platform that's very nice, that's for us to do discussions and to collaborate together. That's another thing that we want to do more and more where we can listen to you. And I think we've listened to the last few months and what we heard is we should focus more on reliability and I think that shouldn't be something that's just for hackers or for whole users. We are running this in a serious production of 1,000 users with 99.99% part time and should we scale this is really important so please focus on that. Then what we want to do is security and you should make sure that it's really, really secure. Then scalability and performance. Our next step is not slow and it can scale but I think all of you, for instance, you all want to be sure that you don't hit any scalability or anything like that. So this is something that you have to focus on and open as a lot of us, really a lot of people ask us can you please be more transparent with your battery screen system, the problems you face, the security you face, your roadmap, and so on and so on. And we also want to do that. One thing we change in the next round is the next round of orders up to 10 years. So if you buy commercial support from us, next time you achieve an agent, we support your instance up to 10 years. This is significantly more than 1.5 years if you get somewhere else. This is really important. It's important to pray that I have no problem with several arcs if it's really fast. I don't want to operate upgrades in pain. I'm not trying to use it, I'm using the face changes and I don't want to operate but I have to operate because my version, I have to boil it while it's 10 years old and it's no longer supported. That's the case. So the next round you can get your experience and then you can feature set. If everything is on for a while, you can buy it for up to 10 years. Next thing is, this next up can you already, so you can monitor the next round of Nagios of OpenNMS to see that it's working and how it's working, how many views are registered, how many views are active at the moment, how many shares are there, how many files are there and so on. So you can all type it into a nice Nagios dashboard and you can see how it is running and what's going on. So this is obviously very important. The thing is, that's a major point. So next up is 100% OpenTalks. So next up is 100% HTML. This is very important. Why do we have stages in the topic production process? This is very important because there is no mandatory audience. If you like what we are doing, you can take out some of that by the way that's on one side, there is a community in the presentation that is on one software. Take it, install it, run it. You can do this without any cost and it's all in the process. Professional support, salary support. At some point if you decide that you don't know what the support is, it doesn't change that you always have the software, you can always run the software. Without a solution, you basically have to rely on enterprise features then you can log on, and you have to use it. It's very insane as it's proprietary. It's very proprietary. The next thing is that when we structured our new company, we structured it in a way between the engineers who do the code and support people who fix the bugs and talk to their customers. These are the same people. I mean obviously we have to maybe meet some people who doesn't know what they're doing or who are in channels, sure. But you get direct access to engineers who do the code in the first place. We can deliver you really good support that is worth the money for you. The second thing is security. I think I'm already running this date at the time. Maybe I'll talk more about it because I'm coming up later today. But security is a very important thing for us to be invested in that. For example, we already have a good force protection in place. Next class can already have a feature where you can contact the force in classes in this specific test standard that has us. So that's already blocked. Then capability performance. So what we do is we have one going over many performance tests. So if you change your code it's very important. We already have loads of database and loads of better framework. When you move this on-going to a big fast forward time it's not enough so that it gets slower and faster. We include object store, market support and we're working on a very easy and very easy storage class to solution that we don't have to talk too much at the moment. There will be some really cool news and really precious capability of next-door completion that's coming in the next few months. And then as we general around what is different here well, we don't rely on external expertise we basically like all the key expertise in our organization where you can really, really support you want. We are a real proper company we don't have density VCs or other external investment or expensive plans when basically we all decided to move that together before we decided that look, this is something an organization company want to build together that we can work in like in the next 10, 20, 30 years. So the whole setup of what we're doing is built for sustainability. We don't have any external investment we don't want to sell to anyone. This is something we want to build for our own for the possible future which also, I think gives you some certainty that what we're doing is a little way in the future. The last thing is you can see nice charts and statistics and then you can see if you compare the development of next-door to other projects that we see with that significance moving a lot faster which I don't think is very important because it means that you will get a better future, a better future a better practice, a better release. Let's say the next or something then as I said we are not a standard plastic company where we do all the work and at some point we are operating a new version that says actually we have a new heart and that wouldn't say 50% it's like just to explain it better only a heart is actually done by employees of the next-door creation of our company. A big heart is done by others that very special measures are offered. Okay, who are our others? I think you can split this up into contributors volunteers so we have a lot of people out there who just contributed because they like it and use themselves to make something that ideal we have a lot of contributors who just work on the software and another thing is that partners and customers sometimes decide to do over next door so maybe if they're open so you are hiring you are not going to do over next door this is really interesting that's not possible and this is this is what you can do here this is really great and then also next door we have our ideas we have our vision and we want to do certain things for the expertise and we just do it but to get new features into the expertise too first of all you can come to us and say hey I really want this feature and I want to do a consulting project and then we will do this feature and then we will do this feature but the development is not ready yet but in the next few months also together with our federal data foundation that we are going to launch that will be a way to formally go under the features from customers and partners that can really do that and also decide what you want to have and then we promise to also implement that so you want to do a review but let's talk a little bit do you have any questions there are so many people how do you do it how do you guarantee the support mode that we make do you support outside code the thing is that the next job is not wanting to code base it's like getting a car that basically plug-ins and the way it usually works is a lot of contributors that start to work on apps or plug-ins that can publish it and use it and it will get experience, it can make a conference and get more basically sucked into our code and beginning it's an optional feature which we probably won't support we don't support all the apps but we don't support like base but then if this developer basically then gets more familiar with what we are doing he might even do a significant change in the code pool for example one of the big features I forgot to say there is a new app store that we are going to launch and thanks to those this is done by three time but he is someone that we work with for many many years you know quite well very good relationship it has to be supported so I agree if you are a random person and someone will come and they will change it will really be a problem but this is probably not the case what are you looking back at since these people are so important do you have a specific thing that you pay for the support in here oh we are outside oh yeah I mean this would be just obviously you don't need a support contract with us to be able to work on those features it would be interesting you talked about coding yes I mean I pay for the support yeah it's my post or work to you yeah I feel less I mean do I have to ask him to go so that's the exact question the exact model it's not finalized this is something that we basically commit developers from us we pay developers this is exactly pay developers we pay developers to work on a certain feature so this load is yes if you are a customer then you have a big boat with customers you yes I mean this is the best we invest like we thought into this feature so this is basically also an influence that we get in here with the support contract but you don't need it right you can also do it yourself or hire us to do it or hire someone else to do it and it's the same review process for the rest of our review that's not an issue if you want us to do a feature that by the way not on our loader it's on our loader then you're the only important feature customer so we have like a nice a nice page with diagram and in the page where you make CPU load and memory loader run then we have this one where we have main ones for the argue of the problem and the protection that we can't that's what some other users need to be to talk about the indication was really really a new feature so it's very clear that it already works with the Google authenticator and for example and there's more coming on this part or there's a boost and I try to get a little bit of support one of you will realize there's another feature which is open source here you can just use it so the feature you can just add a new logo and change the name and color and then it's already themed so that's also a popular feature federated sharing open source that's all I'm telling you and then obviously to the problems integration really can edit the documents in the browser you can edit them and also the limit is being collaboratively but they are basically versions of it a lot of free collaborative work I edit the documents here and this works with all these documents and people also another thing is why speak to integration so as you can know when we come to the next part we did this together we developed this week new technology that we have now that we are integrating next part at the moment so the future the next part we have to that part we already did so we see all these improvements and that we implement that we already had the part that we edit here I think it's safe to say the next part is really at the moment most advanced software in cloud space in the front side and it's all over the source for the software and I think the enterprise model process that we want to set is all definitely not all design but the software doesn't always have impressions on the first book you wrote that part going to tell you which day you have time that's easy to answer it's already out what are you going to do today I'm going to tell you how I am can you follow everything I showed you earlier as you can use it today and I'm going to tell you about it and same as you say what can you how can I get better remember the basics how can you get better for pretty long time to get better I can say the things yeah so what means we have a stage model that's important to do in the first if you're bad at coding and fixing problems but if you get older what means that serious data loss makes that a part that's serious that we don't use data for example or security issues we think security issues do you need more yes can you say this what path you want you won't survive anyway so the idea is that if you today install a server it's an operating system you choose with the key version you choose with the database you choose and with the current and next version and you install all of that and it works and you're happy with that and you're happy from our perspective to run this system out of tables you don't need an operating system or a database support you also need someone who supports the database and they also do long term support for PSP but this is not what is a protection we need to buy support for other components some others so this support stuff you wrote right last five yeah that's a project yes a normal open source version if you want to make one path or you want to save it next path I mean security fixes but this context also means that you can call us and say I have a problem here we debug it together with you and then you fix it we don't I mean we don't do that if you're not a person you're free to open an issue of it it's kind of a forum with others but that's that the process will go back into yeah that's not my position and if you decide to contribute something then it also goes in and it's not a contribution but this is this are our ideas the city's conditions of the problem here it's improved the security significantly then we have really really cool federations movement this is what Björn will show you today this is really nice really exciting about that we have the media voice conferencing I showed you earlier that we're doing audio today but I don't think we're going to get you to work on that but contact is great and responsibility is great native chat and human integration we're going to be asking will there be improvements after the reliability as a really important people complain about creating updating next to audits and falls to go with that could possibly skip major versions and we have to do that we have a new app store which makes this new team not so popular as a lot more easier but these are improvements that we can do by the expectation it's a better way this comes next year we want to work on towing based logins for all clients with the latest version we already implemented towing based of the changes that can lock out the clients more group integration more people say it means that integration school out of exchange of exchange and then we think that at this point we have to meet your voice experience we're up so far that we can quality the use type periods we can start from home call someone else we can call and then the last point was important today the next few days we have a discussion what you want to see together we can make it happen huge development if you follow the development outside you'll see that we really have a lot of people with a lot of enthusiasm a lot of good things coming in that's a huge momentum here we have a lot of people a lot of developers from some other projects with our project and I think we have a good way to work together with you guys who hear your input and I think to get around we can keep on doing what we can push for our future in the next few days not a future big question but you focus on the service side of the project yeah so I really can't say about that but I can say that the zoom clients, the desktop clients the mobile clients are absolutely key to the idea behind Mexico and will be actively developed by us and all of this feature that makes sense in the desktop will probably be great in the desktop and in the industry and we will actively invest in that I have a question because of the integration how long is the next project to other platforms and what are the limited phases and how do you actively go for collaboration that's a question that's very very important because Mexico is always if there is already an API that you can use then you can use it so there are two pieces there is the active client transfer part we hope you can use that part for that and then there is some communication part where you can invite people and observers and share requests and filming so there is some exchange going on and for that part there was no API this is really good so so we have to be doing an API three years ago we developed this API together we work together with other projects like Taiyo, for example France, they also implemented this API look out here we want to make this a standout that would be actually cause next week we will see a working group where also we use more so obviously we will be standing on going long running process but this is fully documented that who also wants to actively implement our project Taiyo technically is competitive but we still have to really try and decide who is who today it's hard it's hard