Project
The primary BlinkHost application boundary containing frontend code and the backend modules, databases, assets, domains and deployments associated with that application.
BlinkHost glossary
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.
The primary BlinkHost application boundary containing frontend code and the backend modules, databases, assets, domains and deployments associated with that application.
Project-scoped server logic written in Rust, Go or Python and compiled to a governed WebAssembly artifact.
A time-bounded pre-deployment session that connects browser-based frontend development to eligible backend modules and project resources.
An explicit connection between application code and the intended managed project database.
A build output with a recorded identity that has passed the checks required before deployment.
The production release process that publishes identified, verified application artifacts through BlinkHost’s delivery path.
A validated project control governing supported runtime limits or behaviour according to the applicable plan.
A file uploaded to project storage, subject to file validation, security scanning and the workspace storage allowance.
Common questions
No. LiveStack Preview is a temporary pre-deployment environment. A deployment publishes verified artifacts through the production release path.
No. A backend module belongs to a BlinkHost project and remains visible alongside the frontend and other application resources.
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