BlinkHost
BlinkHost

WebAssembly backend modules

Backend logic in Rust, Go or Python—inside the project.

A BlinkHost backend module is project-scoped server logic compiled to a governed WebAssembly artifact. Developers can author modules in Rust, Go or Python, build them through the platform, and deploy only after the artifact is verified for the release.

Keep API logic beside its frontend consumerUse a consistent runtime contract across three languagesAvoid publishing an unverified module artifact
01

Three supported languages

Choose Rust, Go or Python according to the module and team, using the BlinkHost runtime contract.

02

Build evidence

Module builds retain status and artifact identity so deployment does not guess which output is ready.

03

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 project-scoped server logic written in Rust, Go or Python and compiled to a governed WebAssembly artifact.

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

Backend module documentationExplore databases