You can identify which experience you're using by checking where you access your integrations. The New Exalate experience operates through a unified web-based console that displays all your connections in workspaces with a centralized interface. If you log in through this address and see a unified dashboard showing multiple connections in one view, you're using the new experience.
Check where you access integrations
Classic Exalate uses separate consoles installed as add-ons within each connected platform. If you access integration settings directly inside Jira, Azure DevOps, ServiceNow, or other individual systems rather than through a central web portal, you're using Classic. Classic displays configuration options specific to that single platform without showing connections across your entire integration landscape.
Look for UI differences
The interface design also differs significantly between versions. New Exalate features workspaces, version management with draft and active states, side-by-side script views, and the Aida AI assistant panel. Classic shows a more traditional settings interface with separate tabs for Rules, Triggers, Statistics, and Info without the unified workspace concept.
If you’re unsure, ask your admin or support
If you're uncertain which version your organization uses, check with your Exalate administrator or contact support for clarification. They can confirm your current deployment model and discuss options for transitioning to the new experience if you're still on Classic. Organizations running both versions during migration will access Classic through platform-specific add-ons and the new experience.