Never Forget to Publish Again: Introducing Auto-Publish | Ploy

You made the edit. The copy is sharper, the new section looks great, the page is done. Then a Slack message pulls you away, and the change sits in preview for three days because nobody hit publish.

If that has never happened to you, you are a more disciplined person than most of us. Between juggling campaigns, calls, and a dozen half-finished tabs, the last click is the one that quietly gets dropped — and the polished work never reaches a single visitor.

Today we’re fixing that with auto-publish.

What it does

Turn on auto-publish for a site, and Ploy publishes every change the moment it finishes it. No separate step, no “did that go live?” No work stranded in preview. You make the change; it ships.

And you decide how far each change goes with two modes:

How to turn it on

Auto-publish is a per-site setting, so you decide site by site:

  1. Open your site dashboard and go to Advanced.
  2. Under Agent permissions, flip Automatic publishing on.
  3. Choose your mode: Preview only or Preview + Production.

That’s it. From then on, when Ploy finishes a change on that site, it publishes to the level you picked.

When to use it — and when not to

Auto-publish is built for momentum, and the two modes let you dial in how much:

And you can always keep auto-publish off entirely when you want a fully manual gate — nothing ships until you click Publish or ask Ploy to publish. Either way, you’re in control of the trade-off.

You’re never locked in

Shipping fast only works if it’s safe to be wrong. Every publish in Ploy is a versioned, immutable deploy, so nothing is one-way. If a change goes live that you’d rather pull back, open Deploys in your site dashboard, find an earlier version, and click Promote. Rollbacks are instant — the previous version is already built and cached, so there’s no rebuild step.

The best change is the one your customers actually see. Auto-publish makes that the default, so the work you finish is the work that goes live.

Read more in the publishing docs.