We decided to go for Nextcloud because Nextcloud is more targeted to be a collaboration platform than just only file storage, and that was very attractive. We thought that this collaboration platform is also something clients will like to use. It has a big ecosystem, and is maintained very well and we decided to offer it as a product to our customers too. We see it as a solution for real world problems, for users that want a safe storage for their data.
While they say that the demand for Nextcloud is high, the goal is to make the experience as smooth as possible, find the simplest way for everyone to have data stored in a safe place. To better explain what Nextcloud offers on certain topics, they cover it in a hosting.de blog section.
Find the feed on our podcast page and listen to the full interview! If you have not heard the previous episodes, check them there as well.
We meet Simon Lindner, software engineer at Nextcloud, the developer of Nextcloud AIO, to duscover the history and present of Nextcloud AIO, Simon's personal journey, and, of course, everything a meticulous admin wants to know about the easiest way to host Nextcloud.
We're joined by Anna and Michael "Monty" Widenius, the people behind the MariaDB Foundation, who are here to help us unpack the challenges of the open source business, vendor lock-in, and owning your data through their unique lens — and experience.
From Andy's approach to problem-solving and guiding others to his personal values that give him direction, this episode is a must-listen for anyone interested in the intersection of technology, community, and personal growth.
We save some cookies to count visitors and make the site easier to use. This doesn't leave our server and isn't to track you personally!
See our Privacy Policy for more information. Customize
Statistics cookies collect information anonymously and help us understand how our visitors use our website. We use cloud-hosted Matomo
Service:Matomo
Cookies description:
_pk_ses*: Counts the first visit of the user
_pk_id*: Helps not to double count the visits.
mtm_cookie_consent: Remembers that consent for storing and using cookies was given by the user.
Cookies expiry:_pk_ses*: 30 minutes
_pk_id*: 28 days
mtm_cookie_consent: 30 days