Clear language maturity
Choose generally available Rust or Go, or evaluate bounded Python, JavaScript and TypeScript Functions in beta.
WebAssembly backend modules
Backend logic in Rust or Go, with three more function runtimes in beta.
A BlinkHost backend module is project-scoped server logic compiled to a governed WebAssembly artifact. Rust and Go modules are generally available, while bounded Python, JavaScript and TypeScript Functions are in beta. Deployment requires a verified artifact for the release.
Keep API logic beside its frontend consumerUse one explicit request-handler contract across available languagesAvoid publishing an unverified module artifact
Reliable work beyond a request
Use beta event, scheduled and background triggers with bounded retries, cancellation and run history.
Build evidence
Module builds retain status and artifact identity so deployment does not guess which output is ready.
Edge execution
Verified WebAssembly modules run through BlinkHost’s governed edge runtime.
Common questions
Clear answers about webassembly backend modules.
What is a BlinkHost backend module?
A backend module is a project-scoped request handler compiled to a governed WebAssembly artifact. Rust and Go are generally available; Python, JavaScript and TypeScript Functions are in beta.
Can frontend code call a backend module?
Yes. Frontend code can call the project’s deployed backend module endpoints and can exercise eligible module flows during LiveStack Preview.
What happens before a backend module is deployed?
BlinkHost builds the source, records the artifact identity and requires artifact verification before the module can participate in a production deployment.
Continue exploring