Seven years ago on this day, Frank Karlitschek announced a project at Camp KDE in San Diego to help people protect their privacy: ownCloud. Today, he and the team that started this effort are still working on this exact same thing (though under a different name). We’re super proud of the huge community we have built over the last 7 years and the millions of users who have been able to take back control over their data thanks to our work!
We have two videos to share, one in which Frank announces this project and another from the Nextcloud Conference where the team from the first years, from the very first ownCloud meeting ever, recalls some fun memories!
How it started
On January 17, 2010, Frank Karlitschek announced the ownCloud project with the goal to develop a free and open source replacement for Dropbox and the like. The goal was to put users back in control over their data.
By the end of the first year, Frank had already announced ownCloud 1.0 and followed it by 1.1. In April 2011, a first meeting with 5 participants and supported by the KDE community kicked off the development of ownCloud 2.0. The write-up on the KDE news site already points to some of the jokes recalled in the video from our Nextcloud Conference below…
The participants where Frank Karlitschek, Jakob Sack, Robin Appelman, Jan-Christoph Borchardt and Arthur Schiwon. Indeed, all people you will know from our contributor page, with four of them part of the Nextcloud GmbH Team servicing enterprise users of ownCloud and, now, Nextcloud, for many, many years!
We’re all very proud to be a part of this project and we look forward to many more years of taking care of you, as users, building a product we can all be proud of.
Nous vous présentons aujourd'hui Nextcloud Hub 26 Spring, notre version anniversaire. Cela vous offre encore plus de choix en matière d'outils, une interface utilisateur optimisée, une collaboration fluide, ainsi qu'une nouvelle stratégie de plateforme qui permet aux développeurs de tirer davantage parti de notre vaste écosystème. Conçus ensemble, pensés pour l'avenir.
Nextcloud Hub 25 Autumn facilite le démarrage d'une collaboration puissante tout en gardant le contrôle de vos données. Des mises à jour globales du design à l'amélioration de la convivialité et des performances, découvrez notre dernière version dans ce blog.
Les organisations, petites et grandes, ont besoin d'un moyen d'assurer la résilience et la souveraineté numérique de leurs opérations - une alternative à Teams, open-source et respectueuse de la vie privée. Aujourd'hui, nous vous présentons cette solution - Nextcloud Talk.
Nous vous présentons une mise à jour majeure de l'assistant Nextcloud IA, ainsi que de nouvelles informations sur notre collaboration avec plusieurs grands fournisseurs d'hébergement tels que IONOS et OVHcloud pour vous proposer des options d'IA en tant que service !
Bechtle et Nextcloud ont annoncé aujourd'hui une plateforme de collaboration entièrement administrée pour le secteur public, qui ne nécessite pas d'appel d'offres et peut être déployée immédiatement.
Découvrez comment passer de ownCloud à Nextcloud. Notre outil d'aide à la migration fournit des informations sur le processus de migration et vous aide à effectuer la transition en douceur.
Want to receive notifications about new messages without relying on Google’s servers? We’ll show you how to set up UnifiedPush for Nextcloud Talk in three steps.
Let's take a closer look at Nextcloud Hub's key components and how they come together to create a unified collaboration platform for your organization.
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*: 13 months
mtm_cookie_consent: 30 days