If the source code and/or precompiled binaries that aren't dependent on an external set of services (or even an OCI image) isn't available, then one has to assume that said software can become inaccessible at any given moment and remain that way.
Sometimes, even if the authors stop development on a project like that but have provided said ways of actually self-hosting it, it can still be used even despite the technology being dead for a while, until a migration path to something else can be found.
Corporations are likely to retire projects eventually, release new major breaking changes and deprecate old API versions, or get acquired and have degraded service after a decade or so. Individual developers are likely to have limited resources to allot to the project and limited capacity to maintain packages long term, with a few exceptions, as well as life circumstances or priorities shifting can have a way larger impact on the future of the project.
Thus, using any non-open-source package carries longevity risks, using any SaaS solution that cannot be self-hosted presents even larger risks. Many people don't care though and will still gladly use either. Something along the lines of: "Why care about where this will be in 10 years if I'll be at a different company in a year, but want to solve this problem now?"
Sometimes, even if the authors stop development on a project like that but have provided said ways of actually self-hosting it, it can still be used even despite the technology being dead for a while, until a migration path to something else can be found.
Corporations are likely to retire projects eventually, release new major breaking changes and deprecate old API versions, or get acquired and have degraded service after a decade or so. Individual developers are likely to have limited resources to allot to the project and limited capacity to maintain packages long term, with a few exceptions, as well as life circumstances or priorities shifting can have a way larger impact on the future of the project.
Thus, using any non-open-source package carries longevity risks, using any SaaS solution that cannot be self-hosted presents even larger risks. Many people don't care though and will still gladly use either. Something along the lines of: "Why care about where this will be in 10 years if I'll be at a different company in a year, but want to solve this problem now?"