How do Coassemble releases reach my integration?

How releases roll out across the two servers, what notifications you'll get, and what to do on release day.

Coassemble ships regular releases. They reach the two server types at different times, which is what gives some customers a preparation window.

Release rollout: the two-stage cadence

1. Standard Release server (previously "Production")
   • Updates land here first, on release day.
   • This is the shared environment that customers receive updates on by default.
2. Controlled Release server (previously "Enterprise")
   • Updates land here after the Standard Release server, following additional validation.
   • The gap gives those customers preparation time. It varies from release to release, so use the dates in the release communications rather than assuming a fixed interval.

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

A Controlled Release server isn't part of every agreement. If you're not sure which server your integration runs on, check with your account contact before planning around a preparation window you may not have.

What you'll receive from Coassemble

For every release that affects partner integrations, you'll receive:

• A preview email, two to four weeks before release, covering what's coming, opt-in status and any UI changes.
• A reminder email, one to two days before the Standard Release.
• A Standard Release confirmation on release day, including documentation links.
• A Controlled Release confirmation when the Controlled Release server receives the same release.

For releases with no partner impact, you'll get a short FYI so you're not surprised by any changes.

What to do on release day

If your integration uses the Standard Release server

• Watch for the Standard Release confirmation email.
• Run your usual smoke tests for the integration.
• If anything looks off, email vip@coassemble.com.

If your integration uses the Controlled Release server

• No action is required on the day the Standard Release ships.
• Use the window before your own release date to prepare.
• Watch for the Controlled Release confirmation email when the release reaches your server.

If you have integrations on both servers

This is a common setup, for example one environment for dev and test and the other for production.

• Use the gap to validate the release on your Standard Release environment before it lands on your Controlled Release environment.

What to watch for after any release

• Visual changes. Review the embedded experience for UI changes that could affect customer workflows.
• Opt-in features. Some features ship disabled by default. Confirm whether anything needs to be enabled for your integration.
• New embeddables. A release may add components you can use but haven't wired in. They don't appear in your product until you add them.

When something breaks

If a release causes issues for your integration:

• Urgent issues: email vip@coassemble.com with "urgent" in the subject.
• Non-urgent issues: email vip@coassemble.com with a normal subject.

We'll triage quickly and either resolve or provide a workaround. If you're on the Standard Release server and a release causes a problem, we may be able to roll back or hotfix as needed.