In short: Oracle’s Fusion Setup and Configuration Registry (FSCR) is an open-source collection of AI skills, scripts, and workflows that helps agents design and build Oracle Fusion Cloud Applications configuration. Configuration management complements it by governing and documenting what goes live, so every change is approved, traceable, and compliant. Flexagon Configuration Management, built on ConfigSnapshot, baselines and compares every environment, then promotes only the approved configuration through approval gates, for implementation, every quarterly update, and the years of change after go-live. Our team is actively studying FSCR, and we will share more details and practical guidance as we learn more.
At Oracle AI World in October, Oracle introduced the Fusion Setup and Configuration Registry (FSCR), a public Git repository that makes Fusion Cloud setup readable and executable by AI agents. It is a meaningful step. Oracle is putting its setup expertise into a form that agents and implementation partners can use to plan and configure Fusion faster.
A simple way to think about it: FSCR helps you design and build the solution, and Flexagon governs which parts of that solution go live and how they are managed from then on. Whether you are planning a new Fusion implementation or running Fusion today, the announcement is good news. As agents start to configure Fusion, knowing exactly what is configured, and controlling what moves to production, becomes more valuable, not less.
What does FSCR do?
FSCR is built to speed up solutioning and implementation. Its skills encode setup options, dependencies, sequencing, and validation, so an agent can turn requirements into a runbook and help carry out initial setup with human review. Systems integrators are invited to extend it with their own methods and accelerators. Oracle’s getting-started guidance begins with a requirements document or configuration spreadsheet. Oracle says FSCR supports new implementations and the addition of features or modules to existing Fusion deployments, and that it makes no configuration changes until you approve.
Oracle is clear about what FSCR is today. Its README describes it as sample and reference material, a scaffold that teams build on, outside Fusion Cloud product support. That makes it a valuable starting point, especially for SI-led projects. The project folder, the runbook, and the review process around it are yours to build and own.
Do AI agents reduce the need for configuration governance?
AI agents do not reduce the need for configuration governance. They multiply it. Oracle makes the same point: its announcement describes expert reviewers approving agent-built configuration, and agents operating within the policies and controls each organization defines.
The first effect is speed of iteration. An agent can turn requirements into a first configuration, the team can review it, adjust the requirements, and have the agent try again, in hours rather than weeks. Trying two or three designs before committing to one becomes realistic. The side effect is that every pass changes the same environment. By the time the design settles, that environment holds the final solution mixed with the history of getting there: trial setups, superseded values, test records, and anything a later iteration replaced. That is what you want in a sandbox. It is not what you want in production, and it should not be carried forward just because it exists.
Speed also changes the risks around it:
- More change, faster. Approval gates before promotion matter more than ever. A prompt where the person running the agent confirms the work is useful, but it is not the same as an enforced gate that holds a change until someone else signs off.
- Less predictable output. Results can vary by model or prompt, so every run should be compared against an approved baseline.
- Harder to tell who did what. Comparisons against a baseline show exactly what changed, and when, so nothing an agent did goes unnoticed.
- Bigger blast radius. Role-based permissions limit what can be loaded, and where.
- Mistakes must be undone fast. Rollback by module, step, or row beats an all-or-nothing restore.
- Auditors still need evidence. Faster change does not relax compliance. Baselines, approval records tied to change requests (for example in ServiceNow), segregation of duties reporting, and a record of exactly what moved give auditors the proof they need.
How do FSCR and Flexagon Configuration Management work together?
You do not have to choose between FSCR and Flexagon. Flexagon Configuration Management, built on ConfigSnapshot, works with live configuration in your Fusion environments, so it can check and control setup no matter what created it: a consultant, a script, an AI agent, a change made directly in production, or Oracle’s own quarterly update. Here is how the two work together for a team using FSCR or another agent tool:
- Baseline first. Capture the environment before any agent run, so every later change is measured against a known starting point. For an existing environment, the same baselines and reports give the team and the agent an accurate picture of what is live today to design against.
- Iterate freely in non-production. Let the agent build, the team review, and the design change as often as needed. Treat this environment as a workspace, not the source of truth, and keep production loads restricted through role-based access.
- Compare when the design settles. Comparing the environment with the baseline shows every difference, so the team can separate what belongs in the solution from what is left over from the iterations. Anything an agent changed and later put back does not show as a difference. Anything left behind does.
- Check the build against the design. FSCR keeps design decisions and blueprints in its project workspace. Flexagon works from what is actually in the environment, so the team can see where the build differs from the approved design before anything is promoted.
- Isolate what is required. Build a migration plan from the approved setup records and leave the experiments out. The plan works out whether each record is an insert, update, or delete in the target.
- Promote through a pipeline. Move the selected configuration through test and on to production using pipelines with approval gates. The pipeline, not a copy of the whole environment, is the only route forward, so nothing travels that was not approved. The same approved set can then be delivered again to further business units, regions, or entities, with the same approvals and the same record of what moved.
- Keep rollback ready, then re-baseline. Restore the affected module, steps, or rows if a load does not behave as expected. After promotion, take a new baseline so the next round starts from the approved state.
Take a team that asks an agent to set up a group of related setup records, tries three variations over a week, and settles on the third. The sandbox still holds pieces of the first two. A comparison against the baseline lists everything that changed, the team confirms which records make up the third design, and only those go into the migration plan and through the pipeline. The earlier variations stay behind in the sandbox, and nobody has to remember to clean them up before go-live.
Faster iteration is only an advantage if what goes forward is a deliberate choice. Agents make it cheap to create configuration. The platform makes sure only the right configuration is promoted.
What does configuration management cover beyond FSCR?
FSCR focuses on designing and configuring the solution, whether for a new implementation or a new module. Flexagon Configuration Management, built on ConfigSnapshot, covers the whole lifecycle: implementation, rollouts, every quarterly update, and the years of change that follow go-live, with live comparisons across all your environments.
In most programs the two are used by different people at different points. SI consultants and project teams use FSCR to work out and build the solution. Release, change, and configuration managers use Flexagon to decide what is promoted, to approve it, and to keep the audit trail and the evidence compliance teams need. Neither replaces the other’s role.
Configuration is only part of a Fusion solution. The Flexagon platform also automates migration and deployment of the technical components around it, including Oracle Integration Cloud (OIC) integrations, OTBI and BI Publisher reports, EPM, APEX, Oracle Process Automation (OPA), and Redwood extensions. Every change, configuration or technical, runs through the same pipelines, approvals, and audit trail.
The Flexagon foundation is proven. Customers have relied on ConfigSnapshot across Oracle Cloud and E-Business Suite to:
- Document live configuration in readable, business-level reports, down to individual records.
- Compare environments, baselines, and plans with differences highlighted.
- Migrate setup with migration plans that work out whether to insert, update, or delete in each target.
- Analyze patch impact by comparing pre-patch baselines with post-patch settings each quarter.
- Catch unplanned change with baselines taken at every stage of a project.
- Control access with role-based permissions over who can extract, compare, or load, and where.
All of it is supported and ready to use, with no coding required.
Common questions
Does FSCR replace a configuration management platform? No. FSCR helps teams design and build configuration for a new implementation. Configuration management governs what is promoted, documents what is live, and tracks change across every environment for years after go-live. They do different jobs, usually for different people.
Can we use FSCR and Flexagon together? Yes. Flexagon works with live configuration whatever created it, so an FSCR-assisted build can be baselined, compared, and promoted through approval gates like any other change.
What about quarterly updates and production changes? FSCR is built to design and set up configuration. Flexagon works with live environments every day: it compares pre-update and post-update baselines each quarter, and it catches changes made directly in production.
Is configuration management only useful after go-live? No. It supports implementation too: planning setup, loading CRP and test environments, and confirming each build matches the approved design before it moves on.
Does Flexagon manage more than configuration? Yes. Beyond Fusion configuration, the Flexagon platform automates migration and deployment of technical components such as OIC integrations, OTBI and BI Publisher reports, EPM, APEX, OPA, and Redwood extensions, with the same governance and compliance controls for every change.
Already a ConfigSnapshot customer?
ConfigSnapshot is not going away. Its capabilities are moving onto the Flexagon platform as Flexagon Configuration Management, and everything comes with them, including your baselines. FSCR tells agents how Fusion should be configured. ConfigSnapshot shows how it is actually configured and how it got that way, which is exactly what teams need as agents start making changes.
What to do next
- Ask your SI whether they plan to use FSCR on your project, and how changes will be reviewed and recorded.
- Make sure every environment has a current baseline before any agent-driven work starts.
- Agree up front how iteration environments will be used, and how only the approved configuration will be selected and promoted from them.
- Review who and what holds credentials that can change production configuration.
- Talk to Flexagon about governing agent-assisted change, whether you are planning an implementation or running Fusion today. Request a Demo

