Oracle Visual Builder is closing its doors to new customers

Oracle Visual Builder is closing its doors to new customers

If you work with Oracle Cloud, you may have seen the notice. Starting October 8, 2026, Oracle is stopping new purchases and new enablement of two Visual Builder offerings: the standalone Oracle Visual Builder (SKU B89646) from the OCI console, and the Visual Builder that comes enabled inside Oracle Integration Cloud.

Does this affect you?

If you already have an active Visual Builder instance in your tenancy, nothing changes. You can keep using it, renew it, and even provision additional instances, within your service limits. Oracle will keep supporting it and shipping security fixes. There is no end-of-life date and no forced migration or rewrite.

If you have no active instance, you won't be able to create or enable one after the cutoff.

What is not affected?

Three things continue as they are:

• Visual Builder auto-provisioned with Fusion Cloud Applications for Sales and Service, typically used for digital customer service portals
• Visual Builder Studio, which is a separate product
• Redwood App Extensions, which are built on Visual Builder Studio and run on Fusion

A common question: can Visual Builder Studio replace it?

Not quite. Visual Builder Studio is built for developers, with Git, CI/CD and an IDE. It is not a hosting platform, so you can build and store apps there, but you still need Visual Builder to run them.

My take

For existing users, this is a non-event for now. For anyone planning a new low-code or integration project on OCI, it is worth checking early whether Visual Builder is part of your design, because that door closes on October 8. If you are unsure where you stand, your Oracle account rep or a Support Request is the quickest way to get a clear answer.