Why lifecycle labels exist
This portal spans mature GA data APIs and brand-new AI agents under active development. Lifecycle labels set the correct expectation for stability, support, and SLAs before you invest in an integration.The four phases
Alpha
First testable version, available for internal evaluation and select design-partner pilots.
Known issues may exist. API contracts will change. Not for production use.
Private preview beta
Stable version for friendly early-adopter customers. Minimal breaking changes; requires
explicit enablement by Cotality. Suitable for controlled production pilots.
Public preview
Feature-complete and open for public opt-in testing. Suitable for pre-production
integrations. Performance and scale validation in progress.
GA — General availability
Official, fully supported, and enterprise-ready. Versioned with a deprecation window.
Covered by standard SLAs. Safe for customer-facing production use.
What each phase guarantees
How status appears in the docs
Each product and solution page carries a status badge. When a page has no badge, treat the capability as GA unless the page notes otherwise.Current capability status
Versioning and deprecation
- GA APIs are versioned (e.g.,
/v1/). Breaking changes ship under a new version. - Deprecations include a migration guide and a minimum advance-notice window.
- MCP tool names and schemas follow the same versioning discipline once a server reaches GA.