As an example, what I do with n8n to hook services together:

• We use Zello in firefighting to document the incident with short verbal notes or take pictures. Voice gets transcribed, sent to MQTT for dashboards, taken by Telegraf to influx. Pictures and mp3s get downloaded from zello, put into minio, linked back with the metadata and also sent to influx. Finally all is displayed in chronological order on a Dashboard. Zello, Minio, MQTT, influx all glued together with n8n.
• Another one is the appsmith app for equipment maintenance. We need reports and appsmith is bad at that. n8n queries the Source pgsql, formats it to JSON, sends it to an online service to generate a PDF (with a template), downloads the PDF and puts it into Nextcloud.

There is more, but just as two examples. Quite easy in n8n, because many integrations are preconfigured (e.g. Nextcloud), but also plain REST API if necessary (zello).

All without AI…

Edit: Forgot one, Rocket Chat to keep everybody updated on a bunch of stuff, e.g. new maintenance report available, message on the day of a training, based on caldav. Also all with n8n.

Last time this came up, I learned that the piece we in the west call queen (you guys in English anyway, in German its Dame (meaning Lady)) is actually called Vesir/Consultant in that region. I think Wikipedia has a list per language, quite interesting.

None so far. And I am using pretty much all the features.

It is also great for my current migration from docker compose to kubernetes.

A newt client on both and I can just switch on the pangolin side.

Using it for several weeks now. Very happy with it, especially now that it is integrated with OAuth, so SSO for getting through Pangolin itself and then on all the services it routes to.

Wow, thanks for all the great answers so far. As for why not latest:

1. Read a lot online and read multiple times it’s “bad practice”
2. Own experience: had latest on an app which crashed and wouldn’t come up again. Got the backup of the persistent volume back and then had the problem that latest at that point is not the same as latest when I spun it up. Actually had no idea which version I was running last and consequently what I would need to pull to fit my backup. In case I have to restore my cluster, this problem is multiplied.
3. I run NixOS on everything, so I am clearly biased towards reproducibility.
4. I am running Services for family and a fire brigade (nothing mission critical, just support stuff, but still…). Stability is important, as sometimes I do not have the time to immediately react to an issue. I prefer a lazy Sunday morning to update/fix and then leave it alone and stable.

So, probably a combination of latest for low criticality and pinned on critical stuff (e.g. authentication, access, etc.)

At the end of the day you have to trust someone (Bitwarden, Hoster, Hardware Manufacturer…). It comes down to your threat profile and what you personally accept as a risk vs. effort (or convenience). For me Bitwarden was acceptable, but I switched to self hosting Vaultwarden ca. 3 years ago. Main reasons being the advanced features (sharing some passwords with the family, setting up a tech savvy friend to take over my vault should I get hit by a bus, etc.). I did not have any relevant downtime of that service in years.