What is OmniOut and what does a team need to consider before committing to it?

OmniOut lets LWC-based OmniScripts and FlexCards run on a web server outside Salesforce while still using the org for data, which is attractive for unauthenticated or heavily branded public experiences.

1. The components must be LWC-based and activated before they can be packaged — the older runtime is not supported.
2. The hosting environment becomes your responsibility: a build process, a web server, deployment, monitoring and certificate management now sit with your team rather than with Salesforce.
3. Cross-origin access and authentication have to be configured so the external domain can reach the org, and the security model for unauthenticated visitors needs designing carefully — whatever the page can call, the internet can call.
4. Release coupling: a change to the OmniScript is no longer live the moment you activate it; it has to be rebuilt and redeployed to the external host, so the two environments can drift.
5. Ask whether Experience Cloud solves it instead. If the requirement is a branded public page and not a hard constraint about hosting outside Salesforce, an Experience Cloud site avoids the entire operational burden. OmniOut earns its cost when the page must live inside an existing corporate web estate.