How backend runtime isolation works
Understand capability-based functions, bounded execution and supported runtime surfaces.
Last updated 2026-09-02
What you'll achieve
- Understand module isolation
- Design within runtime limits
- Assess package portability
Capability-based execution
Backend modules run from verified artifacts with an explicit runtime and SDK contract. Code receives only declared host capabilities such as a named database, object-storage binding, secret reference or approved outbound destination. It does not inherit control-plane credentials.
Bounded work
Execution time, memory, concurrency, payload size and metered operations are limited by runtime policy and plan. When a limit is reached, BlinkHost returns a stable failure category instead of allowing unbounded resource consumption. Long-running work should use supported background or scheduled functions and idempotent retries.
Portability boundary
Rust and TinyGo target the supported WASI contract. JavaScript, TypeScript and Python use reviewed compatibility layers and do not imply support for every native package or long-running server framework. Run the compatibility check before relying on operating-system processes, native extensions, unrestricted filesystems or persistent sockets.
Help improve this page
Sign in to send page-specific feedback. For account-specific help, email support@blinkhost.me.