Google Cloud Scheduler logo

Google Cloud Scheduler

Schedulers 6.1/10

Fully managed cron service for invoking HTTP endpoints, Pub/Sub topics, and Google Cloud workloads.

Google Cloud Scheduler scores 6.1/10 for free value in Schedulers. The main constraint: Google Cloud includes limited free usage in some cases, but billing/project setup and current pricing must be verified.

Category Schedulers Kind Managed cloud scheduler Caveats Heavier account, IAM, and billing setup than lightweight scheduler services. Renewal monthly Card required Yes Eligibility anyone

Free value score

6.1 / 10
Show the math
Overall 6.1/10
value = 6.1/100
weighted_components_v1
Run value 6/10
value = 0.3 $/mo
fixed_log_v1
Reliability 5.7/10
value = 5.7/100
policy_score_v1
Workflow fit 7/10
value = 7/100
policy_score_v1

Key metrics

43.2K/mo Run quota Uses stated run/message/execution quota when present; otherwise a conservative floor.
75.0/hr Granularity/reliability Derived from minimum interval with conservative reliability adjustment.
7 Workflow/runtime api, cron, history, http, logs, retries, timeout
3 jobs Cron jobs
1 min Min interval
Executions billed per job, not per execution
None Run history logs go to Cloud Logging
30 min Job timeout

What you get

Managed cron jobs

HTTP and Pub/Sub targets

Retries and cloud-native auth

Limitations

  • 3 free jobs per billing account/month

    Each Google Cloud billing account gets exactly 3 free Scheduler jobs per month; additional jobs cost $0.10/job/month.

  • Free quota is account-level, not per-project

    The 3 free jobs are shared across all projects on the billing account, so a multi-project setup quickly exhausts the free allowance.

  • Billing account required

    A Google Cloud billing account with a valid payment method must be set up before using Cloud Scheduler, even within the free tier.

  • No built-in job history or long retention

    Cloud Scheduler free tier does not include extended execution history or alerting dashboards beyond what Cloud Logging provides.

  • Executions per job not individually billed but may be throttled

    Billing is per job definition, not per execution, but individual job execution frequency is bounded by minimum 1-minute intervals.

Sources

gcp cron http pubsub managed