Stillgate — Editorial Freeze for Deployments
Freezes editing during deployments and migrations, optionally pauses comments and forms, ends on a timer, and reports what changed.
Solid choice
Stillgate is a solid plugin choice in 2026, with a few things worth checking first. Was last updated 4 weeks ago, and scores 64/100 on our health check.
- Actively developed — last update 4 weeks ago
- Tested with the latest WordPress (7.1)
- Small user base (<10 active installs)
- Very few reviews so far
- Needs PHP 8.1 or newer
How does it stack up?
Side-by-side on installs, updates, ratings & supportDaily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Stillgate stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| deployment | #78 |
| freeze | #36 |
| maintenance | >100 |
| migration | >100 |
| wp-cli | >100 |
About Stillgate
From the official readme · v0.2.0Description
Deploying a WordPress site — syncing a database, pushing files, running a migration — usually needs a window where the database will not change underneath you. In practice, editors keep working, and a post, upload or menu change made mid-sync can be silently lost.
Stillgate puts the backend into a controlled editorial freeze for exactly that window, while the public site keeps working normally the whole time. It ends by itself, and afterwards it tells you whether anything changed.
What you get
- A freeze with a timer. Start one for 15 minutes to 4 hours from a single screen, or with
wp stillgate enable --for=30m. It ends by itself, even if your deploy job dies, and you can extend it when the work runs long. - A receipt of what changed. Every freeze leaves a list of the posts saved, created or trashed while it was on, plus term changes, comments and paused visitors, so you know whether the database you copied at the start is still complete.
- Optional pause of comments and forms. Anything a visitor saves during a deployment can be lost too. Turn on Coverage and visitors are told clearly that comments or forms are paused. Off by default.
- Built for pipelines. WP-CLI commands and a REST API (Application Passwords) let a CI job freeze, extend, check and release a site without SSH.
- Calm and visible. A small status in the admin bar, a notice that explains the freeze to the people it affects and disappears when it ends, and a Site Health test that flags a freeze someone forgot.
A freeze in practice
wp stillgate enable --for=30m --message="Deploying release 42, back shortly."
# ... sync files and database ...
wp stillgate receipt --check
wp stillgate disable
The same operations are one click on Tools > Stillgate.
What a freeze protects
While active, a logged-in user without the deployment_guard_bypass capability cannot create, edit, delete or restore protected content — posts, pages, custom post types, media, revisions, taxonomies and terms, navigation menus, widgets, or the Customizer — through classic wp-admin, the block editor, the REST API and XML-RPC. WP-CLI commands and WP-Cron events are blocked from the same changes. Scheduled posts of a protected type stay scheduled and publish normally once the freeze ends.
A freeze can start now, run for a set time, or follow a scheduled window in the site’s own timezone. Whether it is active is computed from the current time on every relevant request; it never depends on a WP-Cron event firing on time.
Pausing comments and forms
Under Coverage you can include visitor comments and form submissions in a freeze. People who can bypass the freeze can still submit, WooCommerce orders and checkout are never paused, and the check happens when a submission arrives, never when a page is shown, so page caches cannot serve a stale state.
Contact Form 7, WPForms, Ninja Forms, Fluent Forms, Forminator, Formidable and Everest Forms were each checked on a real site, and their visitors see the message in the form. A form set to submit without AJAX shows a plain WordPress notice page instead. Other forms can be added with a filter.
The freeze receipt
A clean receipt tells your deploy that nothing it can see changed while the freeze was on. Otherwise it lists exactly which posts to look at before anything is overwritten. It covers only the time the freeze was on, so run the check while the freeze is still running. It is a detector, not a synchronizer: it does not merge databases, and the documentation says plainly what it cannot see.
Bypass is capability-based, not role-based
Roles with manage_options (Administrator, by default) receive the deployment_guard_bypass capability on activation. The check is against the capability, never a role’s name, so a custom role can be granted it too. A bypass holder keeps working during a freeze, though their own changes can still be lost if a deployment proceeds concurrently; the freeze protects everyone else’s content.
WP-CLI is not exempt. wp post update, wp term create, wp media import and equivalent commands from other plugins are blocked the same way; --user=<account with bypass> is the explicit way to act as a specific person. Stillgate’s own wp stillgate commands keep working, because they only change Stillgate’s own state.
Security and privacy
Stillgate makes no outbound HTTP requests, sends no data anywhere, needs no account or license key, and collects no telemetry. It adds no database table: six small options, all removed on uninstall. Its activity log never stores request payloads, message bodies or IP addresses, and the receipt keeps counts, timestamps and post IDs only.
Known limitations, stated plainly
- A bypass holder’s own changes are not protected from being overwritten.
- Freeze state lives in the database, so a database import during a migration can lift or copy it. The
DEPLOYMENT_GUARD_FORCEconstant inwp-config.php(the booleantrueorfalse) forces the freeze on or off independently of the stored state, for exactly this situation. - With a persistent object cache not shared between WP-CLI and web workers, a CLI-issued change may need
wp cache flushto take effect for web requests; a long-running PHP process keeps the state it read until it restarts. - Changes that go around WordPress’s own content functions and capability checks are not blocked: direct database queries, third-party code that writes content without checking capabilities, plugin REST routes with controllers of their own, and direct
wp_publish_post()calls. - In WP-CLI and WP-Cron, post meta, term assignments to existing terms, widgets, menu locations, theme mods and other options are not blocked, nor are term updates and deletions made during a cron event.
- Automated writes to protected content fail while a freeze is active: cron jobs such as emptying the trash or updating products, and plugin activation routines run through WP-CLI.
- Restricted users cannot preview drafts of protected content during a freeze.
- Users, plugins, themes and general site settings are out of scope. Comments inserted directly with
wp_insert_comment()(importers,wp comment create) are not paused. - The receipt only sees content saved through WordPress. A change written straight to the database that does not touch a post’s modified time is invisible to it, and orders kept outside the posts table are not listed.
- On Multisite, Stillgate works per site; there is no network-wide freeze screen yet.
Architecture notes, the enforcement matrix, every hook and the REST API are documented in the GitHub repository.
Installation
- Upload the plugin files to
/wp-content/plugins/stillgate, or install it through Plugins > Add New > Upload Plugin. - Activate the plugin. Roles with
manage_optionsreceive thedeployment_guard_bypasscapability automatically. - Go to Tools > Stillgate to start a freeze, or use WP-CLI:
wp stillgate enable --for=30m.
Changelog
Adds timed freezes, a REST API, an optional pause of comments and forms, and a receipt of what changed during a freeze. Nothing changes until you use it: the new coverage options are off, and your stored settings carry over.
0.2.0
- Added: timed freezes (
wp stillgate enable --for=30m, a duration picker on the settings screen) andextend, so a deployment that fails halfway can never leave editing locked. - Added: a REST API for pipelines at
stillgate/v1, authenticated with Application Passwords. - Added: an optional pause of visitor comments and form submissions during a freeze, off by default, checked on a real site for Contact Form 7, WPForms, Ninja Forms, Fluent Forms, Forminator, Formidable and Everest Forms.
- Added: a freeze receipt of what changed while the freeze was on (
wp stillgate receipt --check,wp stillgate drift, the settings screen and the REST API). It is a detector, not a synchronizer. - Added: a redesigned settings screen, an admin-bar status, a Site Health test, and new artwork for the plugin page.
- Changed: uninstalling also removes the coverage choice, the receipt and the refusal counters.
- Full changelog: https://github.com/digibold/wp-stillgate/blob/main/CHANGELOG.md
0.1.1
Renamed from Deployment Guard to Stillgate. The stored settings, activity log and bypass capability carry over. The freeze notice now appears only on the screens where editing is affected and explains how the freeze ends. See the full changelog at https://github.com/digibold/wp-stillgate/blob/main/CHANGELOG.md
0.1.0
Initial release. See the full changelog at https://github.com/digibold/wp-stillgate/blob/main/CHANGELOG.md
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Stillgate alternatives
All deployment plugins →FAQ
Stillgate: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Nov 18, 2026
Is Stillgate free?
Yes. Stillgate is free to download and use from the official WordPress.org plugin directory.
Is Stillgate safe to use in 2026?
Stillgate is a solid plugin choice in 2026, with a few things worth checking first. Was last updated 4 weeks ago, and scores 64/100 on our health check.
How many websites use Stillgate?
Stillgate is active on <10 WordPress websites and has been downloaded 210 times since it launched in October 2026. It was downloaded 150 times in the last 30 days.
Does Stillgate work with WordPress 7.1?
Yes. The developer has tested Stillgate up to WordPress 7.1.4, the latest release. It requires WordPress 6.6 or newer.
What PHP version does Stillgate need?
Stillgate requires PHP 8.1 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Stillgate last updated?
The latest version, 0.2.0, was released on October 19, 2026 (4 weeks ago).
Who makes Stillgate?
Stillgate is developed and maintained by twelvell.
What are the best alternatives to Stillgate?
The most popular alternatives to Stillgate are Deployer for Git (600+ installs), Custom Database Application… (400+ installs) and Deploy with NetlifyPress (200+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card