Key details

  1. Effective October 8, 2026.
  2. New OCI standalone VBCS and OIC VBCS enablement unavailable without an existing instance.
  3. Existing VBCS customers retain support, renewals and additional provisioning subject to limits.
  4. Visual Builder Studio and Fusion Cloud embedded Visual Builder unaffected.
  5. No end-of-life date announced for existing instances.

What builders should take away

  1. Check current tenancy eligibility before planning a new Oracle Visual Builder app.
  2. Do not treat Visual Builder Studio as equivalent hosted runtime.
  3. Existing customers should document dependencies and long-term support expectations, but need not invent a forced migration deadline.

What changed

Oracle announced that from October 8, 2026, customers without an existing Oracle Visual Builder instance cannot newly purchase or enable the standalone OCI Visual Builder SKU B89646 or Visual Builder embedded in Oracle Integration Cloud (OIC VBCS). Tenants already running an affected instance can keep using, renewing and adding instances subject to limits, and Oracle says maintenance, support and security fixes continue. Visual Builder Studio and Visual Builder embedded with Fusion Cloud Sales and Service are explicitly unaffected. Oracle has not announced an end-of-life date for existing VBCS instances.

Why it matters

Teams considering Oracle's low-code hosting platform can no longer treat the standalone or OIC VBCS services as available greenfield options. Existing customers do not face an immediate forced migration, but future project architecture and vendor dependency planning need to distinguish hosted VBCS from Visual Builder Studio, which provides developer tooling but is not equivalent app hosting.

Two service routes stop accepting new tenants

The restriction covers standalone Visual Builder from OCI and VBCS enablement from Oracle Integration Cloud for customers without an existing Visual Builder instance. Oracle's detailed notice enumerates the affected Integration Cloud SKUs.

Existing instances keep running

Oracle explicitly says existing affected tenants may continue using, renewing and provisioning more instances under applicable limits. There is no newly announced forced rewrite, migration deadline or shutdown date.

Studio is not a drop-in hosting replacement

Visual Builder Studio remains available as development and CI/CD tooling, but Oracle states it is not an application hosting platform equivalent to VBCS. Fusion Cloud application extensions are outside the change.

Decide based on tenancy and deployment model

Before committing to a new project, verify whether the organisation already has an active VBCS instance and whether the intended application requires hosted VBCS rather than Studio/Fusion extensions. Request written clarification from Oracle for ambiguous tenancy eligibility.

What to watch next

  • Whether Oracle announces an eventual existing-customer EOL or migration path.
  • Whether service availability restrictions extend to more Visual Builder offerings.

Still unclear

  • Oracle has not stated the strategic reason for the new-customer restriction.
  • Additional provisioning remains subject to service limits and tenancy eligibility.

Sources

Direct reading behind this dossier.

2 sources
Oracle Visual Builder update
Oracle primary announcement

Product manager clarifies affected and exempt offerings and existing-customer status.

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment