TL;DR
Today we are shipping Environments and Promotion Pipelines, a release workflow that adds dev, stage, and prod with policy checks, dry runs, and audit trails. It plugs into Git based previews and approval gates so teams can ship faster with fewer incidents. The single most useful takeaway is that you can promote the exact artifact you tested, with the platform enforcing parity and rollback plans. This update is built into the same console where you manage agents, and it is available for all plans. OpenClaw is mentioned once here as the underlying orchestrator for consistency with naming.
What shipped in this release
This update delivers a structured path for changes to move from development to production with guardrails.
- Environments. Named slots such as dev, stage, and prod with isolation for variables, credentials, schedules, and webhooks. Each slot carries its own runtime limits and secrets reference.
- Promotion Pipelines. A declarative sequence that defines the allowed hops and the checks required between them.
- Validation and drift detection. The engine generates a diff that includes playbook definitions, connector contracts, and sensitive settings, and it blocks when parity is broken.
- Dry runs and planned changesets. Before anything applies, the system simulates the change and produces a human readable plan.
- Approvals and policy rules. Teams can require one or more approvals, enforce time windows, and tag sensitive promotions.
- Full audit trail. Every hop is recorded with actor, diff fingerprint, plan output, and log pointers for compliance.
If you are new to the product, skim the overview of our AI marketing automation features to see how environments sit next to agents, connectors, and playbooks.
Why it matters to marketing teams
Release discipline is not only for backend services. Lifecycle campaigns, ad syncs, lead routers, and attribution pipelines are operational software. Research shows that teams with automated release workflows deploy more often and recover faster after incidents. The DORA program documents this pattern across thousands of organizations, and the big takeaway is that safer releases improve speed rather than slow it down.
Promotion Pipelines adopt proven software engineering practices and package them in a way that is natural for marketers and growth engineers. You get predictable releases and fewer surprises when a variable or secret differs between environments. In practical terms this means fewer broken webhooks during a launch, fewer ad set mismatches after an audience sync, and faster recovery when a connector changes its schema.
If you want to see how code backed changes move through review, our write up on Git Sync and preview environments update shows the branch and PR pattern that pairs with the new pipelines.
Architecture at a glance
At a high level the feature adds three primitives that work together.
| Component | Purpose | Key settings | Typical owner |
|---|---|---|---|
| Environment | Isolated runtime for a workspace slot like dev or prod | Variables, secrets references, schedules, webhook endpoints | Ops or platform lead |
| Promotion rule | Defines a hop and required checks | Required approvals, allowed time window, validation level | Team lead |
| Validator | Compares definitions and produces a plan | Diff scope, policy set, health checks | Ops or SRE |
The validator runs before every hop. It generates a diff for the playbook manifest, connector contracts, and any files tagged as inputs. The plan is attached to the audit trail for review. If the plan passes policy, the engine executes the apply phase. If a health check fails, the engine pauses and offers a rollback to the previous known good artifact.
Configuration by example
Below is a minimal example of a promotion definition. The format mirrors how teams describe delivery gates inside a repository.
# promotions.yaml
environments:
- name: dev
variables:
STRIPE_MODE: test
- name: stage
variables:
STRIPE_MODE: test
- name: prod
variables:
STRIPE_MODE: live
pipeline:
- from: dev
to: stage
checks:
- type: diff
scope: ["playbook", "connectors", "variables:required"]
- type: dry_run
- type: approval
reviewers: ["growth-leads"]
- from: stage
to: prod
checks:
- type: diff
scope: ["playbook", "connectors", "secrets:refs"]
- type: dry_run
- type: window
allowed: ["Mon-Fri 08:00-14:00 PT"]
- type: approval
reviewers: ["marketing-ops"]
In practice most teams keep this file in the same repository as their playbooks. When a promotion starts, the engine loads the definition, evaluates checks in order, and only then applies the change to the target environment.
Step by step setup
The section below outlines how to set things up in a typical workspace.
Step 1Connect your repo
Use Git based configuration so changes are versioned and reviewable. If you have not turned it on yet, follow the guide linked from the console and create a branch for your first environment definition. This approach makes it simple to preview changes in an isolated slot before a promotion.
Step 2Define your environments
Create dev, stage, and prod with distinct variables, secrets, and schedules. A helpful long tail query to keep in mind here is how to set up dev stage prod environments for marketing automation. Keep secrets in your vault and reference them by handle rather than copying values. If a connector requires different scopes by environment, document that in the variables section and reference the least privilege token.
Step 3Choose validation and health checks
Start with diffs on the playbook manifest and connector contracts. Add a dry run so everyone sees the planned changeset before apply. For pipelines that write to ad platforms, add a health check that reads a few objects after apply and confirms the expected shape.
Step 4Add approvals and windows
Place an approval between stage and prod so someone reviews the diff and the plan. Add a time window for sensitive promotions so they only land when the on call rotation is staffed. If your security team requires separation of duties, assign approvers who do not have edit permissions on the playbook.
Step 5Run your first promotion
Promote a small, low risk change first. For example, move a copy update or a minor mapping adjustment. Review the diff, glance at the plan, and capture a short retro on what felt smooth and what felt slow. Iterate on your checks to strike the right balance between safety and speed.
Real world scenario: seasonal promo with tight timelines
Imagine an ecommerce team preparing a holiday promotion. The group updates a pricing feed, tweaks a coupon logic step, and expands remarketing audiences. Before this release, the team would edit the live workflow and hope the mapping was correct. With environments and promotions, the same team can run the workflow in dev with sample data, push to stage with a dry run and sanity checks, and then promote to prod right after QA signs off. The audit trail captures who approved, what changed, and when the update reached each slot. If an issue slips through, the rollback plan restores the previous artifact without guessing.
Comparisons and tradeoffs
The new pipelines do not try to replace your CI system. They sit on top of it. Use CI for tests, lint, and packaging. Use environments to control when and where a packaged artifact runs in production. Some teams will prefer approvals only on high risk workflows. Others will want every change to pause for review. Both are supported. The tradeoff is speed versus safety, and you can adjust checks per hop to match the risk profile of a given playbook.
If you need a refresher on adjacent capabilities, scan ButterGrow for a quick sense of the hosted assistant, or jump into the AI marketing automation features for details on agents, connectors, and governance.
Monitoring, audits, and incident review
Every promotion emits structured events. You can filter by actor, environment, and status to build weekly release reports. The audit record links to logs and the dry run plan so incident reviews can move quickly. If a vendor API changed a field type between environments, the drift report captures that mismatch and the validator will block until the difference is resolved.
For teams that field compliance questions, see answers to common questions for how audit data is retained and how access is controlled. When launching a high impact campaign, consider adding a long tail check such as promotion pipelines for safer agent releases so that busy periods do not tempt a side step around review.
Limits and roadmap
This initial release focuses on workspace level environments and promotions inside a single region. Multi region promotion paths are on the roadmap. Another near term item is policy presets that encode common standards for financial services and healthcare teams. Finally, we are exploring automatic quota forecasting that reads your recent job patterns and flags possible breaches before they happen.
Getting started
You can try the new flow in minutes. Create your first environment set, define a simple pipeline, and promote a small change. The console guides you through each step and surfaces diffs, plans, and approvals where they are needed. If you prefer a walkthrough, head to the getting started guide and import one of the sample playbooks.
The simplest path to value is to map one high frequency workflow into this model. Take an audience sync or a daily content scheduler and use promotions to move it from dev to prod. Once the team feels the benefits, expand coverage to lead routing, attribution updates, and post purchase journeys. When you want more background or adjacent techniques, browse more from the ButterGrow blog for related reading and implementation stories.
At the end of your first promotion, you will have a repeatable path for change. That path reduces surprises and gives everyone a clear picture of what is live, what is next, and who approved it.
Our product team ships fast. If something blocks your rollout, let us know and we will prioritize a fix.
Our CTA is simple. If you run growth operations and want safer releases without slowing down, try the new Environments and Promotion Pipelines in ButterGrow. You can create a workspace, wire up a connector, and be running a promotion in under an hour. When you are ready to roll this out across teams, the onboarding flow at get started in minutes shows how to invite collaborators and set basic policies.
References
- Google SRE book chapter on release engineering: Background on release workflows and why consistency matters.
- GitHub Actions environments and protection rules: How software teams gate deployments with environment rules.
- DORA research on deployment performance: Evidence that automation improves release frequency and stability.
Frequently Asked Questions
How do Promotion Pipelines move a playbook from dev to prod without downtime?+
Each environment is isolated with its own variables and secrets. A promotion rule validates version parity, runs a dry run, and then applies the change in the next environment. If health checks or post deploy tests fail, the system halts the pipeline and preserves the previous version.
What does drift detection compare during a promotion?+
The engine compares playbook definitions, connector contracts, secrets references, and variables that are marked required. If a non allowed difference is found, the promotion is blocked and a diff report is attached to the run so the owner can reconcile config before retrying.
Can approvals be required between stage and prod?+
Yes. You can place an approval gate on any hop in the pipeline. Approvers receive a diff, a link to logs, and the planned changeset from the dry run so they can make a quick decision with context. Approvals can be tied to teams or specific users.
How does this feature relate to Git Sync and preview environments?+
Git Sync still provides version control and branch based previews for new playbooks. Promotion Pipelines control the path a reviewed change takes across dev, stage, and prod. Combined, they let you test from a pull request preview to a production release with guardrails at every step.
What happens if an API quota limit is different across environments?+
Quotas are part of environment variables. When a promotion runs, the validator checks for quota mismatches and warns if the new configuration would exceed a known limit. You can set a rule to fail the promotion when the forecasted rate would breach the ceiling.
How do I audit who promoted a change and when?+
Every promotion writes an immutable event with the actor, time, source and target environment, diff fingerprint, and approval trail if used. The audit record links to logs and the dry run plan so investigations can jump straight to evidence.
Ready to try ButterGrow?
See how ButterGrow can supercharge your growth with a quick demo.
Book a Demo