Scheduled Deployments

Ship at the Right Moment,
Automatically

Queue a deployment for any date, time, and timezone. DeployHQ ships when traffic is low and your team isn't on call — no late-night browser tabs required.

Any timezone
Cancel or reschedule anytime
Pairs with availability rules

Last updated on 22nd June 2026

Scheduled Deploy
Branch
main @ 8a3f12c
Server
production
Run at
Sun 02:00 UTC
Queued — 14h 32m
Pending

Scheduled Deployments let you queue a deploy for a specific date, time, and timezone, then walk away. DeployHQ executes the build and rollout at the scheduled moment — using the same pipeline, checks, and availability rules as any other deploy. Reschedule or cancel anytime before it runs.

The Problem with 9-to-5 Deploys

Deploying during business hours hits the worst possible audience — your users and your on-call engineer.

2:30 PM TUESDAY Peak traffic Click "Deploy" now? On-call awake ⚠ Risky window OUTCOME ❌ User-facing blip ❌ Pager goes off ❌ Rollback drama Or wait until 2am yourself — neither is acceptable

Either you ship during the worst possible window, or someone gives up an evening. Scheduled deployments remove the choice.

Scheduled Deployments — Queue and Walk Away

Pick the moment that's right for your users. DeployHQ takes the deploy from there.

QUEUE NOW Pick date and time Pick timezone Confirm and walk away DEPLOYHQ WAITS Cancel anytime Reschedule anytime ⚡ Checks availability 02:00 SUNDAY ✓ Low traffic ✓ On-call asleep ✓ Deploy ran cleanly

How It Works

From queued to deployed in four steps.

1
Text icon

Pick the Deploy

Choose the branch, commit, and target server you'd normally deploy to.

2
Cloud icon

Set Date, Time, Timezone

Pick the moment to ship. DeployHQ stores it in your chosen timezone so DST and travel never trip you up.

3
Server icon

Queue and Walk Away

The deploy waits in the queue. Cancel or reschedule anytime — or trigger the same schedule from the API.

4
Zap icon

Ship Automatically

At the scheduled moment, DeployHQ runs the build, runs your checks, applies availability rules, and rolls out. You get a notification on success or failure.

Why Schedule Deployments?

Ship when it's safest, not when someone happens to be at their desk.

Zap icon

Off-Peak Without Overtime

Ship at 2am without anyone staying up. The deploy runs in the cleanest traffic window with full visibility on success or failure.

Cloud icon

Timezone-Aware

Schedule in your local timezone, or the timezone where your users live. DeployHQ handles the conversion, daylight saving, and locale display.

Check icon

Cancel or Reschedule Anytime

Plans change. Edit the schedule, push it back an hour, or cancel entirely up until the deploy starts running.

Shield icon

API-Driven

Queue scheduled deploys from CI, a release-management tool, or a calendar integration. Every action you can take in the UI works over the API.

Getting Started

Queue your first scheduled deploy

Check mark

Start a Deploy

Open your project, pick the branch and server, and choose "Schedule" instead of "Deploy now".

Check mark

Set the Window

Pick the date, time, and timezone. DeployHQ confirms the queued time in your local timezone too.

Check mark

Manage the Queue

Edit, reschedule, or cancel from the project's Scheduled tab — or from the API if a release tool owns the schedule.

Read the documentation →
SCHEDULE DEPLOYMENT Date: Sun, 28 Jun 2026 Time: 02:00 Timezone: UTC · 03:00 BST · 22:00 EDT Queue deploy →

Frequently Asked Questions

What happens if my server is down at the scheduled time?

The deploy fails the same way an on-demand deploy would — with the same logs, retry options, and notifications. The schedule just decides when DeployHQ runs the deploy; everything afterwards behaves identically to a manual deploy.

Can I cancel or reschedule a queued deploy?

Yes. Until the deploy starts running, you can reschedule or cancel from the project's Scheduled tab or from the API. After it starts, the normal deploy controls (stop, rollback) apply.

Can I queue scheduled deploys over the API?

Yes. The same scheduling parameters you set in the UI are available on the REST API, so CI, release tools, or change-management systems can queue and manage scheduled deploys programmatically.

What happens if a build is still in progress when the scheduled time arrives?

A scheduled deploy queues behind any in-flight deploy on the same project, then runs once the queue is clear. If a queued deploy collides with an availability block, it's rejected and logged for the team to reschedule.

Does this work alongside Automatic Deployments?

Yes. You can run automatic deploys for most pushes and schedule specific releases — such as a customer-visible feature flag flip or a marketing-aligned launch — for a chosen moment. The two features coexist on the same project.

Stop deploying at 2pm. Start deploying at 2am.

Queue the deploy now. Ship when it's safest.

10-day free trial • No setup fees • Cancel anytime

Get started today for just $9/month

That's unlimited deployments and 3 projects.

Start your free 10 day trial