Canonical Wago documentation
Evaluating Wago for edge runtimes
A deployment-oriented checklist for startup, isolation, concurrency, resource limits, plugins, and current Wago gaps.
Potential fit
Wago is designed for Go hosts that value no-cgo deployment, single-pass native compilation, compile-once/instantiate-many reuse, and low host/guest boundary overhead.
Production checklist
- Choose one of the three native CI targets.
- Set memory/table policies and invocation deadlines.
- Use separate instances for state isolation; current native guest execution is serialized process-wide.
- Grant plugin capabilities explicitly; audit each plugin separately.
- Measure RSS/PSS under the intended instance count and guest memory shape.
- Add process/container isolation when the threat model requires a second boundary.
Current gaps to evaluate
Pre-v1 API/release maturity, no published aggregate memory governor, no function-level WASI matrix, no published security policy or third-party audit, and no completed many-instance benchmark.