Release Channels
The lifecycle categories assigned to integrations.
IMSURGE publishes each integration on a release channel so you can balance reliability against early access. Use this guide to decide which channel to run in and what to expect.
Alpha and Beta Integrations
Alpha and Beta integrations are collectively classified as experimental. While they have passed all minimum requirements to function with IMSURGE and are fully operational, they are still in active development. They have been made available to support real-world use case testing and to gather valuable user feedback.
Experimental integrations may be more frequently subjected to the following:
- Unexpected bugs, which may result in temporary outages or anomalies in data sets.
- Updates that modify the behavior of the integration.
- Updates that could cause existing integrations or pipelines to stop working.
- Updates that may require existing integrations or pipelines to be fully reconfigured.
By proceeding with an experimental integration, you acknowledge and accept that you are using it at your own risk.
Stable Integrations
Stable integrations are those that IMSURGE has validated as reliable and suitable for everyday use. Once an integration reaches this status, it means it has already gone through testing and feedback in earlier stages (Alpha and Beta) and has demonstrated consistent performance in real-world conditions.
Legacy Integrations
Legacy integrations remain fully functional and usable. They are categorized as “legacy” because the external platform or integration target is in a state of limited or legacy development. While IMSURGE will continue to support these integrations, no new feature development will be made for them.
Anything that is truly broken or unusable will not appear in the integrations list.
Reference
Tips
Use Alpha if you have been granted early access and want to validate connectivity and schema without cost.
Use Beta if you are comfortable accepting experimental terms and conditions.
Use Stable for production pipelines.
Use Legacy only if you need backward compatibility with older integrations.