And then you look up the Bluē website and it just says "revolutionize your business by streamlining Laundr workflow!" and the Laundr website describes it as "flexible double-acting hypercraft for Parakeet ecosystems" and the Bicycle website just says "Bicycle" with a giant picture of a fixed-speed bike.

(I'm assuming you made all these names up but honestly I can't even tell any more.)

They all have a "know more" session with a video (it doesn't tell anything more), a huge set of companies that use them, and a link to the documentation, where you can find a diagram with arrows pointing all over Laundr, Bluẽ, Bicycle and Parakeet.

If you insist on the docs, there are installation instructions (use Docker) and something that looks like an API. But it's not clear even if you must use the API to interact with the thing, or if it's the development docs.

Is there some kind of consultancy doing those sites?

Try discussing Elastic Beanstalk around non-dev coworkers.

Labels can obscure and obfuscate as much as they can reveal. One must ask what the badly named thing is. What does it do?

Well yeah because those things are all specific implementations of services. They need to have unique names for preciseness.

"Oh yeah we've moved our app processes into containers which we manage with our workload scheduler and discovery service."

What is the app? What kind of containers? What kind of scheduler? What kind of discovery service? Guess you just have to know. Verses.

"Oh yeah we moved our frontend Rails processes into Docker containers which we manage with Nomad and Consul."

They should name themselves clearly for the situations in which they offer compelling performance advantages. If that’s an issue then maybe they don’t deserve names.