Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-mail-logging domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the broken-link-checker domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the health-check domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the updraftplus domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-extended-search domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the rocket domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114 Stadtsparkasse Munich facilitates customer data exchange with Nextcloud by HKN - NextcloudSkip to main content
As one of the oldest banks in Germany, Stadtsparkasse Munich has gone through many groundbreaking changes since its founding in 1824. From introducing cashless payment transactions in 1899, to converting to a computerized electronic data processing system between 1968 and 1971, they have always put modernization first. In fact, the bank was one of the first in Europe to introduce IT. In today’s day and age, they are now at the forefront of the Cloud.
Cloud centered, cloud focused
For some time now, Stadtsparkasse München has been running an on-premises Nextcloud server to exchange confidential data with customers. More recently, in 2020, the bank decided that they wanted to transfer all their internal managed systems to the data centers of competent, regional partners. With a Gold Partnership with Nextcloud, HKN stood out as an ideal partner for running their Nextcloud services.
Nextcloud offers a unique on-premises solution for financial services companies.
HKN delivers Nextcloud on its open cloud
With 25 years of experience in hosting Linux applications, HKN was more than capable to deliver quality results with all Stadtsparkasse’s requirements for a provider. From being a German based data center, to having significant migration experience, their top five requirements were met.
For several months, HKN was there throughout the entire process, ensuring a smooth migration and testing every detail. The end result satisfied employees and administrators.
By switching to HKN’s Open Cloud, Stadtsparkasse München achieved high availability, scalability, DSGVO-compliant hosting, and more.
Nextcloud Enterprise & beyond
Through HKN, Stadtsparkasse München benefits from Nextcloud Enterprise advantages like improved security, stability and of course direct access to our top engineers.
As a highly trusted financial institution, Stadtsparkasse München has always been looking a step ahead to provide the most advanced, modern, and secure solutions that deliver the best service to their valued customers in Munich and beyond. They are a bank committed to their city and with this interest in society they keep an integral focus on new apps and features.
Check out the case study to get a detailed look at how Stadtsparkasse München, HKN, and Nextcloud conquered the challenge, how they implemented it, and the final results.
“When we have welcoming communities of contributors, open source software gets better and more useful to everyone.” Limor Fried, Electrical Engineer, Inventor and Founder of open-source hardware company Adafruit We believe in this ideal and love to work with our community. We are always looking to involve more people in Nextcloud, bringing in their ideas, […]
In Nextcloud Hub 8, we introduced interactive widgets, a completely new mechanic that lets you share, access and interact with items from various apps in a compact widget format throughout your platform.
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
Matomo
_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.
_pk_ses*: 30 minutes
_pk_id*: 28 days
mtm_cookie_consent: 30 days