Google Cloud Run
Runs Clienzo's API and its background jobs as containers.

good
- Deploy a container and get an HTTPS service, no servers to manage
- Pairs with Cloud Tasks for one queued task per scheduled post
watch out
- Every service needs its own environment variables; a second service that misses one fails quietly
Clienzo’s backend runs on Cloud Run, with a separate service for publishing, metrics and inbox jobs. The lesson I keep relearning: when a new integration needs an environment variable, set it on every service that runs that code.