---
title: "Releases"
description: "How do Coassemble releases roll out to Embed integrations?"
canonical_url: "https://support.coassemble.com/articles/releases-dTBu3AJNgh"
md_url: "https://support.coassemble.com/articles/releases-dTBu3AJNgh.md"
---
# How do Coassemble releases roll out to Embed integrations?

Coassemble ships releases in two stages: they land on the Standard Release server first, on release day, then on the Controlled Release server about two weeks later. For any release that affects integrations you get a sequence of email notifications, so there's always a two-week window to validate a release before it reaches the second server.

## The two-stage rollout

* **Standard Release server** (previously "Production"). Updates land here first, on release day. This is the shared environment all customers receive updates on by default.
* **Controlled Release server** (previously "Enterprise"). The same update lands here about two weeks later, after extra validation, giving you more preparation time.

Because of this cadence, there's always a window where a release is live on one server but not yet on the other.

## What Coassemble sends you

For every release that affects integrations, you'll get:

* **A preview email, 2 to 4 weeks before release**, covering what's coming, opt-in status, and any UI changes.
* **A reminder email, 1 to 2 days before the Standard Release.**
* **A Standard Release confirmation on release day**, with documentation links.
* **A Controlled Release confirmation about two weeks later**, when the Controlled Release server receives the same update.

For releases with no integration impact, you'll get a short FYI so nothing is a surprise.

## What to do on release day

* **If your integration is on the Standard Release server:** watch for the Standard Release confirmation, run your usual smoke tests, and email vip@coassemble.com if anything looks off.
* **If your integration is on the Controlled Release server:** no action is needed when the Standard Release ships. Use the two-week window to prepare, and watch for the Controlled Release confirmation on your server's release date.
* **If you have integrations on both servers** (for example, dev/test on one and production on the other): use the two-week gap to validate the release on your Standard Release environment before it reaches your Controlled Release environment.

## What to check after a release

* **Visual changes.** Review the embedded experience for any UI changes that could affect your users' workflows.
* **Opt-in features.** Some features ship disabled by default, so confirm whether anything needs enabling for your integration.

## When something breaks

If a release causes issues for your integration, email vip@coassemble.com. Put "urgent" in the subject for urgent issues, or use a normal subject otherwise. Coassemble triages quickly and either resolves it or provides a workaround. If you're on the Standard Release server, a rollback or hotfix may also be possible.