our usual solution is to run a copy of the app as dedicated process for background-jobs. it has a env-var BACKGROUND_JOB_ENABLED and only if that is set, i run cronjobs or similar. This process also won’t answer public http requests, because some jobs are cpu-bound.
Another option, that works well with multiple server instances is meteor-synced-cron. I’ve used in prod for years.