Are you trying to leave this out?
We need to stay as late as possible.
Before we start with the presentation,
I thank you for everybody who's organizing this room.
So thanks to Leia, to Felix and to Thorsten and also to Sven who's helping us.
So a round of applause on that.
Yeah, great.
Thanks for having us here.
We are here to talk a little bit about the German perspective on how we currently working
around building sovereign software for public sector.
And I'm here with my colleague Alex.
I'm responsible for the platform part.
I'm part of the business where we talk a bit quite soon.
And Alex, it was me here doing the products,
all the products, products, and this.
Maybe one starting point was big numbers.
It's over there.
So last year in Germany we spent more than one billion
just on federal licenses for software within the German government.
So it means there's a big question.
This is also where we don't own, where we don't have an independent
and sovereign solution.
It's not innovation for society on a long term.
So that's a point of stepping in and saying,
okay, is there a part of this money that we could use for more sovereign
perspective on that?
And this is where the center of digital sovereignty came in place.
It was founded two years ago, actually,
but one year ago we really started stepping up.
The idea came from government side saying five years ago,
okay, we have the high level of dependency in the software,
software stacks we're using at public sector.
And we need to find a way of tackling those things.
And the Zenis is a full state on property-owned company.
Our function is, we just here, the Ospo term,
being the open-source program office on one place,
being working like an institution helping the public sector
getting into those fields and into usage of that.
And also being an active solution to play out,
where we are providing things like open-desk for that administration.
And we here's already some of our colleagues here talking about
their President France and EU and we are kind in a close contact
to each other and work together on those fields.
Maybe a few words on the server entity term we work with.
So I think one of the most important things
is having a choice of choosing between options.
So being not able doing that as a public sector
is not like a big deal on negotiating and being contracts.
So you're sitting there and saying, okay, I need that.
Give me a price, I need to sign.
And if you have a choice, if you have an option, you are able to go through.
And we all know there's a lot of things to do
to be getting back to the state where we are really able to choose between options
and that way.
And also for sure we need to adapt in the way.
We need to bring our own features, our requirements into it,
and also having a strong seat on the table,
negotiating those things and defining how digital structure
is defined in the common age.
And that came to the two, one of the two main pillars we're working at the
centers.
The one is talking about products.
And the other one is building a platform where distribution
and the hospital ruling can take place for the whole public sector.
And I will hand over to my colleague.
Cool.
Thanks.
Perfect.
We are always attached to each other just like the development circle
so to say also in that regard.
Yeah, open desk.
Many of you already know of open desk,
but we call it our office and collaborations with.
And basically if you want to have a look at it,
also just visit our website and get a demo,
but also what you have is a bundle of applications in which you can have
your day-to-day productivity, collaboration and also
all sorts of communication, all in one.
I think it's really important to say that.
Open desk is something that we don't develop ourselves,
but it's always a product which is based on a big,
we call ourselves an open desk family,
but but a network of partners.
So we have a general service provider.
We have a possibility to have a software as a service solution,
but also we have a great network of partners.
There was a deaf room just yesterday in the afternoon with.
Many of the colleagues from all sorts of companies,
some of them are here and obviously also going to maybe share and talk
if you want to on their partnership with us and open desk.
So it's a product which consists of many products actually.
Yeah, I think it's really important just to,
it's always good to give numbers in a presentation.
So we launched in mid-October last year with our first enterprise solution.
Ever since we had over a thousand different public institutions
and administrations on all sorts of federal, state levels,
but also from other countries asking us,
giving us inquiries in regards to the usage of open desk,
which is more than we ever hoped and expected at the beginning,
but it's really cool and it shows that there is an urgent need
and as of January we started also providing enterprise licenses
to different partners, so to say,
and we have over 40,000 active users by beginning of this month.
So it's really cool to see that we are jumping all the time.
We had a few thousand less which we announced in January.
Now we are climbing a little bit, but we are going hopefully further up and up
in that regard, so to say, and it's really important, I think,
to show that it's not just a demo or a use case,
which we're working on somewhere in a dark room with no window,
but we have actually people using it and having it in their day-to-day lives.
It's really important and that's one part of the sovereignty aspect,
which we have is that there are different options how you can deploy it,
sometimes especially for the non-tech world,
so to say it's really, it sounds mind-blowing that you can have something
not only as a software as a service solution,
but also in a self-hosted environment nowadays.
This is something which is really important,
especially for institutions within the security sector,
for example, sometimes we never talk about that,
but there are projects with special infrastructure,
where people are thinking about deploying open-desk.
What we are also working on is a solution right now
in regards to confidential cloud computing,
because there are actually there are a few agencies,
also in the German government, which are located mostly outside of Germany,
so they need some sort of a secure access,
and that's where we are with some of our partners
looking into how we can deploy that,
also thanks to that, because some of them are in the room.
Next one.
I think it's really important, and that's the topic,
and that's where I'm going to start the story,
so to say, of why we work on open-desk, on open-code,
and what we call it, it's some sort of a developer experience.
It's not the question in regards to what kind of two we want to put you get into,
but it's the question what kind of outcome you can have
when you use this kind of software.
And if we go back, I don't know, who here is,
is some sort of a public servant or in public administration?
Okay, then the question the other way around,
who is somewhere in the private sector?
Cool.
So you are the ones who I'm going to address right now.
But basically, all of us sometimes had an idea,
and we had an idea and we wanted to give it to somebody,
and somebody within the public administration,
because we say, public sector is a super cool place to host
or to have your software in,
and then you come to the public sector,
and you say, I have an idea, and suddenly,
the public sector, which is always a great sort of,
this is some sort of a high and visual story right now,
which you are experiencing.
But then in the public sector, there are always restrictions, right?
So there are restrictions in regards to security,
procurement, we always hear that.
There are questions in regards to quality,
but also in regards to the support, which is being provided.
And we always get the question on how to get in,
and learn how can we get in.
That's the point of taking over things.
Yeah, so this is a part where we cannot only talk about
the product part of this or anything,
also we need to tackle the whole concept of access to it,
of how to get into the tooling and the using
and how to make it automated and really useful
that we have stable and long-lasting tooling.
So open code on that.
Yeah, open code is also one of these key projects
of the German government saying, okay, this is part.
We use open code is an enabler for digital sovereignty
for the whole sectors or everything around skills, services,
and solution, which we need to strengthen those aspect.
And for sure, this is being done with open source,
because this is a toolkit that has helped us
getting here very fast and much, much more
progress on the line.
In the beginning, and the whole start of a bit
telling about the history of open code, which is two in a year.
So now we've got to be in charge of sets
since one year now with the zeniths.
And it started as a software directory for the public sector,
and we now discussing more and more around
what does it mean as a platform for digital sovereignty?
And in this, I was called the version one of open code
when to get these more, all this question
around the entry door, it was really important
defining for the sector and the political aspect
and what kind of, we need a software directory
where we start collecting all those open source solutions
because we realize there is a lot of this everywhere,
also in the public sector, but we don't have any overview
and that makes it really difficult getting into cooperation
which is one of the key things of open source.
So it's a big issue having a place there is important.
So this was step one, then for sure,
make a definition what is open source for the public sector.
So yeah, this is not a new invention for sure.
We used the OZ definitions, just made it
in a more public sector, suitable effort
and communication layer, usable for that as well.
And then we started talking about license catalog
because we have 13,000 public sector institutions in Germany
when they all start getting knowledge about all the 500 different open source
licenses out there on the country.
It will never lead us anywhere.
And these are these kind of questions we need to answer
when a public sector wants to sign contracts around that.
So we have now with open code one place
where we legally checked over 500 open source solution
that's all publicity on our website
and made an allow list for the public sector saying
when you have a component which sets open source
and it uses license and it's good, you can go proceed
for the next level of your contracts.
And then sure it needs a platform collaboration.
So any member of the public sector needs
as a possibility collaborates there.
And there's an unrestricted and freeway.
And the last one is talking a lot about policy and government.
So figuring out how can we now, when we have a place like this,
how can we bring in the general daily processes of government.
So this was the open code version one.
And this is for sure this is how all the topics we are discussing here
all about this.
This covering and understanding open source sharing developing code
for sure it's finding and using software.
It's documenting and sharing all these knowledge.
It's offering participation on forums and in our example
we offer the discourse and where a lot of groups
are changing their ideas and their experience
from rebuilding community structure around that.
And we give direct support to public sector members
when they have questions how can I get onboard for this
and their first steps for me to get into that.
And for now we have around 4,500 users in Germany
or around the projects.
It's more than 1,000 public freeway level projects
right now on the platform.
Even more on the private side because sometimes needs time
or have rather been into to work together
and to get into using of these two links.
And they also start now realizing,
if I use something like a repository and like a good lab,
there are two links like static pages.
They make my life easier getting into website deployment
out there.
And this is something I don't need to have a long procurement process.
This is two links all there.
And we can really make things much,
it's free in the way because it doesn't cost extra money
and you can do it by your own.
So it's self empowering in a broader way.
So one of these overall layers on the platform open code
is this being a community of many communities.
So we don't have one community is more like we try having
with our formats.
We creating a zenders.
A perspective saying we want to be having
an overview of what kind of communities are out there
and how can we bring them together.
What's what's useful there,
who needs maybe to talk to whom and to learn
and to share experiences and stuff like that.
We have two links which we get now out of these two
box we have there and which we get more and more used
by members of ministries and stuff like that.
For example, one of this here is really interesting.
There's a federal layer, the highest board,
which we're just talking about.
The architect, the IT architecture policy in Germany.
And their process so far was sending emails
and bringing all those answers year by year together
and having an negotiated policy in a way.
But for us it might be quite easy.
OK, use the repository.
Use it as a transparent way of organizing those content.
And we need to get some steps,
but then we also get a lot of possibility we never had before.
So in this example we have a repository in the middle
and we have a front end which makes it really easy
comparing the different version,
also colored layer for people who might not really
have this one or see this on a get few.
And on the output layer we can generate
the next set of these versions,
also generating accessible PDF document,
license free or other machine-readable formats
which might be used to connect with the next steps
and processes we have there, but in this we accept.
So the collaboration platform itself with this tool
starts getting new concepts of how to use it.
For the sector it's really big step.
I know from many people in the room it might not be,
but it's like a culture shift we're seeing right now
which is I guess for everyone for us really important.
We have a batch program.
This is all about how can we record missophic quality.
And currently we are on our way next month starting with the first batches
in this case.
When you have a repository in our software catalog,
makes it really easy to understand,
what can I use it?
So there's a question in public sector.
Yeah, this is software, but is it real?
And can I use it and is it secure and all this stuff?
So we think it's important that we add those extra information
as much as we get an information on the software catalog
and ensuring that there's a first understanding of,
okay, it's a real thing and it's used by others.
And it's also driven and run in operational environments
and all this stuff.
And maybe it's even already a bit of CV checked and all those things.
So this is really important where you're getting open source
and software and solutions into public sector.
And then there's more, again,
when it comes again to the server and it's high,
we say, okay, this platform part,
this has kind of a machine room in it.
And on server and it,
okay, when we talk about server and products like Open Desk,
we now also need to think about how is this components
of Open Desk, how gets they distributed?
And what is the software development,
the software supply chain underneath,
that that's playing a role in that way,
because only if we are able to look at this as well,
we really can have and so when perspective as public sector
means when we talk about Open Desk,
we're talking about container technologies for sure
and when it comes to container technologies,
we need to raise a lot of question as actors.
So the first one is stability in a way.
So where is actually how reliable is these container distributed for us?
So it's, or the question on a little bit other frame,
what does that happen was our digital infrastructure
when Docker happens down or has a kind of a new entry key on that.
So I guess a lot of people in the room would stop being,
okay, it's going to be a problem for me and maybe,
the colleague says, well, and it's a lot of work to be done.
So but actually the main point is we are not really
currently prepared around situations like that
and the problem and it might be really big success
in the last 20 years in the digitalization,
but we kind of proceed the next decade on that.
Security at all on this supply chain,
what is the chain of a way,
this container came to me,
can I have a look into it now, not really,
so no chance on this way.
And who created this container anyway?
So I would say from the, okay, some of these containers
we're using there just from the internet,
so I don't know more.
I guess on content wise,
it has not been always a good idea,
just taking the stuff from the internet and it's
think we don't should do it with the core components as well.
And then we had a lot of talks around,
and I think there's a whole deaf room as well,
and yesterday we really go talk about the ass bombs.
Yeah, there's this ass bombs and it looks good,
okay, we have a long list of things on it,
but we are not really having the two things working with it.
Making detection and allergies and all these stuff,
which we need to have this as a really good tooling,
ensuring this is proper software.
So we are highly depending on those things,
so we have to address this as public sector,
meaning being an infrastructure provider by itself,
going into this role and offering solutions on that,
thinking about offering decentralized container,
image supply infrastructure,
so also there, we just tiered on the news side,
but it means on structural infrastructure layers,
but it also says it's really important if you want to be stable on cloud.
There's a lot about hardening and ensuring the container safety.
For now, we don't really have,
there's a correct rules and criteria as negotiated,
that makes it able to put a stamp on the container and say,
okay, this is the rules and criteria we need in the public sector.
It's still a lot of work to be done working on that.
And then all these two links around as bombs and around.
For us, at open-coded means,
this is our next list of things we currently want to welcome,
saying this is really what we need on this supply chain.
And when the distribution infrastructure,
we want to provide a secure build and development environment
for developing those service,
we already put in an attestation service around open-desk.
We want to establish this registry for all these artifacts
that we can use and also rebuild,
so being able to really know what's in there, what we're using.
We need to negotiate more on the criteria for this supply chain evidence
and builds.
And all these build up on a more decentralized distribution concept.
Because we're not going to grab one again.
What's our relation, so to say, to the partners,
which we work with at open-desk,
and what comes with contribution, so to say, in that regard.
Feature requests we do, it's a long process of planning.
Maybe two colleagues can raise their hands,
run a and victor.
If you have questions in regards to product or tech,
these are the guys who are building open-desk.
And everything we do, two main things I think to mention.
First, all the contributions, which we do,
are part of the open-desk community edition.
We don't fund anything which is behind,
behind some sort of a fence.
That's one thing and the other thing is that everything that we do
is always upstream within the products.
So whenever there is something that we invest into one of the products,
it always also benefits,
or is beneficiary for the entire community.
Next question.
One of the.
Could you maybe talk about your collaboration with France and the less we?
And I also understood that the netlets are entering that collaboration, so.
Yeah.
We had, yeah, thanks.
Thank you, my own card.
The question is in regards to how we work with France and with the Netherlands.
We had a session this morning already on that regard,
and we will have one, the one after the panel.
So it's in half an hour or so.
So you can see the results of our collaboration, so to say.
Basically, we work together on joint projects because we see that digital
sovereignty does not end at once borders.
And you can use the same open source tools in different products and sweet.
Yeah.
So the question is, if we want to do something with other countries,
do we need an umbrella or is it grass roots?
I think so far and it's proven as properly that grass roots is a good way to start that.
But at some point you will need an umbrella.
But the umbrella should not dictate because usually whenever there is an umbrella,
someone in the grass roots or in the bottom sort of phase holding it,
and that should be kept in motion.
That way.
Could you explain to your plans on the espontal chain?
Well.
Exactly.
Currently, I think I will maybe get to back to this one.
The question was to expand on the espontal chain, which is just mentioned.
So what else is the thing?
We currently working on this batch program saying, OK, there is a lot of open source
tooling around which helps us doing analysis and espont creation.
So we use, for example, the open source as the or toolkit or or the three
before containers scanning and all these stuff.
We also using for a software catalog and standard, which is called public
in the summer.
And the ideas we need to bring the results of this running and automated as much as
possible.
And also scaling it up to the eggs.
So make it possible.
That's the reality.
It's get aggregated to something which I really can see in the software catalog and
giving me first impression of this.
For example, OK, the CV is scanned and nothing found for today and for now.
So for example.
But I think we need to expand this quite a lot more because all around this,
having a project like open desk with maybe thousands of entries on the espont.
It's like it's a really huge thing getting it automated and
and day by day generated and having good analysis on this.
So I think there needs to be developed much more on the tool chain for now.
OK, there's many more questions.
Please reach out.
But we have time for one.
One question.
OK, one question.
You decide.
I'll be there.
I guess I want to open desk a project.
It's only for the software.
I always want to say something in our line of settings.
Let's explore.
If you have line also for the open.
The.
I get the idea and maybe that's a good user so the question was whether it's just the web or maybe also an operating system and let's see each other next year.
And then we will talk about that.
And.
Before we go before we go before we go we go we do something really German
And it's called store's lifting.
Please open the door and open the windows and you will see each other on we see each other in the next panel. Thank you guys