BlinkHost
BlinkHost
Dashboard
How ToPreviewFor developerFor agency

Use the browser IDE and preview

Edit the complete project and connect browser-local frontend work to isolated backend preview modules.

Last updated 2026-08-11

What you'll achieve

  • Edit frontend and backend module source in one workspace
  • Understand which work runs on the device and which runs on BlinkHost
  • Test full-stack behavior without changing production

Workspace layout

The Explorer shows frontend source, project configuration and project assets in the normal project tree. Backend module source lives under _server_islands; each module has its own managed source root and can contain nested files and folders. A frontend-only project does not need that folder.

Changes are saved to the BlinkHost project workspace. Wait for the saved state before closing or reloading the page. A preview is not a production release: production changes only after a verified artifact is published and deployed.

Two connected preview runtimes

The frontend development server runs in a WebContainer inside your browser. It uses your device CPU, memory, browser storage and network. A slower device, low free memory, battery-saving mode, many open tabs, browser extensions or a cold dependency download can make startup take longer.

Backend modules do not run in the browser or on the control plane. LiveStack Preview runs verified Rust, Go and Python Wasm artifacts in an isolated BlinkHost preview runtime. The IDE securely connects same-origin frontend requests under /_server_islands/ to the active LiveStack session. BlinkHost chooses the active preview gateway; do not hard-code a gateway hostname.

Preview a full-stack project

  1. Open the IDE and wait for the frontend status to become Preview Ready.
  2. Build each backend module you want to exercise and select its verified artifact.
  3. Open Project resources and start the LiveStack session.
  4. Connect only development or preview database bindings and preview-scoped secrets.
  5. Call a module from frontend code with a same-origin path such as fetch('/_server_islands/orders').
  6. Inspect captured preview email and the visible resource state before publishing.

No database is required for a module that does not use one. LiveStack never substitutes a production database or production secret when a preview resource is absent.

Browser requirements

Use a current desktop Chrome or Edge browser with SharedArrayBuffer and cross-origin isolation support. If startup stalls or a connected backend request fails, use the WebContainer and LiveStack troubleshooting guide. Preserve unsaved work and the first useful diagnostic before restarting anything.

Help improve this page

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

Use the browser IDE and preview | BlinkHost