BlinkHost
BlinkHost

BlinkHost glossary

Clear definitions for the BlinkHost delivery workflow.

The BlinkHost glossary defines the product terms developers and agencies encounter while building and operating an application. Each definition describes current platform behaviour and links back to the relevant product or documentation path.

Understand BlinkHost terminology quicklyDistinguish preview, build and production deploymentUse shared language across development and agency teams
01

Project

The primary BlinkHost application boundary containing frontend code and the backend modules, databases, assets, domains and deployments associated with that application.

02

Backend module

Project-scoped server logic written in Rust, Go or Python and compiled to a governed WebAssembly artifact.

03

LiveStack Preview

A time-bounded pre-deployment session that connects browser-based frontend development to eligible backend modules and project resources.

04

Database binding

An explicit connection between application code and the intended managed project database.

05

Verified artifact

A build output with a recorded identity that has passed the checks required before deployment.

06

Deployment

The production release process that publishes identified, verified application artifacts through BlinkHost’s delivery path.

07

Runtime policy

A validated project control governing supported runtime limits or behaviour according to the applicable plan.

08

Project asset

A file uploaded to project storage, subject to file validation, security scanning and the workspace storage allowance.

Common questions

Clear answers about blinkhost glossary.

Is a preview the same as a deployment?

No. LiveStack Preview is a temporary pre-deployment environment. A deployment publishes verified artifacts through the production release path.

Is a backend module a separate project?

No. A backend module belongs to a BlinkHost project and remains visible alongside the frontend and other application resources.

What does browser-to-edge mean?

Browser-to-edge describes a workflow that begins in BlinkHost’s browser development experience and continues through preview, verified deployment and the governed edge runtime.

Continue exploring

Developer documentationExplore backend modules