Wasmtime 46 sandboxing for WIT components
WebAssembly Components execute with a deny-all WASI context. Host functions are linked only when a policy explicitly permits them.
Read sandbox testKraton / source-aligned status
Show the boundary between built and believed.
This page tracks the current Kraton Engine codebase rather than projecting a finished platform. Each implemented item points to code that can be inspected.
Implemented
Boundaries that exist in the codebase.
HTTP and gRPC pipeline streaming
The pipeline contract has shared admission, metering, and backpressure semantics across HTTP and bidirectional gRPC.
Read streaming testVerified AOT cache warmup before readiness
Cached components are checked and recompiled for compatibility before the host reports that it is ready to receive work.
Read warmup testAttested metering: encrypted RocksDB + Merkle receipts
Fuel, CPU-time, and I/O facts are written to an encrypted local ledger and sealed into host-signed Merkle checkpoints.
Read integrity testSSRF firewall and DNS-rebinding protection
Outbound wasi:http resolves an allowlisted host, rejects private ranges, and pins the TCP connection to the verified address.
Inspect policy sourceExplicitly not complete
Open work keeps its own color.
External anchoring
The local tamper-evident record is implemented. Sending checkpoint roots to an independent party remains a separate trust boundary and is not claimed as complete.
Open registry & distribution
Public discovery and distribution remain deliberately small while artifact verification and composition workflows mature.
Kraton Beacon
The zero-knowledge edge-presence model is research/RFC work, not a present production offering.