Canonical Wago documentation
Embedding Wago without cgo
What Wago’s pure-Go and no-cgo claim means, and where native executable-memory behavior still matters.
What no-cgo means
The Wago engine is implemented in Go and does not wrap a C/C++ runtime. Native backends emit machine code directly, and the runtime maps executable memory using Go and operating-system facilities.
What it does not mean
- It does not mean architecture-independent execution: native runtime targets are currently Linux/amd64, Linux/arm64, and Darwin/arm64.
- It does not remove executable-memory policy, code-signing, or operating-system constraints.
- It does not imply every plugin is dependency-free; evaluate plugin manifests separately.
Canonical target matrix: Wago facts.