Vercel Free Cron Jobs

Not natively, at least not currently during the ChatGPT Sites public beta.

OpenAI’s current Sites documentation does not expose a Cron Jobs or scheduled-functions feature. It specifically notes that some background services and hosting patterns are not supported by the Sites runtime. OpenAI Developers+1

There are two things that sound similar but are different:

FeatureChatGPT SitesVercelServer-side/API logic✅✅Persistent database✅ D1✅ external DB etc.File storage✅ R2✅Native cron scheduler**❌ Not currently documented/supported**✅HTTP/HTTPS endpoints✅✅Background scheduled processes⚠️ Limited/not supported✅

ChatGPT Sites itself is actually more capable than a purely static host. It can provision D1 relational storage up to 10 GB and R2 object storage, for example. OpenAI Developers But there isn't currently an equivalent of:

0 0 * * *
→ run /api/daily-task

There is a workaround

Since Sites supports HTTP/HTTPS, you could potentially structure it like:

External scheduler
       ↓
https://your-chatgpt-site.com/api/cron
       ↓
Site server logic
       ↓
D1 database

So something external could hit an authenticated endpoint on the Site once per day. OpenAI confirms HTTP/HTTPS are supported by the Sites runtime. OpenAI Developers

There is also ChatGPT Scheduled Tasks, but that's a separate ChatGPT automation system rather than a cron service belonging to your deployed Site. Paid ChatGPT plans can currently run recurring Scheduled Tasks as frequently as once per hour. OpenAI Help Center

So for an actual SaaS/app where you need things like expire listings, publish scheduled posts, refresh statistics, process queues, or perform database cleanup, I would still consider:

Vercel + its cron → cleaner production architecture

while

ChatGPT Sites → great for lightweight apps where most actions happen from user requests

until OpenAI adds native scheduled/background jobs to Sites.

Yes. 100 cron jobs is a per-project limit, and Vercel explicitly removed the old per-team cron limits in January 2026. Vercel+1

So on Hobby:

• Project A: up to 100 cron jobs

• Project B: up to 100 cron jobs

• Total across those two projects: 200 cron jobs

And Hobby accounts can currently have up to 200 projects, although all the normal account usage and anti-abuse limits still apply. Vercel

The important restriction remains that each Hobby cron schedule can run only once per day. So 200 cron definitions does not mean Vercel officially gives you a supported 200-times-per-day scheduler for one workload. Vercel

But purely from the documented limits: yes, 2 projects × 100 = 200 cron jobs.

Currently, Vercel’s documented project limits are:

PlanProjectsHobby, free200 projectsProUnlimitedEnterprise****Unlimited

That 200-project Hobby limit applies to the Hobby account/team. Vercel

So in theory, on one Hobby account:

200 projects × 100 cron jobs per project = 20,000 cron definitions.

But that does not mean Vercel intends Hobby to be used as a 20,000-runs-per-day scheduler. You'd still be subject to the shared Hobby usage limits, including 1 million function invocations, 4 CPU-hours, 360 GB-hours provisioned memory, fair-use rules, and each cron definition being restricted to once daily. Vercel

One other useful detail: Vercel currently allows only one Hobby team per account. Vercel

So for your normal setup where each micro SaaS gets its own Vercel project, 200 is a pretty generous ceiling.

For Vercel, the easiest place is the team-level Usage page, not inside an individual project.

Go to your Vercel dashboard, select your Hobby team/account, then click Usage in the sidebar. Vercel shows your current allotment and consumption for things like function invocations, CPU, memory, Edge Requests, image optimization, and other resources. You can also filter the Usage page by a specific project to see which app is consuming the quota. Vercel+1

For Hobby, some useful limits to watch are currently:

ResourceHobby limitProjects200Cron jobs100 per projectFunction invocations1,000,000Active CPU4 CPU-hoursProvisioned memory360 GB-hoursEdge Requests1,000,000Deployments created100/day

Vercel+1

One distinction: Usage does not necessarily give you a nice “37 / 200 projects” meter the way it does for compute usage. For project count, go back to the team's Projects page and look at your project list. The hard documented ceiling is 200 on Hobby. Vercel

And for cron jobs specifically, open:

Project → Settings → Cron Jobs

That will show the cron jobs configured for that particular project. Since the 100 limit is per project, you'd inspect each project's cron list separately.

If your concern is mainly whether you're getting close to exhausting the free Hobby resources, Usage → Function Invocations + Active CPU + Edge Requests are probably the three I'd watch most closely.