Oracle AI World took over the Venetian this year, with more than 16,000 attendees, and the message from the main stage was consistent: AI is no longer a preview, it is running in production.
Clay Magouyrk framed it directly in his keynote, “Now that AI works, what are we going to do with it?” The joint keynote with OpenAI’s Sam Altman pushed it further, bringing ChatGPT and Codex into the Oracle Fusion stack. The product announcements followed the same theme, from the Deep Trust AI architecture to 25 new agentic capabilities inside Fusion Cloud Applications, and the new Fusion Setup and Configuration Registry (FSCR), Oracle’s AI-agent-ready tooling for planning and validating Fusion setup.
Every one of those advances still has to be deployed, configured, governed, and audited inside a live Oracle environment. The more agentic these applications become, the more change they generate. And change is what breaks environments when it is handled by hand.
FSCR makes the point for us. When Oracle itself ships tooling to help AI agents configure Fusion, it confirms what our customers already know: configuration management is now central to running Oracle applications. Knowing how setup should look is the starting point. The harder questions come next. What actually changed, who approved it, how it reaches production safely, and how you roll it back when something goes wrong.
That was the conversation we had over and over at booth 6042. Our theme said it plainly: DevOps and Configuration Management for Oracle applications. Across three days we had close to 400 conversations at the booth, and a large share were exactly the kind we came for: senior teams wrestling with a live Oracle change problem. One word came up more than any other: manual. Teams running Fusion, Oracle Integration Cloud, and E-Business Suite told us their setup changes, comparisons, and migrations are still done by hand. That makes the work slow and the results hard to prove at audit time.
A few specifics stuck with us. Comparison and drift between environments came up as a top pain again and again. Several teams were weighing generic CI/CD, from GitHub Actions to Azure DevOps, against a tool built for Oracle, and more than one admitted they did not know where to start. Audit and security pressure showed up often, usually after a rushed implementation. We also reconnected with former ConfigSnapshot users who are feeling that pain more now, not less.
That gap is the whole reason we build what we build. Flexagon Configuration Management, built on ConfigSnapshot, covers the full lifecycle, from documenting and comparing setup to migrating it through quarterly updates. Approvals and pipelines tie into the tools you already use. Patch impact analysis flags what a quarterly update will break, and rollback goes down to a single module, step, or row. Customers see 5x fewer errors and 60 percent faster deployments, with audit readiness built in.
Thank you to everyone who stopped by, scanned in, and compared notes with our team. If we talked in Las Vegas, or if you wish we had, we would be glad to continue the conversation.