I’ve been using backblaze b2 (via s3fs-fuse container + bidirectional mount propagation to a host path) and a little bit of google drive (via rclone mount + the same mounting business) within kubernetes. I only use this for tubearchivist which I consider to be disposable. No way I’m using these “devices” for anything I really care about. I haven’t tried gauging the performance of either of these, but I can say, anecdotally, that both are fine for tubearchivist to write to in a reasonable amount of time (the bottleneck is yt-dlp ingesting from youtube) and playback seems to be on par with local storage with the embedded tubearchivist player and jellyfin. I’ve had no issues with this, been using it about a year now, and overall I feel it’s a decent solution if you need a lot of cheap-ish storage that you are okay with not trusting.
Piling on to the google alternatives heap: https://searx.space/
You can pick a public instance of searxng and choose which engines it queries by going to the setting cog, then Engines. A few of these public instances I’ve checked out have only google enabled, though, so you really do need to check the settings.
If you want to add a searxng instance as your default engine and your browser doesn’t automatically do it, the URL for that is: https://<searxng_url>/search?q=%s
I have to add this manually for things like ironfox/firefox mobile.