Skip to content

Browse the knowledge base

Promoting a channel to production

Deployment gates — connector preflight, soak and approval — plus inbound allowlists, gateway addresses and how a cutover drains.

Last updated August 12, 2026

On this page

A promotion moves a published revision from one environment to another. It does not rebuild anything: the artifact is packaged once with a pinned engine image digest, and the same artifact runs everywhere.

The gates

Three gates can sit in front of a promotion. Configure the ones your change process needs.

Connector preflight — runs before the promotion. Every connector in the channel is checked against the target environment: DNS resolution, TLS handshake, credentials. This catches the most common cutover failure, which is a firewall rule nobody opened.

Soak — runs after deploy, before cutover. The channel runs in the target environment for a configured window while errors are watched. If the error rate crosses the threshold, the gate does not clear.

Approval — a human gate. A named approver signs off in-app, and the approval, approver and timestamp land in the audit event stream. This is usually the artifact your change advisory board actually wants.

The release timeline

  1. Build — the revision is packaged with a pinned engine digest.
  2. Preflight — connectors are verified against the target.
  3. Soak — the channel runs under observation.
  4. Live — traffic cuts over.

The previous revision drains rather than being cut off: in-flight messages finish processing before the old task stops.

Inbound allowlists

Production listeners require an inbound allowlist. Collect the sending system’s source addresses before the cutover window rather than during it.

Gateway addresses

Cloud listeners are reachable under *.gw.intucloud.ai with TLS 1.2 or higher. By default they use a shared address pool. Dedicated ingress or egress address sets are a $40/mo add-on and are included on Enterprise — worth it when the counterparty needs to allowlist a stable IP on their side.

Rolling back

Every publish creates a revision. Rolling back is promoting an earlier revision, which goes through the same gates. There is no separate rollback mechanism to learn.

Region

IntuCloud is hosted in AWS us-east-1 during the beta.