Oracle to Retire Application Dependency Management (ADM) as Public OCI Service, Shifting Focus for DevOps Teams

Oracle has announced the retirement of its Application Dependency Management (ADM) as a public-facing service within Oracle Cloud Infrastructure (OCI). As of today, October 10, 2026, new external customer onboarding for ADM will cease. Existing eligible customers will continue to receive service and support for a migration period of at least three months, with a final end-of-life date no earlier than December 31, 2026. After this period, external customer access will be terminated across all OCI realms and regions, and associated public interfaces, documentation, and support channels will be retired. This development is significant for organizations leveraging OCI, particularly those with mature DevOps practices that rely on ADM for insights into application dependencies and potential vulnerabilities. The retirement suggests a strategic pivot by Oracle. It could indicate a move to integrate ADM's core functionalities into other OCI services, such as broader application performance monitoring (APM) tools or security offerings, or a decision to de-emphasize standalone dependency management in favor of partner solutions. For practitioners, this means a necessary re-evaluation of their current toolchains and a proactive approach to identifying and implementing alternative dependency management strategies. The broader trend in cloud computing and DevOps emphasizes integrated platforms and automated security. Cloud providers are increasingly offering comprehensive suites that cover everything from infrastructure provisioning to application deployment, monitoring, and security. Oracle's decision with ADM could align with this trend, aiming to streamline its offerings and provide more holistic solutions. It also highlights the dynamic nature of cloud services, where features and services can evolve rapidly, requiring users to maintain adaptable architectures and operational processes. In practice, OCI users who currently depend on ADM should immediately begin assessing their usage and identifying suitable replacements. This might involve exploring other OCI services that offer similar capabilities, such as Oracle Cloud Observability and Management Platform, or considering third-party tools that integrate with OCI. Practitioners should prioritize solutions that offer robust dependency mapping, vulnerability scanning, and integration with their existing CI/CD pipelines. The migration period provides a window to thoroughly test and implement new solutions, ensuring continuity of operations and maintaining visibility into application health and security. Failure to plan for this transition could lead to gaps in application oversight and increased operational risk.