Skip to main content
Your preview runs in an isolated sandbox while you work. Publishing creates a saved build that viewers can open without running your editing session. This page provides background for security reviews. For the publishing steps, see Publish and update an app.

​
While you build

Generated browser code runs inside an isolated frame. Its network policy allows only Wisty’s Salesforce endpoints on the preview’s own origin. The preview’s server also runs in a separate virtual machine. Its outbound network is restricted to Wisty’s backend. Salesforce credentials remain on Wisty’s servers. A separate Wisty session token authenticates sandbox requests; it’s attached outside the virtual machine, where generated code can’t read it. Wisty’s platform files, including the helpers that route Salesforce requests, are protected from edits. Your project files are saved separately from the temporary preview machine.

​
After you publish

Viewers receive a frozen build of the version you published. Editing your project doesn’t change that app until you publish again. Published app code is served from run.wisty.site, a separate domain from the Wisty product. The app runs in an isolated frame with the same restrictions on external network access. Salesforce data is fetched when the viewer uses the app, rather than being included in the published files. Opening an app requires authorization for that viewer. Salesforce requests use the viewer’s own permissions and the access enabled for the app. Sharing an app never gives its viewers the builder’s Salesforce access.

​
Delivery and sessions

Published requests pass through Wisty’s delivery edge, which exposes only the routes needed to run the app. Salesforce responses aren’t cached. A short-lived runtime session authenticates requests without exposing Salesforce credentials to generated code. Record writes use a separate path through the trusted Wisty host and its approval controls. See How Wisty uses your data for the generation and runtime data paths, or the security page for the full architecture and processing details.