Design direction

PLUGINS

A capability-scoped extension model for gateway policies

Normal tenants will not be allowed to upload arbitrary native code into the gateway process.

Last reviewed

The operating problem

Extension systems can bypass request policy, secret boundaries, egress controls, resource limits, and upgrade safety when capabilities remain implicit.

The intended control surface

This capability is part of the reviewed product architecture, not a decorative console module.

  • WebAssembly/WASI sandbox
  • Declared read/write/network/secret capabilities
  • Publisher signatures, checksums, licenses, and SBOM
  • CPU, memory, timeout, and kill-switch controls

What exists today

No tenant plugin runtime or SDK is currently shipped.

Work with the implementation team

Reallexi is accepting architecture conversations with teams whose requirements can shape this production slice. An inquiry does not imply that an unshipped feature is available.

Frequently asked questions

Is this capability generally available?

No. The page describes a reviewed implementation direction. The current capability boundary is stated above and in the public changelog.

Can Reallexi evaluate our requirements?

Yes. Use the enterprise inquiry form without including credentials, private payloads, or regulated data.

NEXT STEP

Shape the requirements before implementation.

Talk to ReallexiRequest platform access