BlinkHost
BlinkHost
Dashboard
How ToPreviewFor developerFor agencyFor operator

Preview a full-stack application with LiveStack

Connect a browser-local frontend to isolated backend modules and development resources before deployment.

Last updated 2026-08-11

What you'll achieve

  • Exercise frontend and backend logic together before deployment
  • Use isolated development resources without exposing credentials to the browser
  • Keep preview activity separate from production

What LiveStack Preview does

LiveStack connects the frontend development server in your browser to verified backend module artifacts running in BlinkHost's isolated preview runtime. It is available from the IDE to customer workspaces. BlinkHost supplies the active gateway automatically and can change that route without requiring a source-code change.

Preview and production are separate environments. A LiveStack session cannot join the production edge fleet, and an absent preview resource never falls back to its production counterpart.

Prepare the project

  1. Create or open a Rust, Go or Python backend module under _server_islands.
  2. Choose Build and wait for validation to produce a verified artifact. An unchanged source and toolchain identity can reuse an existing verified artifact.
  3. If the module needs data, create a development or preview database and enable its named preview binding.
  4. If it needs a credential, create a development- or preview-scoped secret. The value remains outside frontend source and browser JavaScript.
  5. Open the IDE's Project resources panel and start the LiveStack session.

The session can start with zero databases, zero secrets and zero assets. Add only the resources the module actually needs.

Call a backend module

Use the module route from frontend code as a same-origin path:

const response = await fetch('/_server_islands/orders', {
  headers: { 'accept': 'application/json' },
});
if (!response.ok) throw new Error('The preview request failed');
const orders = await response.json();

The IDE bridge sends a short-lived, origin-bound capability directly to the preview frame. It does not expose database provider credentials, secret values or BlinkHost control-plane credentials to the frontend.

Development resources

  • Databases: connect zero, one or several development/preview databases by unique binding name. Production bindings are not accepted.
  • Secrets: only explicitly scoped development/preview secrets are available to an authorised module; values are not displayed in the browser.
  • Blob operations: backend modules receive project-scoped brokered access rather than provider credentials.
  • Email: preview messages are captured in the IDE email sink and are never delivered to recipients.
  • Project assets: validated assets mount into the browser workspace and count against shared organization storage.

End or recover a session

Stop the session when testing is complete. If a new build fails, LiveStack preserves the last known-good verified artifact. A preview error does not alter production. Use logs and the preview troubleshooting guide to distinguish browser startup, module build, session, binding and invocation failures.

Help improve this page

Sign in to send page-specific feedback. For account-specific help, email support@blinkhost.me.

Preview a full-stack application with LiveStack | BlinkHost