Connect releases to real-user performance
Intercube Pipeline can now add successful deployments to RUMvision as annotations. Release context appears where teams investigate real-user performance, making it easier to see when a change followed a deployment.
Release context flow
Selected verified domainIntercube Pipeline
A release runs through the managed deployment workflow.
Deployment completed
The application release is complete before annotation delivery starts.
RUMvision
A release annotation is added to the customer-owned account.
Production by default
Non-production is included only when selected.
Delivery recovery
Bounded retries, history and manual retry.
- Published
- 16 September 2026
- Ownership
- Customer-owned RUMvision account
- Default environment
- Production
Why it matters
See the release moment alongside the performance data it may have changed.
Performance context
Give performance changes a release context
Real-user monitoring shows how an application behaves for the people using it. Release history explains what changed in the application. Those two views are more useful together: a shift in loading, responsiveness or visual stability can be compared with the moment a new version reached production instead of being investigated without a clear starting point.
The Intercube integration connects that operational context. When a selected Intercube Pipeline deployment succeeds, the platform sends a deployment annotation to the relevant verified domain in the customer-owned RUMvision account. RUMvision remains the place where the customer explores its monitoring data; Intercube supplies a dependable record of the release that may explain a change.
An annotation does not declare that a deployment caused an improvement or regression. It gives technical, product and performance teams a shared point on the timeline, so they can ask a better question and investigate the available real-user evidence with the same release in mind.
Account ownership
Keep ownership with the customer
The customer keeps ownership of the RUMvision account, its subscription and the monitoring data collected there. The customer also installs and manages the RUMvision monitoring snippet in the application. That preserves a clear boundary: RUMvision measures the visitor experience, while Intercube operates the hosting and deployment path it is responsible for.
Intercube securely connects the customer-owned account to the managed platform. Only domains that have been selected and verified for the integration can receive annotations. This prevents a release from being attached to an unrelated site and lets organisations decide which production applications should share deployment context with RUMvision.
The result is cooperation without transferring product ownership. Customers continue to work in RUMvision with their own access and monitoring configuration, while Intercube removes the manual step of recording every successful release from an integrated Pipeline.
The Intercube perspective
A release marker should make investigation easier.
Deployment automation already records when code moved into an environment. Passing that moment into RUMvision gives teams useful context without asking them to maintain a second manual release log.
The integration deliberately stops at that boundary. RUMvision remains the real-user monitoring product, the customer remains in control of its account and Intercube makes the deployment event reliable enough to support the investigation.
Environment scope
Focus on releases that affect real users
Production is the default because that is where enough real-user traffic usually exists to evaluate the effect of a release. A successful production deployment can therefore create an annotation without requiring someone to copy the release time into a separate monitoring workflow.
Non-production environments are supported only when they are explicitly selected. This keeps acceptance, preview and test deployments from filling the normal performance timeline by accident, while still allowing a team to annotate a non-production domain when genuine visitor data and a deliberate testing approach make that useful.
Annotations are created after a successful Pipeline deployment. Failed or incomplete releases are not presented as completed application changes. The integration is domain-aware as well as environment-aware, which keeps the release record close to the site and audience it can actually have affected.
- Successful Intercube Pipeline deployments create the release signal.
- Production is included by default for selected verified domains.
- Non-production environments require an explicit choice.
- The RUMvision account and monitoring setup remain customer-owned.
Delivery resilience
Preserve the deployment when delivery fails
Monitoring context is valuable, but it should not become a new release dependency. If RUMvision cannot accept an annotation, the application deployment remains successful. The integration records the delivery problem separately, so an external monitoring response cannot turn a completed release into a failed one.
Intercube applies bounded retries to temporary delivery failures and keeps a delivery history for operational review. When an automatic attempt does not complete, an authorised operator can retry the annotation manually without rerunning the application deployment. This provides recovery where it is useful without creating an endless background loop or duplicate release process.
That separation protects both sides of the workflow. Developers can trust the deployment status to describe the application release, and operators still have enough evidence to see whether its RUMvision annotation was delivered, retried or needs attention.
- Annotation delivery never changes a successful deployment into a failure.
- Temporary failures receive a limited number of retries.
- Delivery history keeps the annotation outcome visible to operators.
- Manual retry recovers the annotation without redeploying the application.
Available now
What the integration delivers
- Successful Pipeline releases can appear as annotations for selected verified RUMvision domains.
- Production is the default, while non-production annotation is an explicit choice.
- Customers retain their own RUMvision account, access, snippet and monitoring data.
- Annotation delivery problems do not interrupt or fail the application deployment.
- Bounded retries, delivery history and manual retry support operational recovery.
Add release context to real-user monitoring.
Talk with us about connecting your RUMvision account to the Intercube Pipeline for the production domains that matter.