Let your customers BYO their own cron schedule

Your B2B product has a "schedule a sync" feature. Each customer wants a different cadence: every 5 minutes, every Monday at 8am EST, the first of the month.

The shared-scheduler version of this feature lives in a sea of caveats: minimum interval, max overlap, fair-queueing rules, "we may delay your job during peak hours." Customer support gets tickets every week.

The Hoody version: each customer's container exposes its own hoody-cron API. The customer types their cron expression into your UI; you POST it to their container's crontab. The schedule lives where the work lives. There's no shared queue to fair-share, no upper bound on schedule density across customers: just the limits of one container.

The customer's cron expression is the customer's, not yours to validate against a global queue.