Control Exactly When Deploys
Can — And Cannot — Happen
Block deployments per project or across your entire account during incidents, change freezes, and planned maintenance. No surprise deploys when the stakes are highest.
Last updated on 22nd June 2026
Deployment Availability lets you define windows when deployments are blocked — at the project level for individual teams, or account-wide for company-spanning rules. Every attempt to deploy during a block is rejected and logged, so change freezes, incident response, and compliance windows are enforced automatically across the UI, API, and CLI.
The Problem with Honor-System Deploy Freezes
Slack announcements and calendar invites don't stop someone from pushing during a freeze, an incident, or a peak-traffic event.
Freezes communicated only in chat or calendars get bypassed at the worst possible moments — exactly when an unexpected deploy can cause the most damage.
Deployment Availability — Enforced at the Platform Layer
Define rules in DeployHQ and every deploy attempt is checked against them — from any interface, by any team member.
How It Works
Two scopes, one consistent enforcement model.
Define the Window
Pick a start and end time, recurrence, and a reason. Rules can be one-off, weekly, or open-ended for incident response.
Choose the Scope
Apply per project for team-specific freezes, or account-wide so compliance and ops can lock the whole estate.
Enforce Automatically
Every deploy attempt — from UI, API, CLI, or auto-deploy webhook — is checked against the rules and rejected if blocked.
Audit and Review
Every blocked attempt is logged with the rule that triggered it, who tried, when, and why — ready for audit and post-incident review.
Why Use Deployment Availability?
Stop relying on chat announcements and good intentions to keep production stable during the riskiest windows.
Compliance Without Friction
Encode change-management windows as rules instead of policies. SOC 2, ISO 27001, and PCI auditors get a clean log of every deploy attempt and every block.
Two Scopes, One Model
Project owners can freeze their own service. Account admins can freeze everything at once. Both run through the same enforcement layer.
No Bypass Surface
The same rules apply to deploys triggered by the API, the CLI, scheduled jobs, and Git webhooks. There's no back door to forget.
Pairs with Scheduled Deploys
Combine with Scheduled Deployments to queue work for the next open window. Engineers don't have to babysit the clock.
Set up availability rules in minutes
Open Availability Settings
Account-wide rules live under Account Settings → Availability. Project-scoped rules sit under each project's Settings tab.
Add a Rule
Set a window, recurrence, and reason. Rules apply immediately — no redeploy needed.
Review the Audit Log
Every block is recorded. Filter by rule, project, or person for incident reviews and compliance reports.
Frequently Asked Questions
How is this different from Deployment Checks?
Deployment Checks validate a single deploy — running SSH commands, HTTP probes, or vulnerability scans before or after the deploy runs. Availability rules sit one layer earlier: they decide whether the deploy is even allowed to start, based on time-based and scope-based policy.
Can I override a block in an emergency?
Account admins can disable or edit any rule. Every override is logged with the user, timestamp, and reason — so emergency deploys are still fully traceable for post-incident review and audit.
Does the block apply to API and CLI deploys too?
Yes. Availability rules are enforced at the deployment service level, so every entry point — web UI, REST API, CLI, scheduled deploys, and Git webhooks — is subject to the same check. There's no bypass surface.
Can finance or compliance staff set account-wide rules without project access?
Yes. Account-wide availability is a separate permission. You can grant compliance or operations staff the ability to manage account rules without giving them deploy or project permissions.
Does this work with Scheduled Deployments?
It pairs naturally. Queue a deploy with Scheduled Deployments, and Availability rules will reject the execution if it falls inside a blocked window — letting you batch deploys safely for the next open window.
Stop surprise deploys before they happen
Encode change freezes and peak-traffic windows as enforced rules — not chat messages.
10-day free trial • No setup fees • Cancel anytime
Explore More Features
Discover all the tools that make DeployHQ the easiest way to deploy your code.
Zero Downtime Deployments
→One-Click Rollback
→Turbo Deployments
→Build Pipelines
→Build Cache
→Scheduled Deployments
→Deployment Availability
→Docker Builds
→Deployment Checks
→Deployment Targets
→Automatic Deployment
→Deployment Templates
→Deploy Behind Firewalls
→SSH Deployment
→Deployment Zones
→Team & Permissions
→Single Sign-On
→Custom Actions
→Server Management
→CLI & Agents
→Powerful Integrations
→Get started today for just $9/month
That's unlimited deployments and 3 projects.