News
Das Neuste aus der Welt von Adfinis SyGroup
If you’re looking to implement Terraform, are you aware that Terraform alone isn’t going to cut it? Sure, it’s a great tool, but have you thought about how it integrates with your IT landscape? And about retraining your operational engineers? To help you, we present 5 building blocks to really
future-proof your infrastructure with a successful implementation of Terraform.
We’ve tried it all before, haven’t we: in order to reduce complexity, we introduce another piece of technology and think we’ve found the holy grail. Only to discover a few months later that the technology in itself is just another piece of equipment. You’re not going to repair any leaks just by having a wrench in your shed. But, it is
a great tool if you know what you’re trying to achieve and
if you know how to use it effectively.
The same’s true for HashiCorp’s Terraform. IT Is a great piece of equipment for managing your infrastructure, lean and mean. Nevertheless, if you just buy the tool, but have no clue how it best serves your business, you’ll be wasting your money. Which of course, is a shame, because the opportunities Terraform offers are a game-changer for any company wanting to safely provision, and easily manage and scale a multi-cloud infrastructure using only code.
But not to worry, we’ve got you covered. We offer you the five building blocks for successful implementation and use of any Terraform roll-out:
1. Coding your infrastructure with Terraform
It’s a bit of an open door of course, but in order to work with Terraform, you’ll need to learn how
to work with it. Obviously, you could experiment yourself, it’s that easy; but if you want someone to show you the ropes, you can always follow our training. We’ll teach you how to build, change, and destroy infrastructure. But you won’t just learn how to work with the easy, human-readable configuration language, because the training will cover the following aspects.
2. The role of testing in successful infrastructure as code
Thinking about testing before
you embark on your infrastructure as code journey is important for two distinct reasons. First: Your developers have a clear idea about the goals you want to achieve and the requirements the infrastructure needs to meet. They’ll be checking their way through their work and that’ll be very satisfying. Second: you’ll make sure the written code actually does what it should do, and
you’re ensuring that connected, previously written code isn’t negatively impacted.
3. Knowing what you did and when with GIT version control
It’s not only testing that ensures that your infrastructure as code works, we encourage you to use GIT for version control as well. GIT enables you to track the changes you’ve made to your code. This is essential if you want to know exactly what you have changed over time. Reverting to specific versions is also possible with GIT. When you’re working as a team on the code, GIT can combine changes made by multiple people, merging them into one version. In other words: GIT helps you keep control over your infrastructure as code.
4. How does Terraform land in your ecosystem?
Terraform is never a standalone product but is often integrated with other on-prem and cloud technologies. Therefore, before you deploy Terraform, you need to know its dependencies and how well it all works together. Plus: have you considered the open source nature of Terraform and your journey to the cloud? Terraform is not only a fine tool for managing your single-cloud infrastructure, but it’s ideal for managing all your clouds. You’ll be able to match different workloads with different clouds, making it possible to build a vendor-independent infrastructure, ensuring that your company is agile, flexible and scalable.
5. Building a developers’ culture
Last, but certainly not least: when you’re adopting infrastructure as code and terraform, you have to think about retraining your operational engineers and
building a culture in which thinking in code is encouraged. For example: a machine is not a pet, but more like a herd of cattle. This means that you don’t manually manage each machine, but use code to manage all
your Machines. Future-proof your company by thinking like a developer, solving issues with code, and scaling up as you grow.
How we can help
These 5 building blocks will help you successfully implement Terraform and use it to achieve your goals. As we’ve said, our Terraform training will not only help you understand its syntax, it will help you with all the other steps as well: start with testing, learn how to use GIT, let it land in your ecosystem and build a developers’ culture. Are you ready to take the next step towards a future-proof infrastructure?
Free Software and Open Source never was “just a technology thing”, it’s a cultural shift; that’s why the movement also has a role model function
When I first got exposed to F/OSS, the world was mostly powered by proprietary software and I didn’t have access to the ‘source’ of the technology that powered my computer. I had no clue how a compiler worked, how a kernel was created or how a photo got rendered onto my screen. Then my good friend Lukas showed up with a bunch of SUSE Linux CDs, and the journey down the rabbit hole began. Countless nights of experimenting, reading manuals, building ‘Linux from Scratch’ and posting on Usenet evolved into being part of one of the leading F/OSS services providers in Switzerland.
Attending conferences, meetups, events, trainings, being involved in non-profit organizations like CH Open, TDF as well as working on a small Linux distribution have all been very rewarding experiences. I made countless friends from all over the world, who showed me new tricks and opened my horizon to new ideas. Through conversations, I also learned to see the world through their eyes. It became clear to me, that F/OSS is not just a technology thing: the movement is about bringing people together, removing barriers and making IT more useful for society.
At Adfinis we try to create an environment where people interested in working on F/OSS find a place where inclusion is one of the main pillars. No matter your gender, age, cultural background, sexual-orientation, political or religious orientation: we welcome you at Adfinis!
Inclusiveness is common sense, and we believe it should be something every organization should not only strive for, but actually fight for. There is no place for toxicity, mobbing and exclusion.
Whilst we are not involved in the current FSF discussions, we urge the board of FSF to find a solution to the severe impact their actions have had on the global free software and open source community.
With Leadership comes responsibility. If leaders do not fully embrace inclusion, they damage their cause and weaken their organization. We therefore ask FSF to take a clear stand on being an inclusive and friendly organization and to live up to its own role model function.
Written by Nicolas Christener, CEO & CTO at Adfinis
It’s with great pleasure that the jury can announce the winners of the LibreOffice Template Contest 2020.
We got over 30 different template submissions and it wasn’t an easy task to narrow the list down to six winners. Thanks to the diverse jury team consisting out of a total of nine people from the community (5), the Document Foundation (2) and Adfinis (2) we came up with a balanced view regarding the three major evaluation criteria (creativity, usefulness and technical expertise) and are happy to announce the winners of this year’s contest!
- Ahmad Bayhaqi, “Line Impression” template for Impress
- David W. Snow, “DWS Novel” template for Writer
- Hervy Qurrotul Ainur Rozi, “ZamZam” template for Impress
- Benjamin Peng, “Minimalist Resume” template for Writer
- Ermind Alita, “Bumi Samudra” template for Impress
- Sven Hielscher, “Style / Feature Preview and Boilerplate” template for Writer
Congratulations to the winners!
Thanks again to everybody who contributed in this contest, we will raffle hoodies, shirts and backpacks among all participants!
We’re still checking with the awesome people from the Document Foundation how and if we can make the templates available to a broad audience. In order to get any template into the upstream LibreOffice installation package, a lot of work needs to be done (especially in terms of internationalization) – one other possibility is to use the LibreOffice Extension functionality and thanks to Heiko Tietze all the sumissions are now available through the extension directory (see at the bottom for the complete list).
Furthermore, we also discussed to blog a bit more about what users should consider regarding templates (e.g. don’t use direct formatting and instead use styles, or work with master slides, etc.). If you’d like to step in and help us with that: feel free to contact me directly.
Thanks again to all the awesome people who made this possible! I hope we can organize a follow-up contest later on this year and will communicate it on the usual channels.
The Adfinis team wishes the whole LibreOffice community all the best and says “THANK YOU!” for making this such a wonderful F/OSS project!
The sumitted templates (winner first, then no particular order):
- [winner] Ahmad Bayhaqi, “Line Impression” template for Impress
- [winner] David W. Snow, “DWS Novel” template for Writer
- [winner] Hervy Qurrotul Ainur Rozi, “ZamZam” template for Impress
- [winner] Benjamin Peng, “Minimalist Resume” template for Writer
- [winner] Ermind Alita, “Bumi Samudra” template for Impress
- [winner] Sven Hielscher, “Style / Feature Preview and Boilerplate” template for Writer
- Peter Grilj, “Vaux” template for Impress
- Mohammed Altaher Bettayeb, “Tiles” template for Impress
- David W. Snow, “DWS Technical Book” template for Writer
- Kálmán Szalai, “Speed Advantage Blue” template for Writer
- Mohammed Altaher Bettayeb, “Safari” template for Impress
- Peter Grilj, “Conference White Paper” template for Writer
- Jun Nogata, “Project Green” template for Impress
- Luís Monteiro, “Weekly Meal Plan” template for Writer
- Daniel Maluszczak, “Sunny GradientTemplate” template for Impress
- Ilija Culap, “Simple Blue” template for Writer
- Utku Berberoğlu, “Signs” template for Impress
- Kálmán Szalai, “Retro 64” template for Writer
- Miha Kočar, “Love OpenSource” template for Impress
- Kálmán Szalai, “Clear Advantage Blue” template for Writer
- Peter Grilj, “Business Modell Canvas” template for Calc
- Jun Nogata, “Marketing Blue” template for Impress
- Rainiero Herrera Guzmán, “Dinamic Format Tables” template for Calc
- Mohammed Altaher Bettayeb, “About Me” template for Impress
- Kálmán Szalai, “Greenfield Documentation” template for Writer
- Benjamin Peng, “Basic Syllabus” template for Impress
- Mohammed Altaher Bettayeb, “We Care” template for Impress
- Kálmán Szalai, “Well Documented Grey” template for Writer
- Andreas Kainz, “Simple” template for Writer
- Brice Hardy, “CV” template for Writer
- Ilija Culap, “Orange Ribbon” template for Writer
Note: many templates need additional fonts to shine and look how the designer intended; the fonts are F/OSS and can be found on the usual place (GitHub, Sourceforge, Google Fonts, etc.) or using your prefered search engine. As most fonts are quite big nowadays (some are >1GB) we didn’t bundle them with the documents.
We kindly ask all contributors to register on the extension platform and ask the admin to take over the maintainership of his/her extension.
Galera is a multimaster MySQL cluster that provides virtually synchronous replication by certifying so called “write-sets”, which ensures that all database transactions are committed on all cluster nodes. The software is developed and maintained by Codership.
This article is a compilation from material targeting the Galera cluster in general, mixed with insights gained in Codership training sessions. We hope it sharpens the readers understanding of the clustering topic for MySQL and its variants such as MariaDB.
The Adfinis team is more than happy to support you, if your organization needs to run highly available MySQL workloads and you’d like to get some helping hands in planning, building and running such a service.
Multimaster Capability
In comparison to traditional leader/follower replication setups, a Galera cluster promises increased availability and the ability to read and write from/to any cluster node. However, replacing a single server database backend with a Galera cluster is not necessarily transparent to the application, thus, cannot always be the recommendation.
Before replacing a traditional database setup with a clustered one, it is crucial to be aware of the changed inter-node isolation levels and limitations in order to estimate the potential impact on workloads. Generally speaking, the isolation and order of transactions will be be affected by the replication protocol. Compared to a response from a single node server, the application might not always get back the expected answer and break. For instance, if results for repeated queries made on separate cluster nodes don’t provide the same results or a read query is performed directly after a write query (read-after-write) and the read query is executed on another node.
Often times, proxies or query routers are installed in front of the cluster direct application traffic to the correct nodes. This mimics the behavior of a single database server. However, these components should be built in a highly available manner as well, which increases the cost and complexity of the entire solution.
Automated failover mechanisms are usually applied sparingly in traditional replication architectures, because data consistency is at risk in split-brain scenarios. Fortunately, these mechanisms are superfluous with Galera cluster due to the multimaster capability. Also, additional cluster nodes can increase the fault tolerance at the node level rapidly. The overall availability at the cluster level depends on the amount of available failure domains, which are mostly limited by the number of datacenters for on-premise deployments.
Galera Manager: Clustering at the Push of a Button
We have seen in the previous discussion above, that failures on cluster level are harder to mitigate with limited resources, especially in locally constrained environments. Luckily, the cloud allows us to distribute workloads across availability zones easily in a cost efficient manner. When nodes are distributed across fault domains, deployments in the cloud can improve the clusters availability from the start, without spending too much thought about resiliency at the cluster level.
Galera Manager is a solution that accelerates the logistics around clusters and nodes on AWS. Additionally, it can be used to monitor existing clusters.
The automatic deployment of Galera nodes using the Galera Manager is primarily tailored to deployments on AWS and is still in the beta phase as of today.
We hope to see support for other deployment targets as well. Having a cloud agnostic deployment tool for Galera would greatly increase platform independence as one could easily proivision a database cluster among different cloud providers and greatly reduce the vendor lock-in of the “database as a service” offerings from major cloud providers.
Because information on deploying Galera clusters on AWS is widely available, this article elaborates on cluster deployments using Linux containers (LXC) and the integration of so called “unamanged” nodes, which is only briefly discussed in the documentation upstream.
Testing the Galera Manager with LXC
If you want to test how the Galera Manager works locally before you do your first deployments in the cloud, we have explained the necessary steps below.
Notes for reproduction: The Ubuntu 18.04 VM on libvirt was allocated 2’048 MB RAM and 2 CPU cores, which was sufficient to launch three LXC based Galera nodes. Also, the installation script does not complete on Ubuntu releases greater than 18.04 (bionic).
The Galera Manager can be installed by invoking the installation script:
root@gm01:~# curl -sO https://galeracluster.com/galera-manager/gm-installer
root@gm01:~# chmod +x gm-installer
root@gm01:~# ./gm-installer install
INFO[0000] OS Detected: Debian / Ubuntu / Linux / bionic / 18.04
...
The installation log is located at /tmp/gm-installer.log
After the installation of Galera Manager, the base configuration for a new cluster can be defined in the Web UI:

Fig. 1: Create a managed Galera cluster
To deploy the actual nodes as containers, it is recommended to have at least a minimally configured LXD service ready:
root@gm01:~# systemctl start lxd
# Initialize LXD with sane default values for testing purposes
# https://linuxcontainers.org/lxd/docs/master/#how-do-i-configure-lxd-storage?
root@gm01:~# lxd init --auto
# Give the Galera Manager daemon (gmd) access to the LXC socket
# https://linuxcontainers.org/lxd/docs/master/security
root@gm01:~# usermod -a -G lxd gmd
root@gm01:~# systemctl restart gmd
The bootstrap script for new Ubuntu nodes assumes that the AppArmor utilities are available in the container. This assumption does not hold true for the default LXC base images which are launched using the Galera Manager. Furthermore, these images don’t include rsync, which will be needed for the state snapshots transfer (SST) between the nodes. Therefore, we should tweak the image slightly before launching the cluster:
# Ubuntu 20.04 (focal) image download from default remote "images:"
root@gm01:~# lxc launch images:ubuntu/focal test
Creating test
Starting test
# Cleanup test image
root@gm01:~# lxc delete -f test
# Show fingerprint of the image
root@gm01:~# lxc image ls -cf --format csv
c3e80efdcd15
# Unpack the rootfs of the image
root@gm01:~# cd /var/lib/lxd/images/
root@gm01:/var/lib/lxd/images# unsquashfs c3e80efdcd15823ef2f372955915f94f65a24a0444e5c32dada6a72ba6e31cd8.rootfs
# Prepare chroot
root@gm01:/var/lib/lxd/images# mount -o bind /dev squashfs-root/dev/
root@gm01:/var/lib/lxd/images# mkdir -p squashfs-root/run/systemd/resolve
root@gm01:/var/lib/lxd/images# mount -o bind /run/systemd/resolve/ squashfs-root/run/systemd/resolve
# Enter the image chroot and install the missing utilities
root@gm01:/var/lib/lxd/images# chroot squashfs-root
root@gm01:/# apt install rsync apparmor
exit
# Cleanup mounts
root@gm01:/var/lib/lxd/images# for m in $(mount | grep squashfs-root | awk {'print $3'}); do umount $m; done
# Create new rootfs image
root@gm01:/var/lib/lxd/images# mksquashfs squashfs-root squashfs-root.rootfs
# Backup original rootfs
root@gm01:/var/lib/lxd/images# mv c3e80efdcd15823ef2f372955915f94f65a24a0444e5c32dada6a72ba6e31cd8.rootfs{,.bck}
# Replace current rootfs of the image with the patched rootfs
root@gm01:/var/lib/lxd/images# mv squashfs-root.rootfs c3e80efdcd15823ef2f372955915f94f65a24a0444e5c32dada6a72ba6e31cd8.rootfs
Admittedly, this process seems esoteric, but unfortunately there exists only a limited selection of base images in the Galera Manager without the option to download from a specific LXC remote. A setting to specify an exact LXC image would greatly simplify this process.
Afterwards, the (Centos or Ubuntu based) LXC container nodes can be added to the cluster in a convenient fashion:

Fig. 2: Automatically deploy LXC container nodes with the Galera Manager
Follow the cluster setup process in the Browser UI or via the Galera Manager log files:
root@gm01:~# tail -f /var/log/gmd/host-*

Fig. 3: Galera LXC node deployment status
Monitoring Unmanaged Nodes with the Galera Manager
Existing clusters can be integrated with the Galera Manager as “unmanaged” nodes. This running mode assumes that the initial configuration and deployment of the node already happened before the node was registered in the Galera Manager. Also, in comparison to the LXC containers from the last section, these types of nodes are not configured automatically (i.e., unmanaged).
But don’t fret. The database administrator training course offered by Codership is designed to equip administrators with everything needed to deploy, configure, join and maintain cluster nodes manually. Feel free to contact us to get more information about the available trainings.
For sake of simplicity, we will simply reuse the suggested MySQL configuration from the previously provisioned LXC containers as a base configuration. Also, we will again install the most “pristine” version of the “Codership” Galera 4 cluster using the original MySQL 8 as the base version.
For the manual setup on unmanaged Ubuntu 18.04 virtual machines, follow the excellent documentation upstream:
root@galera-n:~# cat << EOF > /etc/apt/sources.list.d/codership.list
# Codership Repository (Galera Cluster for MySQL)
# https://galeracluster.com/library/documentation/install-mysql.html
deb https://releases.galeracluster.com/mysql-wsrep-8.0/ubuntu bionic main
deb https://releases.galeracluster.com/galera-4/ubuntu bionic main
EOF
# Receive the repository signing key from the keyserver
apt-key adv --keyserver keyserver.ubuntu.com --recv BC19DDBA
# Non interactive install of Codership Galera components,
# latest Galera 4 on top of the MySQL 8 base version
export DEBIAN_FRONTEND=noninteractive
apt update && apt-get install galera-4 galera-arbitrator-4 mysql-wsrep-8.0 -y
Disable AppArmor for the MySQL daemon for testing purposes with the unmanaged virtual machines (running their own kernel) as advised in the recommendations upstream:
root@galera-n:~# ln -s /etc/apparmor.d/usr.sbin.mysqld /etc/apparmor.d/disable/
root@galera-n:~# apparmor_parser -R /etc/apparmor.d/disable/usr.sbin.mysqld
root@galera-n:~# systemctl stop mysql.service
Next we are ready to apply some initial Galera configuration to our unmanaged nodes:
root@galera-n:~# cat << EOF >> /etc/mysql/mysql.conf.d/mysqld.cnf
# Listen on all interfaces
bind-address = "0.0.0.0"
# WSREP Options
wsrep_on = ON
wsrep_provider = "/usr/lib/libgalera_smm.so"
wsrep_cluster_name = "unmanaged-01"
wsrep_node_name = "$HOSTNAME"
wsrep_cluster_address = "gcomm://galera01,galera02,galera03"
wsrep_node_address = "$HOSTNAME"
wsrep_sst_method = "rsync"
EOF
Note that the above commands on the Galera nodes galera-n are usually run with an infrastructure automation tool of choice, such as Ansible.
To bootsrap the primary component of the unmanaged cluster from any node, run:
root@galera-01:~# mysqld_bootstrap
The remaining nodes can be joined by starting the mysql daemon:
root@galera-n:~# systemctl start mysql.service
To integrate the Ubuntu based cluster VMs into the Galera Manager, simply define a new cluster and add them as “unamanged” nodes through the UI:

Fig. 4: Add unmanaged nodes to the Galera Manager
Finally, the manager presents us with a default dashboard and allows us to add more graphs for certain variables in order to monitor the health of the cluster.

Fig. 5: Monitor unmanaged nodes with Galera Manager
Cluster Operations with Galera 4
We briefly introduced monitoring with Galera Manager above, but there is actually a lot more to it. As we have seen, the manager provides you a perfect overview of important cluster variables. However, in reality you probably need to go far more into details on additional topics regarding backup, cluster recovery, monitoring, logging, performance tuning, write-set cache size calculation, additional wsrep options, different Galera cluster version and more. We’re more than happy to help you with this and bring in the Adfinis expertise. We mange critical infrastructure since more than 20 years and have a team of highly skilled engineers who are happy to assist you in planning, building and running a Galera cluster.
We hope this article was able to provide an overview of some deployment strategies for test-driving Galera clusters with or without Galera Manager (unmanaged nodes). If you are curious to find out more about the latest improvements in the most recent release of Galera, feel free to contact us or head over to the official announcement/changelog for Galera 4 on MySQL 8. Among others, it includes exciting changes regarding:
- Streaming replication, enhanced support for large transactions
- Group commit
- New mysql system tables
- Synchronization functions for custom logic based on transaction IDs
Lastly we would like to refer again to the high quality video material and documentation freely available on the Codership page.
If you found this material useful, share this post or send us a feedback on info@adfinis.com
What Adfinis can do for you
Adfinis offers managed services for all kind of technologies that run on Linux. Be it on-premise, in the cloud or in a mixed environment. We are interested to hear about your requirements and are eager to find out how we can help you in planning, building and running services for you, so your team can concentrate on the core business of your organization. Contact us now or find out more about our managed services.
If you’d like to make a deep dive into the Galera topic on your own we can also recommend to check the Codership online trainings which are offered as classes via Zoom, led by professional instructors guiding through installation and configuration of the Galera cluster.
Links and References
Link to the training course:
https://galeracluster.com/library/training/courses/index.html
Galera transaction isolation guarantees:
https://galeracluster.com/library/documentation/isolation-levels.html
Migrate to Galera cluster:
https://galeracluster.com/library/training/tutorials/migrate.html
Galera Manager documentation:
https://galeracluster.com/library/documentation/galera-manager.html
Manual Galera cluster installation:
https://galeracluster.com/library/documentation/install-mysql.html
Disable AppArmor for Galera cluster installations:
https://galeracluster.com/library/training/tutorials/galera-installation.html#disabling-apparmor
Galera 4 for MySQL 8 Announcement:
https://galeracluster.com/2020/05/galera-cluster-4-for-mysql-8-is-generally-available/
https://galeracluster.com/library/whats-new.html
Video material and full documentation:
https://galeracluster.com/library/training/videos/index.html
https://galeracluster.com/library/documentation
Getreu dem Motto: “Branding erfordert Hingabe; Hingabe, sich stetig neu zu erfinden” haben wir uns entschlossen, im Rahmen unseres Rebrandings auch unsere Vision und Mission aufzufrischen. Für einmal bedeutete CI/CD also nicht Continuous Integration und Continuous Delivery, sondern Corporate Identity und Corporate Design. Was hat sich bei der Adfinis in diesen Gefilden in letzter Zeit getan?
So viel Vorweg: Wir sind immer noch voll und ganz Open Source verschrieben und kämpfen eifrig dafür, den Vendor Lock-In proprietärer Lösungen zu reduzieren.
Corporate Design
Wie schon 2020 kommuniziert, wurde aus der Adfinis SyGroup, neu die Adfinis. So neu ist dieser Name jedoch gar nicht, denn vor der Fusion (2012) gab es sowohl die Adfinis, wie auch die SyGroup. Wieso also wieder “Adfinis”? Ganz einfach: Ein Grossteil unserer Kunden und Partner nannten uns bereits einfach “Adfinis” und zudem erschien uns ein kürzerer Name schlicht handlicher.
Komplett neu ist aber unser Logo, mit dem wir unsere Identität auch visuell ausdrücken und transportieren. Auf den ersten Blick vermag es nur ein “A” für Adfinis zu sein, auf den zweiten oder dritten Blick lässt sich aber erkennen, dass sich hinter der einfachen Struktur weit mehr Tiefgang verbirgt. Zum einen lässt sich ein offenes Schloss erkennen, welches das Aufschliessen des Vendor Lock-Ins symbolisiert und so die Entfaltung des Potentials unserer Kunden in den Mittelpunkt rückt. Zum anderen verbirgt sich darin auch Tux, das Maskottchen von Linux, womit wir auch unser Fundament: Linux und Open Source als wichtigen Baustein unserer Identität widerspiegeln.
Corporate Identity
Auch wenn das neue Design viele unserer Werte impliziert, haben wir mit der neuen Vision und Mission, sowie mit dem neuen Claim unsere Corporate Identity etwas geschärft.
As a company, we shape a world of innovative, sustainable and resilient IT solutions built on trustworthy open source technology to unlock the full potential of our customers.
Mit unserer Vision beschreiben wir unser hochgestecktes Ziel; dort wollen wir hin und dafür setzen wir uns täglich ein. Mit dem Einsatz quelloffener und vertrauenswürdiger Technologien erbauen wir eine Welt, von innovativen, nachhaltigen und resilienten IT-Lösungen mit denen unseren Kunden ihr Potential voll ausschöpfen können. Im Mittelpunkt stehen dabei unsere Kunden und das Wissen, dass wir mit Open Source nicht nur zu ihrem Erfolg beitragen, sondern durch unsere Contributions auch die IT-Welt als solche zu etwas Besserem mitgestalten. Cool, oder?
Our mission is to foster Open Source technology, deliver high-quality work, and run mission-critical systems around the clock so our customers can focus on their core business. By working with us, customers are liberated from vendor lock-in and are one step ahead of their competition.
Mit der Mission beschreiben wir unser tägliches Tun. Daran halten wir uns fest, wenn wir kurz die Orientierung verlieren. Höchster Qualitätsanspruch und 24/7 Support zeichnet uns aus, denn nur so können wir versichern, dass unsere Kunden sich auf ihr Kerngeschäft konzentrieren können. Zudem befreien wir sie von Vendor Lock-In und unterstützen sie dabei, ihrer Konkurrenz einen Schritt voraus zu sein – sei es mit Cloud Native Technologien, klassischen IT Lösungen oder durch von uns entwickelter Software.
Kurz also – At Adfinis we:
plan innovatively. build sustainably. run resiliently.
Claim:
Potential. Unlocked.
Wir nehmen unsere Kunden mit auf eine Reise, welche wir mit innovativen Lösungsansätzen planen und so umsetzen, dass sie langfristig und nachhaltig beständig sind. Zu guter Letzt begleiten wir unsere Kunden aber auch noch lange nach der Umsetzung, damit sie für alle zukünftigen Herausforderung mit einer robusten Lösung gewappnet sind. Wir helfen unseren Kunden ihr volles Potential zu entfalten – ihr Potential zu “öffnen”. Metaphorisch – indem wir proprietäre Lösungen mit quelloffenen und nachhaltigen Open Source Lösungen ersetzen. Aber auch wortwörtlich – in dem wir unseren Kunden den ganzen IT-Bereich abnehmen und sie sich wieder auf ihr Kerngeschäft konzentrieren können.
Wenn du noch mehr zu unserem Rebranding, zu unserer Vision, Mission und unserem Claim erfahren willst, dann schau auf unserer Webseite vorbei und folge uns auf Twitter und LinkedIn.