WASM modules
Agent-runner execution module inventory.
Agent-runner execution module inventory.
This screen belongs to the Router deployment operator, not an ordinary hosted customer. Hosted customers have a separate account page with their own keys and limits; policy and service settings are not exposed there. Contact the operator to change protection. In the operator console, open the route listed above; a report tenant filter does not automatically scope a global setting.
Examples use educational data. Use your own authorized tenant in real integrations. Each screenshot shows the actual frontend, with the source and educational/demo mode stated below it.
Step-by-step actions
- Open Preview /wasm when available.
- Refresh and check the required module version.
- Deliver manifest.json, plugin.wasm and signature through the supported agent-runner process.
- Verify module attachment using a separate test run.
Every control and its meaning
| Control / parameter | Values, units and effect |
|---|---|
| manifest.json / plugin.wasm | Module artifact and metadata for a compatible agent-runner. The list shows name, version and upload time. |
| Подпись / Signature | Signed/unsigned describes the artifact and does not mean it is enabled for traffic security. |
| Загрузить плагин / Upload plugin | The current Preview button does not open an implemented uploader; it cannot configure a new module. |
Verify the result
A catalog entry does not prove DLP or post-processing execution; obtain a runtime result.
Errors, disabling and reverting changes
An inactive Upload plugin button is a Preview limitation. Repeated clicks do not register a module; use the operator workflow.
Detailed security settings · Traffic analysis · FAQ · All application sections